Schau schau, Microsoft stellt barrierefreies und adaptives Zubehör her und stellt auch gleich 3D-Druckdaten zum weiteren Anpassen der Geräte zur Verfügung.
Schau schau, Microsoft stellt barrierefreies und adaptives Zubehör her und stellt auch gleich 3D-Druckdaten zum weiteren Anpassen der Geräte zur Verfügung.
@ashleemboyer the topic of "which tools will work best for collaboration/work/discussion" is one that keep bubbling up (almost as often as the dreaded "isn't it ironic that the acronym #a11y is itself inaccessible?"). there have been many attempts at using various approaches - from the original (horrid) closed mailing lists of old, to the more open public ones, to forums/discussion boards, shared google docs, and indeed github ... 1/
seeing discussions around how "members of the public (tm)" are prevented from taking part in standards development, because tools like github (where discussion/development happens) may not be familiar to them. while i understand the sentiment, i'd hazard a guess that these members of the public won't understand how the sausage is made, and will be frustrated by the consensus-driven standards development ... it's not just a "let me tell you about MY lived experience" thing #a11y #accessibility
How to participate in a video conference and check your visual appearance when you are totally blind https://techesoterica.com/gauging-your-look-before-that-all-important-video-conference/ Gauging your look before that all important video conference; #blind #a11y #The_vOICe
"This is independent of any AI model and there is no need to send your image to the cloud. Everything is local and your look is yours."
We're looking for someone to join the @TetraLogical team as an accessibility Specialist.
If you're resident in the UK, you can apply on Linkedin:
https://www.linkedin.com/jobs/view/4197046475/
Or directly:
https://misc.tetralogical.com/careers/2025-03-accessibility-specialist/
mind the WCAG automation gap — What can automated tools test without humans? https://html5accessibility.com/stuff/2025/03/27/mind-the-wcag-automation-gap/ #a11y #wcag #tools
With the European Accessibility Act enforcement around the corner (June 28), you might want to check your designs for color blindness accessibility
Here's a brief intro on the topic to get you started on the topic.
Access Information News for Monday, March 31, 2025 - Volume 1008
https://accessinformationnews.com/ain2025/03312025/
The Week's News in Access Information
A Mind Vault Solutions, Ltd. Publication
#news #accessibility #a11y #disability #blind #deaf #deafblind #ain
Access Information News. The world's #1 online resource for current news and trends in access information.
Subscribers: 36,339
Whoops! Someone didn't know what they were doing here. A link where the only text inside the a-element is inside a div. The div has aria-label="false" as an atribute.
The result of this is that... "false" becomes the accessible name of the link.
(and there are a number of these instances on this page I'm checking!)
Firefox 137 is around the corner and I realized I didn't wrote DevTools release post since the beginning of the year
Let's start with updates in version 134, which brought a few fixes and some nice accessibility improvements: https://fxdx.dev/firefox-devtools-newsletter-134/
So #Github released their accessibility documentation and, this will be a helpful resource to so many! https://accessibility.github.com/documentation/guide/repos/ #Git #A11y #Accessibility
My Favorite Tools for Web Accessibility Testing. #a11y #webdev #accessibility
Karl Groves: #AI is the future of #accessibility
https://karlgroves.com/ai-is-the-future-of-accessibility/
#A11Y
Cette semaine sur Oxytude, l'Hebdoxytude 401, l'actu des nouvelles technologies et de l'accessibilité.
Putting the final touches on the next release of @PleaseDontRain that I've been working on the last few weeks.
Very happy with how it's turned out.
Quick and dirty testing of WCAG 2.1 Success Criterion 1.4.12 Text Spacing.
Last updated 21st March 2025, now utilizes :not pseudo-class to increase specificity, thanks to https://github.com/brgibson
So an update on Guide: I've exchanged some long emails with Andrew, the lead developer. He's open to dialogue, and moving the project in the right direction: well-scoped single tasks, more granular controls and permissions, etc. He doesn't strike me as an #AI maximalist can and should do everything all the time kind of guy. He's also investigating deeper screen reader interaction, to let AI just do the things we can't do that it's best at. I stand by my thoughts that the project isn't yet ready for prime time. But as someone else in the thread said, I don't think it should be written off entirely as yet another "AI will save us from inaccessibility" hype train. There is, in fact, something here if it gets polished and scoped a bit more. #blind #screenreader #a11y
Tiny, TINY, update to my Viewport Details bookmarklet: I added a line that shows whether the OS is set to light or dark mode. Handy for future reference when you check screenshot to know what mode it was in at the time.
While this baseline support effort is great:
https://w3c.social/@w3c/114229329339928436
Remember that it does not include baseline support for #accessibility features:
https://github.com/web-platform-dx/web-features/issues/498
So continue to test on your own. #a11y
Brill talk on typography and #a11y https://2025.stateofthebrowser.com/speaker/oliver-schondorfer/ at #SotB2025 laughed and snorted and learned, thank you Oliver