-
-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aria-expanded status not announced when ::before element has content #8341
Comments
It looks like in the second example, the node with focus (the button) is being completely replaced each time it is expanded or collapsed. Thus, to NVDA the expanded/collapsed state is not just changing, but rather the focus in its entireity is changing. |
@jcsteh: possibly another real-world testcase where Firefox is re-creating an Accessible element because of a change in CSS. |
Correct. Mozilla bug 395900. |
Thanks for sorting this out, guys. |
Reopened as #8869 had to be reverted for now. |
Hello. Should #5247 be reopened as well? |
I'm seeing this issue even without a pseudo element. Firefox 69.0 + NVDA 2019.2 |
Yes this is also reproducible for me. |
Fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=686400 in Firefox 70 (currently in beta). |
Hi there, looks like this issue still reproduce in Chrome. NVDA blocked events for keypress ENTER/SPACE when pseudo element :before is changed on expand state. Demo: https://codepen.io/accessibility-developer-guide/pen/VdwvwW |
I'm working on a simple dropdown implementation. Using JavaScript, an
aria-expanded
attribute is toggled betweenfalse
andtrue
, and its specific content's visibility is toggled then.I'm used to NVDA announcing a change of
aria-expanded
very reliably when the focus is on the specific link or button.Demo: https://codepen.io/accessibility-developer-guide/pen/pKoJbK
But I noticed that when this link or button has some content with
::before { content: '...' }
, the change is not announced anymore.Demo: https://codepen.io/accessibility-developer-guide/pen/VdwvwW
I wanted to display a
+
or-
sign in front of the dropdown toggler to indicate its status visually. But this doesn't seem to work withcontent: '...'
.Is this expected behaviour? Or a bug?
The text was updated successfully, but these errors were encountered: