WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: for Chrome devs: intro to accessibility course

for

From: Birkir R. Gunnarsson
Date: Sep 11, 2013 10:18AM

HI Olaf

Oh, I perfectly agree with you, and in all my testing and evaluations
I put great emphasis on making sure I am not a screen reader tester.
The market for accessibility is huge, everybody experiences visual
impairment, hearing impairment and various cognitive issues (small
device, noisy environment, multi tasking/cognitive overload),
especially on mobile devices, so making a website that works for
everybody is the goal.
My pointing out the screen reader difference had only to do with the
screen reader emphasis of the course and discussion, and my assumption
(at lesat hope) is that Google will launch other courses focused on
other types of disabilities and usability issues.


On 9/11/13, Olaf Drümmer < <EMAIL REMOVED> > wrote:
> So given the exclusive focus on visually impaired user using a screen reader
> is a bit narrow, when all types of other disabilities and non screen reader
> AT are left out - how can it matter whether ChromeVox is used instead of
> NVDA/VoiceOver/JAWS/... and at the same it does not matter that other types
> of disability and other types of AT are not even thought of?
>
> Aren't we all still blind [pun intended] to disabilities and AT beyond the
> blind user/screen reader combo?
>
> To me, this is like arguing about what is the best car stereo model while
> ignoring the car's wheels are still missing.
>
> Olaf
>
>
> Am 11 Sep 2013 um 17:09 schrieb Birkir R. Gunnarsson
> < <EMAIL REMOVED> >:
>
>> Just remember that Chrome Vox use, as reported by the latest WebAIM
>> screen reader survey, was less then .5%, Voiceover around 12%, NVDA
>> around 14% and Jaws still in the 50% range.
>> As long as screen readers and standards play nice (and there is
>> consistency regarding the interpretation and support of standards)
>> this should not matter too much, but when screen reading applications
>> support standards partially, or come up with their own set of rules
>> and best practices, people need to at least be aware of the fact that
>> if they test with a screen reader with very small userbase and that
>> has its own take on how to most accessibly acquire and communicate
>> info, this could lead to a lot of frustration and inconsistencies in
>> how the developer experiences problems and how the users do. So from
>> that perspective, NVDA would be a lot more useful than Chrome Vox
>> (this is just a general statement, I have not tried using Chrome Vox
>> myself, it is on my ever-lengthening to-do list).
>> I am curious to see what the Google accessibility course will be like
>> and, moreover, if the course is accessible to a screen reader user (it
>> better be, else that would be embarrassing for them to say the least).
>> Cheers
>> -Birkir
>> Birkir Gunnarsson
>> Accessibility Subject Matter Expert | Deque Systems
>>
>>
>>
>>
>> On 9/11/13, Alastair Campbell < <EMAIL REMOVED> > wrote:
>>> Cameron wrote:
>>>> it is a black box with regards to its API
>>>
>>> There is an accessibility inspector that's part of Xcode, if you are on
>>> the
>>> OSX development programme thingy. I assume that would show you the
>>> attributes in the tables Steve mentioned.
>>>
>>> -Alastair
>>> >>> >>> >>>
>> >> >> >
> > > >