Just recently I became aware of that my light dyslexia limits my ability to use command lines.
I have often typos and its correction slows me down. Even the completion suggestions does not help, when I have a typo in the written letters.
I hope for more functions like this tool offers:
Like having a (semi-) auto-correction on command lines.
Semi in the sense that I still have to confirm the choice. But at all getting alternatives shown for typos.
Maybe you can write something in that direction?
Or also similar, less as (explicit) disability perceived, conditions.
You can find a lot of resources related to theory (WCAG, legal requirements) but finding good practical examples is really hard. Most of the training resources are entry-level: headings, buttons, contrasts, and keyboard navigation … ok but let’s speak about all the other really tricky cases.
How to do a full manual report (audit style)
How to manage accessibility in an Agile environment.
How to automate and reasonably set up no-regression testing.
Hi folks, many thanks to those who have responded. I’ve taken onboard your feedback and have these ideas. I’d love some thoughts and feedback on what you think of the potential content and title.
Digital Accessibility - A Tester’s Guide
Chapter ideas / Contents
Introduction - What the guide is (testing described in simple terms), how to use this book (jump to the information you need easily) and who I am (background, experience etc.)
Lived Experience - caveat that as much as I can help people understand accessibility and testing I am not a replacement for having systems tested by the people who are native screen reader users, neurodiverse etc.
What is Digital Accessibility?
What are the Web Content Accessibility Guidelines
Testing the Guidelines - step by step for each WCAG one with test case (couple of formats, given, when, then - as a, I want, so that maybe other(s)
Accessibility Audits - What they are and how to do them
Making it part of your daily testing - keyboard, screen reader sessions. Use this to explain building up screen reader use
Assumptions - common misconceptions
Arguments - how to make the case for accessibility
I was referring to the command line utility referenced by @sebastian_solidwork - “The F*ck”. It would certainly be helpful for those with issues correctly typing (or those who always have to google the commands they need), but with a name like that I can’t see it getting past my employer’s filters. If the security team didn’t kill the idea, the HR team would.
It would be a fun addition to a book about accessibility, though.
Thanks for the clarification. I’ve added a task to look into it properly but a quick check has thrown up possible starting places. It’s an interesting avenue I hadn’t thought of so thank you.
Fish Shell: is a user-friendly shell for Unix-like operating systems that features extensive auto-completion capabilities. It provides intelligent suggestions based on command history, installed packages, and user-defined functions. Fish Shell is known for its excellent auto-suggestion feature.
Oh My Zsh: is a popular open-source framework for managing Zsh configurations. It comes with a variety of plugins and themes, including a powerful auto-completion system.
FZF: (Fuzzy Finder) is a command-line fuzzy finder that enables fast and efficient searching through file systems, command history, and more. It offers auto-completion functionality by providing suggestions based on partial matches and fuzzy search algorithms.
ShellCheck: is a static analysis tool for shell scripts that detects common errors, issues, and potential bugs. It helps improve the quality and accessibility of shell scripts by providing suggestions for improvements.
A11y: (Accessibility) is a command-line tool that checks web pages for accessibility issues. It analyses HTML and CSS code, providing suggestions for improving accessibility compliance.
a book for people with disabilities on resources to help them day-to-day
a book for people to learn about disabilities, to help them understand and empathise with the world around them
a book for reference on legal requirements to reduce their risk as a business from court cases and fines
a book on the statistical significance of disabilities in communities to help best allocate resources to help as many people as possible within a given budget
a book to aid testers in thinking about the needs of people with disabilities to help them build mental models to better serve them, and call out poor design
a book on the technologies that people with disabilities use that interface with your product, e.g. screen readers, and how to implement and test their interface with your product
a book to help testers advocate for accessibility in companies that have no desire to pay for it
a book on how to do user testing with people with disabilities, how to source people, what provisions to make and what equipment to have
For me I’d want to know a big mix of everything maybe starting with getting buy-in, especially saleable points like untapped market share, monetary risk, and anything else that can light a fire under management in the service of a better world, moving on to the best utility per unit cost (in a non-specific, poetic sense) set of approaches to meet requirements and make a product more accessible, then specific examples of popular tech I can get hold of for testing purposes, and resources on further learning. Easy and cheap wins are always welcome, easy to sell and useful to implement.
Essentially I’d want to get budget and then not squander it. Any one of these books would be useful in that regard.
My working title and chapter ideas are outlined in the link below. Does this help Chris?
I feel like a lot of what you mentioned is covered but at the heart it is a testers guide rather than an enterprise model. The Agile Accessibility Handbook covers a lot of that and is now available for free after registration with Deque Agile Accessibility Handbook