General Task
We should define accessibility criteria that are the most important for us in the feature development of the Tech Wishes project. Our general approach throughout the Wikimedia projects is to follow WCAG 2.1 Level AA. See this helpful list of the WCAG. You can find a spreadsheet collecting our thoughts here
Original Task
Investigation to find out to what degree the new UI meets accessibility criteria - specifically, on visual and physical impairments:
- Support for Screenreader
- Use a screen reader to step through the interface and it's worklow
- Support for keyboard navigation
- Try to solve an edit conflict with the keyboard only
- Support for impaired color vision
- Check out some tools to test color vision
https://de.wikipedia.org/wiki/Wikipedia:Technische_W%C3%BCnsche/%C3%9Cber_das_Projekt/Software_f%C3%BCr_diverse_Nutzergruppen (German - last two items in table)
https://www.mediawiki.org/wiki/Accessibility_guide_for_developers (English)
Outcomes
Things we can do:
- T244875: High-contrast text for conflict UI Disabled column textbox should have higher contrast text. "Cancel" button should have higher contrast.
- T244878: Enclose column selection radio buttons in a fieldset
- T244879: Linked text should always capture sufficient context
- T244880: Conflict textboxes should have accessibility labels and associations
- T245115: Conflict popups are not read by a screen reader
- T244881: Guided tour popups should be read by screen reader
- T245113: Guided tour indicators should be focusable using a screen reader or simple browser tabbing
- T244883: Investigate accessible workflow for two column conflict text input
- T245112: Make edit conflict view tab indexes linear
- T245409: Diffs should include semantic information for screen readers