Mugentoki

The way I read it in the readme, that the protected text is set to aria hidden. So a screen reader doesn't even get the gibberish stuff. It just silently stares into a blank website. @mmcknett@hachyderm.io @ralen@social.ralen.top @nixCraft@mastodon.social

@ojrask Completely agree with you. Also I wanna throw something else in: Ignoring accessibility can lead to serious fines. In the European Union for example, we have the "European Accessibility Act (EEA)" which basically requires you to comply with WCAG2 rules. At least if you offer products or services. Fines are depending on the country, but can go up into millions of €.

@gnuplusmatt@fosstodon.org Instead of moving forward, there's a better way to solve it. Let Joe Flanigan finally purchase the franchise.

@tixie@mastodon.guerilla.studio It's definitely possible! Media queries, depending on the desired screen size -> that's your condition https://www.w3schools.com/css/css_rwd_mediaqueries.asp Then: position: static/fixed/sticky; Depending on what kind of popover you want. (Or static to disable the popover again) https://www.w3schools.com/css/css_position.asp

@Isofruit@mastodon.social You are absolutely right and I mostly agree with you. I probably misread it. However, CSS has to do with WCAG, as some assisting tools have the ability to change colours, sizes and so on. So semantic CSS could (or probably should) help a lot to properly use those tools.