Found 34 bookmarks
Custom sorting
Custom Carets and Users: When The Caret Is No Longer a Stick (Yes, That’s a Poor Attempt at a Pun)
Custom Carets and Users: When The Caret Is No Longer a Stick (Yes, That’s a Poor Attempt at a Pun)
@aardrian@toot.cafe shining light on a new CSS property with accessibility implications
I’d feel better if the CSSWG did a better job of outlining risks and best practices, at least beyond stale WCAG links and suggestions that user style sheets are the best approach to get around forcing animations on users. Granted, the CSSWG had shown a certain amount of ignoring the Priority of Constituencies of late, so I’m also not terribly surprised.
#a11y#accessibility#css#webdev
·adrianroselli.com·
Custom Carets and Users: When The Caret Is No Longer a Stick (Yes, That’s a Poor Attempt at a Pun)
Yellow, Purple and the Myth of “Accessibility Limits Color Palettes”
Yellow, Purple and the Myth of “Accessibility Limits Color Palettes”
Terrific article by the wonderful @stephaniewalter@front-end.social who shows how accessibility is about how you combine colors rather than just what colors you use.
So, let’s address the myth head-on. Accessibility does not limit your color palette choices. What feels limiting is often a lack of knowledge about WCAG color contrast, how to build accessible color palettes in tools like Figma. And sometimes, a lack of creativity.
#color#contrast#accessibility#wcag#a11y
·stephaniewalter.design·
Yellow, Purple and the Myth of “Accessibility Limits Color Palettes”
5 Hidden Costs in Your WCAG Audits
5 Hidden Costs in Your WCAG Audits
Some WCAG audit providers inflate findings with issues that are inaccurate, mislabeled, irrelevant, or impractical. They often miss the wider picture, leading to recommendations that do not reflect real accessibility needs These mistakes waste time and budget, while failing to deliver meaningful progress or inclusive outcomes. Worse still, you may still leave the door open […]
#accessibility#a11y#audits#testing
·tab-able.co.uk·
5 Hidden Costs in Your WCAG Audits
What I Wish Someone Told Me When I Was Getting Into ARIA
What I Wish Someone Told Me When I Was Getting Into ARIA
@eric@social.ericwbailey.website writes something @yatil@yatil.social shares it. That’s the rule.
There are no console errors for malformed ARIA. There’s also no alert dialog, beeping sound, or flashing light for your operating system, browser, or assistive technology. This fact is yet another reason why it is so important to test with actual assistive technology.
Browsers should really do this!
#aria#accessibility#wai-aria#standards#a11y
·smashingmagazine.com·
What I Wish Someone Told Me When I Was Getting Into ARIA
Mission Impossible - Accessibility Job Roles
Mission Impossible - Accessibility Job Roles
By @craigabbott@a11y.info
When it comes to running a workshop, 30 people is a large group. So, let's imagine you somehow managed to cram all of the material into a single half-day workshop, and you run it with large groups of 30 people, twice per day, 7 days per week. To get through our low-balled figure of 600 people, it would still be 9 months! That's 3 months more than you'll likely be employed for, and that's not including any coordination, scheduling, prep-time, write-up time, iteration time or specific actions that come from the workshops themselves.
#a11y#hiring#roles
·craigabbott.co.uk·
Mission Impossible - Accessibility Job Roles
Principles Of Web Accessibility
Principles Of Web Accessibility

A set of high-level guiding principles for approaching design and remediation for an accessible web.

By @heydon@front-end.social

Perfection is the enemy By default or death Parity is paramount Design for implementation Structure first Use your words Tools are not identities Less is less Fishing, not fish No points for performance Help evil to fail
#accessibility#a11y#design principles
·github.com·
Principles Of Web Accessibility
FTC Catches up to #accessiBe
FTC Catches up to #accessiBe
By @aardrian@toot.cafe
You might think this feels like vindication, but it does not.
Sure, it’s nice to be validated by the FTC after 5 years of shouting to anyone who will listen that accessiBe is a net harm for the disability community. But the settlement is a pittance.
Reports put accessiBe’s 2024 revenue at $51.3 million. The settlement has a fine of $1 million. Subtracted from its 2024 revenue, that leaves accessiBe with $50.3 million dollars for the year. Dollars earned by lying to customers, misrepresenting itself to the community, and arguably harming disabled users.
#accessibility#a11y#AI#overlays#FTC#accessiBe
·adrianroselli.com·
FTC Catches up to #accessiBe
How to Dehumanize Accessibility with AI | Ashlee M Boyer
How to Dehumanize Accessibility with AI | Ashlee M Boyer
@ashleemboyer@mstdn.social on why it’s dehumanizing and unnecessary to ask “AI” about the disabled experience, when disabled people exist.
AI is not impacted by inaccessibility. It is not a disabled person. It cannot explain web accessibility from the perspective of a disabled person.
Removing the human factor of inaccessibility stories does not build empathy. It dehumanizes the stories. It dehumanizes US.
Additionally, inaccessibility is not a result of a lack of empathy. It’s a result of ableism. To still position lack of empathy as the main problem in almost 2025, is a failure to consider vital historical context.
Creating AI caricatures of disabled people does not help us dismantle systemic ableism.
I also take issue with the alleged need for comments to be “appealing” or “humorous.” Nothing appealing nor humorous about inaccessibility. Inaccessibility is PAINFUL in every single sense of the word. When disabled people encounter inaccessibility, we are harmed every. single. time.
#accessibility#a11y#AI#disability
·ashleemboyer.com·
How to Dehumanize Accessibility with AI | Ashlee M Boyer
WCAG2ICT Note Published
WCAG2ICT Note Published
Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) is a completed W3C Group Note. WCAG2ICT describes how Web Content Accessibility Guidelines (WCAG) principles, guidelines, and success criteria can be applied to non-web information and communications technologies (ICT), specifically to non-web documents and software. The document includes guidance for WCAG 2.0, 2.1, and 2.2 success criteria and glossary terms. WCAG2ICT has been a key resource for including WCAG in ICT accessibility regulation, legislation, and standards around the world. This update facilitates further adoption of WCAG 2.1 and WCAG 2.2 in non-web contexts. For an introduction, see: WCAG2ICT Overview.
WCAG2ICT describes how Web Content Accessibility Guidelines (WCAG) principles, guidelines, and success criteria can be applied to non-web information and communications technologies (ICT), specifically to non-web documents and software.
#wcag#wcag2ict#accessibility#a11y
·w3.org·
WCAG2ICT Note Published