Repository navigation
Non-text contrast of the iOS native focus indicator for external keyboard navigation: author responsibility or AT support gap? #5441
Unanswered
edagercari
asked this question in
Q&A
Replies: 2 comments 4 replies
|
If your components leave the iOS system focus effect as it is, its contrast isn't a 1.4.11 failure of your content. Record it as a platform limitation (advisory), not a WCAG fail.
It stops being exempt once you change it, for example with a custom So when testing:
Adding your own ring on top of the system one is good practice, not a requirement. |
1 reply
|
My interpretation is that if the author changes the background colour, they are changing the appearance of the focus indicator, so the exemption does not apply. Otherwise, they could set the background colour to be very similar to the default focus indicator colour, resulting in very low contrast.
Steve Green
Managing Director
Test Partners Ltd
From: Muhammad Ahmed ***@***.***>
Sent: 02 November 2026 14:12
To: w3c/wcag ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [w3c/wcag] Non-text contrast of the iOS native focus indicator for external keyboard navigation: author responsibility or AT support gap? (Discussion #5441)
If your components leave the iOS system focus effect as it is, its contrast isn't a 1.4.11 failure of your content. Record it as a platform limitation (advisory), not a WCAG fail.
* 1.4.11 exempts the visuals of a component "where the appearance of the component is determined by the user agent and not modified by the author". For native apps, WCAG2ICT says to read "user agent" there as "user agent or other platform software" (WCAG2ICT: Applying SC 1.4.11<https://www.w3.org/TR/wcag2ict-22/#applying-sc-1-4-11-non-text-contrast-to-non-web-documents-and-software>).
* Understanding 1.4.11<https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html> says the same for focus indicators: they need 3:1 "except where the appearance of the component is determined by the user agent and not modified by the author". Its "Default focus style" example: a default focus style the author didn't adjust is exempt from the contrast requirement but must still be visible (2.4.7).
* The Full Keyboard Access indicator is drawn by iOS, and the user picks its color, so it's that platform case.
It stops being exempt once you change it, for example with a custom focusEffect<https://developer.apple.com/documentation/uikit/uiview/focuseffect> or your own focus ring. That one must meet 3:1 against the adjacent colors, like your 2px outline on Android.
So when testing:
* System indicator untouched and visible: 2.4.7 passes and 1.4.11 doesn't apply. Note it as advisory if you want to flag it.
* Author-modified or custom indicator: test it against 1.4.11.
Adding your own ring on top of the system one is good practice, not a requirement.
—
Reply to this email directly, view it on GitHub<#5441?email_source=notifications&email_token=ACSY764XYPAW4YTXLJ22D7D5XCI4PA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJTGUZDKOBSUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FMMZXW65DFOJPWG3DJMNVQ#discussioncomment-19352582>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACSY764BJBX27UFLITVEIDD5XCI4PAVCNFSNUABGKJSXA33TNF2G64TZHM4TSNRXG4YDEO2ENFZWG5LTONUW63R3GEYTCOBYGA3TDILWAI>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/ACSY765PVMNZ2MW424O4I5D5XCI4PA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJTGUZDKOBSUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FKMZXW65DFOJPWS33T> and Android<https://github.com/notifications/mobile/android/ACSY76547QN64GKD4UQGHJ35XCI4PA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJTGUZDKOBSUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FOMZXW65DFOJPWC3TEOJXWSZA>. Download it today!
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I’m working on accessibility testing for UI components and would love some input from the community on a situation I’ve run into with iOS.
When navigating an iOS app with an external keyboard, the native focus indicator is a color overlay whose color the user can customize in system settings. While this indicator satisfies SC 2.4.7 Focus Visible, most of the available colors don’t meet the 3:1 contrast ratio required by SC 1.4.11 Non-text Contrast.
On Android, I addressed a similar issue by recommending a custom 2px focus outline for our components, and I considered doing the same for iOS. I’m aware that the Android default focus highlight is also platform-provided, but there, a custom indicator cleanly replaces it. On iOS, the system indicator can’t be restyled and is customizable by the user. Because of this, I’m unsure whether component authors are expected to supplement it with a custom focus ring, or whether this falls outside the author’s responsibility.
When testing components, should I report this as a WCAG failure, or would it be more accurate to document it as an assistive technology support gap?
I’d really appreciate any guidance, references to the Understanding documents, or insight into how others have handled this in practice.
Thanks in advance!
All reactions