Make accessKeyLabel or an equivalent parseable?

[chaals]

For javascript developers, knowing what accesskey is used, not just what is specified, would enable better conflict management by allowing finer-grained decisions on what accesskeys to request.

The current implementation state of accessKeyLabel seems pretty sad anyway, so it is unlikely that a change would break much.

[chaals]

Firefox implemented accessKeyLabel: https://bugzilla.mozilla.org/show_bug.cgi?id=583533
Webkit bug: https://bugs.webkit.org/show_bug.cgi?id=72715
Chrome bug:https://code.google.com/p/chromium/issues/detail?id=393466

Can't find anything for MS (on a very brief search).

[chaals]

As noted in the WebKit bug, the use case for accessKeyLabel that is presenting user-readable info should provide consistency with platform labeling conventions.

So accepting this issue either requires adding another attribute, destroying the use case for which the attribute was initially promoted, or requiring JS authors to parse a microsyntax based on platform conventions and the assumption that browser developers use them consistently...

[chaals]

If there is a standard underlying syntax, presenting it according to platform convention should be something browsers can do - e.g. represent Meta modifier as whatever key it actually is on whatever platform the browser is on.