What is the purpose of the "landmark" accessibility container type?
The UIAccessibilityContainerType.landmark enumeration case is described as "Landmark data." This description leaves much to the imagination and I have struggled to find information about this enumeration case elsewhere.
I tried setting the accessibilityContainerType value of some of the views in my app to landmark to see whether this changes anything in the VoiceOver experience of my app. I did not see any change. I thought I might see an extra "Landmarks" rotor option if nothing else but this was not the case.
What is the purpose of UIAccessibilityContainerType.landmark enumeration case? Does it have any impact on an app's VoiceOver experience?
Even if a brilliant answer has already been provided by @slugolicious š, I deem it important to bring some information regarding the question in the "iOS world" with the sources. š¤Æ
What is the purpose of UIAccessibilityContainerType.landmark enumeration case? Does it have any impact on an app's VoiceOver experience?
I asked myself the same questions and wrote a TSI (nĀ°1631349) to Apple who answered: "the landmarks are the same as in HTML and are for web content & tvOS". š³
It's definitely not designed for iOS. In the Accessibility design for Mac Catalyst WWDC 2020 video, it is highlighted in the What are accessibility containers? section. š¬
I'm used to watching the WWDC summaries written by Orange Digital Accessibility š¤ but this video isn't present.
Moreover, this assertion is also outlined by the Apple support team:
Finally, don't use this container type in an iOS app for which the semanticGroup is definitely more appropriate and understood by VoiceOver regarding this OS. š
- Move accessibility focus programmatically
- Prevent VoiceOver to focus elements covered by modal when swipe navigating on iPad
- When to use accessibilityRole='link' in ReactNative?
- Voice over announcing unneccesary information
- Voice over: Read items of table cell separately - not as a whole
- How to make Voiceover to spell each letter in a word?
- How can I override a screen-reader's pronunciation of a word in a sentence without having it pause mid-sentence?
- Use aria-label on a span
- What Cisco unity connection messaging system does?
- how to control what voiceover reads when developing a website
- What is accessibilityTextHeadingLevel supposed to do?
- Voice Over Does Not Read Aria-label on iOS Safari but Screen Reader Reads on Chrome
- Adding buttonStyle for SwiftUI Widget intent button messes up VoiceOver
- Can a UIView object combine the accessibility properties of its children automatically?
- setAccessibilityFocus using ref not working
- How to control accessibility voiceover text for the SwiftUI Image
- Is there a way to detect VoiceOver focus change / user interaction at the `UIApplication` or `UIWindow` level?
- How do you swipe a DOM element in Chrome when VoiceOver is on?
- How can I make VoiceOver combine multiple span elements into one read item?
- How do I describe what row/column a <td> cell should read out as with VoiceOver?
- ReactJS accessibility issue Voiceover IOS
- Accessibility: Make VoiceOver read a text without focus on a Web page
- Web accessibility language detection with Voiceover
- Linebreak in a H1 turns the element into a VoiceOver group
- Vertical table headers read wrong in Voice Over on iOS and Mac
- VoiceOver Doesn't Read Colon on iPhone
- What is the purpose of the "landmark" accessibility container type?
- Disable VoiceOver on UIButton/UITableViewCell/UICollectionViewCell Selection
- VoiceOver: force an accessibility element to be selected after a screen transition
- How to setup accessibility containers so that gestures work properly?