| bwang | |
| Nov 22 2022, 7:06 PM |
| F36787981: 11-18-2022 Modern Vector Article Evaluation.docx | |
| Feb 7 2023, 5:37 PM |
| F36787980: Wikimedia Questions with VoiceOver Information.docx | |
| Feb 7 2023, 5:37 PM |
| F36787979: 11-18-2022 Modern Vector Article Evaluation.xlsx | |
| Feb 7 2023, 5:37 PM |
| F35814047: 11-18-2022 Modern Vector Article Evaluation.xlsx | |
| Nov 22 2022, 7:06 PM |
| F35814046: 11-18-2022 Modern Vector Article Evaluation.docx | |
| Nov 22 2022, 7:06 PM |
| F35814045: Wikimedia Questions.docx | |
| Nov 22 2022, 7:06 PM |
Now that American Foundation for the Blind (AFB) has finished their testing, we want to track their findings, either in the form of new tickets or updating existing tickets.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | bwang | T323634 Track AFB accessibility testing results in phab | |||
| Open | None | T20465 Tabs in Monobook and Vector should indicate selected state for assistive technology | |||
| Resolved | jhsoby | T325009 Improper focus when closing Language menu | |||
| Open | None | T325010 Rethink navigation landmark names in Vector | |||
| Open | None | T325008 Chinese, Korean, and Russian menu items in Language menu not spoken by NVDA | |||
| Open | None | T325013 Avoid using table semantics for Infobox | |||
| Open | None | T325015 Suggested task: Describe images with alt text | |||
| Resolved | None | T325016 MultimediaViewer buttons lacking accessible labels | |||
| Open | Volker_E | T325022 TypeaheadSearch screenreader output too verbose | |||
| Resolved | None | T325024 Ensure only one search button is present at a particular time in Vector | |||
| Open | bwang | T325377 Difficult to navigate Personal Tools menu with JAWS |
List of issues
| # | Summary | Notes |
| 1 | Some items in Language menu not spoken by NVDA | T325008 |
| 2 | Improper focus when closing Language menu | T325009 |
| 3 | Difficult to navigate Personal Tools menu with JAWS | T325377 |
| 4 | Improper Landmark name | Fixed T318178 |
| 5 | Improper Landmark name | T325010 |
| 6 | No indication of active tab | T20465 |
| 7 | Improper use of a table for content layout | T325013 |
| 8 | Improper use of a table for content layout | |
| 9 | Poorly tagged images throughout | |
| 10 | Unlabeled buttons | T325016 |
| 11 | Videos have no audio | |
| 12 | Bad titles in Media Player | |
| 13 | Icon should be skipped by screen readers | |
| 14 | Mislabeled button | Fixed T318178 |
| 15 | Focus improperly taken to top of page | T325020 |
| 16 | Focus order of the hidden TOC is not logical | Fixed T318013 |
| 17 | Search Field label too verbose | T325022 |
| 18 | Search field speaks two different shortcuts | T325022 |
| 19 | Go button disappears after entering Search field | T325024 |
| 20 | Unlabeled links | |
| 21 | No reflow | T325025 |
List of questions answered by AFB
| # | Question | Notes |
| 1 | How are your impressions of the landmark regions in modern vs legacy Vector? | Validates T291304 |
| 2 | How are your impressions of the heading structure in modern vs legacy Vector? | Validates T290280 |
| 3a | Modern Vector moves the page toolbar below the page titlebar and into <main>. This has resulted in keyboard users needing to tab through more elements before reaching the article text (more context). What’s the best approach to maintain the experience for keyboard users while adhering to accessibility best practices? | Validates T312818 |
| 3b | How important is it for the TOC to be inside <main>? | Validates T308055 |
| 4 | How accessible are our dropdown menus to screen reader users? | |
| 4a | Additionally, what are your thoughts on this alternate option, which uses aria-hidden on the label element to reduce verbosity for screen readers? | Validates T325026 |
| 5 | How does the accessibility of the table of contents compare in modern vs legacy Vector? Including the collapsed TOC implementation on viewports under 1000px. | |
| 6 | The sticky header in modern Vector is entirely hidden from screen reader users given it contains purely duplicated content. What do you think of this approach? | Validates T290201 and T314949 |
| 7 | How accessible is the contents of the language dropdown in modern Vector? | |
| 8 | Does modern Vector’s search field fulfill user expectations in regards to keyboard and screen reader accessibility and is beneficially usable? | |
| 9 | Does our analysis of accessibility requirements for the in progress Page Tools feature (design prototype, task) cover accessibility concerns? | Validates T318690 |
I realized I never updated this task, but AFB forgot to include feedback from their testing with VO with Safari from the original report. They sent us the updated deliverables but I never updated this task. Here are the updated files, nothing drastically different with the results