Manual test of a word as an accesskey value

There is a button, with accesskey="word", and links with accesskey="слово" and accesskey="この".

Expected result

A strict HTML5 implementation will not make a shortcut available for the button. An HTML4 implementation may do so. The button will try to open a window with the Github repo for this test, so you can update the results section :)

Try a cyrillic: accesskey="слово". The test is on github to enable Pull Requests…

Try a hiragana keyboard: accesskey="この". The test is on github to enable Pull Requests…　And I doubt this works at all on Mac, maybe it does something on Edge…

Value of the button's accessKey DOM attribute:

Value of the link's accessKey DOM attribute:

Results

This test is on github to enable Pull Requests…

Firefox 42, MacOS 10.10.5
Firefox exposes "^⌥word" and "^⌥слово" as a value of the accessKeyLabel DOM attribute, but it seems not to enable any shortcut.
Firefox 42, 64-bit Ubuntu Linux 14.04
Firefox exposes "Alt+Shift+word" as a value of the accessKeyLabel DOM attribute, but it seems not to enable any shortcut.
Firefox 42, 64-bit Windows 7
Firefox exposes "Alt+Shift+word" as a value of the accessKeyLabel DOM attribute, but it seems not to enable any shortcut.
Opera 12, 64-bit Ubuntu Linux 14.04 shows accesskey as "(null)"
Clicking on the accesskey with a mouse in the menu invokes the shortcut
Internet Explorer 11, 64-bit Windows 7
Presses the button with alt+w, though not with alt+o, r or d (some of these are already taken in IE to do other tasks anyway).
Chromium 45, 64-bit Ubuntu Linux 14.04
Epiphany 3.10.3, 64-bit Ubuntu Linux 14.04
Chrome 46, 64-bit Windows 7
Vivaldi 1.0.303.52 beta, MacOS 10.10.5 (based on Chromium)
Safari 9.01, MacOS 10.10.5
Yandex browser 15.4.2272.3909 beta, MacOS 10.10.5 (based on Chromium)
There is no apparent way to trigger the shortcut
All tested user agents reflect the contents of the HTML attributes (word and слово) in the DOM attribute accessKey

Discussion

The accesskey attribute was first defined in HTML 4, and an apparently improved version was redefined in HTML5. This was subsequently removed in HTML 5.1, because it didn't work, as this and related tests demonstrate.

The HTML4 version of accesskey does not define error handling, whereas in the HTML 5 algorithm, @@ will use it as the base of a shortcut. Chaals' proposal for accesskey explicitly allows the use of words, for example as suggested voice commands, or gestures.