Background

An epic task to ensure alignment of Codex components and patterns comply successfully with Web Content Accessibility Guidelines level AA.

Why is this linked to WCAG 2.1?
That has been the last agreement within the Product department and in order to update to 2.2 we would have a few more conversations, for example on the interaction area minimum sizes. So we'll start with the large number of 2.1 criterias to support best-possibly and might extend and update this task in future.

Orientation historically
We've followed widely OOUI's already compliant widget blueprints. Given that we're starting over and also update our components, for example Dialogs, largely, we need to revisit former findings for a good experience.

Open questions

• We could limit this task only to the (design/)technical side in sense of technical compliance. Or expand on areas like UX writing on inclusion levels. Former ensures simpler task accomplishment.
• How to integrate manual and automated testing processes into accomplishing compliance best-possibly?

Criteria for done

• Make components comply to WCAG AA

Note, this is an epic umbrella task, aiming for collecting the goal for the library in subtasks.