Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 29138-3: Information Technology — Accessibility Considerations for People with Disabilities — Part 3: User Needs Mapping
A systematic framework for identifying and addressing accessibility requirements in ICT products and services
ISO/IEC 29138-3 provides a structured framework for identifying, documenting, and addressing the accessibility needs of people with disabilities in information and communication technology (ICT) products and services. As digital inclusion becomes a legal and ethical imperative worldwide, this standard offers a systematic methodology for ensuring that ICT systems are usable by people with diverse sensory, physical, cognitive, and linguistic abilities. The standard bridges the gap between high-level accessibility principles and practical engineering implementation.
The user needs mapping framework in ISO/IEC 29138-3 is designed to work in conjunction with ISO/IEC 29138-1 (which catalogs user accessibility needs) and ISO/IEC 29138-2 (which provides guidance on stakeholder engagement). Together, these standards form a comprehensive toolkit for organizations committed to inclusive product design and digital accessibility.
User Needs Identification and Mapping Framework
The standard defines a four-phase process for accessibility user needs mapping: Discovery, Analysis, Specification, and Verification. In the Discovery phase, organizations identify the range of user diversity scenarios relevant to their product or service, considering the full spectrum of disabilities including visual, hearing, mobility, cognitive, speech, and multiple impairments. The Analysis phase examines how each identified user need maps to specific ICT system components and interaction points.
The Specification phase translates user needs into concrete accessibility requirements with measurable acceptance criteria. For example, the user need for “perceiving visual information” translates to requirements for text alternatives, color contrast ratios meeting WCAG 2.1 Level AA standards, and compatibility with screen reader software. The Verification phase establishes testing protocols to confirm that implemented features meet the defined accessibility criteria.
| Phase | Activities | Key Outputs | Stakeholder Involvement |
|---|---|---|---|
| Discovery | User research, disability scenario analysis, persona development | User diversity matrix, accessibility use cases | End users with disabilities, advocacy organizations |
| Analysis | Gap analysis, interaction mapping, barrier identification | Accessibility requirements traceability matrix | UX designers, accessibility specialists |
| Specification | Requirement definition, acceptance criteria development | Functional accessibility specification | Engineers, product managers, QA teams |
| Verification | Testing protocol development, conformance assessment | Test reports, conformance statements | QA engineers, third-party accessibility auditors |
A common pitfall in accessibility implementation is treating user needs mapping as a one-time activity performed at the beginning of a project. Accessibility requirements must be continually revisited throughout the development lifecycle. Changes in platform capabilities, user feedback, assistive technology updates, and regulatory requirements can all introduce new accessibility considerations that require corresponding adjustments to the user needs map.
Accessibility Requirements for ICT Products
ISO/IEC 29138-3 organizes accessibility requirements across four fundamental principles that align with the Web Content Accessibility Guidelines (WCAG) framework: Perceivable, Operable, Understandable, and Robust (POUR). For ICT products, these principles extend beyond web content to include hardware interfaces, software applications, documentation, and support services. The standard provides detailed requirement categories for each principle with specific applicability to different ICT product types.
Perceivable requirements address the need for content to be presented in multiple sensory modalities — visual, auditory, and tactile. This includes text alternatives for non-text content, captions for multimedia, and adaptable presentation formats. Operable requirements ensure that all users can interact with ICT products regardless of input method, covering keyboard accessibility, voice control, switch device compatibility, and alternative pointing systems. Understandable requirements focus on predictable behavior, clear language, and error prevention. Robust requirements ensure compatibility with current and future assistive technologies.
Organizations that implement the systematic user needs mapping approach described in ISO/IEC 29138-3 consistently report broader benefits beyond disability access. The inclusive design principles identified through this process frequently lead to improvements that benefit all users — such as clearer navigation, more intuitive interfaces, and more flexible interaction methods — a phenomenon known as the “curb-cut effect” in digital accessibility.
Implementation Strategies for Inclusive Design
The standard provides practical guidance for incorporating accessibility requirements into established product development processes. It recommends integrating accessibility user needs mapping into agile development frameworks through dedicated user stories, acceptance criteria, and definition of done that explicitly reference accessibility requirements. For waterfall development models, the standard provides templates for accessibility requirements specification documents and traceability matrices.
Organizational capability building is emphasized as a critical success factor. The standard recommends establishing cross-functional accessibility teams, providing regular training for developers and designers on accessible design patterns, and creating organizational accessibility policies with executive sponsorship. Procurement considerations are also addressed, with guidance on including accessibility requirements in vendor selection criteria and contract terms.
| User Need Category | Examples | Technology Solutions | Testing Methods |
|---|---|---|---|
| Visual accessibility | Low vision, blindness, color blindness | Screen readers, magnification, high contrast, text-to-speech | Screen reader testing, color contrast analysis, keyboard-only navigation |
| Hearing accessibility | Deaf, hard of hearing | Captions, transcripts, visual indicators, hearing aid compatibility | Caption accuracy review, audio alternative verification |
| Mobility accessibility | Limited fine motor control, tremor, paralysis | Voice control, eye tracking, switch access, adaptive keyboards | Voice control testing, switch device compatibility, timing override verification |
| Cognitive accessibility | Learning disabilities, memory impairment, autism | Simplified interfaces, consistent navigation, visual cues, error prevention | User testing with cognitive disability groups, readability analysis |
| Speech accessibility | Speech impairment, communication disability | Text-based alternatives, augmentative communication support | Alternative input method validation, speech recognition tolerance testing |
Failure to address accessibility is not just a design shortcoming but increasingly a legal liability. Numerous jurisdictions have enacted digital accessibility laws with significant penalties for non-compliance, including the European Accessibility Act, the Americans with Disabilities Act (ADA) as applied to digital services, and various national accessibility regulations. ISO/IEC 29138-3 provides a defensible methodology that demonstrates good-faith efforts to meet accessibility obligations and can serve as evidence of due diligence in regulatory proceedings.
When implementing accessibility user needs mapping, engage users with disabilities directly rather than relying solely on checklists or automated testing tools. Automated accessibility testing tools typically detect only 20-30% of accessibility issues. Real user testing with people who have diverse disabilities reveals usability barriers that automated tools miss, including nuanced interaction problems that significantly affect the user experience for people with disabilities.
Frequently Asked Questions
Q: How does ISO/IEC 29138-3 relate to the Web Content Accessibility Guidelines (WCAG)?
A: ISO/IEC 29138-3 and WCAG are complementary frameworks. WCAG provides specific, testable success criteria for web content accessibility, while ISO/IEC 29138-3 provides a broader methodology for identifying and mapping user needs across the full range of ICT products — including hardware, software, documentation, and services. WCAG can be used as a reference for the Specification phase of the user needs mapping process. Together, they provide both the “what” (WCAG criteria) and the “how” (29138-3 methodology) for comprehensive accessibility implementation.
Q: Is ISO/IEC 29138-3 applicable only to software products, or does it cover hardware as well?
A: The standard covers the full range of ICT products including hardware, software, firmware, documentation, and services. For hardware products, accessibility considerations include physical design aspects such as button size and spacing, tactile differentiation of controls, visual indicator design, connector accessibility, and compatibility with assistive technology devices. The user needs mapping framework is equally applicable to hardware product design, though the specific requirements and test methods differ from those used for software accessibility.
Q: What resources are needed to implement the user needs mapping framework effectively?
A: Effective implementation requires a combination of personnel, tools, and organizational commitment. Key resources include: access to users with diverse disabilities for participatory design and testing, trained accessibility specialists who understand both the technical and human dimensions of accessibility, appropriate testing tools including screen readers, accessibility evaluation software, and specialized input devices, and management support for allocating time and budget to accessibility activities throughout the development lifecycle rather than treating accessibility as a last-minute compliance check.
Q: Can small organizations with limited budgets still implement ISO/IEC 29138-3 effectively?
A: Yes. The standard is designed to be scalable. Small organizations can start with a focused approach: identify the most common disability categories relevant to their product, engage with local disability advocacy groups for user testing partnerships, leverage open-source accessibility testing tools, and prioritize the most impactful accessibility improvements. Even incremental implementation of the user needs mapping framework produces meaningful improvements in product accessibility and demonstrates good-faith compliance efforts. The key is to start early in the development process and address accessibility iteratively rather than attempting a complete overhaul at the end.
