Equity - SOEN390-ConUNav/SOEN390-Mini-Cap-Project GitHub Wiki

5.2 Equity

Often, illiterate or marginalized people, as well as people with disabilities including those who are color-blind, blind, deaf, or use wheelchairs are not adequately taken into account during the design and development of software applications. Designing a system that considers these users is essential to make sure that the software is accessible and usable by as many people as possible, regardless of their abilities or limitations. Research in software accessibility highlights that accessibility is often overlooked during early development stages and should be treated as a fundamental design requirement rather than an afterthought [1], [2].

1. Users with Visual Disabilities

Challenges

  • Difficulty differentiating certain colors (color-blind people)
  • Difficulty reading small text
  • Blind users rely on screen readers to navigate and use applications

Accessibility Solutions

  • High color contrast to avoid relying only on color
  • Include text labels alongside icons instead of using color indicators alone
  • Ensure interface elements are clearly labeled and structured to be compatible with screen reader technologies
    • Avoid images of text (use real text so it can be resized/read by screen readers)
    • Use proper structure (headings/landmarks like main) so keyboard/screen-reader users can skip repetitive menus faster
  • Allow users to adjust text size according to their preferences
  • Provide voice-based feedback for essential information when needed

2. Users with Visual Disabilities(Color-Blind)

Challenges -Color-blind people do not all see colors the same way. Some have problems telling red and green apart, what we call protanopia and deuteranopia, while others struggle with blue and yellow, tritanopia and a few see very few colors at all.

  • When an app uses only color to show meaning (like red = error, green = success), the message can be unclear
  • Low‑contrast colors can make text or icons hard to see
  • Charts or graphs that use many similar colors can be confusing
  • Small color changes used for warnings or active buttons may not be noticeable

Accessibility Solutions

  • Do not rely on color alone; always add text, icons, shapes, or patterns to show meaning
  • Choose color‑blind‑friendly palettes and test them with color‑blind simulators and use strong contrast so colors stand out clearly
  • Add text labels to buttons, alerts, and graphs so users can understand them even if colors look similar
  • Make sure important changes (like errors or active states) use more than just a color change, for example, add an icon or bold text

3. Users with Hearing Disabilities

Challenges

  • Cannot rely on audio alerts or announcements to receive information or notifications
  • Audio content without text alternatives

Accessibility Solutions

  • Visual notifications such as flashing lights/strobes or vibrational notifications instead of sound-based cues
  • Text-based updates instead of voice-only information
  • Clear written and simple instructions
  • Provide text alternatives or transcripts for audio-based information

4. Users with Motor Disabilities or Hand Injuries

Challenges

  • Difficulty tapping small buttons
  • Difficulty completing complex gestures due to reduced mobility
  • Accidental taps due to tightly packed UI elements

Accessibility Solutions

  • Use large touch targets to make interaction easier
  • Minimize the number of taps needed to complete tasks
  • Add spacing around buttons (inactive space around touch targets reduces accidental taps)
  • Avoid swipe-only or precise gestures such as typing long inputs by offering alternate input methods

5. Illiterate or Low-Literacy Users

Challenges

  • Difficulty reading long text or understanding complex terms
  • Difficulty processing large amounts of information at once
  • Difficulty remembering multi-step processes

Accessibility Solutions

  • Use simple, plain language
  • Reduce cognitive load by not showing too many objects on the screen at once, keeping actions predictable and avoiding long dense rows of text
  • Pair icons with text to help understanding
  • Provide visual cues, such as maps and symbols, to guide users
  • Break tasks into small, clearly labeled steps
  • Provide immediate feedback after user actions

6. Marginalized or Underrepresented Users

Challenges

  • Unfamiliar with the system or surrounding environment
  • Limited experience with technology or lack of confidence when using unfamiliar applications

Accessibility Solutions

  • Provide clear and straightforward instructions
  • Avoid assuming prior knowledge from users
  • Maintain a consistent layout and interaction style across the application to avoid confusion

Finally, incorporating accessibility considerations early in the software design process allows applications to better support users with diverse abilities, literacy levels, and technological backgrounds [3]. By addressing visual, auditory, motor, cognitive, and social barriers, software can become clearer, more intuitive, and more inclusive for all users. In today’s increasingly digital world, failing to account for accessibility risks unintentionally excluding entire groups of people, making inclusive design not only a technical responsibility but also an ethical and societal obligation.

References

[1] T. Bi, X. Xia, D. Lo, J. Grundy, T. Zimmermann, and D. Ford, “Accessibility in Software Practice: A Practitioner’s Perspective,” ACM Transactions on Software Engineering and Methodology, vol. 31, no. 4, pp. 1–26, Jul. 2022.

[2] W. Shi, H. Moses, Q. Yu, S. A. Malachowsky, and D. E. Krutz, “ALL: Supporting Experiential Accessibility Education and Inclusive Software Development,” ACM Transactions on Software Engineering and Methodology, vol. 33, no. 2, Feb. 2024.

[3] M. Di Gregorio, D. Di Nucci, F. Palomba, and G. Vitiello, “The making of accessible Android applications: An empirical study on the state of the practice,” Empirical Software Engineering, vol. 27, no. 7, 2022.