Search

Items tagged with: A11Y


#a11y





We are excited to be a part of #NFB25 next week and to announce our new partnership with @nationsblind!

First time members can join Bookshare for 30% off our annual membership, and existing members can renew for 20% off. You can sign up and renew at our booth D14. See you at the convention next week!

#A11y #NFB #VI #Accessibility


I love this so much. It's pretty much a GUI for #tampermonkey, offering an easier way for #blind folks to find elements on a webpage and do things to them. Yes, you could do the same things directly by just writing JavaScript yourself. But this is much, much faster, and requires a bit less knowledge. It took me less than 30 seconds to turn all the story titles on fanfiction.net into headings. Labeling a button, or making other small changes would be just as fast. The typos and slightly incorrect English put me off at first; especially the word "blinds" for blind people felt weird and derogatory. apparently the author is from #Cameroon, though, so maybe that's standard there. stsolution2.org/WebAccessibilizer/#a11y#accessibility#screenreader




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.

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.

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.

Events in the agenda view will convey to screen readers of their respective titles and descriptions.

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 @nekohayo 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 @tyrylu 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 🩷

ko-fi.com/theevilskeleton
github.com/sponsors/TheEvilSke…

#Accessibility #a11y #DisabilityPrideMonth #GNOME #GNOMECalendar #GTK #GTK4 #Libadwaita #FreeSoftware #FOSS #OpenSource


Serious #accessibility question:

If I want to mark positive and negative outcomes in color, the "obvious" choice is of course to do that in green and red and have some form of textual fallback.

Now, Im of couse not getting rid of that fallback, but since there is usually a reason to mark things in color (it's much more obvious if you can see it!), so it would be nice to have a combination that is accessible to at least more people (nothing will work for everyone, it's about reaching 95% or 99%[1]), while still being intuitive for everyone else.

I've played around with green and orange before (yellow doesn't work, because it is super bright and I want to support both light and dark mode.)

Anyone any good ideas?

#a11y


Does the feature meet the standards for #accessibility? Is the documentation complete? No? THEN DON’T RELEASE THE FEATURE. Make these things release blockers, it’s literally that simple.

#linux #a11y


Disabled people and allies: We want accessibility in our software!

Developers: It's too hard, too expensive, *whine* (repeat for decades)

Most people I know: We don't want AI in our software!

Developers: We've gone to record lengths to shove AI into everything in less than a year. #a11y #Accessibility #AISucks


#a11y


Gestern mal Signal auf dem Desktop aufgemacht. Konnte mit NVDA nichts lesen und habs dann irgendwie geschafft, dass nicht mal mehr das Menü mit alt aufgeht. Es gab Zeiten, da konnte ich wenigstens meine Chats darüber lesen und beantworten. Dann eben kein Signal mehr für mich. #Signal #A11Y #DisabledAlltag #ScreenReader


#Linux #a11y question with a long self-indulgent preamble: I have been using #emacspeak in the #terminal on #MacOS as my “daily driver” for all writing/notetaking/ #orgmode scheduling/todo organizing for about a month now. I am super in love with it, transformational for this low-vision writer/teacher/editor/producer. (1/8)


interesting story: Today, while discussing VoiceOver commands with a colleague, I kept referring to it as "VoiceOver" (or "VO") + command. This royally confused them, coming from a non-accessibility background: They were not sure if the entire time I just meant for them to press that key while VoiceOver is running. This is an interesting nuance and something that's a holdover for me from the professional #A11Y industry, but clearly, we should nudge more articles to not reference the name of the screen reader but either use the word "modifier" or "SR-modifier" (with clear explanations to the meaning if documentation) or something that won't repeat the name with ambiguity.
#a11y




Question for Android users who use or used Samsung. What is the navigation gesture to go back? While talkback is on? I don't mean the three buttons that are the alternative, but the gestures that are by default, I think. I was asked. I'd be grateful if someone could answer this one. Thank you. #Android #A11Y #Talkback #Samsung


One of Forbes’ renowned 100 lists has just recognised NV Access as a global leader in accessibility.

Forbes’ first-ever Accessibility 100 highlights the biggest innovators & impact-makers in the field of accessibility.

“It’s an honour to be recognised alongside the world’s best innovative organisations advancing accessibility” said NV Access Co-Founder, Mick Curran.

The Forbes Accessibility 100 List is at: forbes.com/lists/accessibility…

#NVDA #NVDAsr #Accessibility #A11y #Forbes #Top100 #BestOf2025



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.
fireborn.mataroa.blog/blog/i-w…
#Linux #Wayland #Accessibility #Orca #GNOME #KDE #COSMIC #FOSS #a11y #BlindTech #xorg


#a11y


#a11y


If you’ve paid attention to my ramblings over the last decade-plus, then you’ve heard me to talk about selfish accessibility.

It’s nice to see others embrace it.

“Selfish reasons for building accessible UIs”
nolanlawson.com/2025/06/16/sel…

#accessibility #a11y


You may think that digital accessibility is unrelated, but I assure you that every successful effort to chip away at rights and protections will be followed by another.

Don’t wait until it affects you personally. Speak up. This is low-risk, so do it while you can.

#a11y #accessibility


i’m in nyc for #unopensourceweek this week. let me know if you want to meet up and talk about #gnome as infrastructure, the free desktop, linux phones, flathub, supply chains, #a11y, the new developer hardware market, or digital sovereignty via ubiquitous computing!


@podfeet interviews Celeste D’Costa from Imaginable Solutions about their Guided Hands assistive device that enables anyone with limited fine motor skills to write, paint, draw, and access technology. #a11y #CSUN2025 podfeet.com/blog/2025/06/csun-…


Open Source Accessibility Summit!
Sunday, Oct 12, Raleigh, NC USA
"Improving the accessibility of open source software"
2025.allthingsopen.org/open-so…
#opensource #oss #a11y #accessibility #events #event #raleighNC


Thank you. I use NVDA it a lot to test the #a11y of my projects at work. Can't wait to try out the new version.
#a11y


Ok, the #Thunderbird chat interface for IRC and Matrix seems to have #a11y issues with #NVDA now. Sometimes NVDA completely freezes, especially when the interface is maximised, though not reliably in all channels. I filed a bug, appreciate anyone who can dig into what on earth is going on: bugzilla.mozilla.org/show_bug.…


#a11y


Incidentally, the company unleashing a new wave of contrast problems on the web (see today’s Codepen Spark for liquid glass copycats) is also the company that seems uninterested in supporting `prefers-reduced-transparency`:
developer.mozilla.org/en-US/do…

#CSS #Safari #accessibility #a11y