RE: RE: accessibility toolbar

I am not seeing the same behaviour as Alan insofar as the button that launches the tool is the second focusable element on each page, whether JAWS is running or not.

There are actually two “Skip to content” links that behave differently. The first one is inserted by the toolbar at the very top of the page and it works ok. However, it is not present when the toolbar is closed. The second one is part of the website and has nothing to do with the toolbar. This is the one that doesn’t work – I see the same behaviour that Alan described. Just to confuse matters, this one is at the top of the page when the toolbar is closed, but the toolbar is inserted above it when it is open, so the original skip link is pushed a long way down the page.

Curiously, the tool does not contain any heading elements even though it contains visual headings. This makes screen reader navigation more difficult than it needs to be. Perhaps they thought that screen reader users would not find anything useful in the tool, but of course not all screen reader users are completely blind. For instance, one of our sales people had perfect sight but used a screen reader because of his extreme dyslexia.

Steve


From: alands289@gmail.com <alands289@gmail.com>
Sent: 20 May 2020 19:08
To: Char Easter <ceaster@seattletimes.com>; w3c-wai-ig@w3.org
Subject: RE: accessibility toolbar

Char,

The toolbar looks very helpful.
These offer a lot of value to end users.
However, they do not necessarily make the site WCAG compliant.

For example, I found these issues on the home page after only a few minutes of checking the page with JAWS:

This tool would be more helpful if it was one of the first links/buttons on the page and not nearly the last link/button at the very bottom of the page.
The Skip to content does not work properly.
           It moves the page up so that visually the navigation items are skipped.
           However, from a tabbing and screen reader reading order perspective, the both start at the top of the page.
           Therefore, both have not “skipped to content”.
Headings are out of order.
H2 is immediately followed by h4.
There is an h3 that does not make sense.
H3 is immediately followed by h5.
There are two regions for Main: one is Main and the other is Main navigation Navigation.
The labeling is not the correct way to label a region since it is repeating the term of the region in its label.
The main menus announce their label and then the term link.
They do not announce that they are menus that will show more sub-menus.
Or that they have expanded and are showing those sub-menus.
They are links that also show sub-menus and should announce that fact.
Main menus should not be links in and of them selves.
Their sub-menus do the same thing.
This is not the proper way to code main menus with sub-menus that also have more sub-menus for non-visual users.
In the row of years, each function as tabs but do not announce that fact or which one is selected and showing its data.
The Cookware and Bakeware elements have this same issue with being tabs but not announcing that fact or which one is selected and showing its data.
In the content of these two tabs, there are two links for each item.
One is the image link and the other is the text link.
With image links, the image is considered decorative and is not needed as a link if the adjacent text is the same label. Only one needs to be a link.
Near the top of the page there are image links and text links for different utensils with similar issues.
           The image link announces a long file name and does not have a proper label.
One is the image link and the other is the text link.
With image links, the image is considered decorative and is not needed as a link if the adjacent text is the same label. Only one needs to be a link.







Alan Smith

From: Char Easter<mailto:ceaster@seattletimes.com>
Sent: Wednesday, May 20, 2020 1:40 PM
To: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: accessibility toolbar

Any thoughts on this accessibility toolbar? It appears on the site, https://farberwarecookware.com/


The tool is authored by, https://hikeorders.com/accessibility/main-accessibility-features/#accessibility-tools


Thanks,

Char Easter
UX Designer at The Seattle Times
p: 206.464.2945
e: ceaster@seattletimes.com<mailto:ceaster@seattletimes.com>
m: 206.779.2427