OOjs UI: Buttons and button-like things should be keyboard-accessible
Closed, ResolvedPublic

Description

'Cos right now they're not, which is bad and sad.


Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=65474

Details

Reference
bz62337
bzimport set Reference to bz62337.
  • Bug 58564 has been marked as a duplicate of this bug. ***

Change 132979 had a related patch set uploaded by Jforrester:
Button accessibility

https://gerrit.wikimedia.org/r/132979

Change 132979 merged by jenkins-bot:
Button accessibility

https://gerrit.wikimedia.org/r/132979

TheDJ added a comment.May 19 2014, 8:47 AM

Far from fixed.

oo-ui-tool-link's for help and edit notices, should have tabIndex=0 and role=button to make them a focusable elements and they need labels to describe them (aria-label[ledby]). The page options groups is a total wash in terms of keyboard accessibility.

I think this is now done given bug 65473's resolution.

(In reply to Derk-Jan Hartman from comment #4)

oo-ui-tool-link's for help and edit notices, should have tabIndex=0 and
role=button to make them a focusable elements and they need labels to
describe them (aria-label[ledby]). The page options groups is a total wash
in terms of keyboard accessibility.

Do we have all of this then? That's definitely not all covered by bug 65474

Apparently not.

Change 143155 had a related patch set uploaded by Alex Monk:
Add tabindex=0 and role=button to tool links

https://gerrit.wikimedia.org/r/143155

Change 143155 merged by jenkins-bot:
Add tabindex=0 and role=button to tool links

https://gerrit.wikimedia.org/r/143155

(In reply to Derk-Jan Hartman from comment #4)

they need labels to describe them (aria-label[ledby]).

Hey. Could you explain this a bit more please?

I think we should close this and open separate bugs for any remaining issues. It seems that the buttons in question (comment 4 and comment 10) are already described by a 'title' attribute, which may not be ideal but is still something. More precise label would probably have to be added in VE, not OOjs UI.

Add Comment