WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen readers usage and support

for

From: Ryan Hemphill
Date: Mar 6, 2012 6:30PM

I'm with Bryan on this 100%. One of the best descriptions of
appropriate a11y strategy is provided by Derek Featherstone, who talks
about the layers of accessibility as a stack.

At the bottom of the stack is HTML, then CSS, then JavaScript, and
finally ARIA. His argument, which is right about 95% of the time, is
that you should be trying to keep your accessibility solutions as low
in the stack as possible and only resort to the next layer when you
have assessed that it is truly required. Point being, stick to basics
and get everything out of each level before you start addressing the
next one - assuming you need to at all.

As far as addressing the needs of multiple groups, this can be a
struggle and I would suggest that you try to review as much of your
508 rules and who it affects before you start building your strategy.
Figuring out what you need to do as a whole can save you a lot of
time, money and bandwidth.

Feel free to reach out when you need a review. I'm sure the group
will respond and help out when we have a better idea of what your
needs are.

Ryan

On 3/6/12, Bryan Garaventa < <EMAIL REMOVED> > wrote:
> I have to say that this is only true when ARIA is viewed as a 'catch all'
> solution, which it isn't.
>
> ARIA should only be added after full keyboard support is already built into
> the feature or application. I agree that the general discussions often focus
> on screen reader support as being the top priority, but ensuring keyboard
> support before adding ARIA will accomplish both.
>
>
> ----- Original Message -----
> From: "Ryan Hemphill" < <EMAIL REMOVED> >
> To: "WebAIM Discussion List" < <EMAIL REMOVED> >
> Sent: Tuesday, March 06, 2012 12:37 PM
> Subject: Re: [WebAIM] Screen readers usage and support
>
>
>> I'd also like to point out that many people coding out there do not
>> realize
>> that ARIA only takes care of Screen Reader users. While this is not part
>> of 508 compliance at all, it has been a general trend in accessibility
>> focus with regard to online research and blogging.
>>
>> Simply put, many supposedly accessible solutions are really not taking of
>> of anyone else except blind users. I'm just backing up Gary's point here.
>> It's very easy to find the accessibility rules for the blind, but it's
>> only a piece of the pie.
>>
>> Ryan
>>
>> On Tue, Mar 6, 2012 at 3:22 PM, Morin, Gary (NIH/OD) [E] <
>> <EMAIL REMOVED> > wrote:
>>
>>> Keep in mind the following
>>> 1. EIT products conform to Section 508
>>> 2. Federal agencies comply (or not) with Section 508
>>> 3. JAWS or any screen reader-compatible software does not equal
>>> Section 508 conformant nor does it equal accessible to oh so many other
>>> people with other disabilities.
>>> 4. Accessible does not always equal Section 508-conformant
>>> 5. Section 508-conformant does not always equal accessible (except
>>> when the Functional Performance Criteria are taken seriously)
>>> 6. Accessible for a (fill in the blank) does not necessarily mean
>>> Accessible for any other (fill in the blank) - using either disabilities
>>> for each blank or assistive technologies for each blank.
>>> Is your Assistive Technology testing being done by real-life users of
>>> that
>>> AT or by non-disabled users who really aren't fluent in the AT?
>>> Is your Assistive Technology testing being done in addition to manual
>>> testing based on the formal Section 508 standards from the US Access
>>> Board?
>>> What company are you with?
>>> Gary M. Morin, Program Analyst
>>>
>>> WHAT IF THE FIRST QUESTION WE ASKED WAS, "WHAT IS SO UNIQUE ABOUT THIS
>>> SITUATION THAT IT JUSTIFIES EXCLUSION? INSTEAD OF, "HOW MUCH DOES IT COST
>>> TO MAKE IT ACCESSIBLE?"
>>>
>>>