Hi everyone.
I'm developing custom control, new incarnation of well-known ShortcutRecorder. New implementation has the following design:
In inactive mode, control appears like a usual button:
<Screen Shot 2012-12-19 at 0.19.15.png>
Once clicked, it becomes active:
<Screen Shot 2012-12-19 at 0.20.37.png>
The snap back button cancels editing and the clear button removes current shortcut.
I was inspired by WWDC videos from 2010 and 2012 to bring Accessibility support to this control.
Here is my vision of how should it work:
Once a user moves VoiceOver cursor to the control, I want it to pronounce View's Description (e.g. assigned in IB) and current shortcut.
Once a user starts editing, he should be able to start interacting with control (move inside the control) and navigate to the snapback and clear buttons.
I decided that the best role for the control would be Button. Unfortunately I have no idea ho solve the following issue:
- Either pronounce both Description and Value (current shortcut) or pronounce only Description and make Value somehow accessible (e.g. by special VO shortcut)
- Make it pronounce Value after shortcut was typed
I would very appreciate any help regarding my Accessibility design and problems.
Best regards,
Ilya Kulakov
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