W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2018

Re: WCAG vialations or accessibility enhancements

From: Srinivasu Chakravarthula <lists@srinivasu.org>
Date: Fri, 2 Mar 2018 14:24:39 +0530
Message-ID: <CAFHrfbyxNfsYfThJ+b+kkp7togFjdRQW-Ebwm8MCQB=t8ebRwQ@mail.gmail.com>
To: chagnon@pubcom.com
Cc: w3c WAI List <w3c-wai-ig@w3.org>
Very well said! Thank you...

Regards,

Srinivasu Chakravarthula - Twitter: http://twitter.com/CSrinivasu/
Website: http://www.srinivasu.org | http://serveominclusion.com

Let's create an inclusive web!

Lead Accessibility Consultant, Informatica


On Fri, Mar 2, 2018 at 1:42 PM, <chagnon@pubcom.com> wrote:

> 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
>
> *— — —*
>
>
>
Received on Friday, 2 March 2018 08:55:46 UTC

This archive was generated by hypermail 2.3.1 : Friday, 2 March 2018 08:55:48 UTC