These toolbarbuttons with class="scrollbutton-up" and class="scrollbutton-down" are defined in tabs binding, they should provide accessible name. It can be done by ARIA like aria-label attribute.

Can we hide them from screen readers instead? Screen reader users don't need to scroll along the tab strip, do they?

(In reply to comment #1) > Can we hide them from screen readers instead? Screen reader users don't need to > scroll along the tab strip, do they? Marco will correct me but I think you're right screen reader users can move between tabs without these buttons. I hope they have effective way. But anyway exposing them to AT shouldn't hurt anybody. You can hide them by @role="presentation".

Does pageup/down move by larger increments when focus is inside the tab strip? For example forward and backward by a fixed amount of tabs?

The tab strip isn't focusable. Accel+PageUp/PageDown always takes you to the next/previous tab. Accel+1 respectively Alt+1 (on Linux) takes you to the first tab, Accel+9 / Alt+9 to the last one.

Forgot to mention: The active tab is focusable. When it's focused, the arrow keys also take you to the previous / next tab.

I'm also thinking about software that might want to interact with these scroll buttons besides screen readers, for example voice input software. They might very well need access to these buttons to be able to scroll the tabs. Motor-impaired people will be helped by this. So I think we *should* give them accessible names even though keyboard users won't interact with these.

Unfortunately we're past string freeze, so that solution is unlikely to make it into Firefox 4.

(In reply to comment #7) > Unfortunately we're past string freeze, so that solution is unlikely to make it > into Firefox 4. it's ok if these changes are explicitly approved by drivers. Though this bug doesn't have known big negative impact, so perhaps it can wait.