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
{{ message }}
Repository navigation
Theme accessibility-ready guidelines: address CSS generated content alternative text #362
Currently, we address several specific resolutions to decorative images needing to be hidden. We do not address the option to use CSS generated content alternatives, e.g. content: '\f26e' / '';. This means that to strictly meet the guidelines, a theme author using generated content would potentially have to change their output HTML in order to meet the requirement.
However, particularly for themes that have already been released, making HTML changes can introduce breaking changes for child themes and extenders, which may make them unwilling to make those changes.
I think we should allow defining empty alternative text for CSS generated content as an option.
Activity
rianrietveld commentedon Jul 3, 2026
@joedolson This could also be a topic page. Content in CSS.