Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

...

Pika Accessibility: Overview

Colorado law (link) requires “exact language” by July 1, 2024. For libraries, this requirement has wide-ranging implications, including for Pika.

In order to be compliant with the law, all public aspects of Pika must address the standards outlined in version 2.1 of the Web Content Accessibility Guidelines (WCAG 2.1). These web accessibility guidelines are organized into four principles: perceivable, operable, understandable, and robust. Each of these four principles is further defined by guidelines. Each guideline is accompanied by success criteria that enable conformance testing. There are three levels of success criteria: A (lowest), AA, and AAA (highest). In order to be compliant with Colorado law, all public aspects of Pika must rate at least AA.

The public aspects of Pika consist of four types of pages: account, search results, record views (grouped and bibs), and advanced search.

The development required to bring all guidelines under Principles 2 (operable) and 4 (robust) into AA compliance is globally applied to all Pika instances. Work will be performed on these principles first. The development to bring all guidelines under Principles 1 (perceivable) and 3 (understandable) requires both global and individual configuration. As Marmot staff begin working on principles 1 and 3, we will schedule meetings with libraries to discuss individual library configuration options.

Accessibility Principles: Details & Status

Principle 2: Operable

User interface components and navigation must be operable.

Guideline

Description & Success Criteria Link

Anticipated Timeline

Status

2.1: Keyboard Accessible

Make all functionality available from a keyboard.

https://www.w3.org/TR/WCAG21/#keyboard-accessible

Development: October-December 2023

Deployment: March 2024

Jira Legacy
serverSystem JIRA
serverIdf1278e8a-ea1d-3b8b-8326-a29a4cedece9
keyPA-5

2.2: Enough Time

Provide users enough time to read and use content.

https://www.w3.org/TR/WCAG21/#enough-time

Development: October-December 2023

Deployment: March 2024

Jira Legacy
serverSystem JIRA
serverIdf1278e8a-ea1d-3b8b-8326-a29a4cedece9
keyPA-6

2.3: Seizures and Physical Reactions

Do not design content in a way that is known to cause seizures or physical reactions

https://www.w3.org/TR/WCAG21/#seizures-and-physical-reactions

Development: October-December 2023

Deployment: March 2024

Jira Legacy
serverSystem JIRA
serverIdf1278e8a-ea1d-3b8b-8326-a29a4cedece9
keyPA-7

2.4: Navigable

Provide ways to help users navigate, find content, and determine where they are.

https://www.w3.org/TR/WCAG21/#navigable

Development: October-December 2023

Deployment: March 2024

Jira Legacy
serverSystem JIRA
serverIdf1278e8a-ea1d-3b8b-8326-a29a4cedece9
keyPA-8

2.5: Input Modalities

Make it easier for users to operate functionality through various inputs beyond keyboard.

https://www.w3.org/TR/WCAG21/#input-modalities

Development: October-December 2023

Deployment: March 2024

Jira Legacy
serverSystem JIRA
serverIdf1278e8a-ea1d-3b8b-8326-a29a4cedece9
keyPA-9

...