Found 6 bookmarks
Newest
ARIA/HTML relationship Severance
ARIA/HTML relationship Severance
By @SteveFaulkner@mastodon.social
What I found back then was that aria relationship attributes didn’t work when an element being referenced was outside the shadow DOM and the element referencing it was inside the shadow DOM, ditto for the opposite. It was same story for native HTML relationships as well. Fast forward to 11 years later, as in now! 2025, and the situation remains the same.
You could use standard HTML controls without all that stinking DOM darkness and encapsulation fandango fucking up your relationships. Defy the JavaScript industrial complex by any means necessary If this is not an option, then there are some ways you can work around these issues in some cases. A relatively simple example is provided:
#aria#shadow dom#html
·html5accessibility.com·
ARIA/HTML relationship Severance
Don’t Use aria-label on Static Text Elements
Don’t Use aria-label on Static Text Elements
This is why it is essential to check for correctimplementations according to the spec first and then verify using assistive technologies. If you follow the spec, you do not run into these cases where assistive technologies try to repair broken code to ensure access.
#aria#roles#html
·benmyers.dev·
Don’t Use aria-label on Static Text Elements
Accessible Description Exposure
Accessible Description Exposure
If you have little experience with ARIA, screen readers, or testing in general, understanding accessible descriptions can be trickier than understanding accessible names (already confusing for many). I have written explanations so many times for clients and in fora that I opted to put this together so I maybe never…
#aria#inputs#html
·adrianroselli.com·
Accessible Description Exposure