Ticket #7848 (closed bug: notabug)

Opened 4 years ago

Last modified 4 years ago

Spinner: accessibility

Reported by: ezufelt Owned by: scott.gonzalez
Priority: minor Milestone: 1.9.0
Component: [meta] ui.dev Version: git
Keywords: a11y Cc:
Blocking: Blocked by:

Description (last modified by scott.gonzalez) (diff)

Firefox 7.0.1 JAWS 13 Spinner demo 1.9pre


  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.


  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

comment:1 Changed 4 years ago by scott.gonzalez

  • Keywords a11y added
  • Version changed from 1.8.16 to git
  • Component changed from ui.core to [meta] ui.dev
  • Description modified (diff)

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 4 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 4 years ago by joern.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 4 years ago by scott.gonzalez

  • Owner set to scott.gonzalez
  • Status changed from new to assigned

I'll post to free-aria abou this.

comment:6 Changed 4 years ago by scott.gonzalez

  • Status changed from assigned to closed
  • Resolution set to invalid

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

Note: See TracTickets for help on using tickets.