-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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) - Uptime Broken ARIA reference #35315
Labels
Comments
rashmivkulkarni
added
the
Team:Uptime - DEPRECATED
Synthetics & RUM sub-team of Application Observability
label
Apr 19, 2019
Pinging @elastic/uptime |
alvarolobato
added
:uptime
and removed
Project:Accessibility
Team:Uptime - DEPRECATED
Synthetics & RUM sub-team of Application Observability
labels
Jun 19, 2019
This has been fixed , although there was only one accessibility issue i saw with wave, but that is related to EUI Basic Table so i have reopened an old issue in EUI, that will be take care there if needed elastic/eui#840 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce (Use WebAIM WAVE chrome plugin)
They are for the various buttons and links on the page. Specifically:
These links are in the sidebar so this issue probably exists on all pages.
Each element has an
aria-describedby
attribute which references a random id (e.g. -aria-describedby="0nyangvc"
) which does not exist on the page, but changes with each load of the page.Each button/link DOES have an
aria-label
which is properly read by a screen reader but the aria-describedby attribute is used to indicate the IDs of the elements that describe the object. (See "Using the aria-describedby attribute"Expected Result
When navigating to a button/link containing an aria-describedby attribute the screen reader should read the description in addition to the lagel for the button/link
Meta Issue
Make Uptime App Accessible for 7.0
Kibana Version:
7.0
Relevant WCAG Criteria:
4.1.2 Name, Role, Value (Level A, Primary Success Criterion)
Other Related Success Criterion:
1.3.1 Info and Relationships (Level A)
3.3.2 Labels or Instructions (Level A)
The text was updated successfully, but these errors were encountered: