W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2015

Re: IOS Accessibility Properties Questions

From: Jim <jhomme1028@gmail.com>
Date: Tue, 28 Jul 2015 06:56:55 -0400
Cc: "<w3c-wai-ig@w3.org>" <w3c-wai-ig@w3.org>
Message-Id: <7D3F6505-9054-4850-8EAD-BD582F41E783@gmail.com>
To: "<lwatson@paciellogroup.com>" <lwatson@paciellogroup.com>

Is it a common practice to put content off screen if you want to hide it from the visual aspect of the page, if you want to use a hand and have it acted like it would normally act in native iOS?

Thanks. Jim

On Jul 27, 2015, at 7:29 PM, Léonie Watson <lwatson@paciellogroup.com> wrote:

>> From: Jim [mailto:jhomme1028@gmail.com]
>> Sent: 27 July 2015 15:35
>> I have a series of questions, all related. Is there a listing somewhere that
>> describes how to properly use the IOS accessibility hint property on the web?
> You would only use the iOS hint property in a native iOS app. This article from 2012 has information on how to do this:
> http://www.creativebloq.com/ipad/make-your-ios-app-accessible-voiceover-8126162 
> The most common design pattern for hints on the web, is to use aria-describedby to associate hint text with a control. This corresponds to the accessible description in most accessibility APIs.
> Léonie.
> -- 
> Léonie Watson - Senior accessibility engineer, TPG
> @LeonieWatson @PacielloGroup
Received on Tuesday, 28 July 2015 10:57:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:57 UTC