Manual test of accessKeyLabel

There is a button, with accesskey="話 я g" and a script that uses accessKeyLabel to show what shortcut should focus or trigger the button.

Expected result

The button text includes some activation based on "я" if you have a cyrillic keyboard, or else one based on "g" - and that if you use this activation the button is focused or pressed. When pressed, the button will try to open a window with the Github repo for this test, so you can update the results section :)

Value of the accessKey DOM attribute:

Likely failure modes

Results

This test is on github to enable Pull Requests…

Firefox 42, 64-bit Ubuntu Linux 14.04
The button has the text Play Github! activation: Alt+Shift+話 я g
Orca 3.18 announces the button text ("Play Github! activation Chinese letter ya g pushbutton") when you navigate to it, but that's simply reading the button text.
Since I cannot generate the 話 or я characters, I cannot find out if those accesskeys work.
Firefox 42, 64-bit Windows 7 with NVDA
The button has the text Play Github! activation: Alt+Shift+話 я g
When navigating to button, NVDA announces "button Alt + Shift + Chinese letter" and then the button text as listed above. It does not mention the other two options.
Since I cannot generate the 話 or я characters, I cannot find out if those accesskeys work. "g" does not work.
Opera 12, 64-bit Ubuntu Linux 14.04, accesskey is "(null)"
Shortcut can be activated with a mouse click on the accesskey menu
Internet Explorer 11, 64-bit Windows 7 with NVDA
When navigating to button, NVDA announces "button Alt + Chinese letter ya g" and then the button text "Play Github!"
Since I cannot generate the 話 or я characters, I cannot find out if those accesskeys work. "g" does not.
Chrome 46, 64-bit Windows 7 with NVDA
When navigating to button, NVDA announces "button Alt + Chinese letter ya g" and then the button text "Play Github!"
Since I cannot generate the 話 or я characters, I cannot find out if those accesskeys work. "g" does not.
Firefox 42, 64-bit Windows 7 with JAWS
The button has the text Play Github! activation: Alt+Shift+話 я g
JAWS merely speaks the button text but with spaces where the 話 or я characters are.
Since I cannot generate the 話 or я characters, I cannot find out if those accesskeys work. "g" does not work.
Internet Explorer 11, 64-bit Windows 7 with JAWS
When navigating to button, JAWS announces the button label and then "g button". It should be noted that neither the 話 or я characters were read out, even in paragraph text.
Since I cannot generate the 話 or я characters, I cannot find out if those accesskeys work. "g" does not work.
Chrome 46, 64-bit Windows 7 with JAWS
When navigating to button, JAWS announces the button text and then "Alt + g button" with a pause where the two unspoken letters are.
Since I cannot generate the 話 or я characters, I cannot find out if those accesskeys work. "g" does not.
Safari 9.01, VoiceOver on MacOS 10.10.5
Voicover announces that the button "has accesskey 話 я g". Technically, this is not an accessKeyLabel implementation but it does a similar thing.
Since I cannot generate the 話 character without using IME, I cannot find out if that accesskey works. I cannot find a key combination for "я" or "g" that works
Firefox 42, MacOS 10.10.5
The button has the text Play Github! activation: ⌃⌥話 я g
Since I cannot generate the 話 character without using IME, I cannot
Safari 9.01, VoiceOver on MacOS 10.10.5
Voicover announces that the button "has accesskey 話 я g". Technically, this is not an accessKeyLabel implementation but it does a similar thing.
Since I cannot generate the 話 character without using IME, I cannot find out if that accesskey works. I cannot find a key combination for "я" or "g" that works
Safari 9.01, MacOS 10.10.5
Vivaldi 1.0.303.52 beta, MacOS 10.10.5 (based on Chromium)
Yandex browser 15.4.2272.3909 beta, MacOS 10.10.5 (based on Chromium)
The button has the text "Play Github!"
I cannot find a shortcut to make the button work
All tested user agents reflect the content of the HTML attribute in the DOM attribute accessKey

Discussion

The accesskey attribute was first defined in HTML 4, and an improved version was redefined in HTML5

The first value for accesskey probably doesn't exist as a single key on any keyboard normal people are likely to have (unless it is in chinese?), so a browser that accepts it as a shortcut isn't helping much.