Search

Items tagged with: accessibility




Here's a quick demo on how to enable TTS on the Nintendo Switch 2 from the home screen. Hopefully these menus are the same across all devices, though I have no way to know that for certain.

Edit: For other blind Switch/Switch 2 owners, I started a WhatsApp group to discuss the accessibility of the console and it's games. DM if you'd like to join.

Download: onj.me/media/Switch2_Accessibi…
#Nintendo #Switch2 #Accessibility #TTS #ScreenReader


I’m speaking at #OSSummit Europe, 25-27 August in Amsterdam! I had two sessions accepted, "Building a Solarpunk Web: Open Source for a Sustainable Digital Future" and "Adding the W3C’s New ARRM To Improve Your Project’s Accessibility". If you are interested in #accessibility #sustainability #solarpunk #DigitalTeams

1 registration will give you access to over 250 great sessions covering the most cutting edge topics in #OpenSource today. Explore the schedule: bit.ly/3NXx5Zp



So AI-based, offline image descriptions are coming to NVDA. Apparently no follow-up questions or longer descriptions for now. The descriptions or captions are also initially in English.
github.com/nvaccess/nvda/pull/…
@NVAccess
#Accessibility #NVDA


“Sassy Outwater-Wright: Accessibility Champion and More, Dies at 42” by @LFLegal:
lflegal.com/2025/07/sassy-outw…

The “and more” is doing a lot of work there, because Sassy was so much more.

#accessibility




Boosts appreciated: I am working on an #accessibility wiki, because info on accessibility for #blind people is fragmented. It is not ready for public release, but I would like to invite volunteers to help me improve the site. I need to get web devs, server maintainers, moderators, writers, and whoever else would be able to contribute. Please send me a DM if you're interested.


Well y'all, I might have to go back to Windows. With Fedora 42, and Orca 48.6, I cannot use Google Docs well at all on Google Chrome, and on Firefox, the outline view which I use to navigate through many, many headings in a document I need for work, isn't usable at all. I can arrow up and down all I want, but nothing speaks.

#accessibility #fedora #linux #blind


Hey everyone, #Linux Access appears to be live! This is a really fantastic resource for beginning Blind Linux users! linuxaccess.org/ #Accessibility #A11y


The overlay shill is not just a shill, but an overlay vendor itself.

It may have failed to disclose that when asking for, and engaging in, a “balanced” and “open” debate about overlays on LinkedIn.

Overlay vendors continue to be ethically dubious (at best).

#overlay #accessibility #a11y


What the fuck is it with #overlay companies and their apologists commenting on my blog?

I got two today (on the same post):
adrianroselli.com/2025/01/ftc-…

They are promoting their water-carrying shill-piece over on LinkedIn.

#accessibility #a11y




Another one of my posts. This one on the topic of AI tools as assistive technology, what's working, what isn't and why, all without the hype that too many people tend to lean into when discussing this technology:

When Independence Meets Uncertainty: My Journey with AI-Powered Vision
A blind user's candid assessment of the promises and pitfalls of current AI accessibility tools
open.substack.com/pub/kaylielf…

#AI #Accessibility #Substack #ComputerVision #AssistiveTechnology #Blog


Just wrapped up high school and exploring what's next! You probably know me from Altbot (the accessibility bot that helps make Fedi more inclusive), but I also build terminal tools, AI integrations, and love working on anything that improves user experience.

Looking for opportunities in full-stack dev, UI/UX, or accessibility-focused roles. Strong in Go, Python, C#, Web, 7+ years Linux experience, and passionate about open source. My projects have thousands of users and I'm always thinking about how to make tech more accessible, inclusive, and user friendly for everyone.

Portfolio: micr0.dev

Boosts appreciated!

#fedihire #developer #accessibility #opensource


I'm considering getting a Linnstrument (as I have been for years), and just came across this super freaking awesome comment w/ response by Roger Linn on one of his YouTube videos.

This is seriously so cool.

Update: I just bought one directly from rogerlinndesign.com because of how hard I support this way of doing business, and wrote him an email to let him know. Let's make it RAIN for people who are kind and empathetic!

#accessibility


Whether you're heading to #ACB2025, #nfB2025, a holiday family vacation, or nowhere at all, enjoy some free #RemoteIncidentManager on us! From now until the 18th, experience a first of its kind independence that is fully accessible remote desktop, free of charge! Experience just how satisfying being able to provide assistance to any computer - even ones without a screen-reader installed - can be! Download RIM to your Windows or Mac today!
getrim.app
#accessibility #inclusivity


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




As a community that includes folks with a range of disabilities ourselves, we’re deeply invested in improving access to Open Source software. We succeed at our mission when we build open computing experiences that are available regardless of ability and fail when accessibility is considered an afterthought or a nice-to-have. This month and always, Inclusive Design is at the core of what we do and we will continue to strive towards that ideal

#Accessibility #DisabilityPrideMonth #InclusiveDesign


Since the release of OS 8 we’ve been working on things like improving contrast, Dark Mode screenshots and brand colors in AppCenter, turning on or snoozing Dark Mode without canceling your schedule, expanding the “Reduce Motion” setting, and more options to reduce distracting notifications. Plus, thanks to feedback from @fireborn—who you may know from his blog series on Linux accessibility—Notifications and the Shortcut Overlay both got releases that add screen reader support

#accessibility



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




We've recently made many tweaks to improve accessibility of our settings pages for keyboard users, screen reader users, and users who have JavaScript disabled. Ensuring Kagi is accessible is a priority for us.

Anything we can do better? Let us know: kagifeedback.org/

#Kagi #Search #Accessibility


Day 3 of running Windows XP in 2025 is up.
I opened Enafore to check my Mastodon replies. It worked—for a few seconds. Then the notifications started. And they didn’t stop. Ping. Ping. Ping. I couldn’t reply. I could barely move the cursor. I watched the system buckle in real time.
So I tore XP apart.
I disabled over thirty services, deleted Windows File Protection, nuked the prefetch cache, rewrote shutdown behavior, and killed every background process that wasn’t strictly mine. If it touched the network, tried to log something, or ran without permission, it’s dead.
And you know what? Enafore runs fine now. JAWS doesn’t read new posts live, but I don’t care. I can read. I can reply. XP obeys.
Discord, though? Wouldn’t even load in the browser. Just a blank page. So tomorrow, I’m pulling in what channels I can through IRC. It’s not over.
Read the full post:
fireborn.mataroa.blog/blog/dea…
#WindowsXP #Retrocomputing #BlindComputing #Accessibility #IRC #Mastodon #DeadOSWalking


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, 20250625,
by @fireborn,
fireborn.mataroa.blog/blog/you…

… via lobste.rs/s/nwvary/you_don_t_o…

> Freedom is also not telling disabled users to go fuck themselves because they asked for a working login prompt […]

>> GNU/Linux is about you owning your machine.

> Then why do I have to reassert that ownership every time a package breaks accessibility?

#linux #accessibility #gatekeeping


Do you love the idea of Free & Open Source Software, and Linux in particular? I certainly do. But until recently, I didn't think too much about what "freedom" means beyond licensing. If you're like me, this blog post by @fireborn could border on heartbreaking. But it may also be a call to action, not only for developers, but for the entire F/OSS community. I hope it is.

Excerpt: »Freedom is also not telling disabled users to go fuck themselves because they asked for a working login prompt. It’s not freedom if it requires you to be perfect, sighted, fluent in C, and emotionally bulletproof.«

fireborn.mataroa.blog/blog/you…

found via @Natanox at chaos.social/@Natanox/11474988…

#Linux #Accessibility #FOSS #Gatekeeping


THIS.
I gonna save this to just post it every time one of those entitled FOSS-bros crosses my path.

If the only way for people to use a computer is to either become a developer yourself or suffer through exploitation by big corporations it isn't an individual failure of those people, it's an absolute failure of the FOSS / Linux community to build good software.
fireborn.mataroa.blog/blog/you…
#Linux #Accessibility



Listen, oh listen, o you great city of #Lyon! Or even better: écoute, ô écoute, ô toi la grande ville de Lyon ! Cet article est en anglais, mais tu peux le traduire si tu veux, y a des moyens. chacun de ceux et celles qui repostent le grand hourra de » À Lyon on abandonne #Windows et #Microsoft #Office pour #Linux » doit lire ceci. Chacun qui prône la soit-disante liberté de Linux et de l'open-source doit clairement avouer : on ne veut pas de gens handicapés, aveugles, âgés, «pas assez smart ». Nous sommes exclus de votre fête de la vie. Si une solution est libre, open-source mais pas accessible, c'est une mauvaise solution. fireborn.mataroa.blog/blog/you… #Accessibility #Accessibilité #EAA


THIS.
I gonna save this to just post it every time one of those entitled FOSS-bros crosses my path.

If the only way for people to use a computer is to either become a developer yourself or suffer through exploitation by big corporations it isn't an individual failure of those people, it's an absolute failure of the FOSS / Linux community to build good software.
fireborn.mataroa.blog/blog/you…
#Linux #Accessibility