6 months and no acknowledgment (still marked as NEW) nor visible activity…
Bug 286267: AX: VoiceOver does not announce text preceding some phrasing elements
https://bugs.webkit.org/show_bug.cgi?id=286267
And it got worse since I reported it in January.
In the past, Safari folks moved on the pile of `display` bugs after I started filing web compat PRs to change support notes.
Trying these as bug reports first, before I make PRs to change support:
• https://github.com/mdn/browser-compat-data/issues/27443
• https://github.com/mdn/browser-compat-data/issues/27444
• https://github.com/mdn/browser-compat-data/issues/27445
• https://github.com/mdn/browser-compat-data/issues/27446
6 months and no acknowledgment (still marked as NEW) nor visible activity…
Bug 286267: AX: VoiceOver does not announce text preceding some phrasing elements
https://bugs.webkit.org/show_bug.cgi?id=286267
And it got worse since I reported it in January.
I’m getting the distinct sense nobody at Google saw this. Or at least nobody with authority. So if you work there, forward it to your boss.
“My Request to Google on Accessibility”
https://adrianroselli.com/2025/05/my-request-to-google-on-accessibility.html
The SmartBase - IoT Adjustable Bed for Comfort and Safety (2019) https://lobste.rs/s/xajwed #a11y #hardware
https://www.hackster.io/jsinglet/the-smartbase-iot-adjustable-bed-for-comfort-and-safety-775f06
Flat design vs realistic (“skeuomorphic”) design https://lobste.rs/s/5n6jcp #a11y #design
https://www.flatisbad.com/
Do people have opinions on dynamic "flash" notification things on web pages, where you get a little warning/info/etc box at the top of the page somewhere that you have to click to dismiss? Especially as far as #UX / #a11y #accessibility?
I have this as part of #Elixir #Phoenix but I'm thinking of throwing it in the trash.
We're happy to finally unveil the full schedule for the upcoming Inclusive Design 24 #id24 24 hour online event on the 25 September 2025 https://inclusivedesign24.org/2025/schedule/ #a11y #accessibility #inclusiveDesign
Happy Disability Pride Month everybody :)
During the past few weeks, there's been an overwhelming amount of progress with accessibility on GNOME Calendar:
• Event widgets/popovers will convey to screen readers that they are toggle buttons. They will also convey of their states (whether they're pressed or not) and that they have a popover. (See !587)
• Calendar rows will convey to screen readers that they are check boxes, along with their states (whether they're checked or not). Additionally, they will no longer require a second press of a tab to get to the next row; one tab will be sufficient. (See !588)
• Month and year spin buttons are now capable of being interacted with using arrow up/down buttons. They will also convey to screen readers that they are spin buttons, along with their properties (current, minimum, and maximum values). The month spin button will also wrap, where going back a month from January will jump to December, and going to the next month from December will jump to January. (See !603)
• Events in the agenda view will convey to screen readers of their respective titles and descriptions. (See !606)
Accessibility on Calendar has progressed to the point where I believe it's safe to say that, as of GNOME 49, Calendar will be usable exclusively with a keyboard, without significant usability friction!
There's still a lot of work to be done in regards to screen readers, for example conveying time appropriately and event descriptions. But really, just 6 months ago, we went from having absolutely no idea where to even begin with accessibility in Calendar — which has been an ongoing issue for literally a decade — to having something workable exclusively with a keyboard and screen reader! :3
Huge thanks to 
@nekohayoJeff Fortin T. for coordinating the accessibility initiative, especially with keeping the accessibility meta issue updated; Georges Stavracas for single-handedly maintaining GNOME Calendar and reviewing all my merge requests; and @tyryluLukáš Tyrychtr for sharing feedback in regards to usability.
All my work so far has been unpaid and voluntary; hundreds of hours were put into developing and testing all the accessibility-related merge requests. I would really appreciate if you could spare a little bit of money to support my work, thank you 🩷
• https://ko-fi.com/theevilskeleton
• https://github.com/sponsors/TheEvilSkeleton
(Boost appreciated)
#Accessibility #a11y #DisabilityPrideMonth #GNOME #GNOMECalendar #GTK #GTK4 #Libadwaita #FreeSoftware #FOSS #OpenSource
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!
https://tesk.page/2025/07/25/gnome-calendar-a-new-era-of-accessibility-achieved-in-90-days/
#GNOMECalendar #GNOME #Accessibility #a11y #DisabilityPrideMonth #Linux #FOSS #OSS #OpenSource #FreeSoftware #GTK #libadwaita
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
GNOME Calendar: A New Era of Accessibility Achieved in 90 Days https://lobste.rs/s/dfket6 #a11y
https://tesk.page/2025/07/25/gnome-calendar-a-new-era-of-accessibility-achieved-in-90-days/
#introductions
Hello everyone! I'm Dan Gero. I'm an amateur #musician, and I love working with #Vocaloid and #vocalsynth programs. I am an aspiring #linguist, and am currently studying #Japanese. I am also #blind, and I am an advocate for #foss, #opensource, #a11y, and #disabilityrights.
Interests:
#computers
#gaming
#audiogames
#tech
#languages
#culture
RFC 9773: ACME Renewal Information (ARI) Extension https://lobste.rs/s/0cwrcl #a11y #security
https://datatracker.ietf.org/doc/rfc9773/
I wish #mastadon saved drafts of posts client side. Mobile web does not guarantee that a page will stay. Especially on lower end phones with lower memory, tabs go away. Which means thoughtful posts disappear, and people who take a while to gather their thoughts into words are disadvantaged.
Why just client side? Because most of the privacy issues are nonexistent. I expect a tiny snippet of JavaScript could be added as part of theme if main clients do not add it.
Hello JATS XML, my old frenemy.
okay so things are ✨happening ✨!!
Fun with #PHP: creating a plugin to enable better diagnostics, accessible remotely via an API to enable debugging.
Improving OJS discussions, notifications, and editorial workflow. Provide more context to editors and make it easier for non-technical editors.
Improving the experience for journals using open-review. Provide more gradients of control for how open-review works for each journal.
Porting in further language/translation and accessibility improvements, especially for plugins
Fixing/Updating Documentation: taking a more task based approach to how OJS/etc. works instead of making people read through a whole thing about the whole workflow for something.
More documentation: integrating progress from previous sprints including for newly created plugins.
(Unofficial) working on thinking about how integrating OJS into the fediverse might work (me, it's me, this is my fault)
There is yet another accessibility overlay vendor out there, though it makes no conformance guarantees. Nor security or privacy guarantees.
“#ARTY Could Get You Sued”
https://adrianroselli.com/2025/07/arty-could-get-you-sued.html
I’m looking for a job or a long-term contract working on websites or online customer service, remote or near Toronto, Canada. Many say I'm best for junior roles as I don't have many years of experience, however I'm open to almost any opportunity.
My specialties are: website developer, website performance, website accessibility, website consultant, and online customer service. I’m also open to other related roles.
I’m well known as someone who can fix or edit something on a website that others may not have the time or know how (especially WordPress, but I can work on other platforms).
Furthermore, I can work fully remote or in-person / hybrid near Toronto, Canada (I’m open to relocation within Canada). I have worked with people from around the world, I’m happy to adjust my schedule as needed.
I can work with any size company, including just yourself. Know of a one-off or short term project that you require help with (such as website evaluation)? I’m also open to those as well.
More details and my email address can be found at https://gregoryhammond.ca/hire-me/. My LinkedIn profile is at https://www.linkedin.com/in/hammondg.
Any referrals, links to job postings, or reposts are welcome (even if you aren’t affiliated with the company).
#fediHire #fediHired #getFediHired #wordPress #webDev #a11y #webPerf #lookingForWork #lookingForJob
Continuing our volunteer effort to make GNOME Calendar fully accessible with a keyboard (see thread for context), we fixed a major bug that was causing the focus to disappear into the abyss when the user tried to tab into the month view in merge request !576. This means, as of this commit, events should now be completely functional and accessible within the month view. Additionally, the merge request changes the keyboard and focus behavior within the month view: Events can only be cycled using arrow buttons, the focus can't escape the month view with arrow buttons, and entering/exiting the month view can only be done with tab. These improvements will be available on GNOME 49.
#GNOME #Accessibility #a11y #GNOMECalendar #Calendar #FOSS #FreeSoftware #Linux
Happy Disability Pride Month everybody :)
During the past few weeks, there's been an overwhelming amount of progress with accessibility on GNOME Calendar:
• Event widgets/popovers will convey to screen readers that they are toggle buttons. They will also convey of their states (whether they're pressed or not) and that they have a popover. (See !587)
• Calendar rows will convey to screen readers that they are check boxes, along with their states (whether they're checked or not). Additionally, they will no longer require a second press of a tab to get to the next row; one tab will be sufficient. (See !588)
• Month and year spin buttons are now capable of being interacted with using arrow up/down buttons. They will also convey to screen readers that they are spin buttons, along with their properties (current, minimum, and maximum values). The month spin button will also wrap, where going back a month from January will jump to December, and going to the next month from December will jump to January. (See !603)
• Events in the agenda view will convey to screen readers of their respective titles and descriptions. (See !606)
Accessibility on Calendar has progressed to the point where I believe it's safe to say that, as of GNOME 49, Calendar will be usable exclusively with a keyboard, without significant usability friction!
There's still a lot of work to be done in regards to screen readers, for example conveying time appropriately and event descriptions. But really, just 6 months ago, we went from having absolutely no idea where to even begin with accessibility in Calendar — which has been an ongoing issue for literally a decade — to having something workable exclusively with a keyboard and screen reader! :3
Huge thanks to @nekohayoJeff Fortin T. for coordinating the accessibility initiative, especially with keeping the accessibility meta issue updated; Georges Stavracas for single-handedly maintaining GNOME Calendar and reviewing all my merge requests; and @tyryluLukáš Tyrychtr for sharing feedback in regards to usability.
All my work so far has been unpaid and voluntary; hundreds of hours were put into developing and testing all the accessibility-related merge requests. I would really appreciate if you could spare a little bit of money to support my work, thank you 🩷
• https://ko-fi.com/theevilskeleton
• https://github.com/sponsors/TheEvilSkeleton
(Boost appreciated)
#Accessibility #a11y #DisabilityPrideMonth #GNOME #GNOMECalendar #GTK #GTK4 #Libadwaita #FreeSoftware #FOSS #OpenSource
As part of our volunteer-driven accessibility initiative in GNOME Calendar, and for the first time in the 10+ years of Calendar's existence, we finally completed and merged the first step needed to have a working calendar app for people who rely on keyboard navigation. This merge request in particular makes the event widgets focusable with navigation keys (arrow left/up/right/down) and activatable with space/enter. This will be available in GNOME 49.
Most of GNOME Calendar's layout and widgets consist of custom widgets and complex calculations, both independently and according to other factors (window size, height and width of each cell, number of events, positioning, etc.), so these widgets need to be minimal to have as little overhead as possible. This means that these widgets also need to have the necessary accessibility features reimplemented or even rethought, including and starting with the event widgets.
We also hope to get other parts of GNOME Calendar accessible before GNOME 49, but I can't promise anything at the moment. We did start working with making the month view accessible: https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/564
#GNOME #Calendar #GNOMECalendar #GTK4 #GTK #Libadwaita #Accessibility #a11y #Linux
Continuing our volunteer effort to make GNOME Calendar fully accessible with a keyboard (see thread for context), we fixed a major bug that was causing the focus to disappear into the abyss when the user tried to tab into the month view in merge request !576. This means, as of this commit, events should now be completely functional and accessible within the month view. Additionally, the merge request changes the keyboard and focus behavior within the month view: Events can only be cycled using arrow buttons, the focus can't escape the month view with arrow buttons, and entering/exiting the month view can only be done with tab. These improvements will be available on GNOME 49.
#GNOME #Accessibility #a11y #GNOMECalendar #Calendar #FOSS #FreeSoftware #Linux
Recreating Laravel Cloud’s range input with native HTML https://lobste.rs/s/fihakk #a11y #css #design
https://phare.io/blog/recreating-laravel-clouds-range-input-with-native-html/
Hi! I have very low vision, and this is how I draw! So when I share my artwork, you'll know how it was made. This is called a desktop video magnifier or a CCTV. #a11y #accessibility #BlindMasto
@patrick_h_lauke Sitze gerade in einer Barcamp-Session und wir freuen uns gemeinsam über eine deiner elaboriertesten Antworten auf ein Github-Issue 😜 (formal komplett korrekt übrigens) Ich feiere! 😅
@jkphlJoschi Kuphal ich nehm mal an, es war das hier? https://github.com/w3c/wcag/discussions/4471 #a11y #accessibility #barrierefreiheit *grins*
Damn. In all their desperation, they’re all falling for those #a11y overlays now. 😔
You Don’t Own the Word “Freedom”: A Full-Burn Response to the GNU/Linux Comment That Tried to Gatekeep Me Off My Own Machine https://lobste.rs/s/nwvary #a11y #linux #rant
https://fireborn.mataroa.blog/blog/you-dont-own-the-word-freedom-a-full-burn-response-to-the-gnulinux-comment-that-tried-to-gatekeep-me-off-my-own-machine/
Good at the Job, Bad at the Interview: Time to Rethink Hiring https://lobste.rs/s/nxwegm #a11y #job
https://www.linkedin.com/pulse/good-job-bad-interview-time-rethink-hiring-christopher-robertson-jdnie
It’s True, “We” Don’t Care About Accessibility on Linux
https://tesk.page/2025/06/18/its-true-we-dont-care-about-accessibility-on-linux/
I Want to Love Linux. It Doesn’t Love Me Back: Post 4 – Wayland Is Growing Up. And Now We Don’t Have a Choice — fireborn via 
@aksAkseli 
https://lobste.rs/s/76i5wh #a11y #linux
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/
I didn’t plan to write about Wayland yet. But Xorg is dying — not eventually, but now. GNOME’s dropping X11 support. RHEL already removed it. Ubuntu and Fedora are next. And if you rely on accessibility, you don’t get to wait this one out.
So here’s Post 4 of I Want to Love Linux. It Doesn’t Love Me Back.
I’m using Wayland now. Primarily. Not because I love it. Because the fallback is disappearing, and I want to be there helping fix what comes next. GNOME with Orca actually works. KDE and COSMIC are making progress. I’ve talked to the people involved. They care.
But a lot is broken.
MATE — the desktop most blind users preferred — isn’t on Wayland.
ocrdesktop doesn’t work. xdotool is gone.
wlroots compositors still don’t reliably support Orca’s keybindings, especially on laptops.
This isn’t GNOME’s fault. They’re the only reason accessibility on Wayland works at all.
But the old excuses are gone. “Just use Xorg” isn’t going to be an option much longer.
So yeah. I’m a Wayland shill now. Because I’m using it. Because I have to.
And I want to make sure we’re not excluded from what comes next.
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/
#Linux #Wayland #Accessibility #Orca #GNOME #KDE #COSMIC #FOSS #a11y #BlindTech #xorg
Accessibility Programming Doesn't Feel Accessible via @aksAkseli https://lobste.rs/s/s0inoo #a11y #programming
https://acidiclight.dev/blog/accessibility-does-not-feel-accessible/
It’s True, “We” Don’t Care About Accessibility on Linux via @aksAkseli https://lobste.rs/s/1nyzfj #a11y #linux #rant
https://tesk.page/2025/06/18/its-true-we-dont-care-about-accessibility-on-linux/
AMA: Ask Masto Anything
Eh not everything.
My question is to HTML and accessibility people:
Can we now happily use <input type="date"> or are the OS implementations of date pickers still too bad?
Basically, want to rip out date pickers because they're such an a11y minefield.
Thank you in advance!
I'm a senior web professional sharing knowledge about #WebQuality mostly #WebPerf and #a11y.
I use #boostmarks to tag resources that are also available in this RSS feed: https://bookmarks.boris.schapira.dev/feed/rss?do=rss&searchtags=boostmarks
To talk about politics, my children or home-made pizzas, mostly in French, I'm 
@borisschapiraChat-Pirate.
Talking accessibility with a stakeholder.
Citoyen intéressé par la politique (option tamagauchiste), sensible aux questions d'égalité, de parentalité, de féminisme (intersectionnel).
J'aime le web, Légifrance et les pizzas, et ne booste que les publications dont les images ont une alternative textuelle #NoAltNoBoost.
***
Pour discuter de qualité Web (majoritairement #WebPerf and #a11y), principalement en anglais, vous pouvez me retrouver sur 
@boostmarksBoris Schapira (Pro)
What I Wish Someone Told Me When I Was Getting Into ARIA via 
@matheusrichMatheus Richard https://lobste.rs/s/utck4y #a11y #web
https://www.smashingmagazine.com/2025/06/what-i-wish-someone-told-me-aria/
I just read “Can accessibility be whimsical?” by the extremely online 
@sarajwSara Joy 
over on Good Internet Magazine (you should too), …
https://goodinternetmagazine.com/can-accessibility-be-whimsical/
📌 #Introduction post on the new server after being evicted from home.social (RIP).
Like it says in my profile, I’m from the UK. I mostly go on about the music I’m into and the work I do, because both are important to me. The cat is called Lucy Fur. My health is a fucking rollercoaster and I’m exhausted.
Hashtag party 🎉
#A11y, #Accessibility, #ActuallyAutistic, #ADHD, #CatsOfMastodon, #ChronicFatigue, #ChronicIllness, #Guitars, #Liverpool, #LucyFur, #Music, #ScouseNotEnglish, #WebDevelopment
I’m sure this means #Canonical, #RedHat and #Gnome have fixed all #Wayland issues that make this desktop totally unusable for blind people. Right? Right?? #a11y
https://www.phoronix.com/news/Ubuntu-25.10-No-GNOME-X.Org
Petit rappel qu'à la question "avez-vous un handicap", il y a seulement deux réponses possibles :
- Oui
- Pas encore
Les questions d'accessibilité nous concernent toutes et tous. Pensez à donner une alternative textuelle (alt text) à vos images. 🥰
Apple’s ‘liquid glass’ contrast hilarity is now a bullet on my post “I Don’t Care What Google or Apple or Whoever Did”
https://adrianroselli.com/2020/03/i-dont-care-what-google-or-apple-or-whomever-did.html
Please please PLEASE do not copy Aero, er, Glass in your Figmas.
Today's Web Design Update: https://groups.google.com/a/d.umn.edu/g/webdev/c/J-MIp3QCJdc
Featuring 
@aardrianAdrian Roselli, 
@SteveFaulkner, 
@deconspray, @sarajwSara Joy , 
@heydon, 
@LFLegalLainey Feingold, 
@yatilEric Eggert, 
@karlgroves, 
@sachagreif, 
@OddBird, and more.
Subscribe info: https://www.d.umn.edu/itss/training/online/webdesign/webdev_listserv.html#subscribe
I only now noticed that 
@stephaniewalterStef Walter is on Mastodon.
Stephanie gave a stellar talk on designing for accessibility at the Smashing Meets #Accessibility conference last February.
I was shocked last month when 
@PleaseDontRainPlease Don't Rain was nominated for a Golden Apple award by @AppleVis .
I wrote a blog post with some thoughts about the experience and bunch of tips that will hopefully help others make their app more accessible.
My team is still looking to hire two mid or senior frontend developers, fully remotely from Europe.
We're looking for like-minded individuals that share our love of artisanal #CSS #A11y, web standards, and #Astro
On the website team at Storyblok, we build marketing websites *for* Storyblok *using* Storyblok 🙂 (but we don't build the product itself)
@
