WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Jared Smith
Date: Dec 28, 2018 12:34PM

Kelly Ford wrote:

> Are the buttons supposed to be the graphics that get numbered starting at 1
> up to how many items are listed for a given category?

The individual icons in the sidebar are not buttons - clicking them
provides a visual highlighting of the relevant location in the page,
but making all of these many icons into buttons would render the
sidebar (and thus all of WAVE) very difficult to use on most pages. I
was instead referring to the WAVE icons in the page itself.

> After you fix the fact that many items are tagged with alt text of 1, won't
> there still be an issue finding the right items in the code.

My hope is that by making the relevant area in the Code panel
navigable that this will make it much easier to find. You could
activate the relevant icon button within the page (for instance a
missing alt text icon adjacent to the site logo), then quickly
navigate to the Code panel region and then Tab to the appropriate
element within the code for that icon (the HTML code for the site
logo).

We're working on a design and UX update to WAVE, so some of these
interactions will be changing. We're committed to ensuring that WAVE
is highly accessible and have received very positive feedback from
screen reader users (it's one of only a few accessibility testing
tools that is itself accessible), but understand that exploring the
Code panel can be rather difficult to do programmatically or with a
keyboard.

Thanks,

Jared