E-mail List Archives
Thread: Simulate Voice Control
Number of posts in this thread: 5 (In chronological order)
From: wolfgang.berndorfer@zweiterblick.at
Date: Mon, Jun 21 2021 9:50AM
Subject: Simulate Voice Control
No previous message | Next message →
Is there a tool to simulate "aural" control over web content and apps for
keyboard only?
I think of desktop simulation without microphone.
Like the display simulation of Smart Phone in Firefox via Ctrl+Shift+M
It could be helpful to evaluate SC 2.5.3 Label in Name.
And it could be helpful to convince web developers.
From: Jonathan Avila
Date: Mon, Jun 21 2021 11:28AM
Subject: Re: Simulate Voice Control
← Previous message | Next message →
HI, there are tools and favlets that will show the accessible name of controls on screen. This is probably the best way for folks to easily check that the accessible name contains the on-screen label text.
Jonathan
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of = EMAIL ADDRESS REMOVED =
Sent: Monday, June 21, 2021 11:50 AM
To: 'WebAIM Discussion List' < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Simulate Voice Control
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Is there a tool to simulate "aural" control over web content and apps for keyboard only?
I think of desktop simulation without microphone.
Like the display simulation of Smart Phone in Firefox via Ctrl+Shift+M
It could be helpful to evaluate SC 2.5.3 Label in Name.
And it could be helpful to convince web developers.
From: wolfgang.berndorfer@zweiterblick.at
Date: Mon, Jun 21 2021 11:53AM
Subject: Re: Simulate Voice Control
← Previous message | Next message →
Hi Jonathan and all,
OK, which tools would you propose that show the Accessible Name strictly according to the specs?
Such a tool would make testing 2.5.3 so much easier with nested elements, titles, aria-labels and sr-only-CSS-classes to.
In my experience, JAWS and NVDA do not always show the same text for interactive elements, perhaps due to browser and configuration variants.
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Jonathan Avila
Sent: Monday, June 21, 2021 7:29 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Simulate Voice Control
HI, there are tools and favlets that will show the accessible name of controls on screen. This is probably the best way for folks to easily check that the accessible name contains the on-screen label text.
Jonathan
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of = EMAIL ADDRESS REMOVED =
Sent: Monday, June 21, 2021 11:50 AM
To: 'WebAIM Discussion List' < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Simulate Voice Control
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Is there a tool to simulate "aural" control over web content and apps for keyboard only?
I think of desktop simulation without microphone.
Like the display simulation of Smart Phone in Firefox via Ctrl+Shift+M
It could be helpful to evaluate SC 2.5.3 Label in Name.
And it could be helpful to convince web developers.
From: Patrick H. Lauke
Date: Mon, Jun 21 2021 1:30PM
Subject: Re: Simulate Voice Control
← Previous message | Next message →
On 21/06/2021 18:53, = EMAIL ADDRESS REMOVED = wrote:
> Hi Jonathan and all,
>
> OK, which tools would you propose that show the Accessible Name strictly according to the specs?
> Such a tool would make testing 2.5.3 so much easier with nested elements, titles, aria-labels and sr-only-CSS-classes to.
>
> In my experience, JAWS and NVDA do not always show the same text for interactive elements, perhaps due to browser and configuration variants.
Browser developer tools, in their Accessibility panel, will show you the
calculated accessible name, which in theory is what JAWS/NVDA should be
announcing (unless it's missing, in which case they'll apply their own
heuristics).
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: wolfgang.berndorfer@zweiterblick.at
Date: Tue, Jun 22 2021 10:39AM
Subject: Re: Simulate Voice Control
← Previous message | No next message
> Browser developer tools, in their Accessibility panel, will show you the calculated accessible name, which in theory is what JAWS/NVDA should be announcing (unless it's missing, in which case they'll apply their own heuristics).
Sorry but those panels always appeared hardly to use for me as a SR-user, even partially sighted. Then I prefer to browse the available code, I can save in the browser and analyze in an editor.
Any further proposals for SR users?
Wolfgang
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Patrick H. Lauke
Sent: Monday, June 21, 2021 9:30 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [WebAIM] Simulate Voice Control
On 21/06/2021 18:53, = EMAIL ADDRESS REMOVED = wrote:
> Hi Jonathan and all,
>
> OK, which tools would you propose that show the Accessible Name strictly according to the specs?
> Such a tool would make testing 2.5.3 so much easier with nested elements, titles, aria-labels and sr-only-CSS-classes to.
>
> In my experience, JAWS and NVDA do not always show the same text for interactive elements, perhaps due to browser and configuration variants.
Browser developer tools, in their Accessibility panel, will show you the calculated accessible name, which in theory is what JAWS/NVDA should be announcing (unless it's missing, in which case they'll apply their own heuristics).
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke