Accissibilty improvements to glow slider widget
Reported by Peter Harvey | April 20th, 2010 @ 12:25 PM | in 1.7
Accessibilty audit showed that users using JAWS could not enter data via the glow slider widget on Lab UK
See screenshot - and see
https://confluence.dev.bbc.co.uk/display/labuk/Accessibility+Audit+...
for details
Comments and changes to this ticket
-
Jake Archibald April 21st, 2010 @ 08:07 AM
- Milestone set to 1.7
- Tag changed from slider accessibility to defect, slider, widgets
- Assigned user set to Jake Archibald
Hi,
The slider labels usually render correctly. It looks like some custom CSS has been applied, is it possible that this custom CSS is also interfering with the label positioning?
We recommend that the slider is linked to a text input element (this can be hidden off-screen but still accessible to a screen reader. Although the slider has ARIA attributes, some screen readers miss it when in forms mode. Is the slider bound to a text input element?
Cheers,
Jake. -
matth April 21st, 2010 @ 09:23 AM
Hi, here is the exact copy from the accessibility report. Not sure if this is our fault or yours yet ...
"The sliding scale was not accessible when using JAWS. When this section of the page was selected the slider could not be moved at all. This meant the page could not be completed and JAWS users could not complete the Web Behaviour Test. However, it is worth noting that sliders can be made to work with JAWS. For example, the volume control on the BBC iPlayer is accessible to screen readers, as they can adjust the slider once it is in focus.
Interestingly, it was possible to move the slider using the keyboard alone (when JAWS was not being used). This could be done by tabbing to the slider and using the arrow keys to move it to the appropriate value. However, JAWS uses the arrow keys to read through bocks of text on a page. This meant that the text above the slider was read out instead; it was not possible to move focus to the slider itself.
It was possible for JAWS to select the values shown on the height/weight scale of the Big Personality Test (e.g. 80, 118, 155, 193, 230 cm). This did not prevent the user completing the form, although it would have been nice to be able to select an intermediate value. If the JAWS user was 178cm tall they would have only been able to select 155 or 193cm on the scale, not any value in between.
One possible way around the issues described above would be to provide a text input box next to the sliding scale. Screen reader users could then tab to the text box and, once given instructions, enter the appropriate value. This would then cause the slider to move to the value they entered."
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A JavaScript Library