@pavelasamsonov@mastodon.social2025-11-12 21:56:59
@pavelasamsonov@mastodon.social2025-11-12 21:56:59
@lornajane@indieweb.social2025-09-09 08:43:18
Bug report here if anyone wants to track or comment on it #a11y
@pavelasamsonov@mastodon.social2025-10-06 13:51:46
Big tech is laying off user researchers in droves, because it believes that coercing its customers is more profitable than silly things like "making good products people want to buy."
But now the FAFO pendulum is coming around, with Amazon's $2.5B dark pattern settlement and #a11y lawsuits galore.
#UX
@matthiasott@mastodon.social2025-09-19 09:54:48
@pavelasamsonov@mastodon.social2025-10-03 13:51:53
@aardrian@toot.cafe2025-10-06 16:55:52
Tell me you don’t understand ARIA (nor accNames) without telling me.
#a11y #accessibility #ARIA #CSS
@unchartedworlds@scicomm.xyz2025-10-04 11:07:59
Content warning: web access design, state of play
Excellent article from @…, including both an overview and illustrative examples.
As an occasional web-tinkerer, I couldn't fully understand the web design details like a professional would. But from the parallels with event organising, I can tell that the overall vibe is spot-on: don't treat access as an afterthought which can be tacked on later, build it in from day 1.
"If you don't know enough about disabled users to understand their needs: find out. Knowing enough about accessibility to know when to seek out specialist guidance, and to understand it when you get it, should be a core competency for standards engineers. ...
"Getting this right requires a bit more work up-front, but – just as it is with front-end development – ultimately saves potential years of clean-up work (or having to scrap projects after years of effort), as well as avoiding harming disabled users."
#access #design #standards #WebStandards #accessibility #a11y #disability #UX