Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is iOS's three finger zoom defined as "assistive technology" on native mobile apps? #527

Open
doesDesign opened this issue Oct 10, 2024 · 1 comment

Comments

@doesDesign
Copy link

doesDesign commented Oct 10, 2024

Hello! I am struggling to understand the definition of "assistive technology" on native mobile.

Comments by @maryjom in #4 suggest the native magnifier on iOS is now a valid way to pass 1.4.4 for mobile apps:

"features including software provided by the platform that provide a means of enlarging the text 200% (zoom or otherwise) without the loss of content or functionality, meet the intent of this success criteria."

The native three finger zoom in iOS is a software feature provided by the platform (iOS) that enlarges text to 200%. It's mainstream, doesn't require third party software to be installed, etc. I've also read through the W3C meeting minutes and can confirm text is not pixelated when using the feature.

If nothing changes from WCAG, then why say anything at all? I can't wrap my head around any other interpretation of this text.

If three finger zoom is still assistive technology because it's designed for users with impaired vision, why is iOS' font resizing (notably the "additional accessibility sizes" required to hit 200%) not assistive technology? That clearly falls beyond mainstream usage into specialized targeted functionality that meets the definition of AT.

In my personal opinion these definitions fall apart under scrutiny.

Why it matters

There are various edge cases on mobile where it is impossible to enlarge text to 200% without failing other SC or breaking the layout.

In mobile apps we don't have the luxury of pinch to zoom that mobile web has, which multiple W3C contributors have mentioned is viable (@patrickhlauke is a great example).

Sometimes we can fall back on Apple's Large Content Viewer or similar, but in a sufficiently complex and large mobile app there will be edge cases where even that is not viable.

Anyways thank you in advance for clarifying. I have done a deep dive into lots of WC3/WCAG material and I am still really struggling with this definition.

@maryjom
Copy link
Contributor

maryjom commented Oct 15, 2024

The definition of “assistive technology” in the updates WCAG2ICT is the same definition that was in the 2013 version of the WCAG2ICT Note and is the same used in WCAG. This is a more general issue for any content viewed on a mobile device and what is (or isn’t) considered assistive technology for mobile devices. The Accessibility Guideline Working Group is the group responsible for reviewing and (possibly) updating the definition. Consider opening an issue in the WCAG GitHub space that the AG WG monitors – we’d also be interested in their thoughts on this matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants