Accessibility

Accessibility

356 bookmarks
Custom sorting
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 […]
·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!
·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.
·craigabbott.co.uk·
Mission Impossible - Accessibility Job Roles
ARIA/HTML relationship Severance
ARIA/HTML relationship Severance
By @SteveFaulkner@mastodon.social
What I found back then was that aria relationship attributes didn’t work when an element being referenced was outside the shadow DOM and the element referencing it was inside the shadow DOM, ditto for the opposite. It was same story for native HTML relationships as well. Fast forward to 11 years later, as in now! 2025, and the situation remains the same.
You could use standard HTML controls without all that stinking DOM darkness and encapsulation fandango fucking up your relationships. Defy the JavaScript industrial complex by any means necessary If this is not an option, then there are some ways you can work around these issues in some cases. A relatively simple example is provided:
·html5accessibility.com·
ARIA/HTML relationship Severance
My Request to Google on Accessibility
My Request to Google on Accessibility
By @aardrian@toot.cafe
Please, if your team cannot explain how the thing satisfies all WCAG Success Criteria at Level AA, then don’t release the thing. If the thing is a new feature for the web platform (HTML, CSS, ARIA, SVG, etc.), then don’t even propose the thing until you have its WCAG conformance sorted.
·adrianroselli.com·
My Request to Google on Accessibility
How to Convince People to Care and Invest in Accessibility by Stéphanie Walter - UX Researcher & Designer.
How to Convince People to Care and Invest in Accessibility by Stéphanie Walter - UX Researcher & Designer.
By @stephaniewalter@front-end.social
This talk, article, is for anyone who’s ever said “we need to make this accessible,” and got ignored, brushed off, or told, “We’ll do that later.” If you’re not in a leadership role, if you’re not officially “the accessibility person,” but you still want to drive change, this is for you.
·stephaniewalter.design·
How to Convince People to Care and Invest in Accessibility by Stéphanie Walter - UX Researcher & Designer.
We launched our first Shopify theme
We launched our first Shopify theme

With accessibility in mind.

By @NicMakesStuff@indieweb.social

building the theme has been a delicate balance of trying to manage merchant expectations with creating an accessible user experience.
Our marquee component has a pause button, respects the user preference for reduced motion, only enables focus for the first unique instance of a link, and only announces the first instance of the text. While there are certainly things that I think can be improved, a huge amount of effort was put in to make sure that disabled users would not be blocked by it. Marquees are not great for accessibility, but one that has considered accessibility is certainly better than one without.
·nicchan.me·
We launched our first Shopify theme
Automated accessibility test tools find even less than expected
Automated accessibility test tools find even less than expected
I find myself increasingly asking what value do I get out of existing commercial accessibility testing tools? What do they catch? What do they not catch? I ask because I want to improve on the results, and I also want to know what exactly I need to manually inspect a web page for. So let's start wit
·linkedin.com·
Automated accessibility test tools find even less than expected
Why I Like Designing in the Browser
Why I Like Designing in the Browser
I love this post by @tylersticka@social.lol. Designing in the browser also allows you to design from the actual real content up instead of structure down. It’s an important skill to have.
Many standards, especially in the last decade, don’t just streamline implementation: They open up whole new creative possibilities! CSS grid and subgrid, high-gamut color, container queries, scroll-driven animations, view transitions, color schemes and more!
Some of these ideas make it into design tools, but the wait can be long… understandably so, making interfaces for this stuff is hard! By the time Figma introduced their flexbox equivalent, the more powerful CSS Grid was already years into baseline availability.
Most HTML elements want to Elasti-Girl their way through any viewport size.
And can we talk about the awesomeness that is dev tools? In any modern browser, developers (or curious nerds of any discipline) can inspect every size, color and property of every single element of the page without any additional effort from the designer. Super-powered design specs, absolutely free.
·cloudfour.com·
Why I Like Designing in the Browser