We want to find technical issues concerning accessibility in "our" code bases:
- Advanced-Search: T339202: Evaluate & improve accessibility of Advanced Search
- T179589: Display image filename extension rather than MIME types in Advanced Search criteria pills
- T193389: Tab-key should select first entry in autosuggest dropdown - seems fixed already
- T197613: TagItemWidget gets destroyed when enter is pressed on the link inside of it - would need an OOUI solution, requires design
- T267842: Search order can't be removed, but shows a remove button - requires design
- Reference Previews Cite: T339230: Evaluate & improve accessibility of Reference Previews
- T274108: Reference links in wikitext are intransparent to screen readers - needs design to define use cases and useful amount of text
- T274110: Jumping back up from a reference lets NVDA read the whole paragraph again - would require more testing with different screen readers
- Revision-Slider: T339254: Improve accessibility of Revision Slider
- Two-Column-Edit-Conflict-Merge: T244206: Review accessibility requirements in TwoColConflict
- no design:
- T244879: Linked text should always capture sufficient context - done
- T244881: Guided tour popups should be read by screen reader
- T251747: Increase min space for column lables in talk page use case - carefully change
- T258166: Short unchanged paragraphs should not have a collapse button - carefully change
- T254579: TwoColConflict & MinervaNeue: Misplaced info icon - good first task
- with design:
- design, but why?
- T245113: Guided tour indicators should be focusable using a screen reader or simple browser tabbing - worth an investigation
- T245115: Conflict popups are not read by a screen reader - worth an investigation
- should maybe include design?
- no design:
- Maps (Kartographer) (including nearby feature): T308320: Improve accessibility for Kartographer
- Move-Files-To-Commons
- Quite a lot of existing tickets ask for better error messages.
- …?
- TemplateData
- Keyboard support is incomplete. E.g. elements can't be reached with tab, enter doesn't submit a field, esc doesn't do back. Many tickets exist.
- RTL support is incomplete. Some tickets exist.
- T339806: Layout issue with edit link in table caption in TemplateData
- …?
To improve accessibility we want to:
- check if all relevant elements are visible (buttons, links, etc.)
- test keyboard usage (tab navigation, arrow keys, +/-, etc.)
- test screen reader
- check with a11y tools for issues
We can test for accessibility in:
- full screen & embedded
- mobile & desktop
- different browser
- different skins
We are collecting our findings in a doc first and then create tickets when we talked them through.