WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL] Graphical element instead of the role link presence. Howshould I report it?

for

From: Mark Magennis
Date: Mar 3, 2021 9:45AM

Wow!

That site is really terrible from an accessibility point of view. The logo Home page link is really the least of the problems.

The biggest problem is that the site as a whole is completely inaccessible using the keyboard because you cannot Tab to any of the interactive elements.

It's slightly better using a screen reader because at least you can arrow through it, read most of the content, and activate many of the menu items.

I would suggest you mention these two points and then arrow though it with a screen reader yourself to find other issues you can point out in your report, such as:

1. Some content, including navigation menu items, is skipped.
2. Navigation menus don't behave correctly (e.g. you can't close them without selecting an option)
3. Some headings are not marked up and heading levels aren't correct.
4. Information is contained in images without text alternatives.
5. Some non-informational images have unnecessary and meaningless text alternatives.
6. Etc.

You can look at a lot of the HTML code in the Inspector - right click on any element and select Inspect from the menu.

Good luck,
Mark

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of ???????? ?????
Sent: 03 March 2021 15:53
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [EXTERNAL] [WebAIM] Graphical element instead of the role link presence. How should I report it?

Hello everyone,
There is a webpage that I need to provide an accessibility testing for. It was given to me as the practice.
The issue is that there is practically no html markup on a webpage, if I press ctrl+u and review the code the only thing I find is the connection process of java scripts in body of the document.
So I cannot review the code and report it as it would be more correctly.
The issue is that the element that logically should be stated as the element as the link role is presented as the graphical element with the alt text "Ceotech logo". When pressed, it returns back to the home page.
Here's how I have written a report.
Please feel free to correct me if I am wrong, because I have no idea how to tell it correctly in this case.
The graphical logo instead of the link role element is presented.
The element which is ment to be a home forwarding link is stated as an image that should be replaced with the element with name "home" and role link.
It will allow a screen reader user to interact with this element as needed.
Now it is not clear if it is an image or a link.
Expected result: An html element with the name "Home" and the link role should be presented.
Actual result: An aria-control element. The image element doesn't have a link role and has the wrong name which is confusing when using a screen reader.
Standards and guidelines:https://www.w3.org/TR/WCAG21/#non-text-content
https://www.w3.org/TR/WCAG21/#name-role-value
See also:https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html
https://dequeuniversity.com/rules/axe/4.1/image-alt?application=AxeFirefox
Reproduced on: Windows 10 (64 bit)
NVDA 2020.4.
Firefox 85.0.
P.s.:
There are no elements with the link role at all. All links are presented as divs or graphical elements.
The url is:
https://ceotech.ca
Thank you in advance!
Best regards,
Vsevolod
<EMAIL REMOVED>
My telegram channel (russian only):
http://t.me/vsevapopov2
The channel chat:
http://t.me/vsevapopovclub