Search results

World Wide Web Consortium @w3c@w3c.social
Public

Why you should W3C? We work to support the community that develops web standards, the building blocks of our digitally connected world.

Show you care about the long-term growth of the open, interoperable web that caters for accessibility, privacy, security, and internationalization. today w3.org/support-us/

youtube.com/watch?v=6bXp8Eet0HM

circular shape of lines and nodes with text "We are global"
0
0
0
Craig Abbott @craigabbott@a11y.info
Public

Finally hit publish on a blog post I've been writing for a while.

It's common to hear the term "fully accessible" used to describe products which have passed WCAG 2.2 level AA. But, are they really?

In this post, I explore 5 examples which highlight why WCAG, as awesome as it is, is not a measure of great usability or performance.

craigabbott.co.uk/blog/2025/5-

Craig Abbott presenting at a conference

5 reasons why WCAG AA compliance does not mean your website is accessible

5 reasons why WCAG compliance does not mean accessible accessible

craigabbott.co.uk · craigabbott.co.uk

0
0
0
TheEvilSkeleton @TheEvilSkeleton@treehouse.systems
Public

At last, all the accessibility improvements on GNOME Calendar are finally available as a stable release. Get it on Flathub while it's hot!!!

flathub.org/en/apps/org.gnome.

GNOME Calendar: A New Era of Accessibility Achieved in 90 Days

There is no calendaring app that I love more than GNOME Calendar. The design is slick, it works extremely well, it is touchpad friendly, and best of all, the community around it is just full of wonderful developers, designers, and contributors worth collaborating with, especially with the recent community growth and engagement over the past few years. Georges Stavracas and Jeff Fortin Tam are some of the best maintainers I have ever worked with. I cannot express how thankful I am of Jeff’s underappreciated superhuman capabilities to voluntarily coordinate huge initiatives and issue trackers. One of Jeff’s many initiatives is gnome-calendar#1036: the accessibility initiative, which is a big and detailed list of issues related to accessibility. In my opinion, GNOME Calendar’s biggest problem was the lack of accessibility support, which made the app completely unusable for people exclusively using a keyboard, or people relying on assistive technologies. This article will explain in details about the fundamental issues that held back accessibility in GNOME Calendar since the very beginning of its existence (12 years at a minimum), the progress we have made with accessibility as well as our thought process in achieving it, and the now and future of accessibility in GNOME Calendar.

tesk.page · TheEvilSkeleton

Link author: TheEvilSkeleton@TheEvilSkeleton@treehouse.systems

TheEvilSkeleton @TheEvilSkeleton@treehouse.systems
Public

After two long and painful years, several design iterations, and more than 50 rebases later, we finally merged the infamous, trauma-inducing merge request !362 on GNOME Calendar.

The calendars list in the quick-add popover has undergone accessibility improvements, providing a better experience for assistive technologies and keyboard users (to a limited extent). Specifically: tabbing from outside the list will focus the selected calendar in the list; tabbing from inside the list will skip the entire list; arrow keys automatically select the focused calendar; and finally, assistive technologies now inform the user of the checked/selected state.

Admittedly, the quick-add popover is currently unreachable via keyboard because we lack the resources to implement keyboard focus for month and week cells. We are currently trying to address this issue in merge request !564, and hope to get it merged for GNOME 50, but it's a significant undertaking for a single unpaid developer. If it is not too much trouble, I would really appreciate some donations, to keep me motivated to improve accessibility throughout GNOME and sustain myself: tesk.page/#donate

For non-accessibility-related details about this merge request, feel free to check out mastodon.social/@nekohayo/1155

quick-add-popover: Port to libadwaita widgets and merge stack pages (!362) · Merge requests · GNOME / gnome-calendar · GitLab

Both stack pages are merged into one, to avoid additional clicks. Mnemonics were added to accommodate keyboard users as well. Closes

gitlab.gnome.org · GitLab

0
0
0
0
0
0
Robin Kanatzar @Robinkanatzar@mastodon.green
Public

"Is my app accessible? Where do I start making it better?"

These are the first two questions I've been getting from my clients, and they want the answers right away. That's why I'm now offering a new service called the "accessibility checkup" to give you those answer is two business days or less. Same great report you've seen earlier drive.google.com/file/d/19rSHK
delivered to you fast.

Sound like something you or your team would be interested in? Let me know!

Sample Audit Report - Essential.pdf

drive.google.com · Google Docs

0
0
0
Marcus Helvig @MarcusP@mastodon.social
Public

Longtime computer geek. Newly working in digital accessibility , after desktop/API server development, desktop support & sysadminning. I still enjoy , and our pets (mammals, reptiles). Endurance motor racing, especially and my annual attempt at a 24 hour marathon for the 24 Hours of Le Mans ().

I'm learning about the implications of late life Spectrum Disorder () and Attention Deficit/Hyperactivity Disorder ().

0
0
0
skimm @skimm@fosstodon.org
Public

Guess I never posted or pinned an if I had one. I've been on Mastodon for a bit now, since 2019 if my profile is to be believed. I'm _really_ bad at social media in general but am a fan of the vibes and federation of Mastodon and other AP offerings.

Former frontend > full stack dev now living the life. Currently located in America pushing for change. I believe in and .

More in bio.


0
0
0
W3C Developers @w3cdevs@w3c.social
Public

The @w3cWorld Wide Web Consortium breakouts schedule is now available! They will take place from 10 to 13 November 2025. Check it out:
▶️ w3.org/calendar/tpac2025/break

participants organize discussions among the full W3C about new or existing topics. This year, a total of 79 proposals were proposed, including topics like Agents,, , , , , and more: github.com/w3c/tpac2025-breako

TPAC 2025, 10 to 14 November 2025, Kobe, Japan and online
0
0
0
0
0
0
0
0
0
Adrian Roselli @aardrian@toot.cafe
Public

If you saw my tees at and wondered where you could squander money on them…

The POURP shirt:
aardrian.threadless.com/design

The W*C*A*G shirt (brown version):
aardrian.threadless.com/design

POURPN, Atkinson Hyperlegible, white text Men's T-Shirt | aardrian's Shop

POURPN, Atkinson Hyperlegible, white text on Men's T-Shirt – <p> The four principles of WCAG plus more related to real-life accessibility. Set in Atkinson Hyperlegible as white text for darker colored shirts. There is a version in black text and another in Neue Helvetica Heavy. </p> <p> <em>alt</em>: Perceivable & Operable & Understandable & Robust & Punch Nazis. The words are stacked vertically. </p>

aardrian.threadless.com · aardrian's Shop

0
0
0
0
0
0
Snugug @snugug@mas.to
Public

For those who wanted to see the code behind my CSS-only magical sticky auto-expanding sidebar nav in action, I've put together a little CodePen for you! I've narrowed down the relevant code to just what's needed to get this to work, with some very minimal JavaScript to improve the accessibility of it! I've even left you a little challenge in there for you, let me see how you accomplish it!

codepen.io/Snugug/pen/VYezVKr
mas.to/@snugug/115259058092836

0
0
0
just adrienne @adrienne@social.treehouse.systems
Public

Folks, i need a job or a contract so bad. I'm a full-stack developer, i work in several frameworks (including and ), and with several CMSes (notably and but i can also work in Wordpress). I've got SQL wizard skills and a deep focus on and solid, maintainable, semantic HTML and CSS on the front end. Please hire me!

I'm a dual US/Canadian citizen and prefer fully remote work but can also do in-office in Vancouver/the Lower Mainland area.

0
0
0
0
0
0
Daniela Kubesch @dnikub@front-end.social
Public

Simplified Accessibility Testing, right from your browser?! 💡🔍

I designed and coded this little landing page to showcase all the browser powered by and created by my wonderful team here at mindscreen.

Take a look: tools.caat.report/

Perhaps one of these bookmarklets could be integrated into your process? 👀

A stylized icon of a cat below the text: Simplified accessibility testing, right from the browser. Powered by caat.report.

Accessibility Bookmarklets by CAAT.report

Simplify accessibility testing, right from your browser with bookmarklet powered by CAAT.report.

tools.caat.report · CAAT

0
0
0
Stefan Bohacek @stefan@stefanbohacek.online
Public

Anyone interested in helping me test a tool I'm working on?

Right now it can tell you how many of your images are missing alt text. Some ideas I am playing with:

- check for image descriptions that are too long or too short (Whatever that means! And what about non-English text?)
- check if you CapitalizeYourHashtags properly

Link: data.stefanbohacek.com/project

A screenshot from the linked website showing my profile image, my name, and the text below, followed by a grid of images: Out of your 5,549 posts, 269 have visual media attached. Out of the 278 images and videos you posted in total, 269 have alt text. That's about 97%. You're doing a great job! Here are some of the images that are missing description.
0
0
0
0
0
0
Robin Kanatzar @Robinkanatzar@mastodon.green
Public

Come hear me speak about "Engineering Accessibility: Practical, Maintainable, Testable" at Pragma Conference and Do iOS this fall!

🍝 Pragma Conference: October 30th in Bologna, Italy
pragmaconference.com/

🧇 Do iOS: November 12 in Amsterdam do-ios.com/

Pasta and stroopwaffles, here I come! 🤣

#Pragma Conference 2025 | The iOS, macOS, visionOS, watchOS, tvOS Developers Conference

#Pragma Conference 2025 | October | Italy | The Apple Developers Conference

pragmaconference.com

0
0
0
Jimmie Jephson @jimmiejephson@mastodon.social
Public

I was asked to write a short , I'm a Accessibility Specialist, Front-end dev and scrum Master from Sweden. Been in the industry for about 20 years. I work at Axess Lab doing audis to help companies with their digital solutions and trying to make the digital world a better place for everyone. A big thing but if we all come together and help out with this we will achieve some great things!

If you have any questions, just fire away! :)

0
0
0
0
0
0
Sara Joy :happy_pepper: @sarajw@front-end.social
Public

Hello accessibility friends,

I'm working on gathering information for accessibility bug tickets - our customer supporters would like to know what to ask the people chatting in.

My first concern is how to respectfully find out as much as we can about the customer's setup without outright asking for their disability.

I'm hoping most cases will be clear, like "I can't read that text, it's grey on grey" or "I can't access the [interactive element] with my keyboard"

1/2

0
0
0
TheEvilSkeleton @TheEvilSkeleton@treehouse.systems
Public

After two weeks of writing, revising, and trying to make everything as digestible as possible, I finally published "GNOME Calendar: A New Era of Accessibility Achieved in 90 Days", where I explain in detail the steps we took to turn GNOME Calendar from an app that was literally unusable with a keyboard and screen reader to an app that is (finally) accessible to keyboard and screen reader users as of GNOME 49!

tesk.page/2025/07/25/gnome-cal

GNOME Calendar: A New Era of Accessibility Achieved in 90 Days

There is no calendaring app that I love more than GNOME Calendar. The design is slick, it works extremely well, it is touchpad friendly, and best of all, the community around it is just full of wonderful developers, designers, and contributors worth collaborating with, especially with the recent community growth and engagement over the past few years. Georges Stavracas and Jeff Fortin Tam are some of the best maintainers I have ever worked with. I cannot express how thankful I am of Jeff’s underappreciated superhuman capabilities to voluntarily coordinate huge initiatives and issue trackers. One of Jeff’s many initiatives is gnome-calendar#1036: the accessibility initiative, which is a big and detailed list of issues related to accessibility. In my opinion, GNOME Calendar’s biggest problem was the lack of accessibility support, which made the app completely unusable for people exclusively using a keyboard, or people relying on assistive technologies. This article will explain in details about the fundamental issues that held back accessibility in GNOME Calendar since the very beginning of its existence (12 years at a minimum), the progress we have made with accessibility as well as our thought process in achieving it, and the now and future of accessibility in GNOME Calendar.

tesk.page · TheEvilSkeleton

Link author: TheEvilSkeleton@TheEvilSkeleton@treehouse.systems

TheEvilSkeleton @TheEvilSkeleton@treehouse.systems
Public

At last, all the accessibility improvements on GNOME Calendar are finally available as a stable release. Get it on Flathub while it's hot!!!

flathub.org/en/apps/org.gnome.

GNOME Calendar: A New Era of Accessibility Achieved in 90 Days

There is no calendaring app that I love more than GNOME Calendar. The design is slick, it works extremely well, it is touchpad friendly, and best of all, the community around it is just full of wonderful developers, designers, and contributors worth collaborating with, especially with the recent community growth and engagement over the past few years. Georges Stavracas and Jeff Fortin Tam are some of the best maintainers I have ever worked with. I cannot express how thankful I am of Jeff’s underappreciated superhuman capabilities to voluntarily coordinate huge initiatives and issue trackers. One of Jeff’s many initiatives is gnome-calendar#1036: the accessibility initiative, which is a big and detailed list of issues related to accessibility. In my opinion, GNOME Calendar’s biggest problem was the lack of accessibility support, which made the app completely unusable for people exclusively using a keyboard, or people relying on assistive technologies. This article will explain in details about the fundamental issues that held back accessibility in GNOME Calendar since the very beginning of its existence (12 years at a minimum), the progress we have made with accessibility as well as our thought process in achieving it, and the now and future of accessibility in GNOME Calendar.

tesk.page · TheEvilSkeleton

Link author: TheEvilSkeleton@TheEvilSkeleton@treehouse.systems

0
0
0
0
0
0