Universal Design: Seven Principles for Inclusive Software

UPI Study › Courses › System Analysis and Design › Free lessons › Lesson 4.10 Free with a free account

Universal Design: Seven Principles for Inclusive Software

System Analysis and Design · Chapter 4: Requirements Validation, Modeling, and UMLSection 4.10 · lesson 33 of 699 min · free with a free account

← The Design Phase Within the Software Development Life CycleNext lesson: Rules and Guidelines for Human-Centered Interface Design →

Earn 3 college credits for System Analysis and DesignRecommended for credit by NCCRS · Computer Science 390 · self-paced · one payment, lifetime access
Enroll in System Analysis and Design · $250 →Download the syllabus (PDF)

In this lesson

7 principles for inclusive software - and how they relate to WCAG.

  • Define accessibility, and why it is a requirements concern
  • Identify the 7 principles of Universal Design, with a software example of each
  • Explain how Universal Design relates to WCAG, and where each is used

Transcript

Everything said in the video, section by section (1,124 words). Read along, or search it.

Requirements Validation, Modeling, and UML

Universal Design

This chapter has been about capturing requirements, and modeling them precisely. It ends with a kind of requirement that is easy to overlook until it is too late. Accessibility. We will define accessibility, and see why it belongs in analysis rather than testing. Then the seven principles of Universal Design, each with a software example. And finally, how those principles relate to WCAG, the web's testable accessibility standard.

What Accessibility Means

The Widest Possible Range of Abilities

Accessibility is the extent to which a product can be used by people, across the widest possible range of abilities. And without requiring a special, adapted version. That range is broader than it first appears. It includes permanent conditions, such as blindness, or limited hand mobility. It includes temporary ones, such as a broken arm. And it includes purely situational ones. Trying to read a screen in bright sunlight, or using an app one-handed while holding a bag. Seen that way, almost every user is, at some point, a user who benefits from accessible design.

Why Design It In Early

Accessibility Helps Everyone

Designing for accessibility from the start, rather than patching it in afterward, tends to produce a better product for everyone. Not just for the users a feature was originally aimed at. A ramp built for wheelchair users also helps someone pushing a stroller, or rolling a suitcase. Captions built for deaf users also help someone watching a video with the sound off, on a train. That spillover benefit is part of why accessibility is treated as a requirement to gather during analysis. Not a technical detail to leave until testing. And remember the cost of change curve. Accessibility patched in at the end is expensive accessibility.

Universal Design

A Philosophy From Physical Design

Universal Design is a broader design philosophy. It aims to make things usable by as many people as possible, without needing adaptation, or specialized redesign. It was originally developed for physical spaces and products. But its seven principles translate directly into software. For an analyst, that is the real value. They provide a vocabulary for accessibility requirements that goes beyond a single checklist.

The 7 Principles (1 of 3)

Equitable Use and Flexibility in Use

Principle one is equitable use. The design is useful to people with diverse abilities. It offers the same means of use for everyone, or an equivalent means when identical use is not possible. In software, alt text gives a screen-reader user access to the same image content a sighted user sees. Without a separate, lesser version of the page. Principle two is flexibility in use. The design accommodates a wide range of preferences and abilities, by offering choices in how it is used. For example, supporting full keyboard navigation alongside the mouse. And letting users adjust font size, or color contrast, to their own needs.

The 7 Principles (2 of 3)

Simple, Perceptible, and Error-Tolerant

Principle three is simple and intuitive use. The design is easy to understand, regardless of the user's experience, language skill, or current level of concentration. In software, that means consistent navigation placement on every screen, and plain-language labels instead of jargon or unexplained icons. Principle four is perceptible information. Necessary information is communicated effectively, regardless of ambient conditions, or the user's own sensory abilities. That means captions on video content. And it means never using color alone to signal an error, since that information would be lost on a colorblind user. Principle five is tolerance for error. The design minimizes the hazards and consequences of accidental or unintended actions. A confirmation prompt before a destructive action, such as deleting an account. And an undo option after a change is made.

The 7 Principles (3 of 3)

Low Effort, and Room to Operate

Principle six is low physical effort. The design can be used efficiently and comfortably, with a minimum of fatigue. That means avoiding interactions that require holding a key combination for a long press. And supporting voice input as an alternative to typing. Principle seven is size and space for use. Appropriate size and space are provided to approach, reach, and operate the design, regardless of body size, posture, or mobility. In software, that means touch targets large enough to tap reliably. And a responsive layout that still works when zoomed in significantly on a small screen.

A Testable Standard

WCAG and POUR

Universal Design has a close relative in the web world. The web content accessibility guidelines, or WCAG, are a specific, testable technical standard for web and digital content. They are organized around four principles, often remembered by the acronym POUR. Content must be perceivable. It must be operable. It must be understandable. And it must be robust.

2 Tools, One Goal

Universal Design vs. WCAG

Universal Design and WCAG pursue the same goal. But they work at different levels of specificity. Universal Design is a general philosophy, originally developed for physical spaces and products, and later applied to software. WCAG is a technical standard, published by the W three C, specifically for web and digital content. Universal Design offers broad principles, meant to guide thinking about a design. WCAG offers specific, numbered success criteria, describing exactly what must be true of the content. Universal Design is not directly testable. A design either reflects the spirit of a principle, or it does not. WCAG is directly testable, and each success criterion has defined conformance levels. A, double A, and triple A. Universal Design shapes requirements and design decisions early, for any kind of product. WCAG verifies that specific web or software content meets a defined, auditable bar.

Working Together

Principles Early, Standard Later

In practice, the two work together. They do not compete. Universal Design's principles are a useful way to think through accessibility while requirements are still being gathered. They apply broadly, and they prompt the right questions early. WCAG becomes the tool used later, once there is actual content and interface to check. It confirms that the product meets a specific, testable bar, rather than only a general intention. Principles to shape the system. A standard to prove the result.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. Accessibility is the extent to which a product can be used across the widest possible range of abilities, without a special adapted version. Universal Design is a philosophy of making things usable by as many people as possible, expressed in seven principles. WCAG, the web content accessibility guidelines, is a specific, testable standard published by the W three C. POUR stands for perceivable, operable, understandable, and robust. And conformance levels, A, double A, and triple A, describe how fully WCAG's success criteria are met.

Key Takeaways

What to Carry Forward

To pull this together. Accessibility means a product can be used across the widest range of abilities, including permanent, temporary, and situational conditions. The seven principles of Universal Design translate directly into software requirements. Equitable use, flexibility, simple and intuitive use, perceptible information, tolerance for error, low physical effort, and size and space for use. Universal Design shapes early design thinking. WCAG is a specific, testable standard used to verify the result. And designing for accessibility from the start tends to benefit every user, not only the ones a feature was first intended for.

About System Analysis and Design at UPI Study

System Analysis and Design (Computer Science 390) is a self-paced online course of 69 video lessons in 9 chapters, from the analyst's role and requirements to UML modeling, interface and database design, testing, maintenance and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take System Analysis and Design with UPI Study

From business problem to working systemSystem Analysis and Design teaches how analysts study a business need and turn it into a system design: requirements, UML and data-flow models, interface and database design, implementation and project management. It is a core course in information systems and IT degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

System Analysis and Design carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Universal Design: Seven Principles for Inclusive Software

What does accessibility mean in software design?
Accessibility is the extent to which a product can be used by people across the widest possible range of abilities without needing a special, adapted version. That range includes permanent conditions such as blindness, temporary ones such as a broken arm, and situational ones such as reading a screen in bright sunlight. Because it is a requirement, it is best gathered during analysis rather than patched in during testing.
What are the seven principles of Universal Design?
The seven principles of Universal Design are equitable use, flexibility in use, simple and intuitive use, perceptible information, tolerance for error, low physical effort, and size and space for use. In software they translate into features such as alt text, keyboard navigation, plain-language labels, captions, undo options and confirmation prompts, voice input, and touch targets large enough to tap reliably.
What is the difference between Universal Design and WCAG?
Universal Design is a broad design philosophy, originally developed for physical spaces and products, while WCAG is a specific, testable technical standard published by the W3C for web and digital content. Universal Design's principles guide thinking early but are not directly testable. WCAG has numbered success criteria organized around POUR (perceivable, operable, understandable, robust) and conformance levels A, AA, and AAA, used to verify the result.
Why does accessible design benefit users without disabilities?
Accessible design benefits nearly everyone because features built for one group often help many others. Captions created for deaf users also help someone watching a video with the sound off on a train, much as a wheelchair ramp also helps a person pushing a stroller. Almost every user faces a temporary or situational limitation at some point, such as holding a bag while using an app one-handed.

About the System Analysis and Design course

How many college credits is System Analysis and Design?
System Analysis and Design (Computer Science 390) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does System Analysis and Design cost and what is included?
$250, paid once, with lifetime access: all 69 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does System Analysis and Design take?
It is self-paced with no deadlines. The 69 lessons total about 9 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in System Analysis and Design.

69 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in System Analysis and Design →Download the syllabusEvery course with PRO →
System Analysis and Design
3 credits · NCCRSEnroll →