E-mail List Archives

Thread: The Accessibility of Browser-based Development Environments

for

Number of posts in this thread: 15 (In chronological order)

From: Jim Homme
Date: Tue, Aug 01 2017 6:52AM
Subject: The Accessibility of Browser-based Development Environments
No previous message | Next message →

Hi,
I know that extensive work was done to make Firebug accessible. I thought I read that that work was brought into FFirefox itself. This prompted me to want to see if anyone who is blind here has either good experiences with the development tools in either the newest Firefox, the newest IE, Edge, or Chrome. I’m also wondering how Google is doing with Chrome accessibility in general, and how the screen reader venders are doing with closing the gap from their side, since Chrome seems to be very popular among sighted vendors.

Thanks.

Jim

=========Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
= EMAIL ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

From: Brandon Keith Biggs
Date: Tue, Aug 01 2017 7:15AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

Hello,
I use the console on Firefox and that is it. Other than that, I really love
the debugging tools for React. create-react-app is fantastic.
Thanks,


Brandon Keith Biggs <http://brandonkeithbiggs.com/>;

On Tue, Aug 1, 2017 at 5:52 AM, Jim Homme < = EMAIL ADDRESS REMOVED = > wrote:

> Hi,
> I know that extensive work was done to make Firebug accessible. I thought
> I read that that work was brought into FFirefox itself. This prompted me to
> want to see if anyone who is blind here has either good experiences with
> the development tools in either the newest Firefox, the newest IE, Edge, or
> Chrome. I’m also wondering how Google is doing with Chrome accessibility in
> general, and how the screen reader venders are doing with closing the gap
> from their side, since Chrome seems to be very popular among sighted
> vendors.
>
> Thanks.
>
> Jim
>
> =========> Jim Homme,
> Team Lead and Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> = EMAIL ADDRESS REMOVED =
> http://www.benderconsult.com/our%20services/hightest-
> accessible-technology-solutions
> E+R=O
>
> > > > >

From: Beranek, Nicholas
Date: Tue, Aug 01 2017 7:47AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

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

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jim Homme
Sent: Tuesday, August 01, 2017 8:52 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] The Accessibility of Browser-based Development Environments

Hi,
I know that extensive work was done to make Firebug accessible. I thought I read that that work was brought into FFirefox itself. This prompted me to want to see if anyone who is blind here has either good experiences with the development tools in either the newest Firefox, the newest IE, Edge, or Chrome. I’m also wondering how Google is doing with Chrome accessibility in general, and how the screen reader venders are doing with closing the gap from their side, since Chrome seems to be very popular among sighted vendors.

Thanks.

Jim

=========Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
= EMAIL ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

From: Jim Homme
Date: Tue, Aug 01 2017 12:49PM
Subject: Re: The Accessibility of Browser-based DevelopmentEnvironments
← Previous message | Next message →

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 ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

From: Beranek, Nicholas via WebAIM-Forum<mailto: = EMAIL ADDRESS REMOVED = >
Sent: Tuesday, August 1, 2017 9:47 AM
To: WebAIM Discussion List<mailto: = EMAIL ADDRESS 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

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jim Homme
Sent: Tuesday, August 01, 2017 8:52 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] The Accessibility of Browser-based Development Environments

Hi,
I know that extensive work was done to make Firebug accessible. I thought I read that that work was brought into FFirefox itself. This prompted me to want to see if anyone who is blind here has either good experiences with the development tools in either the newest Firefox, the newest IE, Edge, or Chrome. I’m also wondering how Google is doing with Chrome accessibility in general, and how the screen reader venders are doing with closing the gap from their side, since Chrome seems to be very popular among sighted vendors.

Thanks.

Jim

=========Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
= EMAIL ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

From: Birkir R. Gunnarsson
Date: Wed, Aug 02 2017 7:06PM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

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 ADDRESS 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 ADDRESS REMOVED =
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>
> From: Beranek, Nicholas via
> WebAIM-Forum<mailto: = EMAIL ADDRESS REMOVED = >
> Sent: Tuesday, August 1, 2017 9:47 AM
> To: WebAIM Discussion List<mailto: = EMAIL ADDRESS 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
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Jim Homme
> Sent: Tuesday, August 01, 2017 8:52 AM
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Subject: [WebAIM] The Accessibility of Browser-based Development
> Environments
>
> Hi,
> I know that extensive work was done to make Firebug accessible. I thought I
> read that that work was brought into FFirefox itself. This prompted me to
> want to see if anyone who is blind here has either good experiences with the
> development tools in either the newest Firefox, the newest IE, Edge, or
> Chrome. I’m also wondering how Google is doing with Chrome accessibility in
> general, and how the screen reader venders are doing with closing the gap
> from their side, since Chrome seems to be very popular among sighted
> vendors.
>
> Thanks.
>
> Jim
>
> =========> Jim Homme,
> Team Lead and Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> = EMAIL ADDRESS REMOVED =
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>
> > > http://webaim.org/discussion/archives
> > >
> The information contained in this e-mail is confidential and/or proprietary
> to Capital One and/or its affiliates and may only be used solely in
> performance of work or services for Capital One. The information transmitted
> herewith is intended only for use by the individual or entity to which it is
> addressed. If the reader of this message is not the intended recipient, you
> are hereby notified that any review, retransmission, dissemination,
> distribution, copying or other use of, or taking of any action in reliance
> upon this information is strictly prohibited. If you have received this
> communication in error, please contact the sender and delete the material
> from your computer.
> > > > >
> > > > >


--
Work hard. Have fun. Make history.

From: Srinivasu Chakravarthula
Date: Thu, Aug 03 2017 2:02AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

I know my former colleague at Yahoo, Victor Tsaran (@VTsaran on Twitter)
writes a lot of code; am not sure if he is on this list; but he may be of
some help.

Regards,

Srinivasu Chakravarthula - Twitter: http://twitter.com/CSrinivasu/
Website: http://www.srinivasu.org | http://serveominclusion.com

Let's create an inclusive web!

Lead Accessibility Consultant, Informatica


On Thu, Aug 3, 2017 at 6:36 AM, Birkir R. Gunnarsson <
= EMAIL ADDRESS REMOVED = > wrote:

> 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 ADDRESS 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 ADDRESS REMOVED =
> > http://www.benderconsult.com/our%20services/hightest-
> accessible-technology-solutions
> > E+R=O
> >
> > From: Beranek, Nicholas via
> > WebAIM-Forum<mailto: = EMAIL ADDRESS REMOVED = >
> > Sent: Tuesday, August 1, 2017 9:47 AM
> > To: WebAIM Discussion List<mailto: = EMAIL ADDRESS 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
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> Behalf
> > Of Jim Homme
> > Sent: Tuesday, August 01, 2017 8:52 AM
> > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > Subject: [WebAIM] The Accessibility of Browser-based Development
> > Environments
> >
> > Hi,
> > I know that extensive work was done to make Firebug accessible. I
> thought I
> > read that that work was brought into FFirefox itself. This prompted me to
> > want to see if anyone who is blind here has either good experiences with
> the
> > development tools in either the newest Firefox, the newest IE, Edge, or
> > Chrome. I’m also wondering how Google is doing with Chrome accessibility
> in
> > general, and how the screen reader venders are doing with closing the gap
> > from their side, since Chrome seems to be very popular among sighted
> > vendors.
> >
> > Thanks.
> >
> > Jim
> >
> > =========> > Jim Homme,
> > Team Lead and Accessibility Consultant,
> > Bender HighTest Accessibility Team
> > Bender Consulting Services, Inc.,
> > 412-787-8567,
> > = EMAIL ADDRESS REMOVED =
> > http://www.benderconsult.com/our%20services/hightest-
> accessible-technology-solutions
> > E+R=O
> >
> > > > > archives at
> > http://webaim.org/discussion/archives
> > > > > >
> > The information contained in this e-mail is confidential and/or
> proprietary
> > to Capital One and/or its affiliates and may only be used solely in
> > performance of work or services for Capital One. The information
> transmitted
> > herewith is intended only for use by the individual or entity to which
> it is
> > addressed. If the reader of this message is not the intended recipient,
> you
> > are hereby notified that any review, retransmission, dissemination,
> > distribution, copying or other use of, or taking of any action in
> reliance
> > upon this information is strictly prohibited. If you have received this
> > communication in error, please contact the sender and delete the material
> > from your computer.
> > > > > > > > > >
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >

From: Yura Zenevich
Date: Thu, Aug 03 2017 7:23AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

Hi all (first time poster). I help out with Firefox DevTools accessibility
and indeed we landed improvements to markup inspector some time last year.
We also made overall keyboard accessibility somewhat better. Though this
year has been slower, we have a commitment to a high bar for Firefox
DevTools accessibility this and next year. Later this year we are planning
on releasing Accessible tree inspector as part of our DevTools, for
example. Expect to see a lot more next year!
yura

On Tue, Aug 1, 2017 at 9:47 AM, Beranek, Nicholas via WebAIM-Forum <
= EMAIL ADDRESS REMOVED = > wrote:

> 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
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> Behalf Of Jim Homme
> Sent: Tuesday, August 01, 2017 8:52 AM
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Subject: [WebAIM] The Accessibility of Browser-based Development
> Environments
>
> Hi,
> I know that extensive work was done to make Firebug accessible. I thought
> I read that that work was brought into FFirefox itself. This prompted me to
> want to see if anyone who is blind here has either good experiences with
> the development tools in either the newest Firefox, the newest IE, Edge, or
> Chrome. I’m also wondering how Google is doing with Chrome accessibility in
> general, and how the screen reader venders are doing with closing the gap
> from their side, since Chrome seems to be very popular among sighted
> vendors.
>
> Thanks.
>
> Jim
>
> =========> Jim Homme,
> Team Lead and Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> = EMAIL ADDRESS REMOVED =
> http://www.benderconsult.com/our%20services/hightest-
> accessible-technology-solutions
> E+R=O
>
> > > at http://webaim.org/discussion/archives
> > >
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The information
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
> > > > >

From: Jonathan Cohn
Date: Thu, Aug 03 2017 8:20AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

Having an accessible tree inspector would be of great advantage to my
sighted co-workers who are not very comfortable with a screen reader. Right
now they have to rely on my presence to check if what they did had any
effect.

Is there a way to encourage this work?

Thanks,

Jonathan Cohn

On Thu, Aug 3, 2017 at 9:24 AM Yura Zenevich < = EMAIL ADDRESS REMOVED = > wrote:

> Hi all (first time poster). I help out with Firefox DevTools accessibility
> and indeed we landed improvements to markup inspector some time last year.
> We also made overall keyboard accessibility somewhat better. Though this
> year has been slower, we have a commitment to a high bar for Firefox
> DevTools accessibility this and next year. Later this year we are planning
> on releasing Accessible tree inspector as part of our DevTools, for
> example. Expect to see a lot more next year!
> yura
>
> On Tue, Aug 1, 2017 at 9:47 AM, Beranek, Nicholas via WebAIM-Forum <
> = EMAIL ADDRESS REMOVED = > wrote:
>
> > 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
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> > Behalf Of Jim Homme
> > Sent: Tuesday, August 01, 2017 8:52 AM
> > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > Subject: [WebAIM] The Accessibility of Browser-based Development
> > Environments
> >
> > Hi,
> > I know that extensive work was done to make Firebug accessible. I thought
> > I read that that work was brought into FFirefox itself. This prompted me
> to
> > want to see if anyone who is blind here has either good experiences with
> > the development tools in either the newest Firefox, the newest IE, Edge,
> or
> > Chrome. I’m also wondering how Google is doing with Chrome accessibility
> in
> > general, and how the screen reader venders are doing with closing the gap
> > from their side, since Chrome seems to be very popular among sighted
> > vendors.
> >
> > Thanks.
> >
> > Jim
> >
> > =========> > Jim Homme,
> > Team Lead and Accessibility Consultant,
> > Bender HighTest Accessibility Team
> > Bender Consulting Services, Inc.,
> > 412-787-8567 <(412)%20787-8567>,
> > = EMAIL ADDRESS REMOVED =
> > http://www.benderconsult.com/our%20services/hightest-
> > accessible-technology-solutions
> > E+R=O
> >
> > > > > > at http://webaim.org/discussion/archives
> > > > > >
> > The information contained in this e-mail is confidential and/or
> > proprietary to Capital One and/or its affiliates and may only be used
> > solely in performance of work or services for Capital One. The
> information
> > transmitted herewith is intended only for use by the individual or entity
> > to which it is addressed. If the reader of this message is not the
> intended
> > recipient, you are hereby notified that any review, retransmission,
> > dissemination, distribution, copying or other use of, or taking of any
> > action in reliance upon this information is strictly prohibited. If you
> > have received this communication in error, please contact the sender and
> > delete the material from your computer.
> > > > > > > > > >
> > > > >

From: Yura Zenevich
Date: Thu, Aug 03 2017 8:44AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

This work is starting to being reviewed and landing in Firefox Nightly very
shortly - https://bugzilla.mozilla.org/show_bug.cgi?id51468
cheers,
yura


On Thu, Aug 3, 2017 at 10:20 AM, Jonathan Cohn < = EMAIL ADDRESS REMOVED = > wrote:

> Having an accessible tree inspector would be of great advantage to my
> sighted co-workers who are not very comfortable with a screen reader. Right
> now they have to rely on my presence to check if what they did had any
> effect.
>
> Is there a way to encourage this work?
>
> Thanks,
>
> Jonathan Cohn
>
> On Thu, Aug 3, 2017 at 9:24 AM Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> wrote:
>
> > Hi all (first time poster). I help out with Firefox DevTools
> accessibility
> > and indeed we landed improvements to markup inspector some time last
> year.
> > We also made overall keyboard accessibility somewhat better. Though this
> > year has been slower, we have a commitment to a high bar for Firefox
> > DevTools accessibility this and next year. Later this year we are
> planning
> > on releasing Accessible tree inspector as part of our DevTools, for
> > example. Expect to see a lot more next year!
> > yura
> >
> > On Tue, Aug 1, 2017 at 9:47 AM, Beranek, Nicholas via WebAIM-Forum <
> > = EMAIL ADDRESS REMOVED = > wrote:
> >
> > > 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
> > >
> > > -----Original Message-----
> > > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> > > Behalf Of Jim Homme
> > > Sent: Tuesday, August 01, 2017 8:52 AM
> > > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > > Subject: [WebAIM] The Accessibility of Browser-based Development
> > > Environments
> > >
> > > Hi,
> > > I know that extensive work was done to make Firebug accessible. I
> thought
> > > I read that that work was brought into FFirefox itself. This prompted
> me
> > to
> > > want to see if anyone who is blind here has either good experiences
> with
> > > the development tools in either the newest Firefox, the newest IE,
> Edge,
> > or
> > > Chrome. I’m also wondering how Google is doing with Chrome
> accessibility
> > in
> > > general, and how the screen reader venders are doing with closing the
> gap
> > > from their side, since Chrome seems to be very popular among sighted
> > > vendors.
> > >
> > > Thanks.
> > >
> > > Jim
> > >
> > > =========> > > Jim Homme,
> > > Team Lead and Accessibility Consultant,
> > > Bender HighTest Accessibility Team
> > > Bender Consulting Services, Inc.,
> > > 412-787-8567 <(412)%20787-8567>,
> > > = EMAIL ADDRESS REMOVED =
> > > http://www.benderconsult.com/our%20services/hightest-
> > > accessible-technology-solutions
> > > E+R=O
> > >
> > > > > > > archives
> > > at http://webaim.org/discussion/archives
> > > > > > > > >
> > > The information contained in this e-mail is confidential and/or
> > > proprietary to Capital One and/or its affiliates and may only be used
> > > solely in performance of work or services for Capital One. The
> > information
> > > transmitted herewith is intended only for use by the individual or
> entity
> > > to which it is addressed. If the reader of this message is not the
> > intended
> > > recipient, you are hereby notified that any review, retransmission,
> > > dissemination, distribution, copying or other use of, or taking of any
> > > action in reliance upon this information is strictly prohibited. If you
> > > have received this communication in error, please contact the sender
> and
> > > delete the material from your computer.
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >

From: Lucy Greco
Date: Thu, Aug 03 2017 2:53PM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

hey Birkir thanks for the plug man a couple of us of them working on
videos but had kept failing at completing them real jobs get in the way of
bats definitely. We would really like to have that Firefox dev tools
article as soon as possible thanks Lucy

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Thu, Aug 3, 2017 at 7:44 AM, Yura Zenevich < = EMAIL ADDRESS REMOVED = > wrote:

> This work is starting to being reviewed and landing in Firefox Nightly very
> shortly - https://bugzilla.mozilla.org/show_bug.cgi?id51468
> cheers,
> yura
>
>
> On Thu, Aug 3, 2017 at 10:20 AM, Jonathan Cohn < = EMAIL ADDRESS REMOVED = >
> wrote:
>
> > Having an accessible tree inspector would be of great advantage to my
> > sighted co-workers who are not very comfortable with a screen reader.
> Right
> > now they have to rely on my presence to check if what they did had any
> > effect.
> >
> > Is there a way to encourage this work?
> >
> > Thanks,
> >
> > Jonathan Cohn
> >
> > On Thu, Aug 3, 2017 at 9:24 AM Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> > wrote:
> >
> > > Hi all (first time poster). I help out with Firefox DevTools
> > accessibility
> > > and indeed we landed improvements to markup inspector some time last
> > year.
> > > We also made overall keyboard accessibility somewhat better. Though
> this
> > > year has been slower, we have a commitment to a high bar for Firefox
> > > DevTools accessibility this and next year. Later this year we are
> > planning
> > > on releasing Accessible tree inspector as part of our DevTools, for
> > > example. Expect to see a lot more next year!
> > > yura
> > >
> > > On Tue, Aug 1, 2017 at 9:47 AM, Beranek, Nicholas via WebAIM-Forum <
> > > = EMAIL ADDRESS REMOVED = > wrote:
> > >
> > > > 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
> > > >
> > > > -----Original Message-----
> > > > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> > > > Behalf Of Jim Homme
> > > > Sent: Tuesday, August 01, 2017 8:52 AM
> > > > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > > > Subject: [WebAIM] The Accessibility of Browser-based Development
> > > > Environments
> > > >
> > > > Hi,
> > > > I know that extensive work was done to make Firebug accessible. I
> > thought
> > > > I read that that work was brought into FFirefox itself. This prompted
> > me
> > > to
> > > > want to see if anyone who is blind here has either good experiences
> > with
> > > > the development tools in either the newest Firefox, the newest IE,
> > Edge,
> > > or
> > > > Chrome. I’m also wondering how Google is doing with Chrome
> > accessibility
> > > in
> > > > general, and how the screen reader venders are doing with closing the
> > gap
> > > > from their side, since Chrome seems to be very popular among sighted
> > > > vendors.
> > > >
> > > > Thanks.
> > > >
> > > > Jim
> > > >
> > > > =========> > > > Jim Homme,
> > > > Team Lead and Accessibility Consultant,
> > > > Bender HighTest Accessibility Team
> > > > Bender Consulting Services, Inc.,
> > > > 412-787-8567 <(412)%20787-8567>,
> > > > = EMAIL ADDRESS REMOVED =
> > > > http://www.benderconsult.com/our%20services/hightest-
> > > > accessible-technology-solutions
> > > > E+R=O
> > > >
> > > > > > > > > > archives
> > > > at http://webaim.org/discussion/archives
> > > > > > > > > > > >
> > > > The information contained in this e-mail is confidential and/or
> > > > proprietary to Capital One and/or its affiliates and may only be used
> > > > solely in performance of work or services for Capital One. The
> > > information
> > > > transmitted herewith is intended only for use by the individual or
> > entity
> > > > to which it is addressed. If the reader of this message is not the
> > > intended
> > > > recipient, you are hereby notified that any review, retransmission,
> > > > dissemination, distribution, copying or other use of, or taking of
> any
> > > > action in reliance upon this information is strictly prohibited. If
> you
> > > > have received this communication in error, please contact the sender
> > and
> > > > delete the material from your computer.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >

From: Brandon Keith Biggs
Date: Fri, Aug 04 2017 4:25AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

Hello yura,
1. Do you have any screen reader users who guide one through using the dev
tools?
2. Do I need to install anything other than Firefox to get the latest
accessibility changes?
Thank you,


Brandon Keith Biggs <http://brandonkeithbiggs.com/>;

On Thu, Aug 3, 2017 at 7:44 AM, Yura Zenevich < = EMAIL ADDRESS REMOVED = > wrote:

> This work is starting to being reviewed and landing in Firefox Nightly very
> shortly - https://bugzilla.mozilla.org/show_bug.cgi?id51468
> cheers,
> yura
>
>
> On Thu, Aug 3, 2017 at 10:20 AM, Jonathan Cohn < = EMAIL ADDRESS REMOVED = >
> wrote:
>
> > Having an accessible tree inspector would be of great advantage to my
> > sighted co-workers who are not very comfortable with a screen reader.
> Right
> > now they have to rely on my presence to check if what they did had any
> > effect.
> >
> > Is there a way to encourage this work?
> >
> > Thanks,
> >
> > Jonathan Cohn
> >
> > On Thu, Aug 3, 2017 at 9:24 AM Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> > wrote:
> >
> > > Hi all (first time poster). I help out with Firefox DevTools
> > accessibility
> > > and indeed we landed improvements to markup inspector some time last
> > year.
> > > We also made overall keyboard accessibility somewhat better. Though
> this
> > > year has been slower, we have a commitment to a high bar for Firefox
> > > DevTools accessibility this and next year. Later this year we are
> > planning
> > > on releasing Accessible tree inspector as part of our DevTools, for
> > > example. Expect to see a lot more next year!
> > > yura
> > >
> > > On Tue, Aug 1, 2017 at 9:47 AM, Beranek, Nicholas via WebAIM-Forum <
> > > = EMAIL ADDRESS REMOVED = > wrote:
> > >
> > > > 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
> > > >
> > > > -----Original Message-----
> > > > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> > > > Behalf Of Jim Homme
> > > > Sent: Tuesday, August 01, 2017 8:52 AM
> > > > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > > > Subject: [WebAIM] The Accessibility of Browser-based Development
> > > > Environments
> > > >
> > > > Hi,
> > > > I know that extensive work was done to make Firebug accessible. I
> > thought
> > > > I read that that work was brought into FFirefox itself. This prompted
> > me
> > > to
> > > > want to see if anyone who is blind here has either good experiences
> > with
> > > > the development tools in either the newest Firefox, the newest IE,
> > Edge,
> > > or
> > > > Chrome. I’m also wondering how Google is doing with Chrome
> > accessibility
> > > in
> > > > general, and how the screen reader venders are doing with closing the
> > gap
> > > > from their side, since Chrome seems to be very popular among sighted
> > > > vendors.
> > > >
> > > > Thanks.
> > > >
> > > > Jim
> > > >
> > > > =========> > > > Jim Homme,
> > > > Team Lead and Accessibility Consultant,
> > > > Bender HighTest Accessibility Team
> > > > Bender Consulting Services, Inc.,
> > > > 412-787-8567 <(412)%20787-8567>,
> > > > = EMAIL ADDRESS REMOVED =
> > > > http://www.benderconsult.com/our%20services/hightest-
> > > > accessible-technology-solutions
> > > > E+R=O
> > > >
> > > > > > > > > > archives
> > > > at http://webaim.org/discussion/archives
> > > > > > > > > > > >
> > > > The information contained in this e-mail is confidential and/or
> > > > proprietary to Capital One and/or its affiliates and may only be used
> > > > solely in performance of work or services for Capital One. The
> > > information
> > > > transmitted herewith is intended only for use by the individual or
> > entity
> > > > to which it is addressed. If the reader of this message is not the
> > > intended
> > > > recipient, you are hereby notified that any review, retransmission,
> > > > dissemination, distribution, copying or other use of, or taking of
> any
> > > > action in reliance upon this information is strictly prohibited. If
> you
> > > > have received this communication in error, please contact the sender
> > and
> > > > delete the material from your computer.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >

From: Jim Homme
Date: Fri, Aug 04 2017 7:05AM
Subject: Re: The Accessibility of Browser-based DevelopmentEnvironments
← Previous message | Next message →

Hi,
I am a good writer. I would be glad to team up with a developer to be shown how things work, and write it all down.

Jim

=========Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
= EMAIL ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

From: Birkir R. Gunnarsson<mailto: = EMAIL ADDRESS REMOVED = >
Sent: Wednesday, August 2, 2017 9:06 PM
To: WebAIM Discussion List<mailto: = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] The Accessibility of Browser-based Development Environments

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 ADDRESS 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 ADDRESS REMOVED =
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>
> From: Beranek, Nicholas via
> WebAIM-Forum<mailto: = EMAIL ADDRESS REMOVED = >
> Sent: Tuesday, August 1, 2017 9:47 AM
> To: WebAIM Discussion List<mailto: = EMAIL ADDRESS 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
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Jim Homme
> Sent: Tuesday, August 01, 2017 8:52 AM
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Subject: [WebAIM] The Accessibility of Browser-based Development
> Environments
>
> Hi,
> I know that extensive work was done to make Firebug accessible. I thought I
> read that that work was brought into FFirefox itself. This prompted me to
> want to see if anyone who is blind here has either good experiences with the
> development tools in either the newest Firefox, the newest IE, Edge, or
> Chrome. I’m also wondering how Google is doing with Chrome accessibility in
> general, and how the screen reader venders are doing with closing the gap
> from their side, since Chrome seems to be very popular among sighted
> vendors.
>
> Thanks.
>
> Jim
>
> =========> Jim Homme,
> Team Lead and Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> = EMAIL ADDRESS REMOVED =
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>
> > > http://webaim.org/discussion/archives
> > >
> The information contained in this e-mail is confidential and/or proprietary
> to Capital One and/or its affiliates and may only be used solely in
> performance of work or services for Capital One. The information transmitted
> herewith is intended only for use by the individual or entity to which it is
> addressed. If the reader of this message is not the intended recipient, you
> are hereby notified that any review, retransmission, dissemination,
> distribution, copying or other use of, or taking of any action in reliance
> upon this information is strictly prohibited. If you have received this
> communication in error, please contact the sender and delete the material
> from your computer.
> > > > >
> > > > >


--
Work hard. Have fun. Make history.

From: Yura Zenevich
Date: Fri, Aug 04 2017 8:32AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

Hi Brandon,

1. Yes one of my co-workers Marco Zehe is the one helping me with testing
improvements before they land and finding existing and new accessibility
issues with DevTools. We have a list of accessibility bugs that we found
some time ago (https://bugzilla.mozilla.org/show_bug.cgi?idÞvtoolsa11y)
but it has not been updated in a little while because I was focusing on the
Accessibility tree inspector. If you are trying our DevTools, it would be
great to get some feedback or, even better, bugs filed for us to look into.

2. Changes that I mentioned regarding markup inspector accessibility and
some keyboard accessibility are part of already released version of Firefox
(you can open and try them in Tools -> Web Developer -> Toggle Tools)

yura

On Fri, Aug 4, 2017 at 6:25 AM, Brandon Keith Biggs <
= EMAIL ADDRESS REMOVED = > wrote:

> Hello yura,
> 1. Do you have any screen reader users who guide one through using the dev
> tools?
> 2. Do I need to install anything other than Firefox to get the latest
> accessibility changes?
> Thank you,
>
>
> Brandon Keith Biggs <http://brandonkeithbiggs.com/>;
>
> On Thu, Aug 3, 2017 at 7:44 AM, Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> wrote:
>
> > This work is starting to being reviewed and landing in Firefox Nightly
> very
> > shortly - https://bugzilla.mozilla.org/show_bug.cgi?id51468
> > cheers,
> > yura
> >
> >
> > On Thu, Aug 3, 2017 at 10:20 AM, Jonathan Cohn < = EMAIL ADDRESS REMOVED = >
> > wrote:
> >
> > > Having an accessible tree inspector would be of great advantage to my
> > > sighted co-workers who are not very comfortable with a screen reader.
> > Right
> > > now they have to rely on my presence to check if what they did had any
> > > effect.
> > >
> > > Is there a way to encourage this work?
> > >
> > > Thanks,
> > >
> > > Jonathan Cohn
> > >
> > > On Thu, Aug 3, 2017 at 9:24 AM Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> > > wrote:
> > >
> > > > Hi all (first time poster). I help out with Firefox DevTools
> > > accessibility
> > > > and indeed we landed improvements to markup inspector some time last
> > > year.
> > > > We also made overall keyboard accessibility somewhat better. Though
> > this
> > > > year has been slower, we have a commitment to a high bar for Firefox
> > > > DevTools accessibility this and next year. Later this year we are
> > > planning
> > > > on releasing Accessible tree inspector as part of our DevTools, for
> > > > example. Expect to see a lot more next year!
> > > > yura
> > > >
> > > > On Tue, Aug 1, 2017 at 9:47 AM, Beranek, Nicholas via WebAIM-Forum <
> > > > = EMAIL ADDRESS REMOVED = > wrote:
> > > >
> > > > > 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
> > > > >
> > > > > -----Original Message-----
> > > > > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ]
> On
> > > > > Behalf Of Jim Homme
> > > > > Sent: Tuesday, August 01, 2017 8:52 AM
> > > > > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > > > > Subject: [WebAIM] The Accessibility of Browser-based Development
> > > > > Environments
> > > > >
> > > > > Hi,
> > > > > I know that extensive work was done to make Firebug accessible. I
> > > thought
> > > > > I read that that work was brought into FFirefox itself. This
> prompted
> > > me
> > > > to
> > > > > want to see if anyone who is blind here has either good experiences
> > > with
> > > > > the development tools in either the newest Firefox, the newest IE,
> > > Edge,
> > > > or
> > > > > Chrome. I’m also wondering how Google is doing with Chrome
> > > accessibility
> > > > in
> > > > > general, and how the screen reader venders are doing with closing
> the
> > > gap
> > > > > from their side, since Chrome seems to be very popular among
> sighted
> > > > > vendors.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > Jim
> > > > >
> > > > > =========> > > > > Jim Homme,
> > > > > Team Lead and Accessibility Consultant,
> > > > > Bender HighTest Accessibility Team
> > > > > Bender Consulting Services, Inc.,
> > > > > 412-787-8567 <(412)%20787-8567>,
> > > > > = EMAIL ADDRESS REMOVED =
> > > > > http://www.benderconsult.com/our%20services/hightest-
> > > > > accessible-technology-solutions
> > > > > E+R=O
> > > > >
> > > > > > > > > > > > > archives
> > > > > at http://webaim.org/discussion/archives
> > > > > > > > > > > > > > >
> > > > > The information contained in this e-mail is confidential and/or
> > > > > proprietary to Capital One and/or its affiliates and may only be
> used
> > > > > solely in performance of work or services for Capital One. The
> > > > information
> > > > > transmitted herewith is intended only for use by the individual or
> > > entity
> > > > > to which it is addressed. If the reader of this message is not the
> > > > intended
> > > > > recipient, you are hereby notified that any review, retransmission,
> > > > > dissemination, distribution, copying or other use of, or taking of
> > any
> > > > > action in reliance upon this information is strictly prohibited. If
> > you
> > > > > have received this communication in error, please contact the
> sender
> > > and
> > > > > delete the material from your computer.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >

From: Brandon Keith Biggs
Date: Fri, Aug 04 2017 10:40AM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | Next message →

Hello yura,
I am wondering if there are videos or guides on how to use the debugging
tools with a screen reader?
From what people have said, there doesn't seem to be and there is a demand
for them.
Thanks,


Brandon Keith Biggs <http://brandonkeithbiggs.com/>;

On Fri, Aug 4, 2017 at 7:32 AM, Yura Zenevich < = EMAIL ADDRESS REMOVED = > wrote:

> Hi Brandon,
>
> 1. Yes one of my co-workers Marco Zehe is the one helping me with testing
> improvements before they land and finding existing and new accessibility
> issues with DevTools. We have a list of accessibility bugs that we found
> some time ago (https://bugzilla.mozilla.org/show_bug.cgi?idÞvtoolsa11y)
> but it has not been updated in a little while because I was focusing on the
> Accessibility tree inspector. If you are trying our DevTools, it would be
> great to get some feedback or, even better, bugs filed for us to look into.
>
> 2. Changes that I mentioned regarding markup inspector accessibility and
> some keyboard accessibility are part of already released version of Firefox
> (you can open and try them in Tools -> Web Developer -> Toggle Tools)
>
> yura
>
> On Fri, Aug 4, 2017 at 6:25 AM, Brandon Keith Biggs <
> = EMAIL ADDRESS REMOVED = > wrote:
>
> > Hello yura,
> > 1. Do you have any screen reader users who guide one through using the
> dev
> > tools?
> > 2. Do I need to install anything other than Firefox to get the latest
> > accessibility changes?
> > Thank you,
> >
> >
> > Brandon Keith Biggs <http://brandonkeithbiggs.com/>;
> >
> > On Thu, Aug 3, 2017 at 7:44 AM, Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> > wrote:
> >
> > > This work is starting to being reviewed and landing in Firefox Nightly
> > very
> > > shortly - https://bugzilla.mozilla.org/show_bug.cgi?id51468
> > > cheers,
> > > yura
> > >
> > >
> > > On Thu, Aug 3, 2017 at 10:20 AM, Jonathan Cohn < = EMAIL ADDRESS REMOVED = >
> > > wrote:
> > >
> > > > Having an accessible tree inspector would be of great advantage to my
> > > > sighted co-workers who are not very comfortable with a screen reader.
> > > Right
> > > > now they have to rely on my presence to check if what they did had
> any
> > > > effect.
> > > >
> > > > Is there a way to encourage this work?
> > > >
> > > > Thanks,
> > > >
> > > > Jonathan Cohn
> > > >
> > > > On Thu, Aug 3, 2017 at 9:24 AM Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> > > > wrote:
> > > >
> > > > > Hi all (first time poster). I help out with Firefox DevTools
> > > > accessibility
> > > > > and indeed we landed improvements to markup inspector some time
> last
> > > > year.
> > > > > We also made overall keyboard accessibility somewhat better. Though
> > > this
> > > > > year has been slower, we have a commitment to a high bar for
> Firefox
> > > > > DevTools accessibility this and next year. Later this year we are
> > > > planning
> > > > > on releasing Accessible tree inspector as part of our DevTools, for
> > > > > example. Expect to see a lot more next year!
> > > > > yura
> > > > >
> > > > > On Tue, Aug 1, 2017 at 9:47 AM, Beranek, Nicholas via WebAIM-Forum
> <
> > > > > = EMAIL ADDRESS REMOVED = > wrote:
> > > > >
> > > > > > 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
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ]
> > On
> > > > > > Behalf Of Jim Homme
> > > > > > Sent: Tuesday, August 01, 2017 8:52 AM
> > > > > > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > > > > > Subject: [WebAIM] The Accessibility of Browser-based Development
> > > > > > Environments
> > > > > >
> > > > > > Hi,
> > > > > > I know that extensive work was done to make Firebug accessible. I
> > > > thought
> > > > > > I read that that work was brought into FFirefox itself. This
> > prompted
> > > > me
> > > > > to
> > > > > > want to see if anyone who is blind here has either good
> experiences
> > > > with
> > > > > > the development tools in either the newest Firefox, the newest
> IE,
> > > > Edge,
> > > > > or
> > > > > > Chrome. I’m also wondering how Google is doing with Chrome
> > > > accessibility
> > > > > in
> > > > > > general, and how the screen reader venders are doing with closing
> > the
> > > > gap
> > > > > > from their side, since Chrome seems to be very popular among
> > sighted
> > > > > > vendors.
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > Jim
> > > > > >
> > > > > > =========> > > > > > Jim Homme,
> > > > > > Team Lead and Accessibility Consultant,
> > > > > > Bender HighTest Accessibility Team
> > > > > > Bender Consulting Services, Inc.,
> > > > > > 412-787-8567 <(412)%20787-8567>,
> > > > > > = EMAIL ADDRESS REMOVED =
> > > > > > http://www.benderconsult.com/our%20services/hightest-
> > > > > > accessible-technology-solutions
> > > > > > E+R=O
> > > > > >
> > > > > > > > > > > > > > > > archives
> > > > > > at http://webaim.org/discussion/archives
> > > > > > > > > > > > > > > > > >
> > > > > > The information contained in this e-mail is confidential and/or
> > > > > > proprietary to Capital One and/or its affiliates and may only be
> > used
> > > > > > solely in performance of work or services for Capital One. The
> > > > > information
> > > > > > transmitted herewith is intended only for use by the individual
> or
> > > > entity
> > > > > > to which it is addressed. If the reader of this message is not
> the
> > > > > intended
> > > > > > recipient, you are hereby notified that any review,
> retransmission,
> > > > > > dissemination, distribution, copying or other use of, or taking
> of
> > > any
> > > > > > action in reliance upon this information is strictly prohibited.
> If
> > > you
> > > > > > have received this communication in error, please contact the
> > sender
> > > > and
> > > > > > delete the material from your computer.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >

From: Yura Zenevich
Date: Fri, Aug 04 2017 7:30PM
Subject: Re: The Accessibility of Browser-based Development Environments
← Previous message | No next message

I don't think there are at the moment. I'm asking internally if we can get
some public documentation or tutorials available. I'll update when I hear
back.
Yura

On Fri, Aug 4, 2017 at 12:40 PM, Brandon Keith Biggs <
= EMAIL ADDRESS REMOVED = > wrote:

> Hello yura,
> I am wondering if there are videos or guides on how to use the debugging
> tools with a screen reader?
> From what people have said, there doesn't seem to be and there is a demand
> for them.
> Thanks,
>
>
> Brandon Keith Biggs <http://brandonkeithbiggs.com/>;
>
> On Fri, Aug 4, 2017 at 7:32 AM, Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> wrote:
>
> > Hi Brandon,
> >
> > 1. Yes one of my co-workers Marco Zehe is the one helping me with testing
> > improvements before they land and finding existing and new accessibility
> > issues with DevTools. We have a list of accessibility bugs that we found
> > some time ago (https://bugzilla.mozilla.org/show_bug.cgi?idÞvtoolsa11y
> )
> > but it has not been updated in a little while because I was focusing on
> the
> > Accessibility tree inspector. If you are trying our DevTools, it would be
> > great to get some feedback or, even better, bugs filed for us to look
> into.
> >
> > 2. Changes that I mentioned regarding markup inspector accessibility and
> > some keyboard accessibility are part of already released version of
> Firefox
> > (you can open and try them in Tools -> Web Developer -> Toggle Tools)
> >
> > yura
> >
> > On Fri, Aug 4, 2017 at 6:25 AM, Brandon Keith Biggs <
> > = EMAIL ADDRESS REMOVED = > wrote:
> >
> > > Hello yura,
> > > 1. Do you have any screen reader users who guide one through using the
> > dev
> > > tools?
> > > 2. Do I need to install anything other than Firefox to get the latest
> > > accessibility changes?
> > > Thank you,
> > >
> > >
> > > Brandon Keith Biggs <http://brandonkeithbiggs.com/>;
> > >
> > > On Thu, Aug 3, 2017 at 7:44 AM, Yura Zenevich < = EMAIL ADDRESS REMOVED = >
> > > wrote:
> > >
> > > > This work is starting to being reviewed and landing in Firefox
> Nightly
> > > very
> > > > shortly - https://bugzilla.mozilla.org/show_bug.cgi?id51468
> > > > cheers,
> > > > yura
> > > >
> > > >
> > > > On Thu, Aug 3, 2017 at 10:20 AM, Jonathan Cohn < = EMAIL ADDRESS REMOVED =
> >
> > > > wrote:
> > > >
> > > > > Having an accessible tree inspector would be of great advantage to
> my
> > > > > sighted co-workers who are not very comfortable with a screen
> reader.
> > > > Right
> > > > > now they have to rely on my presence to check if what they did had
> > any
> > > > > effect.
> > > > >
> > > > > Is there a way to encourage this work?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Jonathan Cohn
> > > > >
> > > > > On Thu, Aug 3, 2017 at 9:24 AM Yura Zenevich <
> = EMAIL ADDRESS REMOVED = >
> > > > > wrote:
> > > > >
> > > > > > Hi all (first time poster). I help out with Firefox DevTools
> > > > > accessibility
> > > > > > and indeed we landed improvements to markup inspector some time
> > last
> > > > > year.
> > > > > > We also made overall keyboard accessibility somewhat better.
> Though
> > > > this
> > > > > > year has been slower, we have a commitment to a high bar for
> > Firefox
> > > > > > DevTools accessibility this and next year. Later this year we are
> > > > > planning
> > > > > > on releasing Accessible tree inspector as part of our DevTools,
> for
> > > > > > example. Expect to see a lot more next year!
> > > > > > yura
> > > > > >
> > > > > > On Tue, Aug 1, 2017 at 9:47 AM, Beranek, Nicholas via
> WebAIM-Forum
> > <
> > > > > > = EMAIL ADDRESS REMOVED = > wrote:
> > > > > >
> > > > > > > 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
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: WebAIM-Forum [mailto:webaim-forum-bounces@l
> ist.webaim.org]
> > > On
> > > > > > > Behalf Of Jim Homme
> > > > > > > Sent: Tuesday, August 01, 2017 8:52 AM
> > > > > > > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > > > > > > Subject: [WebAIM] The Accessibility of Browser-based
> Development
> > > > > > > Environments
> > > > > > >
> > > > > > > Hi,
> > > > > > > I know that extensive work was done to make Firebug
> accessible. I
> > > > > thought
> > > > > > > I read that that work was brought into FFirefox itself. This
> > > prompted
> > > > > me
> > > > > > to
> > > > > > > want to see if anyone who is blind here has either good
> > experiences
> > > > > with
> > > > > > > the development tools in either the newest Firefox, the newest
> > IE,
> > > > > Edge,
> > > > > > or
> > > > > > > Chrome. I’m also wondering how Google is doing with Chrome
> > > > > accessibility
> > > > > > in
> > > > > > > general, and how the screen reader venders are doing with
> closing
> > > the
> > > > > gap
> > > > > > > from their side, since Chrome seems to be very popular among
> > > sighted
> > > > > > > vendors.
> > > > > > >
> > > > > > > Thanks.
> > > > > > >
> > > > > > > Jim
> > > > > > >
> > > > > > > =========> > > > > > > Jim Homme,
> > > > > > > Team Lead and Accessibility Consultant,
> > > > > > > Bender HighTest Accessibility Team
> > > > > > > Bender Consulting Services, Inc.,
> > > > > > > 412-787-8567 <(412)%20787-8567>,
> > > > > > > = EMAIL ADDRESS REMOVED =
> > > > > > > http://www.benderconsult.com/our%20services/hightest-
> > > > > > > accessible-technology-solutions
> > > > > > > E+R=O
> > > > > > >
> > > > > > > > > > > > > > > List
> > > > > archives
> > > > > > > at http://webaim.org/discussion/archives
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > The information contained in this e-mail is confidential and/or
> > > > > > > proprietary to Capital One and/or its affiliates and may only
> be
> > > used
> > > > > > > solely in performance of work or services for Capital One. The
> > > > > > information
> > > > > > > transmitted herewith is intended only for use by the individual
> > or
> > > > > entity
> > > > > > > to which it is addressed. If the reader of this message is not
> > the
> > > > > > intended
> > > > > > > recipient, you are hereby notified that any review,
> > retransmission,
> > > > > > > dissemination, distribution, copying or other use of, or taking
> > of
> > > > any
> > > > > > > action in reliance upon this information is strictly
> prohibited.
> > If
> > > > you
> > > > > > > have received this communication in error, please contact the
> > > sender
> > > > > and
> > > > > > > delete the material from your computer.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >