E-mail List Archives
Re: Screen Readers And Code Inspection Within Browser Dev Tools
From: Lucy GRECO
Date: Sep 30, 2020 1:08PM
- Next message: glen walker: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- Previous message: Mallory: "Re: "Error feedback MUST be programmatically-associated with the appropriate element""
- Next message in Thread: glen walker: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- View all messages in this Thread
hello:
please send a message to the bats list as many of the people on that list
have found tricks to do this. subscribe at
bats.fiy
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 Tue, Sep 29, 2020 at 5:36 PM Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:
> I find code inspection in Chrome pretty tolderabletolerable.
> Right click where you want to look at the code and choose "inspect
> code" from the menu.
> You're landed on the DOM tree, make sure your screen reader is in
> forms/application mode, then you can use arrow key to traverse the
> tree, context menu to add or modify attribute, or even ctrl-c to copy
> the node and its descendants, then you can paste it into your favorite
> code editor to inspect and play with, then you could paste it back if
> you wanted to see your changes on the page in real time.
> There are a few other tricks and there are things that I am still
> finding hard to do, e.g. seeing the CSS associated with the currently
> selected node in the DOM tree (Firebug did that really well in the old
> days).
>
>
>
> On 9/29/20, Jim Homme < <EMAIL REMOVED> > wrote:
> > Hi,
> > So far my experience in both Firefox and Chrome with code inspection
> using
> > screen readers has been very slow and clunky. Does anyone have
> experiences
> > to share that might make the experience more pleasant?
> >
> > Thanks.
> >
> > Jim
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >
- Next message: glen walker: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- Previous message: Mallory: "Re: "Error feedback MUST be programmatically-associated with the appropriate element""
- Next message in Thread: glen walker: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- View all messages in this Thread