-
Notifications
You must be signed in to change notification settings - Fork 791
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
[UI/UX] APIM 3 General Accessibility #3935
Comments
We could use react-a11y to identify the missing ARIA practices at the development time. We could use Google LightHouse command line tool and integrate it with the product build to get the accessibility coverage report or we could use @dakshika's pa11y-full-report tool to get a more descriptive report |
Using react-axe article |
Automating lighthouse report with puppeteer: Sample repo |
Following doc is created as a guideline |
React A11y library is deprecated. |
axe - Web Accessibility Testing |
Closing the issue as this is older than 3 years. Please reopen if the issue is valid still. |
Description:
We need to consider the accessibility best practices mentioned in
http://www.w3.org/TR/wai-aria-practices/
when developing web apps for APIM products.
Since we are using Material UI for building the React SPA apps, MUI already supports ARIA practices and enforce it in some components.
Further, we need to follow the guidelines given in the React Documentation for adapting the aria practices.
WCAG21 reference
Affected Product Version:
The text was updated successfully, but these errors were encountered: