E-mail List Archives
Re: for Chrome devs: intro to accessibility course
From: Birkir R. Gunnarsson
Date: Sep 11, 2013 9:09AM
- Next message: Cameron Cundiff: "Re: for Chrome devs: intro to accessibility course"
- Previous message: Alastair Campbell: "Re: for Chrome devs: intro to accessibility course"
- Next message in Thread: Cameron Cundiff: "Re: for Chrome devs: intro to accessibility course"
- Previous message in Thread: Alastair Campbell: "Re: for Chrome devs: intro to accessibility course"
- View all messages in this Thread
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
> > > >
- Next message: Cameron Cundiff: "Re: for Chrome devs: intro to accessibility course"
- Previous message: Alastair Campbell: "Re: for Chrome devs: intro to accessibility course"
- Next message in Thread: Cameron Cundiff: "Re: for Chrome devs: intro to accessibility course"
- Previous message in Thread: Alastair Campbell: "Re: for Chrome devs: intro to accessibility course"
- View all messages in this Thread