WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: DOM Inspector

for

From: Birkir R. Gunnarsson
Date: Aug 18, 2016 8:45AM

I always use Firebug, see my instruction article at:
http://bats.fyi/2016/06/17/using-firebug-jaws-analyze-webpages/
Firefox, as of version 49, will have pretty awesomely accessible
developer tools.
https://www.marcozehe.de/2016/05/24/the-firefox-developer-tools-inspector-panel-is-becoming-accessible/

At their CSUN presentation this year, Microsoft promised to make the
Edge developer tools accessible, I don't have Edge installed so I
don't know what the progress is.
I sat down for a couple of hours with the Google folks to explain the
problems with Chrome dev tools accessibility. I need to follow up and
see if they have managed to turn that very fun session into useful
feedback or action.
That's all I know, Firefox is your mom, if you want to inspect the DOM
(getting poetic).
-B


On 8/18/16, Jamous, JP < <EMAIL REMOVED> > wrote:
> Folks,
>
> I have pages where I am unable to see the markup using Internet Explorer
> Source View. If I press F12 to use the DOM Inspector, JAWS 17 does not work
> with it well. AT least, I haven't found a way for it to work with it.
>
> Do you recommend any instructions or browser extension that I can use to
> view how JavaScript is creating he markup after it executes?
>
> I do not care if it works with IE, firefox or chrome. As long as it works
> with JAWS 17 and allows me to read the code easily.
>
> Thanks.
>
>
>
>
> **************************************************
>
> Jean-Pierre Jamous
> Digital Accessibility Specialist & Developer
> UI Accessibility Team
>
> The only limitations in life are those we set for ourselves
>
> **************************************************
>
>
> > > > >


--
Work hard. Have fun. Make history.