E-mail List Archives
Thread: Potential Firefox bug with W3C ARIA pattern?
Number of posts in this thread: 3 (In chronological order)
From: Graham Armfield
Date: Wed, Jul 27 2022 7:13AM
Subject: Potential Firefox bug with W3C ARIA pattern?
No previous message | Next message →
Hi All,
I've been having a look at the W3C's ARIA APG patterns and using them to
demo screen readers to developers. I've come across a situation in NVDA on
Firefox on one of the patterns where I'm not hearing expected
announcements. I'm not certain but I think it's a bug in Firefox, and I
wondered if anyone else had come across this.
It's on the Select-Only Combobox pattern at
https://www.w3.org/WAI/ARIA/apg/example-index/combobox/combobox-select-only.html
which effectively presents equivalent functionality to the HTML select
element.
When running NVDA over the working example in the page everything seems to
work OK, except that NVDA does not announce the current value of the
combobox - whether it's set to the initial default value or after selecting
one of the items to change the value to something else.
I've tried NVDA on the same page in Chrome and the current value is
announced. JAWS also announces the value in Chrome, but not in Firefox so
I'm guessing this is an issue in Firefox.
The value is presented as text inside a div with a role=combobox, and I'm
guessing that maybe the presence of aria-labelledby on the div might be
causing the suppression of the text.
Anyone got any thoughts on this?
Regards
Graham Armfield
coolfields.co.uk <http://www.coolfields.co.uk/>;
M:07905 590026
T: 01483 856613
@coolfields <https://twitter.com/coolfields>
From: Birkir R. Gunnarsson
Date: Wed, Jul 27 2022 6:49PM
Subject: Re: Potential Firefox bug with W3C ARIA pattern?
← Previous message | Next message →
I took a quick ook with the latest version of Jaws.
On Chrome the value of the combobox is always communicated (in close
or open state)
In Firefox the aria-activedescendant values are announced just fine
(while the comcobox is open and you arrow between the fruits), but the
value of the combobox is only announced sometimes when closed (i.e.
the selected value).
I have to dig deeper into the code to see if I can figure it out, but
this seems to be some sort of a potential Firefox/NVDA bug.
On 7/27/22, Graham Armfield < = EMAIL ADDRESS REMOVED = > wrote:
> Hi All,
>
> I've been having a look at the W3C's ARIA APG patterns and using them to
> demo screen readers to developers. I've come across a situation in NVDA on
> Firefox on one of the patterns where I'm not hearing expected
> announcements. I'm not certain but I think it's a bug in Firefox, and I
> wondered if anyone else had come across this.
>
> It's on the Select-Only Combobox pattern at
> https://www.w3.org/WAI/ARIA/apg/example-index/combobox/combobox-select-only.html
> which effectively presents equivalent functionality to the HTML select
> element.
>
> When running NVDA over the working example in the page everything seems to
> work OK, except that NVDA does not announce the current value of the
> combobox - whether it's set to the initial default value or after selecting
> one of the items to change the value to something else.
>
> I've tried NVDA on the same page in Chrome and the current value is
> announced. JAWS also announces the value in Chrome, but not in Firefox so
> I'm guessing this is an issue in Firefox.
>
> The value is presented as text inside a div with a role=combobox, and I'm
> guessing that maybe the presence of aria-labelledby on the div might be
> causing the suppression of the text.
>
> Anyone got any thoughts on this?
>
> Regards
> Graham Armfield
>
> coolfields.co.uk <http://www.coolfields.co.uk/>;
> M:07905 590026
> T: 01483 856613
> @coolfields <https://twitter.com/coolfields>
> > > > >
--
Work hard. Have fun. Make history.
From: Moiz Yamani
Date: Tue, Aug 02 2022 10:47PM
Subject: Re: Potential Firefox bug with W3C ARIA pattern?
← Previous message | No next message
Response:
Yes, here it seems to be Firefox bug wherein the inner text is not exposed =
to screen reader like JAWS/NVDA. As you can see within the below screenshot=
- this one is with the inner text being part of the <div> with role of com=
bobox - in DOM tree under Accessibility - the inner text value is not expos=
ed.
[The inner text being part of the <div> with role of combobox, in DOM tree =
under Accessibility, the inner text value is not exposed]
However, if we create a new node within the same div with role of combobox =
and provide the current value - it is getting exposed as you can see in the=
attached screenshot.[A new node within the same div with role of combobox =
and provide the current value, it is getting exposed]
Thanks and Best,
Moiz Yamani | Manager - Strategic Partnerships
BarrierBreak & 247 Accessible Documents
Email: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
BarrierBreak Solutions Private Limited