Opened 6 years ago

Closed 5 years ago

#7848 closed bug (notabug)

Spinner: accessibility

Reported by: ezufelt Owned by: Scott González
Priority: minor Milestone: 1.9.0
Component: [meta] ui.dev Version: git (not yet released)
Keywords: a11y Cc:
Blocked by: Blocking:

Description (last modified by Scott González)

Firefox 7.0.1 JAWS 13 Spinner demo 1.9pre

Problem

  1. JAWS reports as a spinner, but doesn't indicate that up / down arrows change value. Perhaps, since this is a relatively new control on the web a default, or recommended, tooltip would be useful.
  2. Up button has no name, down button has name of 'black down pointing triangle'.
  3. Up / down buttons do not appear to receive focus.

Solution

  1. Make sure that up / down buttons have appropriate accessible names
  2. Make sure that up / down buttons can receive keyboard focus * this may be annoying as for N spinners there would be N*3 tab stops, thoughts?

Change History (6)

comment:1 Changed 6 years ago by Scott González

Component: ui.core[meta] ui.dev
Description: modified (diff)
Keywords: a11y added
Version: 1.8.16git

We're intentionally forcing focus to the text field when you interact with the buttons. The idea is that screen reader users should just use the arrow keys instead of the buttons. What kind of interaction do you get from a desktop spinner field?

comment:2 Changed 6 years ago by ezufelt

I just tested a spinner (font size) in Firefox options. When tabbing to the spinner JAWS reads: "Size combo box. To change selection use the arrow keys".

This is likely a true combo and not a spinner. I do see what you're saying, I tab to, and then past, the spinner, without landing on the up / down buttons (if they are present).

Since all of the functionality is available without access to the buttons, and since the buttons clutter the set of focusable controls, I agree that they should remain as they are now.

comment:3 Changed 5 years ago by Jörn Zaefferer

I've talked to Hans twice about the right role, and our use of role=spinbutton is correct. I don't see how we could get the screenreader to announce that up/key cursor keys can be used.

comment:4 Changed 5 years ago by Scott González

Owner: set to scott.gonzalez
Status: newassigned

I'll post to free-aria abou this.

comment:6 Changed 5 years ago by Scott González

Resolution: invalid
Status: assignedclosed

There doesn't appear to be anything we should be doing differently.

Note: See TracTickets for help on using tickets.