-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: 📚 Provide Accessibility (A11y) Information for All Components #1670
Comments
Under "Reviewed" you will find a list of components that I took a look at to add a11y information. if checked, the section has been included. If unchecked, it means that I did not include a11y information because there was not relevant information available (eg: no a11y issues or all issues are resolved)
#### Components Checklist
|
@coraliefeil since code is now having a section called "Accessibility Information" should we rename our "Accessibility" section in figma to match storybook? |
Figma "Accessibility" renamed to "Accessibility Information" to match code future improvements in this ticket |
Blocked by #1699 and will need refactor due to #1379 . Current status: Components in conformity with figma:
Components with diferences between Storybook and Figma:
Components with no information in Accessibility Information section in figma:
Components with no Accessibility Information (storybook and figma):
|
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:
• Each component has an “Accessibility Information” section beneath its description.
• Provide a detailed list of known A11y issues.
• The information must be easy to update as compliance or known issues change.
Notes:
Where to put the documentation
Storybook
DoR
DoD
feature
branchThe text was updated successfully, but these errors were encountered: