Verify Rapid Diffs accessibility compliance
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
We must ensure Rapid Diffs follow accessibility guidelines mentioned in the blueprint document. The accessibility testing should be automated as much as possible.
Automated tests
We can utilise axe-core gem based tests in feature tests. See documentation on how to add automated accessibility tests. The same gem could be used for unit tests for haml component.
It's important to note that these tests only check the component/page at a given moment in a current state. This means any triggered or rendered later elements need to have a designated test block. In the context of Rapid Diffs, this could be:
- additional check when another portion of diff is being streamed
- additional check when another portion of diff has been streamed
- additional checks for parallel view
- additional checks for whitespace changes visibility
Manual tests
Manual testing should make sure we adhere to the guidelines highlighted in the blueprint. Make sure it is possible to perform all possible tasks with the following modalities:
- keyboard
- screenreader (at least NVDA + Firefox)