WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Unaware of sitemap due to forced focus


From: Barry
Date: Feb 10, 2021 7:29AM

Thanks, Wolfgang.

A user would reach these particular dynamic web pages via a link from another part of the site and the SR focus would land on the h1, which is below the sitemap. Perhaps this is the problem. I don't think it goes against any WCAG, but I am concerned that it is not best practice.

The sitemap does have a navigation region tag, and I'm going to suggest that they change this to a sitemap region tag.



-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of <EMAIL REMOVED>
Sent: 09 February 2021 9:00 PM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Unaware of sitemap due to forced focus

My thoughts as a SR user:

When I visit a Single-Page web application or anything else for the first time, I must explore the page.
If I understood you right, I at first arrive at the sitemap. So, I know about it.

If each journey (in the form) really is realized as a button and not a link, I must know that I don't get to a new address but that something happenes on the page. So, the focus should be there, where I must interact next.
And I should have the sitemap above in mind.

Your sitemap probably should be realized with links or it is not a sitemap.

I know that the distinction between button- and link-semantics are underestimated even in tutorials. But I imagine, this could help understanding your website.

Now you should still consider usability issues since users have to keep the existence of the sitemap above in mind. What if they forgot?

Perhaps the application / form standing alone with an added link to a sitemap could help?

Are you concerned about SC 3.2.5 Change on Request? Thank you very much since it is positioned only under AAA.


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Barry via WebAIM-Forum
Sent: Tuesday, February 9, 2021 12:20 PM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: [WebAIM] Unaware of sitemap due to forced focus

Hi all

I am looking at a Single-Page web application where several journeys can be
undertaken via hitting buttons. Hitting a button forces the focus to the
title of the updated content virtually as if the focus has not moved and the content was always there for a screen reader. There is a sitemap, but the focus is always past it so the screen reader user is unaware of its presence. The alt left cursor does take the screen reader user back, closing the actioned page update and leaving the focus on the button that actioned the update. Each use of 'back' takes the user back in the journey in this way.

My question is, is not being aware of the sitemap an issue? My concern is that the sitemap has buttons that can take the user back to anywhere in the journey in one go. My problem is that the current forced focus is very neat and accessible.

Thanks in anticipation