Re: Duplicate Accesskey Values

Hi Guy,

I do not disagree with your sentiment, but here I am seeking specific
clarity on an edge-case scenario.

I've been doing this for a very long time now, and the biggest issue I see
is when evaluators do not understand the nuances of issues like this. So
while I don't disagree with what you said, I posed this question for a very
specific reason - to try and get a definitive resolution to a technical
possibility - because being an expert entails knowing the answers to *all*
of the questions (HA!) - or at least being able to reason things out using
the existing rulesets we have.

Advocating for users is NOT the same thing as providing developers and QA
specialists with concrete answers to technical questions: they both have to
co-exist to achieve success (at least, IMHO).

JF

On Thu, Dec 15, 2022 at 12:40 PM Guy Hickling <guy.hickling@gmail.com>
wrote:

> I appreciate the importance of raising matters like this, so something can
> be done about them, perhaps in WCAG 3 or even in a WCAG 2.3. In a practical
> way, however, this kind of thing is only an issue if we restrict ourselves
> to "WCAG audits". In my view, all accessibility audits should include both
> WCAG compliance, and accessibility best practice, and we should be
> educating our clients (if we are an external auditor), or developer teams
> (if working in-house in a company) to understand that. We ought to impress
> on them that they should be aiming to be inclusive of disabled people, not
> simply doing it to comply with some law or regulation.
>
> We do, after all, call ourselves "accessibility consultants", not "WCAG
> consultants"!
>
>
>

-- 
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"