You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing I noticed is that when enabling these a11y features, the output of the title and desc elements do not have ID’s associated with them, which the aria-labelledby attribute expects.
I find the SitePoint article that was referenced a bit confusing here, because they do give these element ID’s, but the name of the ID’s are also the name of the elements themselves:
Not only is that hard to follow, there’s also a problem in that these ID’s are super generic and are in high risk of accidentally colliding with a duplicate ID somewhere else on the page. And we all know that ID’s need to be unique. Maybe an example like the following would be a bit more clear:
I was super happy to find out about the new accessibility features introduced! Thank you for that.
One thing I noticed is that when enabling these a11y features, the output of the
title
anddesc
elements do not have ID’s associated with them, which thearia-labelledby
attribute expects.I find the SitePoint article that was referenced a bit confusing here, because they do give these element ID’s, but the name of the ID’s are also the name of the elements themselves:
Not only is that hard to follow, there’s also a problem in that these ID’s are super generic and are in high risk of accidentally colliding with a duplicate ID somewhere else on the page. And we all know that ID’s need to be unique. Maybe an example like the following would be a bit more clear:
Ultimately what I’m getting at here is that
inline_svg
is currently referencing thetitle
anddesc
elements, instead of ID’s:Making the ID’s unique is the interesting part; maybe a simple hash could help here?
The text was updated successfully, but these errors were encountered: