Commitment to those of us who use AT

Bevi,

I liked your statement “What’s happened to our commitment to those of us who use assistive technologies”.

I sent out an email to the WCAG group asking:
“Team,
Since we put so much effort into WCAG 2.1, much from a theoretical and experiential viewpoint of those on the various taskforces, is there any effort to have actual users with disabilities who may be attending CSUN queried on whether the new SCs in WCAG 2.1 will in fact meet the needs of those they are intended for?
This seems like a perfect opportunity to get actual user feedback on this effort.
Best. “

Only a few replied and the answer was “NO”.

I’m disappointed in that reply. 

Alan Smith

From: chagnon@pubcom.com
Sent: Friday, March 2, 2018 3:27 AM
To: w3c-wai-ig@w3.org
Subject: RE: WCAG vialations or accessibility enhancements

I’m just a lurker on this list, but I’m a member on other accessibility standards committees.

This issue of non-sequential (or out-of-order) headings has become a heated debate everywhere and I believe it’s a terrible trend. It certainly violates, in principal, the concept of making digital media accessible to people.

Writing, editing, publishing — regardless of the media that delivers it — has always stressed a logical hierarchy of headings and that theory has worked well over the past 100 years of communication. It’s called good writing.

I don’t understand what has brought about this change in thought on all the standards committees, that it’s OK to jump from H2 to H5. 

It is not ok. It harms many people who use assistive technologies.

What’s happened to our commitment to those of us who use assistive technologies, who depend upon them? Does the community’s needs no longer have any merit? During the past couple of years, those of us on standards committees seem to have put the cart before the horse.

Our standards are developed for people who use technology — not for the computers or technologies that deliver the content. Otherwise, we are just wasting our time developing any accessibility standards at all.

Peoples’ need first. Then it’s the software engineers’ job to make their technology meet those needs.

—Bevi Chagnon

— — —
Bevi Chagnon, founder/CEO  |  Bevi@PubCom.com 
— — —
PubCom: Technologists for Accessible Design + Publishing
consulting • training • development • design • sec. 508 services
Upcoming classes at www.PubCom.com/classes
— — —