Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 29140: Information Technology — Accessibility of IT Products
Comprehensive accessibility requirements and design guidelines for inclusive information technology products
ISO/IEC 29140 establishes comprehensive accessibility requirements and evaluation methodologies for information technology products, covering hardware devices, software applications, operating systems, and integrated IT systems. As technology becomes increasingly embedded in every aspect of daily life and work, ensuring that IT products are accessible to people with diverse abilities is both a social imperative and a market opportunity. This standard provides a unified framework that consolidates and extends existing accessibility guidelines into a coherent set of requirements applicable across the full spectrum of IT products.
ISO/IEC 29140 serves as a comprehensive reference for organizations seeking to implement accessible IT product design across their entire product portfolio. Unlike guidance documents focused on specific technologies (such as WCAG for web), this standard addresses the accessibility of IT products in their entirety, including hardware-software integration, installation procedures, configuration interfaces, and technical support systems.
Accessibility Requirements Framework for IT Products
The standard defines a hierarchical requirements framework organized into five domains: User Interface Accessibility, which covers all interaction modalities including graphical user interfaces, command-line interfaces, touch interfaces, and voice-controlled systems; Content Accessibility, addressing the accessibility of text, images, multimedia, and data presented through IT products; Hardware Accessibility, covering physical design aspects including input devices, displays, connectors, and form factors; Documentation and Support Accessibility, ensuring that user manuals, online help, installation guides, and technical support services are accessible; and Ecosystem Compatibility, addressing interoperability with assistive technologies and accessibility features of underlying platforms.
Each domain contains specific requirements with defined priority levels: Level 1 requirements represent fundamental accessibility features that must be implemented to achieve basic usability for people with disabilities, Level 2 requirements address enhanced accessibility for more effective use, and Level 3 requirements cover specialized features for specific disability populations or use cases. This prioritization enables organizations to implement accessibility incrementally while ensuring that the most critical requirements are addressed first.
| Domain | Level 1 Requirements (Essential) | Level 2 Requirements (Enhanced) | Level 3 Requirements (Specialized) |
|---|---|---|---|
| User Interface Accessibility | Keyboard navigation, screen reader compatibility, adjustable font size | Voice control, high contrast modes, customizable color schemes | Eye tracking, brain-computer interface, gesture control |
| Content Accessibility | Alt text for images, captions for video, structured headings | Plain language summaries, multilingual support, sign language video | Braille output, tactile graphics, audio description |
| Hardware Accessibility | Tactile differentiation of controls, accessible connector placement | Adjustable mounting, one-handed operation, voice feedback | Custom input devices, sip-and-puff interfaces, prosthetic compatibility |
| Documentation and Support | Electronic documentation in accessible formats, accessible help system | Video tutorials with captions, documentation in plain language | Sign language support, personal assistance services |
| Ecosystem Compatibility | Standard API for assistive technology, platform accessibility support | Third-party accessibility tool compatibility, accessibility profiles | Custom accessibility scripting, extensible accessibility framework |
The three-level priority system in ISO/IEC 29140 is designed to support staged implementation, not to suggest that Level 2 and 3 requirements are optional. Organizations should assess their target markets and user populations to determine appropriate target levels. For products intended for public sector procurement, educational institutions, or healthcare settings, Level 1 and Level 2 requirements are typically mandatory, and Level 3 requirements may be required for specific use cases.
Conformance Assessment and Testing Methodologies
ISO/IEC 29140 establishes a comprehensive conformance assessment framework that combines automated testing, expert evaluation, and user testing. Automated testing addresses programmable checks such as code validation, color contrast analysis, and API compliance verification. Expert evaluation involves accessibility specialists conducting systematic reviews against the standard’s requirements. User testing engages people with disabilities in realistic task scenarios to identify usability barriers that automated and expert methods may miss.
The standard provides detailed testing protocols for each requirement, specifying test conditions, test procedures, required tools, and pass/fail criteria. For hardware accessibility testing, physical measurement protocols are defined for parameters such as actuation force, button size, display viewing angle, and connector accessibility. For software accessibility, the standard references platform-specific accessibility APIs and provides guidance on testing with assistive technologies including screen readers, screen magnifiers, and alternative input devices.
The multi-method conformance assessment approach prescribed by ISO/IEC 29140 significantly improves accessibility outcomes compared to checklist-based approaches. Studies have shown that combining automated testing (which catches 20-30% of issues), expert review (catching 40-60%), and user testing (catching 60-80%) achieves comprehensive coverage approaching 90% or higher when all three methods are applied iteratively throughout the development lifecycle.
Design for All: Universal Design Principles in Practice
The standard embeds universal design principles throughout its requirements framework, emphasizing that accessible design benefits all users, not just those with permanent disabilities. The seven principles of universal design — equitable use, flexibility in use, simple and intuitive use, perceptible information, tolerance for error, low physical effort, and size and space for approach and use — are mapped to specific requirements in each domain.
Practical implementation guidance addresses common challenges including: retrofitting accessibility into existing products versus designing for accessibility from the outset, managing accessibility across product families with shared components, balancing accessibility requirements with security constraints, and addressing conflicts between different accessibility requirements (for example, the tension between simplified interfaces for cognitive accessibility and rich customization options for advanced users). The standard provides decision frameworks for resolving such conflicts through user-centered design processes.
| Universal Design Principle | IT Product Application | Implementation Example | Beneficiary Population |
|---|---|---|---|
| Equitable use | Identical or equivalent functionality for all users | Voice and keyboard input achieving same functions | All users, especially mobility-impaired and situationally constrained |
| Flexibility in use | Choice of interaction methods | Multiple input methods: mouse, keyboard, touch, voice, switch | Users with varied physical, sensory, and cognitive abilities |
| Simple and intuitive | Consistent navigation patterns, clear language | Logical tab order, meaningful icons, consistent menu structure | Cognitive disabilities, non-native speakers, new users |
| Perceptible information | Multi-modal information presentation | Visual + auditory + tactile feedback for system status | Visual, hearing, and attention-related disabilities |
| Tolerance for error | Undo/redo, confirmation dialogs, error suggestions | Autosave, undo history, actionable error messages | Cognitive disabilities, all users in high-stress situations |
| Low physical effort | Minimize repetitive or sustained physical actions | Keyboard shortcuts, auto-complete, macro recording | Motor disabilities, repetitive strain injury, power users |
| Size and space | Accessible physical design dimensions | Appropriate button spacing, reachable connector positions | Mobility disabilities, users of assistive devices |
Organizations pursuing IT product accessibility must avoid the trap of “accessibility theater” — implementing superficial features that check compliance boxes without genuinely improving usability for people with disabilities. Examples include adding alt text that does not convey meaningful information, implementing keyboard navigation that is technically present but practically unusable, or including accessibility settings that are themselves inaccessible to configure. ISO/IEC 29140’s emphasis on user testing and conformance assessment is specifically designed to prevent these outcomes by requiring evidence of actual usability rather than just feature presence.
The business case for IT product accessibility is increasingly compelling. The global market of people with disabilities represents over 1.3 billion individuals with an estimated annual disposable income exceeding 1.2 trillion USD. Additionally, inclusive design features frequently benefit the broader population — voice control aids hands-free operation, captions benefit users in noisy environments, and high contrast modes reduce eye strain for all users during extended use. Accessibility is not just compliance — it is good product design and sound business strategy.
Frequently Asked Questions
Q: What is the relationship between ISO/IEC 29140 and ISO/IEC 29138-3?
A: ISO/IEC 29138-3 focuses specifically on the methodology for identifying and mapping user accessibility needs — the “upstream” process of understanding what users with disabilities require from ICT products. ISO/IEC 29140 takes those identified needs and provides the corresponding “downstream” requirements framework, conformance assessment methods, and design guidelines for IT products. Together, they form a complete lifecycle: 29138-3 tells you what user needs to consider, and 29140 tells you how to build products that meet those needs and how to verify compliance.
Q: Does ISO/IEC 29140 apply to mobile applications and mobile operating systems?
A: Yes, the standard’s scope explicitly includes mobile platforms. Mobile accessibility requirements cover touch screen accessibility, gesture customization, screen reader compatibility (such as VoiceOver for iOS and TalkBack for Android), adjustable text sizing, orientation support, and compatibility with external assistive devices via Bluetooth and USB. The standard addresses both native mobile applications and mobile web interfaces, recognizing the increasing convergence of these platforms.
Q: How does ISO/IEC 29140 address emerging technologies such as artificial intelligence and virtual reality?
A: The standard’s requirements framework is designed to be technology-neutral and extensible. For AI-powered IT products, accessibility considerations include ensuring that AI-driven interfaces (such as chatbots and voice assistants) are accessible to users who cannot use voice input, providing transparency about AI decision-making in accessible formats, and ensuring that machine learning training data includes diverse user populations. For virtual reality (VR) and augmented reality (AR), the standard addresses motion sickness considerations, alternative navigation methods for users with mobility limitations, audio descriptions for visual AR content, and captioning for spatial audio.
Q: What documentation is required to demonstrate ISO/IEC 29140 conformance?
A: The standard requires a conformance statement documenting which requirements have been addressed and at what level, test reports from all three assessment methods (automated, expert, and user testing), a description of the accessibility features implemented and instructions for accessing them, documentation of any known limitations or workarounds for users with disabilities, and a process description showing how accessibility was integrated into the product development lifecycle. Third-party certification is not required by the standard but may be demanded by specific procurement or regulatory requirements.
