E-mail List Archives
Thread: Screen reader speed in demo
Number of posts in this thread: 4 (In chronological order)
From: Barry
Date: Sat, Aug 06 2022 8:39AM
Subject: Screen reader speed in demo
No previous message | Next message →
Hi all
When demonstrating the use of a screen reader to developers and designers,
is it better to reflect real world where the user may have the rate set to
high-speed, which has great impact but can be uninteligable to non-screen
reader users, or to have the rate set to a normal speaking rate that they
can understand? A compromise might be to demonstrate a power-user speed,
then to slow it down to an intelligable speed.
Thanks in anticipation.
Cheers
Barry
A11y tip: To Make Your tabular HTML Emails More Accessible for screen
readers, use the ARIA presentation role.
From: Karen McCall
Date: Sat, Aug 06 2022 8:52AM
Subject: Re: Screen reader speed in demo
← Previous message | Next message →
I demonstrate both. Well I don't use my screen reader at the highest speed I've seen other people use it, it's a good indication to people who aren't familiar with screen readers on how the screen reader is actually used.
When I explain why not to use abbreviations in labels or other aspects of the user interface, I use the speed I read at so that they can understand that sometimes when you're reading something fast abbreviations can be misinterpreted.
When I'm going through the user interface piece by piece and want them to understand what the screen reader is saying, I slow jazz down to about 15% speed.
I also use the Eloquence synthesizer because this is the one that I use, and it gives a more realistic perspective of the screen reader.
Some of the natural phone invoices don't have pronunciation dictionaries that are as complete as the eloquent synthesizer. This is another reason that I use that synthesizer. I also take the opportunity to explain the difference between the old robotics synthesized voices such as eloquence and the natural phone invoices that most people would prefer to use.
Cheers, Karen
Sent from Outlook<https://aka.ms/qtex0l> for iOS
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > on behalf of Barry via WebAIM-Forum < = EMAIL ADDRESS REMOVED = >
Sent: Saturday, August 6, 2022 10:39:59 AM
To: = EMAIL ADDRESS REMOVED = < = EMAIL ADDRESS REMOVED = >
Cc: = EMAIL ADDRESS REMOVED = < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Screen reader speed in demo
Hi all
When demonstrating the use of a screen reader to developers and designers,
is it better to reflect real world where the user may have the rate set to
high-speed, which has great impact but can be uninteligable to non-screen
reader users, or to have the rate set to a normal speaking rate that they
can understand? A compromise might be to demonstrate a power-user speed,
then to slow it down to an intelligable speed.
Thanks in anticipation.
Cheers
Barry
A11y tip: To Make Your tabular HTML Emails More Accessible for screen
readers, use the ARIA presentation role.
From: David Farough
Date: Thu, Aug 18 2022 8:42AM
Subject: Re: Screen reader speed in demo
← Previous message | Next message →
All good points to consider.
Make sure the screen reader is highlighting text as it is read.
Both JAWS and NVDA have this feature.
That should help people understand the text.
Keeping the speech setting to a moderate rate on balance will help you make=
your points.
I like the point on speech rate with abbreviations and labels. I hadn't tho=
ught of that before.
From: Darryl Drozdik
Date: Thu, Aug 18 2022 9:27AM
Subject: Re: Screen reader speed in demo
← Previous message | No next message
When I was looking at âdemosâ on Youtube it would have helped to get an idea of how fast a power user might use the screen reader. Like, quickly blow through some tasks just to give UX'ers like me an idea of what we're dealing with. Then slow it down so we can comprehend the reads, pauses, keystrokes, etc. I'd be interested in watching the demonstration if you happen to record it!
Regards,
Darryl
> On Aug 6, 2022, at 9:39 AM, Barry via WebAIM-Forum < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi all
>
>
>
> When demonstrating the use of a screen reader to developers and designers,
> is it better to reflect real world where the user may have the rate set to
> high-speed, which has great impact but can be uninteligable to non-screen
> reader users, or to have the rate set to a normal speaking rate that they
> can understand? A compromise might be to demonstrate a power-user speed,
> then to slow it down to an intelligable speed.
>
>
>
> Thanks in anticipation.
>
>
>
> Cheers
>
>
>
> Barry
>
>
>
> A11y tip: To Make Your tabular HTML Emails More Accessible for screen
> readers, use the ARIA presentation role.
>
>
>
> > > >