W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2016

RE: WCAG 2.0 - A progressive approach to Website Accessibility

From: Herin Hentry <hhentry@planittesting.com>
Date: Mon, 15 Aug 2016 03:56:37 +0000
To: "Steinberg,Richard (HHSC)" <Richard.Steinberg@hhsc.state.tx.us>, "WAI Interest Group" <w3c-wai-ig@w3.org>, Shawn Henry <shawn@w3.org>, "shadi@w3.org" <shadi@w3.org>
Message-ID: <HK2PR01MB091670D65240D630E2BD231BB9120@HK2PR01MB0916.apcprd01.prod.exchangelabs.com>
Thank you Richard for your feedback.

Herin Hentry
Senior Test Analyst

Planit
Main: +61 2 9464 0600
Dir: +61 2 9464 0614
Mob: +61 431 030 071
Email: hhentry@planittesting.com<mailto:hhentry@planittesting.com>
Web: www.planittesting.com<http://www.planittesting.com>

152 Gloucester St, Sydney NSW 2000
From: Steinberg,Richard (HHSC) [mailto:Richard.Steinberg@hhsc.state.tx.us]
Sent: Tuesday, 2 August 2016 12:55 AM
To: Herin Hentry <hhentry@planittesting.com>; WAI Interest Group <w3c-wai-ig@w3.org>; Shawn Henry <shawn@w3.org>; shadi@w3.org
Subject: RE: WCAG 2.0 - A progressive approach to Website Accessibility

I like your approach and enjoyed your article. In working with developers and UAT testers who know only the basics about accessibility, I have found it helpful to them to point out the parts of WCAG 2.0 that apply to the particular applications they are working on at the time. To help, I began working on a decision tree of sorts. If the application has certain elements, then pay attention to particular parts of WCAG 2.0. For example, most of our applications don't have any animations, audio, or video.

There are probably some in the accessibility community who would disagree with this, but I am trying to enforce compliance without many resources. And there is always apathy--threats of possible lawsuits and "doing the right thing" don't always seem to work with some people.

I also have situations in which developers want to install JAWS and use it as a test tool for a couple hours a week without any training, but I have to explain that it wasn't designed as a test tool per se and the learning curve is a bit steeper than that.

Richard Steinberg
Accessibility Coordinator for Electronic Information Resources
Texas Department of State Health Services
1100 W 49th St., Tower Building, Room 103.00
512-776-2913




From: Herin Hentry [mailto:hhentry@planittesting.com]
Sent: Saturday, July 30, 2016 12:33 AM
To: WAI Interest Group; Shawn Henry; shadi@w3.org<mailto:shadi@w3.org>
Subject: WCAG 2.0 - A progressive approach to Website Accessibility


Hello everyone at WAI Interest group,



I have been working on an easy learning + development strategy for WCAG 2.0 and have published an article in LinkedIn. It would be a great help if this group can review this article and provide me feedbacks.



http://www.linkedin.com/pulse/wcag-scary-anymore-progressive-approach-website-herin-hentry?trk=pulse_spock-articles

I would like to work with W3C working group on similar strategies and plans. Can someone please advise what's the procedure for applying to be part of such working group and if we have any group working on this?



Thank you,

Herin Hentry

Web Accessibility Consultant, Planit Software Testing
Received on Monday, 15 August 2016 03:57:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 15 August 2016 03:57:15 UTC