Accessibility issues with hotspot pop-ups
I have identified one, maybe two issues with the pop-up windows that appear when selecting a hotspot.
Issue #1: There is a heading withing the pop-up window that is not using a heading level eleme...
Forum Discussion
Hi Marvie, it sounds like it has gone through some consideration and testing. It didn't feel like a natural experience for me using a screen reader, but I may be in the minority here.
My thought was that the order of appearance doesn't necessarily need to change, but the order order in the DOM could change, and then the elements positioned as they are now using CSS.
So, the DOM element order would be like this: Heading > Content > Back arrow > Next arrow, but the visual order could remain the same: Heading > Back arrow > Next arrow > Content. This would address any concerns of the focus order being thrown off, as it would not need to be manipulated using script.
We take this approach in courses we build where the visual layout may work better if they "appear" not to follow the natural order in the DOM. Hope that makes sense.
Absolutely, it does makes sense! This is exactly what we did before - visually, the design layout is preserved, and in the DOM it was ordered as Title > Content > Prev > Next. In this case, the screen reader would highlight them in the same order. But a user that has a learned reading pattern, or expectation of the typical sequential, natural order of left to right, top to bottom may throw them off if visually it highlights going down the marker bubble contents (which can be long, with text & media), and then back up to the previous & next buttons.
I appreciate this conversation! It make us a11y advocates better everyday!
Cheers!
Marvie
