E-mail List Archives
Thread: Text not read by screenreader on first focus.
Number of posts in this thread: 5 (In chronological order)
From: glen walker
Date: Mon, Jan 16 2023 7:53PM
Subject: Re: Text not read by screenreader on first focus.
No previous message | Next message →
Sounds like 4.1.2 Name, Role, Value (
https://www.w3.org/TR/WCAG21/#name-role-value)
If the label of the dropdown is announced, then it passes the "Name" part.
If the element is read as a "dropdown" or "combobox" (or similar), then it
passes the "Role" part.
It's the last part, the "Value" of the dropdown that doesn't sound like
it's being announced until you change the value. That would fail.
From: Mark Magennis
Date: Wed, Jan 18 2023 1:17AM
Subject: Re: Text not read by screen reader on first focus.
← Previous message | Next message →
Hi Kevin,
Have you ruled out the possibility that it may be a screen reader bug?
In some cases name, role, and value may all be exposed correctly but a screen reader may not read them due to a bug in the screen reader, not a fault of the coding. This would not be a WCAG failure (arguably, notwithstanding the Accessibility Supported issue).
What's in your dropdown? If it's a menu and the first item is a menuitemcheckbox or menuitemradio and if you are using NVDA, then you will get the behaviour you describe due to an NVDA bug.
Mark
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Kevin Prince
Sent: Tuesday 17 January 2023 03:10
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [EXTERNAL] Re: [WebAIM] Text not read by screenreader on first focus.
Excellent - value is the bit I was struggling to find.
Kevin Prince
Product Accessibility & Usability Consultant
Foster Moore
A Teranet Company
E = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
Christchurch
fostermoore.com<http://www.fostermoore.com/>;
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> On Behalf Of glen walker
Sent: Tuesday, 17 January 2023 3:53 pm
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >>
Subject: Re: [WebAIM] Text not read by screenreader on first focus.
CAUTION: This email originated from outside of the organization.
Sounds like 4.1.2 Name, Role, Value (
https://www.w3.org/TR/WCAG21/#name-role-value)
If the label of the dropdown is announced, then it passes the "Name" part.
If the element is read as a "dropdown" or "combobox" (or similar), then it passes the "Role" part.
It's the last part, the "Value" of the dropdown that doesn't sound like it's being announced until you change the value. That would fail.
From: Steve Green
Date: Wed, Jan 18 2023 1:52AM
Subject: Re: Text not read by screen reader on first focus.
← Previous message | Next message →
That's possible, but it could also be an incorrect calculation of the aria-activedescendant value.
Steve Green
Managing Director
Test Partners Ltd
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Mark Magennis
Sent: 18 January 2023 08:17
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] [EXTERNAL] Re: Text not read by screen reader on first focus.
Hi Kevin,
Have you ruled out the possibility that it may be a screen reader bug?
In some cases name, role, and value may all be exposed correctly but a screen reader may not read them due to a bug in the screen reader, not a fault of the coding. This would not be a WCAG failure (arguably, notwithstanding the Accessibility Supported issue).
What's in your dropdown? If it's a menu and the first item is a menuitemcheckbox or menuitemradio and if you are using NVDA, then you will get the behaviour you describe due to an NVDA bug.
Mark
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Kevin Prince
Sent: Tuesday 17 January 2023 03:10
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [EXTERNAL] Re: [WebAIM] Text not read by screenreader on first focus.
Excellent - value is the bit I was struggling to find.
Kevin Prince
Product Accessibility & Usability Consultant
Foster Moore
A Teranet Company
E = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
Christchurch
fostermoore.com<http://www.fostermoore.com/>;
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> On Behalf Of glen walker
Sent: Tuesday, 17 January 2023 3:53 pm
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >>
Subject: Re: [WebAIM] Text not read by screenreader on first focus.
CAUTION: This email originated from outside of the organization.
Sounds like 4.1.2 Name, Role, Value (
https://www.w3.org/TR/WCAG21/#name-role-value)
If the label of the dropdown is announced, then it passes the "Name" part.
If the element is read as a "dropdown" or "combobox" (or similar), then it passes the "Role" part.
It's the last part, the "Value" of the dropdown that doesn't sound like it's being announced until you change the value. That would fail.
From: Kevin Prince
Date: Mon, Jan 30 2023 6:25PM
Subject: Re: Text not read by screen reader on first focus.
← Previous message | Next message →
Thank you sir - that is possibly the issue - I wasn't aware of the bug. It's the first item in a filtered selection
I shall try it with Voiceover
Kevin Prince
Product Accessibility & Usability Consultant
From: Kevin Prince
Date: Mon, Jan 30 2023 7:35PM
Subject: Re: Text not read by screen reader on first focus.
← Previous message | No next message
Hi Mark,
Thank you, this has been both a bane for me, and for the developers. I just went back systematically and ran through the bug on a MAC - bingo. It speaks to me. So it's highly likely it's the NVDA bug. I shall try JAWS now, assuming my IT team have it enabled (Not the obvious thing it might seem)
Kevin
Kevin Prince
Product Accessibility & Usability Consultant