Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Tracking Issue: WCAG 2.1 AA Accessibility - Fixing known issues #31476

Closed
umpox opened this issue Feb 18, 2022 · 0 comments
Closed

Tracking Issue: WCAG 2.1 AA Accessibility - Fixing known issues #31476

umpox opened this issue Feb 18, 2022 · 0 comments

Comments

@umpox
Copy link
Contributor

umpox commented Feb 18, 2022

Problem to solve

This tracking issue reflects the Fixing stage of the accessibility work that began in Q1. Today, the Sourcegraph web application does not comply with current WCAG guidelines. Our ultimate goal and measure of success is to reach (and maintain) compliance by the end of FY23 (January 2023).

Measure of success

Accessibility issues within each product area have been fixed and we are ready for a comprehensive audit in Q3. The VPAT (the certification we need) is issued alongside the audit, so we want to be in the best shape possible in order to avoid paying (and waiting) for another audit.

Solution summary

  • Accessibility champions use this issue template (found in How to conduct an accessibility audit) to begin fixing accessibility issues within their product areas.
  • Frontend Platform Team supports accessibility champions in auditing and fixing accessibility issues.
  • Frontend Platform Team will take responsibility for any work that spans multiple teams.
  • Where possible, Frontend Platform Team will delegate work to Gitstart to minimize effort required from accessibility champions and their teams.

Artifacts:

What specific customers are we iterating on the problem and solution with?

Impact on use cases

This work contributes to the overall effort to scale our business.

Delivery plan

Step 2: Self auditing (June, July)
Teams have committed to the following deadlines for fixing known issues:

  • Frontend Platform
  • Repo Management
  • Growth and Integrations
  • Cloud SaaS
  • Search
  • Code Insights
  • Batch Changes - June 28
  • Conde Intel

Tracked issues

@unassigned: 68.00d

Completed: 46.00d

@BolajiOlajide: 2.50d

Completed: 2.00d

@abeatrix: 2.00d

Completed: 2.00d

@adeola-ak: 1.50d

Completed: 1.50d

@almeidapaulooliveira: 0.50d

Completed: 0.50d

@cesrjimenez: 4.00d

Completed: 4.00d

@courier-new: 1.00d

Completed: 1.00d

@efritz: 0.50d

Completed: 0.50d

@eseliger: 1.00d

Completed: 1.00d

@felixfbecker

Completed

@fkling: 11.00d

Completed: 11.00d

@gitstart-sourcegraph: 71.00d

Completed: 71.00d

@kopancek

Completed

@limitedmage: 44.50d

Completed: 42.50d

@lmelende20: 1.50d

Completed: 1.50d

@lrhacker: 9.00d

Completed: 5.00d

@novoselrok: 1.00d

Completed: 1.00d

@philipp-spiess

Completed

@plibither8: 0.50d

Completed: 0.50d

@rrhyne: 0.50d

Completed

@st0nebraker

Completed

@taras-yemets

Completed

@tjkandala: 10.50d

Completed: 10.50d

@umpox: 55.50d

Completed: 55.50d

@vovakulikov: 47.00d

Completed: 28.00d

Legend

  • 👩 Customer issue
  • 🐛 Bug
  • 🧶 Technical debt
  • 🎩 Quality of life
  • 🛠️ Roadmap
  • 🕵️ Spike
  • 🔒 Security issue
  • 🙆 Stretch goal
@umpox umpox moved this to Tracking Issue in WCAG 2.1 AA Accessibility Feb 18, 2022
@umpox umpox added the wcag/2.1 label Feb 18, 2022
@umpox umpox mentioned this issue Jul 26, 2022
8 tasks
@github-project-automation github-project-automation bot moved this from Tracking Issue to Done in WCAG 2.1 AA Accessibility Oct 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants