-
Notifications
You must be signed in to change notification settings - Fork 705
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
Accessibility compliance for kubeapps.dev #5397
Comments
|
Current status:
Summary:
|
Thanks for the complete revision and detailed comment. |
Reopen as we need to confirm with the a11y team before actually closing this issue. |
Accessibility issues have been assigned to the audit team to review all the evidence and reply to the questions performed by @antgamdia. |
Let's close this issue and reopen it if any issues from the acceptance review. |
Unfortunately, some issues have been reopened. Further work seems to be required. Closed with a comment for them to reconsider
Fixes required
Triage pending
|
|
### Description of the change While working on #5397, I discovered some minor issues with the meta tags we were using. Mainly, the title and description of each page were always the same, hindering the crawler process we run via Algolia. ### Benefits Title and other meta tags will have more meaningful content. ### Possible drawbacks N/A ### Applicable issues - related #5397 ### Additional information I'm removing some unused files as well. ![image](https://user-images.githubusercontent.com/11535726/198228723-83b7cc56-c4bd-49c7-a397-1684291bcff3.png) Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
### Description of the change This PR aims at fixing the remaining a11y issues that were reopened. Details at #5397 (comment) Summary of the changes: 1. Change the border color of the searchbox 2. Display a menu behind "documentation" if the screen is small. If you don't like it, we can always remove it and try to convince a11y folks. 3. Fix the overflow of the left menu 4. Add a "space" and "enter" keyboard events handler for the OneTrust cookie manager. 5. Remove the focus on code blocks (every code block, indeed) ### Benefits a11y compliance ### Possible drawbacks N/A ### Applicable issues - fixes #5397 ### Additional information This PR is based on top of #5578, as I assume it will get merged soon. Also, I've removed some unused files (images mainly) and unified the icons we are using (ie, using the SVG ones, and resizing them, via CSS, instead of having several logos for the same purpose) ~EDIT: there are more issues to solve I've just seen, will add the fixes to this PR~ Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
All the pending issues have been moved to "acceptance review". If any of them happen to be reopened, I'll also reopen this issue (hope we don't have to 🤞 ) |
Summary
The goal is to ensure kubeapps.dev website is accessible
Background and rationale
All VMware’s OSS products must meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards.
Devices, Assistive Technology combinations used: Chrome + NVDA on Windows, Safari + Voiceover on Mac
Description
Review the results of the accessibility audit for kubeapps.dev and fix all issues reported (JIRA - internal tool)
Acceptance criteria
Additional context
An Accessibility Testing has been completed for kubeapps.dev with several issues identified to comply with Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards (issues: 7 critical, 20 High, 2 Medium, 5 Low)
The text was updated successfully, but these errors were encountered: