WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Meaningful Sequence in SPAs

for

From: L Snider
Date: Apr 16, 2024 10:46AM

I will add to the previous comment. In my experience with PSAs, there
should be a way to go back, and go forward (or there should be)-usually
using a button not a link. Now people can argue button or link, but for me
this case would be a button in my view. So if they are switching, would
they not be switching with new headings? So heading 2 on page A is Contact
Information, and then Heading 2 on Page B is location preference, etc. Just
ensure that as the other commented said, that people can get back and forth
whether they are using a screen reader (and test with multiple kinds) or
voice control. I have been stuck in these things using voice, and it isnt
pretty when it happens.

Cheers

Lisa


On Tue, Apr 16, 2024 at 11:47 AM Brian Lovely < <EMAIL REMOVED> >
wrote:

> I'm curious about focus order in single-page application-style websites,
> where the base URL doesn't change, but the content of the previous page is
> "blown away" and replaced by the content of the new page. Let's call them
> pages A and B.
>
> If on page A there is a control that causes page A to be replaced with page
> B, then the currently focused element is removed from the DOM, along with
> the rest of page A, when that control is activated. Screen reader users
> will hear nothing, and if they try navigating "forward" they will be at
> roughly the same distance from the top of page B as they were from the top
> of page A (that's been my experience, anyway.) Navigating forward, they may
> just encounter the footer, but no matter what they encounter it will be
> confusing to be at some random point in the page B content.
>
> My question is when changing views in a single-page application-style
> website, how should focus be handled? I specify "website" to differentiate
> from a single page application that is simply a series of form views.
> > > > >