HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tspivey
tdsr
Python2018–2019
tspivey / tdsr

tdsr

A console screen reader for macOS and Linux

2Distinct people
4Mentions
0Explicit recommenders
106GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A console screen reader for macOS and Linux

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2018-12-20 16:32:07 UTC to 2019-12-30 17:49:07 UTC.

012018-12-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 20182019-01-01 00:00:00 UTC to 2019-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-01 00:00:00 UTC to 2019-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-01 00:00:00 UTC to 2019-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-01 00:00:00 UTC to 2019-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-01 00:00:00 UTC to 2019-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-06-01 00:00:00 UTC to 2019-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 20192019-07-01 00:00:00 UTC to 2019-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-01 00:00:00 UTC to 2019-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-09-01 00:00:00 UTC to 2019-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-01 00:00:00 UTC to 2019-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-01 00:00:00 UTC to 2019-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 20182018-12-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
Jan 20192019-01-01 00:00:00 UTC2019-02-01 00:00:00 UTC000
Feb 20192019-02-01 00:00:00 UTC2019-03-01 00:00:00 UTC000
Mar 20192019-03-01 00:00:00 UTC2019-04-01 00:00:00 UTC000
Apr 20192019-04-01 00:00:00 UTC2019-05-01 00:00:00 UTC000
May 20192019-05-01 00:00:00 UTC2019-06-01 00:00:00 UTC101
Jun 20192019-06-01 00:00:00 UTC2019-07-01 00:00:00 UTC000
Jul 20192019-07-01 00:00:00 UTC2019-08-01 00:00:00 UTC000
Aug 20192019-08-01 00:00:00 UTC2019-09-01 00:00:00 UTC101
Sep 20192019-09-01 00:00:00 UTC2019-10-01 00:00:00 UTC000
Oct 20192019-10-01 00:00:00 UTC2019-11-01 00:00:00 UTC000
Nov 20192019-11-01 00:00:00 UTC2019-12-01 00:00:00 UTC000
Dec 20192019-12-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

What Hacker News says

4 sources
I can't speak for the OP. And while I'm visually impaired, I'm not totally blind, and I do my programming visually (though I often use a screen reader for other tasks). Still, I can point you at some projects by blind programmers. The largest project I know of that's written primarily by blind people is the open-source NVDA screen reader, written primarily in Python with some C++. It's on GitHub here: https://github.com/nvaccess/nvda For a fairly large, and long-running, project developed primarily by a single blind programmer, check out Emacspeak, written in Emacs Lisp with some Tcl, available on GitHub here: https://github.com/tvraman/emacspeak Edit: I almost forgot about brltty, a Linux console screen reader designed primarily for braille rather than speech output, written in C: https://github.com/brltty/brltty Now for a few small proj
Read the rest
ects written by blind friends of mine: tdsr (screen reader for Unix terminals, written in Python): https://github.com/tspivey/tdsr libaudioverse (C++ 3D audio library, now sadly abandoned): https://github.com/libaudioverse/libaudioverse tma (tmux automator, written in Rust): https://github.com/ndarilek/tma
In Blind software development at 450 words per minute (2017)
> Unless you’re referring to the screen reader I am. I would never claim MacOS couldn't be used by professionals in a more general sense. > but my impression is Apple is generally regarded as the best in what comes to accessibility features, and they keep improving. They’re so proud of it they frequently brag about it in promotional videos For screen reader users, they're the best in terms of what they ship with the OS. You get a fully accessible experience out of the box, which includes a tutorial for first-timers. You can even run with text to speech in the Recovery mode e.g. to format your disks. Contrast that with Microsoft, with Windows 10 being the very first version to offer an accessible setup/installation process, no obvious way to use a screen reader in Safe Mode, and next to nobody using Narrator in their day-to-day computer
Read the rest
use because it took so long to be developed to any usable degree. One of the most popular Windows screen readers (JAWS) also costs hundreds of dollars - thousands over a user's lifetime if they purchase upgrades along the way. Apple are definitely winning there. Everything is free and just works, and I'm quite happy for them to brag about it. Where it starts to fall apart is when you want to actually get things done outside of a core set of Apple apps. For example, Office support is pretty lacking, with poor or no accessibility for advanced word processing and spreadsheet features. The terminal support is so bad that an enterprising blind user made his own terminal screen reader to combat it[1]. There are other problems, such as the screen reader's slow performance making the entire OS feel sluggish. Plus, if there are any bugs in it, you have to wait for an entire MacOS update before it gets fixed. That's annoying when it's a Window Manager bug, but can be completely disruptive when your only gateway to your computer won't read your email for a while without crashing. There are also tons of more opinionated stuff that users can (and do) argue about, like the efficiency of the way you browse the web with VoiceOver on MacOS vs the way Windows screen readers do it. But once you've assessed that the core accessibility experience isn't going to work for you, debating the rest is pretty pointless. Plus (and this is entirely anecdotal) it can become exhausting trying to have a discussion about these problems, only to have hordes of users tell you that you're wrong even though they're unemployed (or employed in a different field) and don't have people relying on them to get anything advanced done in the first place. Sometimes I think there's a tendency to want to justify how much money they've spent on expensive Apple hardware which, realistically, they didn't really need, especially if the cost of a cheaper Windows laptop plus JAWS would've been less or the same anyway. And these days, there's a fantastic free, open source screen reader for Windows[2]. [1] https://github.com/tspivey/tdsr [2] https://www.nvaccess.org
In If you must run Windows 10
If you have a Windows machine handy, I suggest you grab the NVDA screen reader (https://www.nvaccess.org/) and try it out with the Windows console to get a feel for what a good screen reader plus terminal experience is like. I understand that the Orca screen reader for GNOME also has good terminal support, and I think JAWS for Windows does as well, but I'm more familiar with how it works with NVDA. Here's how you move around the terminal with NVDA. For all of these commands, you need a keyboard with a numeric keypad, and NumLock should be off. I believe there are alternatives for laptops without a keypad, but I'm only familiar with the desktop layout. To read the current line, press numpad 8. To move to the previous line, press numpad 7. Next line is numpad 9. The same pattern applies for words (numpad 4-6) and characters (numpad 1-3). In
Read the rest
cidentally, on Mac, VoiceOver's terminal support is crappy enough that my friend Tyler Spivey wrote his own screen reader for the terminal environment, called tdsr [1]. [1]: https://github.com/tspivey/tdsr
In The difference between keyboard and screen reader navigation

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.