WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Apple Accessibility API


From: Jonathan Avila
Date: Feb 27, 2020 7:28AM

Hi Sean, any UI elements that implement the UIAccessibility protocol will have all of those properties and methods available. However, setting a value on a control with a button trait won't have any impact on VoiceOver or other assistive technology. Based on some tests I did several years ago I was able to set these properties in code even if they are hidden in the UI of Xcode -- but setting extra properties was generally ignored by VoiceOver when they were not relevant to the to the control's traits.

It is not possible to create custom traits or properties -- although traits can be created in combination such as a button that is disabled, etc. Some combinations obviously won't make sense even if you can set those combination of traits in the code.


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Murphy, Sean
Sent: Wednesday, February 26, 2020 10:01 PM
Subject: [WebAIM] Apple Accessibility API

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.

Is anyone on the list knowledgeable about how States work on the iOS platform?

For example if UIAccessibilityTraitButton is defined with the correct below properties:
accessibilityLabel - The accessibilityLabel should have to return the suitable word to describe the element.
accessibilityValue - Describes the value of an element accessibilityHint - accessibilityHint can have a phrase to describe what happens when you choose action on an element

Does the object for button contain the relevant states? Can you custom build the states in an class / object?

Is there a dedicated list for accessibility iOS mobile?