Pika Accessibility: Marmot Knowledge Base content

Principle 2: Operable User interface components and navigation must be operable.
Guideline	Description & 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	PA-5 - Getting issue details... STATUS
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	PA-6 - Getting issue details... STATUS
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	PA-7 - Getting issue details... STATUS
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	PA-8 - Getting issue details... STATUS
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	PA-9 - Getting issue details... STATUS

Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.

Guideline

Description & Success Criteria Link

Anticipated Timeline

Status

4.1: Compatible

Maximize compatibility with current and future user agents, including assistive technologies.

Development: January-February 2024

Deployment: March 2024

PA-10 - Getting issue details... STATUS

Principle 3: Understandable Information and the operation of the user interface must be understandable.
Guideline	Description & Success Criteria Link	Anticipated Timeline	Status
3.1: Readable	Make text content readable and understandable. https://www.w3.org/TR/WCAG21/#readable	Development: March-April 2024 Deployment: June 2024	PA-11 - Getting issue details... STATUS
3.2: Predictable	Make Web pages appear and operate in predictable ways. https://www.w3.org/TR/WCAG21/#predictable	Development: March-April 2024 Deployment: June 2024	PA-12 - Getting issue details... STATUS
3.3: Input Assistance	Help users avoid and correct mistakes. https://www.w3.org/TR/WCAG21/#input-assistance	Development: March-April 2024 Deployment: June 2024	PA-13 - Getting issue details... STATUS

Principle 1: Perceivable Information and user interface components must be presentable to users in ways they can perceive.
Guideline	Description & Success Criteria Link	Anticipated Timeline	Status
1.1: Text Alternatives	Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. https://www.w3.org/TR/WCAG21/#text-alternatives	Development: May-June 2024 Deployment: June 2024	PA-14 - Getting issue details... STATUS
1.2: Time-based Media	Provide alternatives for time-based media. https://www.w3.org/TR/WCAG21/#time-based-media	Development: May-June 2024 Deployment: June 2024	PA-15 - Getting issue details... STATUS
1.3: Adaptable	Create content that can be presented in different ways (for example simpler layout) without losing information or structure. https://www.w3.org/TR/WCAG21/#adaptable	Development: May-June 2024 Deployment: June 2024	PA-16 - Getting issue details... STATUS
1.4: Distinguishable	Make it easier for users to see and hear content including separating foreground from background. https://www.w3.org/TR/WCAG21/#distinguishable	Development: May-June 2024 Deployment: June 2024	PA-17 - Getting issue details... STATUS