Opened 6 years ago

Closed 5 years ago

#17698 closed defect (fixed)

Dojo mobile slider widget is not accessible

Reported by: Patrick Ruzand Owned by: Patrick Ruzand
Priority: high Milestone: 1.10
Component: DojoX Mobile Version: 1.9.2
Keywords: a11y Cc: Sebastien Pereira
Blocked By: Blocking:

Description

The Dojo mobile slider widget has the following a11y issues: Not keyboard accessible Cannot operate when VoiceOver? is enabled

Reconstruct current Slider by making "decrease" and "increase" buttons accessible under VoiceOver? and keyboard enabled. Or consider using the html5 input element with type="range".

Change History (7)

comment:1 Changed 6 years ago by Patrick Ruzand

Keywords: a11y added
Owner: set to Patrick Ruzand
Priority: undecidedhigh
Status: newassigned

comment:2 Changed 5 years ago by Patrick Ruzand

Milestone: tbd1.10

comment:3 Changed 5 years ago by Sebastien Pereira

Cc: Sebastien Pereira added

comment:4 Changed 5 years ago by Sebastien Pereira

Symptoms are confirmed, plus ARIA-valuenow has no effect with JAWS on FF/IE desktop.

ARIA attributes aria-valuemin, aria-valuemax, aria-valuenow and role="slider" have to be set on the handle. tabindex="0" has to be set as well in order to allow keyboard navigation.

comment:5 Changed 5 years ago by Sebastien Pereira

On iOS, even with the correct aria attributes:

  • Voiceover wrongly states "swipe up or down with one finger to adjust the value". In fact users should double-tap-and-hold the handle to be able to slide the handle and change the value.
  • Voiceover doesn't speak the new value when aria-valuenow changes, but it does when the user tap on the Slider.
Last edited 5 years ago by Sebastien Pereira (previous) (diff)

comment:6 Changed 5 years ago by Sebastien Pereira

comment:7 Changed 5 years ago by Patrick Ruzand <pruzand@…>

Resolution: fixed
Status: assignedclosed

In d0454672368a4b38d8d5b6406161af174d1b4303/dojox:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 
Note: See TracTickets for help on using tickets.