Ramondaaccess-key
This fails the run. Where it is wrong about your code, // ramonda-check-ignore <reason> on the line says so, and the reason is printed on every run.
Reported when an accessKey is written, which overrides a shortcut the reader's own software may be using.
accessKey binds a character to this element, and the character is not the page's to give.
Browsers already bind most letters, and so does every screen reader — the software of the
people most likely to be using keyboard shortcuts at all. One page's accessKey overrides
that binding, on that page only, with nothing to discover it by and no way to switch it off.
It cannot be got right either: the modifier differs by browser and platform, the conflicts differ by screen reader, and nothing announces the binding — so the page cannot even tell the reader the shortcut is there.
Where a shortcut really is wanted, own it: a key handler the page documents on screen, which can be listed, chosen to avoid the common bindings, and turned off.
Next
- All rules — the other checks this one runs beside.
- Checking your app — how to run it, and what it proves.