Accessibility

[euanmillar]

We should aim to ensure that OpenCRVS conforms to WCGA 2 Level A Compliance: https://www.w3.org/WAI/WCAG2A-Conformance

Roadmap to WCAG A-level accessibility

We'll go through the application views one view at a time. First, we assess the individual components used in the view, second, we test the whole view.

Prioritization:

1. views that are refactored to use new components, like <Button>, <Workqueue>, <Frame>
2. prioritize views that users most frequently use

• Current accessibility of OpenCRVS views

Component testing

• Current accessibility of OpenUI-Kit components
• todo: Guide to component A11y testing

View testing

• todo: Guide to view A11y testing

Daily work

• Briefing developers?
  • 13 days of accessibility (13 * 10 minutes): http://a11ycalendar.kaseybon.com/
  • Require accessibility review on pull requests
• Install A11y ESLint plugins and fix the issues they raise (~ 3 days, in component library there were around 10 files with errors)
  • https://www.npmjs.com/package/eslint-plugin-styled-components-a11y
  • https://www.npmjs.com/package/eslint-plugin-jsx-a11y
• QA testing accessibility on new features