- From: Ta, Duc <duc.ta.740@my.csun.edu>
- Date: Mon, 27 Jul 2015 16:45:41 -0700
- To: Jim <jhomme1028@gmail.com>
- Cc: w3c-wai-ig@w3.org
- Message-ID: <CAOcfqAQGVwrMuJ0zqoZP+xy0tdt6_S4tzkoFQbA5X7VaQE5CJQ@mail.gmail.com>
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 Monday, 27 July 2015 23:46:10 UTC