Posts
-
Grrrrr. -
A person I know who is in the early stages of a career in accessibility is hoping to find a screen reader user with web development experience to mentor them for a while.A person I know who is in the early stages of a career in accessibility is hoping to find a screen reader user with web development experience to mentor them for a while. They're a screen reader user themselves and they want to level-up their knowledge of HTML/CSS/JavaScript/ARIA in order to offer better recommendations when testing for accessibility. If this is you, or if you know someone it might be, drop me a DM? Thanks.
-
Introducing Slowww.ml – the slow web server@Edent It did play a bit of havoc with my screen reader though - I suspect because as the content gradually loaded it forced the DOM to rebuild which in turn forced the accessibility tree to be rebuilt.
-
Introducing Slowww.ml – the slow web server@Edent It did, yes. Some content about slow content loading and 20 characters/second average reading rate and some other stuff.
-
What are some of the biggest accessibility fails you found on a website where the people building the site wanted to do something good but actually made the situation worse, e.g. by using verbose alt texts, overusing ARIA, etc.?@matuzo My current "favourite" is the British Airways website. Once you're logged in there are parts of the website with `role="application"` applied to a container that holds all of the page content.
-
Dev Tools AI first try: a mix of nonsense and okay advice.@matuzo Back in the day I remember someone solving this by making part of the text the link (the heading for example) then using JS to expand the clickable area over the whole lot. No idea if that's still an advisable technique or not though.
-
If you're concerned what might happen to your .io domain, @tantek.com has some practical suggestions:https://tantek.com/2024/285/t1/io-domain-suggested-stepsIf you're concerned what might happen to your .io domain, @tantek.com has some practical suggestions:
https://tantek.com/2024/285/t1/io-domain-suggested-steps