Re: Making a two state switch more accessible than just a checkbox
Re: Making a two state switch more accessible than just a checkbox
- Subject: Re: Making a two state switch more accessible than just a checkbox
- From: Josh Scotland <email@hidden>
- Date: Mon, 15 Oct 2012 22:52:06 -0700
Hi Doug,
> I'm looking for the initial state and changing state announcement behavior of check box, but the custom action descriptions of button and it would be nice to have a completely custom help text that doesn't say checkbox or button but instead uses a custom description.
I took a look at your project and you almost had it working. Since you have two different button states, try using a SplitGroup role and a SortButton subrole. Then all you need for the action description is "turn".
> As an aside, not having documentation for the expected behaviors of the different roles is really frustrating.
Is this the documentation you're looking for?
http://developer.apple.com/library/mac/#documentation/UserExperience/Reference/Accessibility_RoleAttribute_Ref/Role.html
If you haven't been using it already, a really handy accessibility debugging tool is the Accessibility Inspector, which is bundled with Xcode.
http://developer.apple.com/library/mac/#documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXTesting/OSXAXTestingApps.html
Josh
On Oct 15, 2012, at 8:44 PM, Doug Russell <email@hidden> wrote:
> I'm creating a two state switch that's very similar to the on/off switch in the Time Machine preference pane, but in my case the two values aren't on and off, but rather two values worth describing more specifically than check or unchecked.
>
> I tried overriding accessibilityActionDescription: but the checkbox role never calls accessibilityActionNames or accessibilityActionDescription:.
>
> I then tried switching to the button role, which still doesn't call accessibilityActionNames but does call accessibilityActionDescription:.
>
> However with the button role, I don't see a way to cause it to read it's initial value or announce it's value on value changes the way that the check box role does.
>
> Both roles don't use the action or role description I supply in their help text which seems confusing for users.
>
> I'm looking for the initial state and changing state announcement behavior of check box, but the custom action descriptions of button and it would be nice to have a completely custom help text that doesn't say checkbox or button but instead uses a custom description.
>
> Here's a sample app to demonstrate the issue: http://cl.ly/0S3B3M470a41
>
> As an aside, not having documentation for the expected behaviors of the different roles is really frustrating.
>
> - Doug Russell
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Accessibility-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden