We want to find technical issues concerning accessibility in [[ https://phabricator.wikimedia.org/project/profile/2323/ | "our" code bases ]]:
* #advanced-search: {T339202}
* {T179589}
* {T193389} - seems fixed already
* {T197613} - would need an OOUI solution, requires design
* {T267842} - requires design
* #reference_previews #cite: {T339230}
* {T274108} - needs design to define use cases and useful amount of text
* {T274110} - would require more testing with different screen readers
* #revision-slider: {T339254}
* {T165489}
* {T167768}
* {T336729}
* #TwoColConflict: {T244206}
* no design:
* {T244879} - done
* {T244881}
* {T251747} - carefully change
* {T258166} - carefully change
* {T254579} - good first task
* with design:
* {T244875}
* {T244878}
* {T244880}
* {T244883}
* design, but why?
* {T245113} - worth an investigation
* {T245115} - worth an investigation
* should maybe include design?
* {T245409}
* #kartographer (including nearby feature): {T308320}
* {T308240}
* {T321435}
* {T328137}
* {T328139}
* {T328140}
* {T328142}
* #FileImporter
* 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.
* …?
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 [[ https://docs.google.com/document/d/1coxL4n-fxwVOzsxrrF1HNHAll29wwC7F3Yp_zy0g460/edit#heading=h.kpfk6summrw9 | doc ]] first and then create tickets when we talked them through.