E-mail List Archives
WCAG 2.1 - 1.3.5 - How to capture a violation?
From: pratik roy
Date: Jul 25, 2018 3:13AM
- Next message: Lovely, Brian: "Re: [External Sender] WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: glen walker: "Re: no alt-text: lesser of two evils?"
- Next message in Thread: Lovely, Brian: "Re: [External Sender] WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: None
- View all messages in this Thread
Hi Everyone,
WCAG introduced this new guideline a part of there 2.1 release to provide
more purpose to the input fields. But my question is, how can we capture a
violation against this guideline? Beacuse currently there is on faliure
technique provided by WCAG.Although, there is a sufficient technique which
talks about use of auto-fill attributes in input fields.
But can we capture a violation if that sufficient technique is not followed
in a scenario?
Example: In a form, suppose we have two password fields one for current and
other one for new password. Purposeful label is provided for both but no
auto-fill="{current-password | new-password}". Now the question is, can we
capture a violation here?
Please share your thoughts.
Thanks & Regards
PRATIK ROY
- Next message: Lovely, Brian: "Re: [External Sender] WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: glen walker: "Re: no alt-text: lesser of two evils?"
- Next message in Thread: Lovely, Brian: "Re: [External Sender] WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: None
- View all messages in this Thread