WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: KellyFord
Date: May 15, 2018 10:26AM

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

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of <EMAIL REMOVED>
Sent: Tuesday, May 15, 2018 10:37 AM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Google Lighthouse with a screen reader?

If I were going down the continuous integration route, I'd probably use a headless browser and automate a lot of what we do. But right now all I want to do is to run Lighthouse over a single-page application in its various states and see how it performs. If Lighthouse is accessible, it isnt' obviously so.

Cheers.

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Tim Harshbarger
Sent: 15 May 2018 14:14
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Google Lighthouse with a screen reader?

Unless you are looking to write code to integrate Google Lighthouse into a continuous integration system, it sounds like you either access Google Lighthouse from Chrome DevTools or the commandline.

If you find Chrome DevTools accessible enough, then you don't need to install Node to use the features. If you prefer to use the command line, you definitely will need to install Node.

I use a screen reader, but it has been a couple months since I tried working with the Chrome DevTools. If I recall correctly, I think I found some things seemed accessible while others weren't. I think I was able to access the audit tab and review the accessibility information provided there.

Thanks,
Tim

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of <EMAIL REMOVED>
Sent: Tuesday, May 15, 2018 7:26 AM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: [EXTERNAL] [WebAIM] Google Lighthouse with a screenreader?

Hi all,



Is it possible to use Google Lighthouse with a screenreader without installing NodeJS? I'll do that if I have to, but it's an extra step and I'm lazy.



Cheers.