E-mail List Archives
Re: WCAG 2.1 - 1.3.5 - How to capture a violation?
From: chagnon
Date: Jul 27, 2018 9:24AM
- Next message: chagnon@pubcom.com: "Re: en-dash, dash and minus"
- Previous message: Jonathan Cohn: "Re: en-dash, dash and minus"
- Next message in Thread: Karlen Communications: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: Jared Smith: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread
Agee with Jared, quoted below:
" It favors the machine over the human, and does so by burdening human
authors. "
Which nimrod turned accessibility around to now make machines happy, rather
than the people who use machines? Is this why we're all here?
Flip around the focus: we should figure out how to make content work better
for people, and then program the machines to provide the content in the way
it's needed.
Accessibility is for people, not for machines.
--Bevi Chagnon
- - -
Bevi Chagnon, founder/CEO | <EMAIL REMOVED>
- - -
PubCom: Technologists for Accessible Design + Publishing
consulting . training . development . design . sec. 508 services
Upcoming classes at www.PubCom.com/classes
- - -
Latest blog-newsletter - Accessibility Tips
- Next message: chagnon@pubcom.com: "Re: en-dash, dash and minus"
- Previous message: Jonathan Cohn: "Re: en-dash, dash and minus"
- Next message in Thread: Karlen Communications: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: Jared Smith: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread