RE: iOS Accessibility Settings ~ auto-magically compliant?

All,

Would anyone have a similar link for Android? Searched, but cannot find the right resource.

[https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/02_standard_ciscoblue02.png]
Sean Murphy
SR ENGINEER.SOFTWARE ENGINEERING
seanmmur@cisco.com<mailto:seanmmur@cisco.com>
Tel: +61 2 8446 7751




Cisco Systems, Inc.
The Forum 201 Pacific Highway
ST LEONARDS
2065
Australia
cisco.com
[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]
Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html> for Company Registration Information.


From: Jonathan Avila <jon.avila@levelaccess.com>
Sent: Wednesday, 18 September 2019 12:42 AM
To: caroline <woodward.caroline@gmail.com>; w3c-wai-ig@w3.org
Subject: RE: iOS Accessibility Settings ~ auto-magically compliant?

Below is a link to the iOS UIAccessibilityIsOnOffSwitchLabelsEnabled function (and links to other similar functions)
https://developer.apple.com/documentation/uikit/3131973-uiaccessibilityisonoffswitchlabe?language=objc


I agree with others that you can’t rely on settings in the platform to meet contrast requirements.

Jonathan

From: caroline <woodward.caroline@gmail.com>
Sent: Monday, September 16, 2019 8:13 PM
To: w3c-wai-ig@w3.org
Subject: iOS Accessibility Settings ~ auto-magically compliant?

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

I asked a group of accessibility subject matter experts this question but wanted to extend it to this discussion group. I admit I'm rather hoping that a note in the WCAG that speaks to this situation might be possible.

  *   Does iOS's Accessibility Settings, excuse designers and developers from ensuring that the default view is accessible?
  *   What is your view on custom components, is it bad that they aren't connected to the suite of iOS Accessibility Settings?
  *   If a person or organization complains about the accessibility of an iOS item that is a native iOS item. Who is at fault? (This one is more of a legal question and my brain immediately thought of Winn-Dixie when I was added this..)
For example:
Can designers now choose text colors that don't meet contrast requirements?
Is it ok that the native iOS switch is not contrast compliant because iOS Accessibility Settings has a switch that enables the appearance of a visible label?

My view is that this situation isn't unlike a website and browser settings. We don't rely on users adjusting their browser settings to make elements of the site accessible and so why would it be any different for mobile?

At the moment, I'm asking for custom radio buttons and checkboxes. I was informed by the iOS mobile dev team that their concern is that custom items are not associated with Apple's Accessibility Settings. Also if something were to happen I was asked wouldn't that be more of the fault of Apple for not having a native radio button or checkbox? Again I keep thinking Winn-Dixie.

This is a topic that repeatedly resurfaces at the organization I work for. I do my best to reach out to other accessibility specialists because I would just be the opinion of 1 at my organization. I think it would be helpful to have this documented. Especially for folks who are working on changing the minds of some folks who are new to accessibility.