Background

In T337967, we discovered the W3C Authoring Practices Guidelines (APG) and how our Tabs component differs quite a bit from the recommendations for that pattern and may not comply with WCAG 2.1 or WAI-ARIA standards requirements for keyboard navigation/input or screen reader accessibility.

Goal

Have understanding of which Codex components are not conforming to W3C recommendations and what we can do to fix them, as well as whether or not we need to fix them right now. Ideally the engineer who is auditing a component is not the same person who implemented it initially.

Acceptance Criteria

For each Codex components that have an APG pattern recommendation:

• Issues are catalogued in this Google Sheet and there is an outline of what guideline it is breaking. If there are multiple issues per component, create a new row per issue.
• Each issue has an initial recommendation for addressing it based on W3C guidelines.
• The relative priority for addressing each issue is determined as a team.
• Phabricator tasks are created for all High Priority issues.