E-mail List Archives
Re: Logical focus flow on carousel
From: glen walker
Date: Apr 2, 2019 7:28PM
- Next message: Duff Johnson: "Re: Accessible P Tag Usage"
- Previous message: glen walker: "Re: Word Accessibility Question About Built-in Styles"
- Next message in Thread: Aditya: "Re: Logical focus flow on carousel"
- Previous message in Thread: Greg Jellin: "Logical focus flow on carousel"
- View all messages in this Thread
Whatever order the DOM is should remain in that order. That is, the way
you described how you'd like to see the behavior, sounds like the DOM order
should change after the user selects next. Hopefully that's not the case.
As you swipe or tab through the page, if you get to the prev button, then
the carousel contents, then the next button, selecting the next button
should load more carousel content but leave the focus on the next button.
You'd have to swipe/tab backwards to get to the contents.
If the DOM order were carousel contents, prev button, next button, then
selecting next should leave the focus on next and the user would have to
swipe/tab backwards twice to get to the contents.
You could mitigate this a little for screen reader users by having a live
region and announce that new content was added, or announce the actual
content that was added, and perhaps tell the user to navigate backwards to
get to the new content. For me, personally, if I hear prev, then carousel
contents, then next and I select next, I know the content is "behind" me
and I have to navigate backwards to get to it.
Glen
- Next message: Duff Johnson: "Re: Accessible P Tag Usage"
- Previous message: glen walker: "Re: Word Accessibility Question About Built-in Styles"
- Next message in Thread: Aditya: "Re: Logical focus flow on carousel"
- Previous message in Thread: Greg Jellin: "Logical focus flow on carousel"
- View all messages in this Thread