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:53:33 -0400
Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-Id: <2BC3A930-6BC8-4034-B102-B6DB998F51EA@gmail.com>
To: "Ta, Duc" <duc.ta.740@my.csun.edu>

> Hello, does the title attribute do anything visually in a mobile browser?

Thank you. Jim 
> On Jul 27, 2015, at 7:45 PM, Ta, Duc <duc.ta.740@my.csun.edu> wrote:
> I think you can use hint property in native app. For common design on the web, the hint is usually coming from the accessible description which I think most people are using aria-describedby and some uses title. For native app, I think you can try to use Accessibility Inspector which is part of X-Code to check the accessibility state, role, name and description (correct me if I'm missing anything).
>> On Mon, Jul 27, 2015 at 4: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:54:05 UTC

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