As a user,
I need clear and detailed accessibility (A11y) information for each component
so that I can understand if a component is A11y compliant and, if not, what the known issues are.
Acceptance Criteria:
Accessibility Section in Documentation:
• Each component has an “Accessibility Information” section beneath its description.
• Provide a detailed list of known A11y issues.
Content Management:
• The information must be easy to update as compliance or known issues change.
Notes:
Known issues should include links to any relevant tickets or documentation for transparency.
This information helps users make informed decisions about which components to use in A11y-sensitive contexts.
Ensure the documentation itself meets accessibility standards.
Add information in contribution guide about "how/when to update these information"
DoD would be checking and adding it to all components.
Where to put the documentation
Storybook
DoR
[x] Item has business value
[ ] Item has been estimated by the team
[x] Item is clear and well-defined
[x] Item dependencies have been identified
DoD
[ ] Relevant stories (Features, A11y) are created/updated
[ ] Migration Guide has been created/updated (if applicable)
[ ] Implementation works successfully on feature branch
Description
As a user, I need clear and detailed accessibility (A11y) information for each component so that I can understand if a component is A11y compliant and, if not, what the known issues are.
Acceptance Criteria:
Notes:
Where to put the documentation
Storybook
DoR
DoD
featurebranch