The HTML accesskey attribute’s value is used by the user agent as a guide for creating a keyboard shortcut that activates or focuses the element. (See the HTML spec)
Actual implementation of accesskey is very varied, making it difficult to produce reliable results for international users.
When it comes to simple keypresses, Firefox on Mac doesn't support Greek (but Chrome and Safari do), and Edge doesn't support Devanagari.
Firefox and Safari on Mac only treat ASCII case-sensitively (Chrome ignores case for other Latin and for Greek). Edge ignores case for Greek, but not for non-ASCII Latin.
Chrome & Safari on Mac allow use of shift to modify the key to be matched against the accesskey value. Firefox doesn't. On Windows, Chrome only does this for Devanagari and Edge only for Greek (which could be related to case-insensitive matching). Firefox results for Windows are not given, but this will be problematic, since shortcut keys for Firefox on Windows require alt+shift always.
Chrome & Safari happily match keys that produce mulitple characters with accesskey attributes. Firefox doesn't, but that may be because the only keys of that kind i found so far require use of the shift key to reach them. So another test case is needed really. Edge also fails this test, possibly for the same reason.
The HTML
accesskey
attribute’s value is used by the user agent as a guide for creating a keyboard shortcut that activates or focuses the element. (See the HTML spec)Actual implementation of accesskey is very varied, making it difficult to produce reliable results for international users.
The tests at https://www.w3.org/International/tests/repo/results/accesskey indicate that:
When it comes to simple keypresses, Firefox on Mac doesn't support Greek (but Chrome and Safari do), and Edge doesn't support Devanagari.
Firefox and Safari on Mac only treat ASCII case-sensitively (Chrome ignores case for other Latin and for Greek). Edge ignores case for Greek, but not for non-ASCII Latin.
Chrome & Safari on Mac allow use of shift to modify the key to be matched against the accesskey value. Firefox doesn't. On Windows, Chrome only does this for Devanagari and Edge only for Greek (which could be related to case-insensitive matching). Firefox results for Windows are not given, but this will be problematic, since shortcut keys for Firefox on Windows require alt+shift always.
Chrome & Safari happily match keys that produce mulitple characters with accesskey attributes. Firefox doesn't, but that may be because the only keys of that kind i found so far require use of the shift key to reach them. So another test case is needed really. Edge also fails this test, possibly for the same reason.