The HTMLElement.accessKeyLabel read-only property returns a human-readable string representing the actual keyboard shortcut assigned to the element by the browser, based on the user’s platform and browser. If no access key is assigned, it returns an empty string.
If you give an HTML element the accesskey attribute, users can use a keyboard shortcut to activate it. However, the exact key combination is different in each browser and operating system, so it’s hard for users to know which keys to press. The accessKeyLabel property solves this by returning the actual key combination for the user’s current browser and OS as a string. Since WebKit, Firefox already support it, bringing it to Chromium will improve interoperability as well.
Safari 14 and Firefox 8 have already shipped the feature.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
No milestones specified