E-mail List Archives
Re: WCAG 2.1 - 1.3.5 - How to capture a violation?
From: Jeremy Echols
Date: Jul 27, 2018 12:51PM
- Next message: Jared Smith: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Karlen Communications: "Re: 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: Karlen Communications: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread
As a developer, I find this burdensome, but it also makes a great deal of sense. If somebody has a form input labeled "Last Name", sure, that's pretty clear. But sometimes you'll see something like "Enter your surname" or "What is your last name / surname?". I can figure this out. Most people I know can figure it out. But inclusive design should never be about what "most" people can figure out.
For people who already have cognitive challenges like dyslexia, I can see a huge benefit in using a machine-friendly taxonomy that can map to unambiguous terms.
- Next message: Jared Smith: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Karlen Communications: "Re: 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: Karlen Communications: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread