By Yasmine Elglaly — Inaccessible software prevents users from accessing the digital information or the functionality it provides. This can result in limited or no access to educational services in the case of a learning management system or job search functionality in the case of an inaccessible job search platform. Consequently, the impact of inaccessible software on the quality of life of people with disabilities goes beyond the inability to access or operate the software; it is about the significance of that software in enabling them to be effective members of society. With accessible software, people with disabilities have an equitable opportunity to participate in society, including economical and political activities.
Inaccessible software can cause harm by excluding certain users, but the consequences of discrimination are even greater with AI‑based systems. These systems have the potential to magnify harm and make disability bias more systematic. For example, AI‑based systems may discriminate against people with disabilities by excluding them from advertisements for job positions and insurance services, and face, body, and speech recognition systems may not work effectively for them.
It is essential for software engineers to actively prioritize inclusion in AI‑based systems. Inclusive datasets are crucial and should ensure equitable representation of people with disabilities. Additionally, models must be trained to equally serve people with disabilities to ensure that these systems are fair and inclusive. It may seem unlikely, but the design of a software’s user interface or interaction can have a physical impact and cause harm. Certain features of software, especially those affecting users with neurological conditions like epilepsy, can pose health risks. Accessibility flaws can also negatively impact the well‑being of neurodivergent users. Therefore, it’s crucial to follow accessibility guidelines to protect the health of all users.
Although accessibility guidelines don’t address neurodiversity extensively, the WCAG 2.2 guidelines include coverage for photosensitive and motion‑sensitive users in Guideline 2.3 Seizures and Physical Reactions. For instance, one guideline states that nothing on display should flash more than three times per second. This guideline, although marked as level AAA and not required by law to be implemented, is crucial for the well‑being of neurodivergent users.
It’s important to understand that a violation of an accessibility guideline isn’t just a minor bug. An accessibility violation can render an app unusable and actively harm neurodivergent users. Therefore, it’s essential to prioritize accessibility in software design to ensure the safety and well‑being of all users.
From Horton, S., & Sloan, D. (2024). What Every Engineer Should Know About Digital Accessibility. CRC Press, Boca Raton, Florida.
Know About Accessibility 