Documentation and planning on WCAG 2.1 AA compliance

Created by: taylorsperry

Problem to solve

Today, the Sourcegraph web application does not comply with current WCAG guidelines.

Ensuring our web application becomes--and stays--compliant is essential not just because we have current contractual obligations to do so, but also because:

We believe in the value of making our application compliant in furthering our mission
Compliance will likely be a requirement of future clients
Compliance can be a unique selling point

We want to ensure our application is WCAG 2.1 AA compliant by the end of FY23 (January 2023).

Measure of success

Any team is able to accurately audit their own areas of ownership and set up automated accessibility testing.

Solution summary

The Q1 part of this effort is to lay groundwork, share documentation, and line up Accessibility Champions for impacted teams. For Q2 efforts, see the Auditing and Fixing roadmap issues.

Artifacts:

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 1: Documentation and planning (February, March, April)
- @umpox Create WCAG 2.1 AA tracking issue
- Feb 18 @taylorsperry: Identify all relevant teams that will need to be involved in this work
- March 18 @umpox Add documentation for conducting accessibility audits
- March 22 @taylorsperry: Form a working group of "accessibility champions." Communications can be directed to the #wg-accessibility-champions channel or @accessibility-champions handle.
- March 29 @taylorsperry: Form a comprehensive list of user journeys that need to be audited
- March 29 @umpox TPGi automated scanning setup
- April 12 @umpox TPGi automated branch CI scanning