Why do we need this?
https://www.notion.so/epicmax/Accessibility-Improvements-v-1-7-Q2-7276524a28ae431db028a10d5d686dbd?pvs=4
Workflow
- Convert component from the list below list to a separate issue.
- Compare component with a11y patterns or (if there are no pattern for it) with other frameworks.
- Implement WAI-ARIA and keyboard navigation (if needed).
- Test functionality on screen readers.
- Create accessibility docs section in component's docs page.
List of covered components (WAI ARIA + keyboard navigation + a11y section in docs page):
Refs
https://www.w3.org/WAI/ARIA/apg/patterns/
https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/
https://m3.material.io/
https://www.magentaa11y.com/web/
https://a11y-guidelines.orange.com/en/articles/?tag=web
https://la-va11ydette.orange.com/?list=wcag-web&lang=en
Why do we need this?
https://www.notion.so/epicmax/Accessibility-Improvements-v-1-7-Q2-7276524a28ae431db028a10d5d686dbd?pvs=4
Workflow
List of covered components (WAI ARIA + keyboard navigation + a11y section in docs page):
Refs
https://www.w3.org/WAI/ARIA/apg/patterns/
https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/
https://m3.material.io/
https://www.magentaa11y.com/web/
https://a11y-guidelines.orange.com/en/articles/?tag=web
https://la-va11ydette.orange.com/?list=wcag-web&lang=en