WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: When to use WCAG 2.4.3and WCAG 2.1.1

for

From: Mark Magennis
Date: Apr 22, 2022 9:01AM

JP, I think your explanation of 2.1.1 is a little misleading. You say "every HTML element that can be operated by a user is responsive to keyboard functionality" but it's about functions, not elements. So for example you could have an element that is clickable using a mouse but not accessible using the keyboard and that would be okay as long as you can carry out the function that it does using the keyboard by some other means.

Regards,
Mark

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of jp Jamous
Sent: 22 April 2022 15:33
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [EXTERNAL] Re: [WebAIM] When to use WCAG 2.4.3and WCAG 2.1.1

Reinhard,

I don't know of a reference that would give you such comparison. I can help you explain it, but you are not allowed to plagiarize. *Smiles*

I am going to keep my explanation simple and to the point, without covering the technical aspect of it.
2.1.1 focuses on ensuring that every HTML element that can be operated by a user is responsive to keyboard functionality. In other words, if it can be operated via the mouse, it must be fully operable via the keyboard. It's that simple.
2.4.3 focuses on the order of navigation from one focusable element to another. This ensures that visually and programmatically the navigation is logical and meaningful, as the designer intended it to be. If 2.4.3 fails, it would automatically fail 2.4.7 from a visual perspective, because the visual outline would be visually jumping all over the page or its various sections. On the other hand, failure of 2.4.3 can automatically fail 1.3.2 - (Meaningful Sequence), because screen reader users may not be able to make sense of how a "billing" link was included amongst the "various Support" links in a dropdown menu.

In summation, 2.1.1 is to ensure keyboard users can operate the elements that are operable by mouse users. Whereas 2.4.8 ensures that the keyboard user is not disoriented both visually, using visible focus indicator, or programmatically, using a screen reader.


From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Reinhard Stebner
Sent: Thursday, April 21, 2022 7:54 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] When to use WCAG 2.4.3and WCAG 2.1.1

I am looking for good resources that will have good explanations of when to use WCAG 2.4.3 and WCAG 2.1.1. I have been given a task by my team lead to write a comparison and contrast of these two guid External ( <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >)
INKY is learning...<https://protection.inkyphishfence.com/report?id=bmV0b3JnZnQxMDM2OTU1NC9qcEBqZXBlbHN5LmNvbS80NWU2NWM1NmMyYTU3NDQyN2E2MWRjNTY2NmNhYzBhYS8xNjUwNTg4ODgxLjY2#key8c082392072be3c20bd88f7a95bb1f4> Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnZnQxMDM2OTU1NC9qcEBqZXBlbHN5LmNvbS80NWU2NWM1NmMyYTU3NDQyN2E2MWRjNTY2NmNhYzBhYS8xNjUwNTg4ODgxLjY2#key8c082392072be3c20bd88f7a95bb1f4> FAQ<https://www.inky.com/banner-faq> GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>


I am looking for good resources that will have good explanations of when to use WCAG 2.4.3 and WCAG 2.1.1. I have been given a task by my team lead to write a comparison and contrast of these two guidelines.