Posted by casey on June 8, 2011 at 3:26pm
4 followers
Jump to:
| Project: | Drupal core |
| Version: | 9.x-dev |
| Component: | contextual.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
| Issue tags: | accessibility, html5 |
Issue Summary
If supported - there are currently no browser that support the <menu> nor the <command> nor the contextmenu attribute - the Contextual links module should definitely use them.
We can even start using them and provide graceful degration; shouldn't be too hard.
Comments
#1
Hmm, it is possible that user agents will only implement support for applications (using application role or something).
#2
@Casey
I think new screen-readers will support these elements by switching into forms mode (would need to test). But, the support won't go back very far, so we will need an accessible fallback for screen-readers without this support.
#3
#1184718: Wrap page in application role as soon as administrative controls are added
#4
FF8 is going to support it: https://developer.mozilla.org/en/Firefox_8_for_developers
#5
Subscribe.
#6
Can someone put together a patch for this?
#7
Marking this as postponed because we're not sure what need this is filling. Also, would want to watch use case via http://caniuse.com/
Note: This is a quick summary from the A11ySprint.
#8
Can somebody explain what this is about exactly?
#9
The menu element was meant to represent a list of commands, and still has very little support. See:
html5 menu element
#10
Hm, indeed: http://caniuse.com/menu. I'd never heard about this before :)
That means this is definitely D9 material.