- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Thu, 15 Dec 2022 19:58:34 +0000
- To: Wai-Ig <w3c-wai-ig@w3.org>, WCAG <w3c-wai-gl@w3.org>
- CC: John Foliot <john@foliot.ca>
Received on Thursday, 15 December 2022 19:59:19 UTC
Andrew wrote: > There is nothing in the HTML spec that forbids using the same accesskey I wasn’t ruling out there being a behaviour for duplicate attribute values defined somewhere else, but from Jon & Oliver’s comments it appears not. John wrote: > it is important to remember that the title of SC 4.1.1 is "Parsing" and not "No Duplicate IDs". Sure, but the other parts of 4.1.1 don’t apply to this scenario either. If you’re looking for a WCAG fail, it should be apparent from the SC text. There are grey areas when we have broad guidelines, but 4.1.1 is one of the more narrow criteria. It could be a parsing issue and not covered by 4.1.1, the SC wasn’t intended to capture all parsing issues. From Jon & Oliver, duplicate accesskeys might even be a desirable behavior. (My lack of knowledge on accesskey workings shows how much I come across them these days!) > I presume your response is/was as a SME, and not on behalf of the WCAG Chairs Of course. Chairs manage agendas, discussions, and consensus. Our opinions on a topic like this have the same value as anyone else’s. Any “official” opinion would be based on group consensus and stated as such. Kind regards, -Alastair
Received on Thursday, 15 December 2022 19:59:19 UTC