shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

252
active users

#screenreader

7 posts7 participants0 posts today

There's a growing movement on the #fedi that wants people to switch away from Big (US-based) Tech and towards #FOSS alternatives like #Linux, alternatives to #google, #Microsoft, #dropbox etc.
For #screenReader users, that might not be as simple as all that due to #accessibility reasons. This weekend's IC_Null stream aims to dig into this, but I need your help. What tools, services etc. should I look at from an #accessibility perspective? Anyone here who needs their tools evaluated? Anyone here who's curious about a particular tool or suite of tools? Let me know and I'll add it to the list. Anything goes. #selfHosting #blind #tech #EU

NVDA 2025.1.2 has been released: nvaccess.org/post/nvda-2025-1-

This release fixes a crash when opening certain Microsoft Word versions before version 16.0.18226.

Also, a reminder that if you have downgraded from 2025.x to earlier versions, your profile may become corrupted. This can cause your profile to be reset to factory defaults when you update again, but NVDA should work correctly after that.

Steam just added screen reader support in the latest Big Picture Mode beta. On the Deck. On SteamOS. On Linux.
Not hacked in. Not community-patched. Built-in. From Valve.
There's an accessibility tab. There's a screen reader. There's high-contrast mode, UI scaling, color filters, reduced motion, and more.
I can’t believe I’m saying this but: I need a Steam Deck now.
Accessibility isn’t just coming to gaming — it’s here, and it’s official.
Let’s make some noise so they keep going.
🔗 theverge.com/games/689922/stea
#Accessibility #Gaming #SteamDeck #ScreenReader #Linux #valve

An OLED Steam Deck showing the Steam interface with games including Control
The Verge · Steam is adding screen reader support and other accessibility toolsBy Adi Robertson

Really wishing there was a good textbook reading app for someone with both visual and cognitive #disabilities.

I just started a new course at Colorado Christian University, and this week's reading is 7 chapters from a book called Introducing Christian Doctrine—which is pretty heavy stuff. I've been struggling just to get through the first chapter.

I tried reading in Word with JAWS, but quick navigation keys keep getting disabled, and adding comments isn’t very accessible. So I switched to the ePub version in Bookworm, which lets me add bookmarks, named bookmarks, and comments. That’s been a huge help.

For notes, I’m using Joplin, which works well for organizing thoughts in Markdown. And when I hit a sentence I don’t understand—like “propounded dogmatically” (what even is that?)—I just open Copilot in the browser and ask for a plain-language explanation.

It’s not perfect, but it’s working. I just wish there were tools designed with both cognitive load and screen reader accessibility in mind. Reading theology is hard enough without fighting the tech too.

(My degree is in computer science, but theology is part of the core curriculum.)

#disability #multipleDisabilities #Accessibility #JAWS #ScreenReader #CognitiveDisability #ActuallyAutistic #Autism #Blind #Neurodivergent #NeurodivergentBlind #BookwormReader #JoplinNotes #Joplin #Markdown #TheologyStudent #Christian #ChristianUniversity #InclusiveTech #EdTech #AccessibleReading #DisabilityInEducation #StudyTools #ePub #AssistiveTechnology #MastodonEdu

@mastoblind @main @actuallyautistic @neurodivergentblind

#AudioMo Day 8: A Listen to Some Nintendo Switch 2 Screens and brief look at Mortal Kombat One (Audio Only) youtu.be/RHHECo7BKcg

In this demo, I take you through some of the screens on the Nintendo Switch 2 console using the built-in TTS.
We look at the system settings, accessibility options, user page and go into a few places where TTS doesn't work, and one game that has built-in TTS functions of it's own.
#Accessibility #A11Y #ScreenReader #Nintendo #Switch2

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

About a month ago, I had the privilege of presenting #FreeBSD at the Institute for the Blind in Milan, during an event held in connection with #GAAD (Global Accessibility Awareness Day). It was a profoundly meaningful experience that deepened my commitment to digital accessibility and the development of assistive technologies.

I'm excited to share that the #Accessibility Handbook, focused on vision-related assistive technologies in FreeBSD, is nearly complete. This task has been made possible thanks to the tireless dedication of FreeBSD community volunteers and the support of the @FreeBSDFoundation for new projects and documentation centered on visual accessibility.

#AudioMo day 5: A Quick Look At The Nintendo Switch 2 TTS Accessibility youtu.be/xt5sPvaoshc

I've just gotten a hold of this console so I know nothing much yet, but I will learn more over the coming days and weeks.
This is a quick demo with me only having had access to it for about 30 minutes if that.
#Nintendo #Switch2 #ScreenReader #TTS #Accessibility

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

NV Access are pleased to advise that Beta (and alpha) versions of NVDA are once again available. To celebrate, we've released Beta 10 of NVDA 2025.1: nvaccess.org/post/nvda-2025-1b

Beta 10 includes:
* Updates to translations
* Correct context help navigation for Remote Access dialogs

Thank you everyone for your patience and support, and as always with pre-release builds, please do file any issues on GitHub: github.com/nvaccess/nvda/issue

www.nvaccess.orgNV Access | NVDA 2025.1beta10 available for testing

Hoping those familiar with #LaTeX can give me some advice here. I've started using it to create my assignments for school. I'm not writing technical papers yet, but I find using LaTeX with #Zotero in #VSCode more #accessible with a #ScreenReader than most other setups I've tried.
Since my discussion posts have to follow #APA style, I’m using LaTeX for those as well as full papers. That part is going well—but I’m running into trouble when I need to actually post what I’ve written.
My school uses Brightspace, which allows discussion posts in either rich text or #HTML. I have #Pandoc installed, so I tried converting my LaTeX source to HTML and pasting the code. But Pandoc didn’t include my references section in the output.
I also tried copying from the PDF, but that stripped all formatting.
Does anyone know how I can get a clean HTML version of my work—with references included—that I can paste into Brightspace?
Here’s the command I’ve been using:
pandoc main.tex \
--bibliography=references. Bib \
--csl=apa.csl \
--standalone \
-o main.html
It creates the HTML file, but the references section is missing.
Any tips?
#Accessibility #AssistiveTech #Pandoc #APAstyle #Brightspace #EdTech #AcademicWriting #InclusiveTech #BlindTech #HigherEd #CitationTools #OpenSource #WritingWorkflow

Replied in thread

@BrodieOnLinux @qdot I find it weird to see #FLOSS #devs use an #InformationBlackhole like #discord which combines all the disadvantages of #MailingList, #IRC, #XMPP, #Matrix and even #MicrosoftTeams and #Signal without any redeeming qualities of any of those, like a functioning search & logging.

  • Like the #LKML is kinda shit in terms of UX but at least there are searchable indexes for it so one can just point at a specific message & comment wthout having to be granted access to it.

Not to mention that discord is #ableist af by literally preventing the use of #Screenreader-friendly browsers such as #Lynx and #dillo to work, blocking @torproject / #Tor users and explicitly banning the use of it's #API to build better clients.

  • Not even a #paid-for exception is offered, thus making integration into even paid-for tools like #HootSuite not legally possible!

I’ve published Part 3 of “I Want to Love Linux. It Doesn’t Love Me Back.”

This one’s about the so-called universal interface: the console. The raw, non-GUI, text-mode TTY. The place where sighted Linux users fall back when the desktop breaks, and where blind users are supposed to do the same. Except — we can’t. Not reliably. Not safely. Not without building the entire stack ourselves.

This post covers Speakup, BRLTTY, Fenrir, and the audio subsystem hell that makes screen reading in the console a game of chance. It dives into why session-locked audio breaks espeakup, why BRLTTY fails silently and eats USB ports, why the console can be a full environment — and why it’s still unusable out of the box. And yes, it calls out the fact that if you’re deafblind, and BRLTTY doesn’t start, you’re just locked out of the machine entirely. No speech. No visuals. Just a dead black box.

There are workarounds. Scripts. Hacks. Weird client.conf magic that you run once as root, once as a user, and pray to PipeWire that it sticks. Some of this I learned from a reader of post 1. None of it is documented. None of it is standard. And none of it should be required.

This is a long one. Technical, and very real. Because the console should be the one place Linux accessibility never breaks. And it’s the one place that’s been left to rot.

Link to the post: fireborn.mataroa.blog/blog/i-w

fireborn.mataroa.blogI Want to Love Linux. It Doesn't Love Me Back: Post 3 – Speakup, BRLTTY, and the Forgotten Infrastructure of Console Access — fireborn

🎓 Returning #Blind #CS #Student – Seeking Advice on LaTeX & #Accessible #Math Tools

Hi everyone! I’m a blind student returning to college to pursue a B.S. in Computer Science through Colorado Christian University Online. This is my third attempt at college due to chronic illness, but I’m excited to be back and determined to make it work.

I’m looking for advice on two fronts:

📝 1. LaTeX on #Windows

I’ve recently started learning LaTeX and find it a more accessible way to write papers—especially when paired with Zotero for citations. My main machine is a Windows 11 Pro mini PC, and I also have a Raspberry Pi running Arch Linux ARM.

So far, I’ve tried:

  • Overleaf – nice interface, but the PDF viewer isn’t very screen reader-friendly and the editor has some issues too (JAWS/NVDA repeat lines).
  • VS Code with LaTeX Workshop – most accessible option I've tried
  • TeXnicCenter – only briefly.

👉 Question: What LaTeX editors or workflows do you use on #Windows, and how accessible have you found them?

➗ 2. Relearning College-Level Math

I’ll be starting with calculus early next year. It’s been a long time since high school, and chronic illness has affected my memory and cognition. I used to use a Perkins Brailler for math, but arthritis/lupus (still being diagnosed) makes that painful now.

👉 Question: Can anyone recommend accessible resources for relearning math—especially for someone doing everything online?

Any tips for doing math, science, or programming fully online as a blind student would be incredibly appreciated.

Thanks in advance! I’m happy to share what I learn along the way.

Feel free to boost or tag others who might have insights.

#BlindTech #Accessibility #LaTeX #STEM #DisabilityInSTEM #MathAccessibility #JAWS #NVDA ##ScreenReader Zotero #ChronicIllness #OnlineLearning @mastoblind @main