Last modified: 2014-08-19 16:59:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T64923, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62923 - MultiMediaViewer: Accessibility for keyboard users and screen readers
MultiMediaViewer: Accessibility for keyboard users and screen readers
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
MultimediaViewer (Other open bugs)
master
All All
: Unprioritized major (vote)
: ---
Assigned To: Nobody - You can work on this!
: accessibility
: 66357 (view as bug list)
Depends on:
Blocks: 367
  Show dependency treegraph
 
Reported: 2014-03-21 13:30 UTC by Derk-Jan Hartman
Modified: 2014-08-19 16:59 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Derk-Jan Hartman 2014-03-21 13:30:41 UTC
This should take care of the most severe problems:

* The thumbs should have aria-haspopup

* The image displayed in the mediaviewer, possibly should copy over the alt attribute of the original image.. Although we might consider using aria-describeby=file description instead.

* aria-hidden should be applied to all the content and interface elements outside the modal dialog when the light box is open. (difficult, because we have multiple divs and skins that need this that are direct children of body tag)

* The content should somehow indicate that the user is no longer in the same 'view'. role=dialog or role=document (probably due to the FS and opaque nature of the view and separate content context of the view it should be document ???? verify)

* The dialog/document needs a label (using aria-labelledby or aria-label) (where did the user end up ????)

* When the dialog opens, remember the current focused element, put focus on the first focusable element in the dialog. When closing the dialog, restore the focus.

* There are several interface buttons in MMV, that are not actual buttons. (role=button or <button> should be used). Things that take you away form the page can be <a> elements.

* Image buttons require labels. Use aria-labelledby or aria-label if you don't want them to be visible. 

* div's need tabindex="-1" to make them keyboard actionable. They should respond to space and enter keys, as if they are clicks.

* Use this file needs to have aria-haspopup

* Use this file dialog needs equal amount of keyboard navigation love

* mw-mob-image-category is a listitem, but the list that it includes is not a list. (use hlist)

* view more in the license box needs aria love
Comment 1 Derk-Jan Hartman 2014-03-21 13:53:40 UTC
"div's need tabindex="-1" to make them keyboard actionable"

that should be tabindex="0" of course
Comment 2 Tisza Gergő 2014-03-21 18:12:31 UTC
The related Mingle ticket is https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/58
Comment 3 Tisza Gergő 2014-08-19 16:59:19 UTC
Merging bug 66357:

Navigation buttons (next/prev, close, fullscreen) should be first in tab order (with an easy-to notice focused style) so they are easily accessible from the keyboard.
Comment 4 Tisza Gergő 2014-08-19 16:59:28 UTC
*** Bug 66357 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links