WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: The Accessibility of Browser-based Development Environments

for

From: Yura Zenevich
Date: Aug 3, 2017 8:44AM

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 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 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 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 REMOVED> ] On
> > > Behalf Of Jim Homme
> > > Sent: Tuesday, August 01, 2017 8:52 AM
> > > To: WebAIM Discussion List < <EMAIL 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 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.
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >