E-mail List Archives
Re: WCAG 2.1 - 1.3.5 - How to capture a violation?
From: Jonathan Avila
Date: Jul 25, 2018 6:30AM
- Next message: Jared Smith: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Lovely, Brian: "Re: [External Sender] WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Next message in Thread: Jared Smith: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: Lovely, Brian: "Re: [External Sender] WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread
At this time it is my understanding that the autocomplete attribute is the only sufficient technique for HTML.
So you could use a favlet such as the one I made at the following page (https://labs.levelaccess.com/index.php/Autocomplete_Attribute_Favlet) to display the autofill attributes. You would need to manually determine if the field needs to have it's purpose communicated programmatically and then if the right autocomplete attribute is used. The accessible name cannot be used to communicate the purpose.
1. Determine if field is related to information for the the user rather than other users or non-user information. Only information about the user is covered.
2. Determine if the purpose is listed in WCAG section 7 input purpose (https://www.w3.org/TR/WCAG21/#input-purposes)
3. Review the autocomplete attribute if one exists and determine if it is appropriate from the list above.
Jonathan
- Next message: Jared Smith: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Lovely, Brian: "Re: [External Sender] WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Next message in Thread: Jared Smith: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: Lovely, Brian: "Re: [External Sender] WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread