Skip to content

[Accessibility]: Audit Batch Changes user journeys

Created by: courier-new

As part of our goal to obtain WCAG 2.1 AA Accessibility compliance by the end of FY23, we will need to audit all major user journeys within the Batch Changes product, log accessibility issues, and plan to fix as many as we can.

This issue reflects the auditing stage of this work.

See https://github.com/sourcegraph/sourcegraph/issues/31475 for more.

How to use this issue

At the end of every sprint, @courier-new will identify and ⭐ 5 new user journeys that have not yet been audited, in order of relative importance, until every user journey has been audited. These issues should be moved into P0, and their audits completed over the course of that sprint. Next-up issues will be identified and pre-flagged with ⬆️, and moved into P1.

For planning purposes, each team member should plan to set aside at least half a day per sprint to dedicate to conducting a new audit and fixing issues reported from a previously-completed audit.

During an audit, a team member can try to fix any trivial issues encountered as they are conducting the audit. For larger, non-trivial issues or issues with design questions, a team member should record the issue using the accessibility issue template to follow up on in the fixing stage. For issues with straightforward requirements and steps to reproduce, consider setting the ticket aside to delegate to GitStart.

An issue should be marked as done when each type of audit is complete and all accessibility issues identified in it have been logged.

List Page

Preview Page

Details Page

Settings/Admin

Marketing/Onboarding

SSBC