WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL] Google Lighthouse with a screen reader?

for

From: Lucy Greco
Date: May 15, 2018 12:39PM

hello:
this is a great conversation. Kelly do you think you could write this up
for Bats. I think it would be a great post 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 Tue, May 15, 2018 at 9:27 AM KellyFord < <EMAIL REMOVED> > wrote:

> Hi,
>
> Here is how I access Lighthouse with a screen reader in Chrome. There may
> be faster ways so suggestions welcome. I do this with both JAWS and NVDA.
>
> 1. Open the dev tools with F12.
> 2. Press ctrl+[ or ctrl+] to cycle through the tabs. That's control and
> left or right bracket. Note you can also tab to the list of tabs and press
> right arrow until you get to Audits. Depending on how many tabs are shown,
> a menu may appear as you arrow.
> 3. Use my screen readers jump to button key (typically b) to find the Run
> Audit button.
> 4. Check the boxes for which audits I want to run and launch the audit.
>
> When reading the results, the different categories of the report do not
> have headings so a search for accessibility as an example is the fastest
> way for me to find that section in the report. I can then expand the
> different problem sections and failing elements. From the screen reading
> web mode (JAWS virtual PC or NVDA Browse mode) I can press enter on the
> failing element. This seems to shift back to the Elements tab and
> scroll/expand the DOM tree to the problem element.
>
> To get back to the audit report, I have to press the ctrl+[ or ctrl+] keys
> again until I'm back on the correct tab. Perhaps there is a hotkey to
> select the tab directly but so far I have not found it.
>
> All this said, using the dev tools for me does still require a bit of
> jumping back and forth between the different screen reading modes. This is
> true for whatever browser/screen reader combination I've tried.
>
> Kelly
>
>