WCAG 2.1 AA Accessibility - Comprehensive audit and response

[taylorsperry]

Problem to solve

This tracking issue reflects the audit 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

Sourcegraph has been issued a VPAT (Voluntary Product Accessibility Template) to indicate our compliance with WCAG 2.1 AA guidelines.

Solution summary

Engage our accessibility partner, TPGi, to conduct a comprehensive audit of the Sourcegraph application. We expect this process to take 4 - 7 weeks. If we meet WCAG requirements, we can move onto WCAG 2.1 AA - Maintaining compliance. If we don't, we'll need to fix outstanding issues and arrange for a second audit from TPGi. Though not ideal, we've deliberately built time into our schedule to accommodate this possibility.

Artifacts:

• Documentation and planning on WCAG 2.1 AA compliance #31200
• https://github.com/sourcegraph/sourcegraph/issues/31475
• https://github.com/sourcegraph/sourcegraph/issues/31476
• Sourcegraph Accessibility Remediation Plan
• RFC 557: WCAG 2.1 AA Compliance Plan
• Accessibility Champions
• WCAG 2.1 AA Accessibility Project Board
• How to conduct an accessibility audit

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

• https://github.com/sourcegraph/accounts/issues/278

Impact on use cases

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

Delivery plan

• Step 3: Comprehensive audit and response (August, September, October)