...
https://www.w3.org/TR/WCAG21/#abstract
Principle 2: OperableUser interface components and navigation must be operable. | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Guideline | Description & Link | Anticipated Timeline | Status | ||||||||
2.1: Keyboard Accessible | Make all functionality available from a keyboard. | Development: October-December 2023 Deployment: March 2024 |
| ||||||||
2.2: Enough Time | Provide users enough time to read and use content. marmot-support.atlassian.net/browse/PA-5 | ||||||||||
Development: October-December 2023 Deployment: March 2024 |
| ||||||||||
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 |
| ||||||||
2.4: Navigable | Provide ways to help users navigate, find content, and determine where they are. | Development: October-December 2023 Deployment: March 2024 |
| ||||||||
2.5: Input Modalities | Make it easier for users to operate functionality through various inputs beyond keyboard. | Development: October-December 2023 Deployment: March 2024 |
|
Principle 4: RobustContent 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 |
| ||||||||
Principle 3: UnderstandableInformation 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. | Development: March-April 2024 Deployment: June 2024 |
| ||||||||
3.2: Predictable | Make Web pages appear and operate in predictable ways. | Development: March-April 2024 Deployment: June 2024 |
| ||||||||
3.3: Input Assistance | Help users avoid and correct mistakes. | Development: March-April 2024 Deployment: June 2024 |
| ||||||||
Principle 1: PerceivableInformation 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. | Development: May-June 2024 Deployment: June 2024 |
| ||||||||
1.2: Time-based Media | Provide alternatives for time-based media. | Development: May-June 2024 Deployment: June 2024 |
| ||||||||
1.3: Adaptable | Create content that can be presented in different ways (for example simpler layout) without losing information or structure. | Development: May-June 2024 Deployment: June 2024 |
| ||||||||
1.4: Distinguishable | Make it easier for users to see and hear content including separating foreground from background. | Development: May-June 2024 Deployment: June 2024 |
| ||||||||