WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: The Accessibility of Browser-based Development Environments

for

From: Birkir R. Gunnarsson
Date: Aug 2, 2017 7:06PM

I got back in touch with my Chrome contacts. They have been working to
make Chrome development tools accessible for some time now, with help
from some pretty high class experts.

Progress has been frustratingly slow though and progress in Chrome 60
is still only marginal.
So I am going to try and turn up the Twitter heat on those folks and
hope Chrome dev tools are on the way to becoming accessible.
Someone needs to write an article for BATS on using FF49 dev tools
with a screen reader.
IN fact, we need to re ignite BATS. After getting a new job last year
I have simply not been able to give it the attention it needs to keep
growing.
I can't say I see much slowdown on the horizon but I still need to
find a way to carve out time.
Anyone who wants to contribute articles, please get in touch.
http://www.bats.fyi



On 8/1/17, Jim Homme < <EMAIL REMOVED> > wrote:
> Hi Nick,
> Do you think it would be OK with him to tell me his story? I'm going down
> the path of learning web development so I can understand web accessibility
> both from a screen reader, user, dangerous coding perspective, and, someday,
> from a real developer sperspective, as someone who actually knows how to
> make sites and applications.
>
> Thanks.
>
> Jim
>
> =========> Jim Homme,
> Team Lead and Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> <EMAIL REMOVED>
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>
> From: Beranek, Nicholas via
> WebAIM-Forum<mailto: <EMAIL REMOVED> >
> Sent: Tuesday, August 1, 2017 9:47 AM
> To: WebAIM Discussion List<mailto: <EMAIL REMOVED> >
> Subject: Re: [WebAIM] The Accessibility of Browser-based Development
> Environments
>
> One of my colleagues really enjoys the accessibility improvements that
> Firefox has made to its developer tools. He uses NVDA with it. He says that
> they are very close to being made fully accessible, but he is able to
> inspect code.
>
> Nick
>
>