Loading...
Loading...
How blind PhD researchers use Emacs, LaTeX, and CLI tools for accessible academic work. Real workflows, real solutions.
"Terminal is pure text... universally accessible. I can do anything in the terminal."
Blind PhD in Astrophysics, r/accessibility
Most accessibility tools are designed by sighted developers for sighted users. They assume:
This guide is different. It's grounded in workflows blind STEM researchers have described publicly in accessibility and academic communities.
Here's a typical daily research workflow, as blind researchers describe it:
# Text editing and coding
emacs manuscript.tex
# With Emacspeak for audio feedback
emacspeak-toggle-auditory-icons
# Compile LaTeX
pdflatex manuscript.tex
# Python data analysis
python analyze_spectra.py
# Version control
git commit -m "Add statistical analysis"
Aelira doesn't disrupt your workflow. It adds one command to your existing terminal routine:
# Your existing workflow
emacs paper.tex
pdflatex paper.tex
# Add one command for accessible output
aelira latex-to-mathml paper.tex --output paper-accessible.html
# Equations converted to MathML
# Structure preserved
# ARIA labels added automatically
# Output: 98/100 accessibility score
Blind researchers consistently rank presentations as the worst accessibility problem — worse than PDFs. Here's why:
Aelira provides two solutions:
# Create slides in Beamer (LaTeX)
emacs presentation.tex
# Convert to accessible HTML slides
aelira beamer-to-html presentation.tex --output slides/
# Each slide becomes an HTML page
# Keyboard navigation (arrow keys)
# Screen reader announces slide numbers
# Collaborator sends you slides.pptx
curl -O https://collaborator.edu/slides.pptx
# Generate accessible text summary
aelira pptx-to-text slides.pptx --output slides.txt
# Extracts all text content
# Generates alt text for images (AI)
# Describes slide layouts
# Terminal-readable format
Here's how a blind astrophysics researcher might prepare a paper for publication:
Manual accessibility work: 40+ hours (if you could even do it)
With Aelira CLI: 5 minutes of terminal commands
Difference: You focus on research, not accessibility bureaucracy
Add Aelira to your LaTeX compilation hooks:
~/.emacs.d/init.el
Now you can compile accessible versions with C-c C-a.
The core insight: the terminal is pure text, which makes it universally accessible to screen readers.
Blind power users consistently report that terminal workflows stay accessible where GUI point-and-click software does not. This is exactly why we built Aelira with a CLI-first approach. We respect your workflow.
Built by developers who understand that terminal accessibility isn't a limitation - it's a feature.