New draft accesskey rule

[WilcoFiers]

Based on the work in issue #43.

[gianwild]

Should we exclude known accesskey combinations (like ALT+Q to quit, ALT+F to open the file menu etc)?

[josehilera]

Its ok for me.
Remaining gianwild comment about accesskey combinations, I think that it does not affect this rule, because the accesskey combination is controled by the browser:

• https://webaim.org/techniques/keyboard/accesskey
• https://www.w3.org/TR/html/editing.html#assigning-keyboard-shortcuts-processing-model

[EmmaJP]

The rule is about the uniqueness of the accesskey values in a page, rather than whether or not they are sensible values.

[WilcoFiers]

We need to add tests to this as well.

[WilcoFiers]

@gianwild Merging this into draft, we'll open an issue to discuss your comment.

[kensgists]

Does what it says on the tin.

[EmmaJP]

Issue raised for adding tests ... #58

[gianwild]

I think we should make sure that people use this only for web applications, not standard web sites. It's a bit like role=menu - only makes sense on a complex web app not a standard web site.
And I always thought accesskeys were ALT + a character - not CTRL. Has that changed?

[EmmaJP]

@gianwild I think it's OK for either, as this rule about the uniqueness of the attribute value rather than how suitably it has been applied. That would be a different test, if there is need for one.

[gianwild]

Thanks @EmmaJP