E-mail List Archives
Re: Associating Errors From Wave Plug-in to the HTML Source
From: JP Jamous
Date: Dec 30, 2018 11:55AM
- Next message: KellyFord: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Next message in Thread: KellyFord: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message in Thread: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- View all messages in this Thread
Kelly,
If you are using JFW, try switching to NVDA and try it. Sometimes, you get
either the browser or the screen reader crashing. This will help you
diagnose the problem since Jared is not able to duplicate it.
Jared,
Is it possible to have the WAVE icon show up in the Chrome context menu or
is that a browser restriction? I like how in Firefox, I just press the
Applications key and the menu item is there. I dislike where Chrome
typically places its extension buttons. Not user friendly from a UX
prospective.
Secondly, is it possible to have the WAVE extension results load in a new
browser tab? This can be quite convenient to switch between tabs using CTRL
+ Tab key, while inspecting the page using a DOM inspector. It can be more
productive based on my experience with WAVE.
Keep up the outstanding work with WAVE.
--------------------
JP Jamous
Senior Digital Accessibility Engineer
E-Mail Me |Join My LinkedIn Network
--------------------
- Next message: KellyFord: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Next message in Thread: KellyFord: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message in Thread: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- View all messages in this Thread