Manual test of HTML5 accesskey using cyrillic and latin

There is a button, with accesskey="я g".

Expected result

For users with a cyrillic keyboard, there should be a standard key based on "я" plus modifiers that either activates or focuses the button. For users who do not have a cyrillic keyboard but do have a latin keyboard, the shortcut should be based on "g". The button will try to open a window with the Github repo for this test, so you can update the results section :)

Play Github!

Value of the accessKey DOM attribute:

Likely failure modes

• In browsers that implement a tolerant version of the HTML 4 definition of accesskey, but not the HTML5 version, only a shortcut based on "я" will work.

Results

This test is on github to enable Pull Requests…

Firefox 42, 64-bit Ubuntu Linux 14.04 on "g"

Firefox 42, MacOS 10.10.5

Firefox exposes "Alt+Shift+я g" on Windows/Linux, ^⌥я g on Mac as a value of the accessKeyLabel DOM attribute

FireFox 42, Windows 7

Chrome 46.0.2490.86 m, Windows 7

Internet Explorer 11.0.9600.18097, Windows 7

Epiphany 3.10.3, 64-bit Ubuntu Linux 14.04 on "g"

Chromium 45, 64-bit Ubuntu Linux 14.04 on "g"

Firefox 42, 64-bit Windows 7 on "g"

Opera 12, 64-bit Ubuntu Linux 14.04 shows accesskey as "(null)"

Shortcut can be activated from accesskey menu with mouse

Internet Explorer 11, 64-bit Windows 7 on "g"

Chrome 46, 64-bit Windows 7 on "g"

Safari 9.01, VoiceOver on MacOS 10.10.5

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)

With a cyrillic keyboard set, none of these browsers enables accesskey using their standard modifiers plus "я"

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 is standard on cyrillic keyboards, so a browser that implements the HTML5 algorithm will use it as a shortcut. For users who do not have the key "available" but for whom the "g" key is "available", the shortcut should be based on "g".

Unfortunately the HTML 5 specification does not define what "available" means. At the very least, it should be simple for the user to generate such a key, and using the HTML5 definition which requires the user agent to assign modifiers, "available" should mean it must not require any modifiers to generate the base key.