E-mail List Archives
Thread: Landmarks on Mobile web
Number of posts in this thread: 4 (In chronological order)
From: Sudheer Babu
Date: Tue, Aug 24 2021 11:29PM
Subject: Landmarks on Mobile web
No previous message | Next message →
Hi All,
Hope everyone is doing well and staying safe!
Can someone please point me to the support of landmarks across screen
readers,
especially for Mobile screen readers like Talkback and VoiceOver on the
Mobile web? Will the same markup as on desktop web would work with Mobile
screen readers?
I am seeing that sub-links under footer landmarks are also being announced
as article landmarks using mobile screen readers which actually are not
marked up as landmarks. Is this correct behavior?
Thanks,
Sudheer
From: Birkir R. Gunnarsson
Date: Wed, Aug 25 2021 6:10AM
Subject: Re: Landmarks on Mobile web
← Previous message | Next message →
Generally, I have found that landmarks on mobile add verbosity with
very little benefit.
The page header in responsive view is typically collapsed into a
hambruger menu, maybe a logo, so the header only has two pieces of
content.
The footer is often removed altogether, or equally collapsed into a
skinny representation hidden behind collapsable menus
It mostly leaves the main content, so it doesn't have to be marked as
the main landmark.
Last time I tested I found that support for role="group" was better
than role="navigation", specifically on Voiceover, so I had developers
change the roles of navigation menus when in responsive view.
I had them drop other landmark roles when transitioning to responsive.
This doesn't exactly answer the question *grin* but offers up one
solution, just to drop the landmark roles in responsive view, at least
banner/main/contentinfo, or alterantively not worry about how well
they are supported because they have a lot less importance on the
mobile device screen.
On 8/25/21, Sudheer Babu < = EMAIL ADDRESS REMOVED = > wrote:
> Hi All,
>
> Hope everyone is doing well and staying safe!
> Can someone please point me to the support of landmarks across screen
> readers,
> especially for Mobile screen readers like Talkback and VoiceOver on the
> Mobile web? Will the same markup as on desktop web would work with Mobile
> screen readers?
> I am seeing that sub-links under footer landmarks are also being announced
> as article landmarks using mobile screen readers which actually are not
> marked up as landmarks. Is this correct behavior?
>
> Thanks,
> Sudheer
> > > > >
--
Work hard. Have fun. Make history.
From: glen walker
Date: Wed, Aug 25 2021 1:21PM
Subject: Re: Landmarks on Mobile web
← Previous message | Next message →
It can be handy to navigate by landmarks on mobile. Whether some of those
landmarks should disappear when in responsive or mobile view is more of a
UX discussion, as Birkir notes. With VoiceOver on iOS, I can change my
rotor to navigate by landmarks so swiping up/down goes to the next
landmark. Unfortunately, VoiceOver treats the <article> element as a
landmark when it absolutely is *not* a landmark. So that clutters up my
navigation when I'm on a news site like CNN.
See https://www.w3.org/TR/wai-aria/#article. The second sentence says "an
article is not a navigational landmark".
The VoiceOver rotor also lets you navigate by articles so it's doubly
confusing why Apple decided to include articles in the landmarks list when
they can be navigated separately.
From: Jonathan Cohn
Date: Sat, Aug 28 2021 3:55PM
Subject: Re: Landmarks on Mobile web
← Previous message | No next message
Glen,
I wonder if there are any Apple Bugs on this. I remember when JAWS used to treat articles as landmarks.
Best wishes,
Jonathan Cohn
> On Aug 25, 2021, at 15:21, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
>
> It can be handy to navigate by landmarks on mobile. Whether some of those
> landmarks should disappear when in responsive or mobile view is more of a
> UX discussion, as Birkir notes. With VoiceOver on iOS, I can change my
> rotor to navigate by landmarks so swiping up/down goes to the next
> landmark. Unfortunately, VoiceOver treats the <article> element as a
> landmark when it absolutely is *not* a landmark. So that clutters up my
> navigation when I'm on a news site like CNN.
>
> See https://www.w3.org/TR/wai-aria/#article. The second sentence says "an
> article is not a navigational landmark".
>
> The VoiceOver rotor also lets you navigate by articles so it's doubly
> confusing why Apple decided to include articles in the landmarks list when
> they can be navigated separately.
> > > >