Skip to content
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

Uptime - Field Labels for Filter controls do not provide sufficient information #36294

Closed
barlowm opened this issue May 8, 2019 · 6 comments · Fixed by #82249
Closed

Uptime - Field Labels for Filter controls do not provide sufficient information #36294

barlowm opened this issue May 8, 2019 · 6 comments · Fixed by #82249
Assignees
Labels
loe:small Small Level of Effort Project:Accessibility Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability v7.11.0 WCAG A

Comments

@barlowm
Copy link
Collaborator

barlowm commented May 8, 2019

Field Labels for Filter controls do not provide sufficient information

Steps to reproduce (assumes NVDA or JAWS Screen Reader or similar)

NVDA Screen Reader is a free Screen Reader which can be downloaded from the NV Access Website
Deque has a page of shortcuts for help on using NVDA as well as a Quick Reference Guide for using NVDA

  1. Launch NVDA from the workstation.
  2. Open the uptime page in the browse.
  3. Navigate to the filter control directly after the search control.

FilterControls

Using Tab key to focus on any of the "drop down" controls and focus shifts to the edit field with a magnifying glass.

1556727561314

Actual Result

Screen Reader says

Edit

Expected Result

Screen Reader should say

Search for followed by the type of filter selected (e.g. "ID", "Name", "URL", "Port", "Scheme")

Meta Issue:

Accessibility Audit for Kibana 7.0
Make Uptime App Accessible for 7.0

Kibana Version:

7.0

Relevant WCAG Criteria:

WCAG Criterion

Input Assistance/Labels or Instructions (Level A)
Also see: Minimize Error Cues

@barlowm barlowm added Project:Accessibility Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability EUI WCAG A labels May 8, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime

@andrewvc andrewvc added :uptime EUI and removed Feature:EUI Project:Accessibility Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability labels Jul 9, 2019
@andrewvc andrewvc removed the :uptime label Sep 24, 2019
@myasonik myasonik added the Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability label Feb 10, 2020
@myasonik myasonik added loe:small Small Level of Effort and removed EUI labels Oct 1, 2020
@myasonik
Copy link
Contributor

myasonik commented Oct 1, 2020

Removed EUI label because this field just needs a better label, nothing for EUI to do

@shahzad31
Copy link
Contributor

image

This is apparently already fixed, there is a placeholder, it will say 'Search port' instead of 'Edit'

@myasonik
Copy link
Contributor

Placeholder text is not typically read to screenreaders. Is there an associated aria-label for that <input />?

@myasonik myasonik reopened this Oct 30, 2020
@zube zube bot added [zube]: Inbox and removed [zube]: Done labels Oct 30, 2020
@zube zube bot closed this as completed Oct 30, 2020
@zube zube bot reopened this Oct 30, 2020
@zube zube bot added [zube]: Inbox and removed [zube]: Done labels Oct 30, 2020
@zube zube bot closed this as completed Oct 30, 2020
@zube zube bot added [zube]: Done and removed [zube]: Inbox labels Oct 30, 2020
@zube zube bot reopened this Oct 30, 2020
@zube zube bot added [zube]: Inbox and removed [zube]: Done labels Oct 30, 2020
@zube zube bot closed this as completed Oct 30, 2020
@zube zube bot added [zube]: Done and removed [zube]: Inbox labels Oct 30, 2020
@zube zube bot reopened this Oct 30, 2020
@zube zube bot added [zube]: Inbox and removed [zube]: Done labels Oct 30, 2020
@zube zube bot closed this as completed Oct 30, 2020
@zube zube bot added [zube]: Done and removed [zube]: Inbox labels Oct 30, 2020
@shahzad31
Copy link
Contributor

@myasonik i did test with Vox screenreader

@myasonik
Copy link
Contributor

The Vox plugin unfortunately is not a good screen reader to test with.

It is entirely unique in how it works (it uses the DOM, instead of the Accessibility Tree) and is now in maintenance mode so it hasn't been updated in some time.

If you can test in VoiceOver (on Mac) or NVDA (on Windows) that would give us more accurate results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
loe:small Small Level of Effort Project:Accessibility Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability v7.11.0 WCAG A
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants