Background

Throughout the Desktop Improvement project modern Vector has accumulated various accessibility issues, ranging from small miscellaneous bug to larger semantic HTML issues. This goal would allow us to prioritize fixing these issues.

Specific: What do we want to achieve?

Address known accessibility issues with modern Vector, incorporate feedback from American Foundation for the Blind's (AFB) testing, and improve the experience for keyboard and screenreader users in modern Vector to be on par with or improved compared to legacy Vector.

Measurable: How will we know when we've reached our goal?

• When all tasks above medium priority in the "Accessibility goal" column are completed, or are confirmed by AFB (American Foundation for the Blind) as tasks that can be closed.
• When all additional issues discovered by AFB's testing are tracked in new tasks.

Achievable: What support will we need to achieve our goal?

Several tickets are blocked by, or at least unable to sign off on, until we get additional feedback from AFB's testing

Relevant: Is this goal worthwhile?

With the launch of Desktop Improvements and the upcoming input from the [[ T310033 | AFB contract ]], now is an opportune time to shore up modern Vector's accessibility.

Time-bound: What is the time frame? Can we achieve this goal in the timeframe we've set?

These tasks should be achievable in a 3 month time frame with 2 people working 2 days a week with the assumption that we are able to hear back from AFB by mid Nov. If the results are delayed, some of the larger tasks around semantic HTML could be delayed or need to be descoped, especially considering decreased capacity in Dec.