mi6
Add information to the website explaining how we make the ICDS components accessible
What component is this related to?
Accessibility guidance
Why do we need it?
This ticket was inspired by a customer asking me if I could give them the assurance that the ICDS components meet WCAG 2.2 Level AA. I explained the processes we go through to make sure our components are designed and developed accessibly.
It would be good to create a page on the website in case other customers would like to know more about this.
We provide lots of guidance about how people can make their own apps accessible, but (as far as I can tell) only a small amount about our own approach to accessibility with the ICDS components (e.g. a few sentences, plus component-specific info with the "Accessibility" tabs). I think we need an overview of our overall accessibility approach so customers can be confident that ICDS components are accessible.
Some ideas of what we could include:
- Design:
- Colour contrast
- Keyboard behaviour
- Research we carry out e.g. comparing other libraries, speaking to users / customers
- Development:
- PR checklist (e.g. short summary of the steps)
- Testing with screen reader users
- Any accessibility issues we find are captured on our backlog with a "high" priority
- Mention the "Accessibility" tab for each component
- Explain people will still need extra testing (especially if a component has been highly customised, for example - or testing page layout is logical etc.)
(Just some suggestions!)
