Re: Best practices for wording of accessibility hints
Re: Best practices for wording of accessibility hints
- Subject: Re: Best practices for wording of accessibility hints
- From: Ilya Konstantinov <email@hidden>
- Date: Sat, 07 Oct 2017 23:40:41 +0000
Apple is a pretty big company, so its engineers might stray from guidelines
written by other engineers. Eventually we should probably listen to our own
users rather than Apple (or some foolish principles of "consistency"), at
least as long as the App Store reviewers don't enforce the accessibility
guidelines :)
In the Lyft app we also occasionally add "double tap to ..." hints contrary
to Apple's guidelines, where we find that otherwise it wouldn't be obvious.
On Sat, Oct 7, 2017 at 3:32 PM Jamal Mazrui <email@hidden>
wrote:
> Sending again in hope of a response.
>
>
> On 9/19/2017 7:00 AM, Jamal Mazrui wrote:
> > The official guidance from Apple on accessibility hints seems to be
> > contradicted by practices in its builtin apps for iOS. The following
> > points are recommended (my wording):
> >
> >
> > Non-obvious. A hint is only supposed to be given if the functionality
> > is not obvious from other information such as label and role
> > information. Yet, there are examples of a hint like "Double tap to
> > open" when that is obvious, e.g., opening an app from the Home screen.
> >
> >
> > No mention of gesture. The gesture to invoke an action, e.g., "Double
> > tap," is not supposed to be included in the hint since there may be
> > multiple ways of invoking an action. Yet, there are numerous examples
> > of gestures being mentioned.
> >
> >
> > Third person perspective. The hint is not supposed to be worded in a
> > second person perspective, telling you what to do to achieve an
> > action. Instead, it is supposed to describe the result of an action
> > from the standpoint of the control, e.g., "Opens book" rather than
> > "Open book." This practice is regularly violated as well.
> >
> >
> > Has Apple changed its mind about best practices for accessibility
> > hints or is it just failing in implementing its own guidelines? I am
> > not attached to particular practices, except for being as succinct in
> > wording as possible for hearing efficiency. I do want to adopt
> > consistent, best practices in this area.
> >
> >
> > Thoughts?
> >
> >
>
> _______________________________________________
> 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