E-mail List Archives
Re: WCAG 2.1 - 1.3.5 - How to capture a violation?
From: Jared Smith
Date: Jul 29, 2018 5:34PM
- Next message: John Foliot: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Birkir R. Gunnarsson: "Re: Web: Examining True Font Size With Screen Reader"
- Next message in Thread: John Foliot: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: John Foliot: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread
Jon and John -
I agree with both of you. Your explanations have helped me better see
how this will be useful for accessibility in the future and why it
should be advocated for today. I do still find the language of the
success criterion a bit troublesome and I think it could be a bit of a
hard sell to authors in cases where they can't associate adding
@autocomplete with any clear user benefit *today*, but perhaps there
will soon be new or better assistive technologies that will further
utilize this to greatly improve form completion for users with
cognitive and learning disabilities.
Thanks,
Jared
- Next message: John Foliot: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Birkir R. Gunnarsson: "Re: Web: Examining True Font Size With Screen Reader"
- Next message in Thread: John Foliot: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: John Foliot: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread