WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Recommendable settings for speak hints

for

Number of posts in this thread: 7 (In chronological order)

From: surbhi Mudgal
Date: Thu, Mar 08 2018 3:46AM
Subject: Recommendable settings for speak hints
No previous message | Next message →

Hi all

Warm Greetings.

As part of screen reader testing on mobile apps, would like to know what
is the recommendable setting for speak hints.
Whether this setting should be turned on or off?
Specially when testing a third party application.

Thanks in Advance.
Regards,
Surbhi Mudgal.

From: shankar shan
Date: Thu, Mar 08 2018 3:56AM
Subject: Re: Recommendable settings for speak hints
← Previous message | Next message →

Hi there,

as for as my concern, it has to be turned on.

the setting may explain to the user how to interact with the
perticular element/ctrl.

On 3/8/18, surbhi Mudgal < = EMAIL ADDRESS REMOVED = > wrote:
> Hi all
>
> Warm Greetings.
>
> As part of screen reader testing on mobile apps, would like to know what
> is the recommendable setting for speak hints.
> Whether this setting should be turned on or off?
> Specially when testing a third party application.
>
> Thanks in Advance.
> Regards,
> Surbhi Mudgal.
> > > > >


--
jammed and internet hanged?Reach through the following means:
mobile: +91 7795927572
whats app: +91 7795927572
skype: Shankar.a
email: = EMAIL ADDRESS REMOVED =
Thanks and regards
Shankar
*****
ACCESSIBILITY AND USABILITY TESTER AT Cerner Health Care Solutions.
*****

From: JP Jamous
Date: Thu, Mar 08 2018 5:10AM
Subject: Re: Recommendable settings for speak hints
← Previous message | Next message →

It depends on how comfortable you are with using the screen reader. For example, I find it to be too verbose and keep it turned off, but I am an advanced screen reader user.

If you are new to the application, then it can be quite beneficial to have it on. Just remember that it won't announce any hints if the objects are not providing their object type to the screen reader. Most likely, the screen reader would read those as static text, when in some situations they do receive finger taps.

From: Jonathan Cohn
Date: Thu, Mar 08 2018 6:33AM
Subject: Re: Recommendable settings for speak hints
← Previous message | Next message →

Yes, you should be somehow checking hints to verify that the default hint is appropriate for your interactions. Either you are doing that in the accessibility checker in for the OS or if you confirm them with actual phones. By default the Hints are enabled for but as already mentioned many advanced users turn them off.
Best wishes,

Jonathan Cohn



> On Mar 8, 2018, at 5:46 AM, surbhi Mudgal < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi all
>
> Warm Greetings.
>
> As part of screen reader testing on mobile apps, would like to know what
> is the recommendable setting for speak hints.
> Whether this setting should be turned on or off?
> Specially when testing a third party application.
>
> Thanks in Advance.
> Regards,
> Surbhi Mudgal.
> > > >

From: surbhi Mudgal
Date: Thu, Mar 08 2018 10:12PM
Subject: Re: Recommendable settings for speak hints
← Previous message | Next message →

But I see talkback does not announce the control type for many option like
button or tab and just announces the hints when they are turned on.
So my query here is whether this is android behaviour or due to bad code
practice the control types are not announced/missing.

Regards,

> Surbhi Mudgal.
>
>

From: JP Jamous
Date: Fri, Mar 09 2018 1:52AM
Subject: Re: Recommendable settings for speak hints
← Previous message | Next message →

I never used talked back, but it sounds like the control is not providing its object type. But it has hints included to accommodate for that missing object type.

I could be wrong though.

From: surbhi Mudgal
Date: Sun, Mar 11 2018 10:16PM
Subject: Re: Recommendable settings for speak hints
← Previous message | No next message

But I see talkback does not announce the control type for many option like button or tab and just announces the hints when they are turned on.
So my query here is whether this is android behaviour or due to bad code practice the control types are not announced/missing.

Regards,
> Surbhi Mudgal.