E-mail List Archives
Re: When to use WCAG 2.4.3and WCAG 2.1.1
From: jp Jamous
Date: Apr 22, 2022 9:19AM
- Next message: Mike Warner: "Re: enter key to check radio button?"
- Previous message: Mark Magennis: "Re: When to use WCAG 2.4.3and WCAG 2.1.1"
- Next message in Thread: None
- Previous message in Thread: Mark Magennis: "Re: When to use WCAG 2.4.3and WCAG 2.1.1"
- View all messages in this Thread
Mark,
You are correct about this. However, I did not want to complicate things. I wanted to keep them simple.
On another note, it is best to have the same approach with inclusive design rather than using 2 different approaches. While this may not always be possible, it is best to lean toward inclusivity so the user experience is the same. This can be quite beneficial for UX Designers when applying accessibility to their designs. They typically don't like to have 2 separate ways of doing things.
I try to keep my responses simple. It is easy to get into a rabbit hole with WCAG. Different cases require different approaches. ð
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Mark Magennis
Sent: Friday, April 22, 2022 10:02 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: When to use WCAG 2.4.3and WCAG 2.1.1
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
External ( <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >)
INKY is learning...<https://protection.inkyphishfence.com/report?id=bmV0b3JnZnQxMDM2OTU1NC9qcEBqZXBlbHN5LmNvbS9iNDY2NGM0MDc4ODk5NDU3NjEzOWEzMWQxZmE5MDZkZi8xNjUwNjM5NzA2LjI3#keyq960b67c2cfaa648b8686a3ae4ea2d5> Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnZnQxMDM2OTU1NC9qcEBqZXBlbHN5LmNvbS9iNDY2NGM0MDc4ODk5NDU3NjEzOWEzMWQxZmE5MDZkZi8xNjUwNjM5NzA2LjI3#keyq960b67c2cfaa648b8686a3ae4ea2d5> FAQ<https://www.inky.com/banner-faq> GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>
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
- Next message: Mike Warner: "Re: enter key to check radio button?"
- Previous message: Mark Magennis: "Re: When to use WCAG 2.4.3and WCAG 2.1.1"
- Next message in Thread: None
- Previous message in Thread: Mark Magennis: "Re: When to use WCAG 2.4.3and WCAG 2.1.1"
- View all messages in this Thread