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
Hi!
We are currently validating the accessibility of our website using various tools, and we've encountered an issue related to WCAG 2.2 guideline 1.3.1. The problem seems to be caused by the use of :after or :before pseudo-elements in the CSS.
According to accessibility best practices, it's generally not recommended to generate content purely via CSS. However, we've found the following example in cookieconsent.css:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
We are currently validating the accessibility of our website using various tools, and we've encountered an issue related to WCAG 2.2 guideline 1.3.1. The problem seems to be caused by the use of :after or :before pseudo-elements in the CSS.
According to accessibility best practices, it's generally not recommended to generate content purely via CSS. However, we've found the following example in cookieconsent.css:
Do you have any suggestions or solutions regarding this?
Thanks a lot in advance!
Beta Was this translation helpful? Give feedback.
All reactions