WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: The Accessibility of Browser-based Development Environments

for

From: Yura Zenevich
Date: Aug 4, 2017 7:30PM

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 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 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 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 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 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: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 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
> > > > > > >
> > > > > > > > > > > > > > > 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.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >