WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Associating Errors From Wave Plug-in to the HTML Source


From: JP Jamous
Date: Dec 30, 2018 5:26PM


For the latter one, the goal was to be able to go through the list of errors
and switch over to the original window that has the page and change the DOM
markup. This would enable evaluators to modify the markup and hear how it
sounds with a screen reader or look visually.

If using the duplicate window does not make the WAVE report disappear, I am
fine with that.

JP Jamous
Senior Digital Accessibility Engineer
E-Mail Me |Join My LinkedIn Network

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Jared
Sent: Sunday, December 30, 2018 5:38 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Associating Errors From Wave Plug-in to the HTML

> Is it possible to have the WAVE icon show up in the Chrome context
> menu or is that a browser restriction?

It is already. Just ensure that you don't have anything selected within the
page and the "WAVE this page" item should appear in the context menu. There
is also a default shortcut key of Control + Shift
+ U (Command + Shift + U on Mac). If this doesn't work, it may need to
be defined in the Keyboard Shortcuts settings for Extensions (also available
at chrome://extensions/shortcuts).

> Secondly, is it possible to have the WAVE extension results load in a
> new browser tab?

This isn't optimal because in many cases you may want to evaluate a dynamic
state of the page, and re-loading the page in a new tab would negate this.
You can, however, duplicate the tab (there is an option for Duplicate in the
Window menu) and then run WAVE there. I will, however, look into an option
for doing this automatically with the WAVE extension in cases where this
functionality is desired.