Accessibility of Command Line Interfaces (2021)
dl.acm.org
dl.acm.org
"learn more about the research behind Gitless, take a look at the following papers:
Purposes, Concepts, Misfits, and a Redesign of Git S. P. De Rosso and D. Jackson.
What's Wrong with Git? A Conceptual Design Analysis S. Perez De Rosso and D. Jackson.
If you want a thirty-minutes summary presentation, watch "What’s Wrong With Git?" from Git Merge 2017."
Recommendation 1: Ensure that a HTML version of all documentation is available
Recommendation 2: Provide a way to translate long outputs into another accessible format.
Recommendation 3: Document the output structure for each command.
Recommendation 4: Provide a way to translate tables in CLI output into another accessible format
Recommendation 5: Ensure that all commands provide status and progress indication.
Recommendation 6: Ensure that all status and progress indicators used are screen reader friendly.
Recommendation 7: Ensure that error messages are understandable when read aloud.
Sometimes I read them aloud to myself and it still doesn't help. Perhaps: Ensure that error messages are understandable.