Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Scope and Purpose
The standard formally registered as ISO 10027-1:2018, traceable to its development phase as IEC 10027-95 within ISO/IEC Joint Technical Committee 1 (JTC 1), establishes a rigorous taxonomy and specification for user interface (UI) component accessibility. It addresses a critical gap in modern software architecture by defining exactly how UI elements—from simple text fields to complex tree views—must behave to ensure compatibility with assistive technologies. This article provides a detailed technical examination of the standard’s scope, core requirements, and compliance pathways.
Scope and Purpose
ISO 10027-1:2018 specifies accessibility requirements and recommendations for user interface components. Unlike broad standards focused on content (such as WCAG), this standard zooms into the granular software engineering level, targeting developers, UI framework designers, and quality assurance engineers. The standard applies to all interactive systems, including web applications, desktop environments, and mobile operating systems.
Key Contribution: ISO 10027-1:2018 provides a unified component model, allowing developers to implement accessibility once in a framework and ensure consistency across all applications using that framework.
Core Technical Requirements
Component Taxonomy
The standard defines a hierarchical classification of UI components: basic controls (button, text field, checkbox), composite controls (combo box, date picker), containers (window, panel, group box), and abstract roles (live region, presentation). Each type inherits mandatory accessibility properties.
Accessibility Properties
Every UI component must expose a consistent set of properties to the platform accessibility API:
- Role: The semantic purpose (e.g.,
button,slider). - Name: A human-readable label (computed via labeling logic: text content,
aria-label, or associated<label>). - Value: Current state for controls like sliders (e.g., “25%”) or toggles (e.g., “checked”).
- State: Interactivity flags such as disabled, expanded, selected.
- Description: Help text or contextual hints.
- Keyboard Support: Specific key handlers for arrow keys, Enter, Escape, Tab.
| Component Role | Required Properties | Required Actions | Focus Support |
|---|---|---|---|
| Button | Role, Name, State (disabled) | Click, Focus | Yes |
| Slider | Role, Name, Value (min, max, current), State | Set Value, Increment, Decrement | Yes |
| Tree View | Role, Name, State (expanded, selected), Level | Expand, Collapse, Navigate, Select | Yes |
| Text Field | Role, Name, Value (text content), State (readonly) | Set Text, Focus | Yes |
Implementation Pitfall: The standard mandates that naming priority must follow a strict algorithm (e.g.,
aria-labelledby > aria-label > associated label). Developers must ensure their custom controls respect this cascading logic to avoid “silent” components. Implementation Highlights
Implementing ISO 10027-1:2018 requires close alignment with platform-level accessibility frameworks. The standard explicitly maps its component model to APIs such as Microsoft UI Automation (UIA), Apple’s NSAccessibility (MAC OS) and UIAccessibility (iOS), Android’s AccessibilityNodeInfo, and the WAI-ARIA specification for web content. Conformance to the standard can be verified through automated testing tools (checking property exposure) and manual keyboard auditing.
Best Practice: When building a custom component library, design an abstraction layer over the native accessibility API. Implement the ISO 10027 component taxonomy once, then map it to iOS, Android, and Web. This drastically reduces per-platform development overhead.
Conformance Levels
The standard defines two conformance tiers: Core (mandatory support for name, role, value, keyboard navigation) and Extended (support for descriptions, custom actions, live regions, and grid navigation). Most enterprise applications aim for Core conformance as a baseline, with critical controls achieving Extended conformance.
Compliance Criticality: Failure to expose the correct Role for a component is a Critical Conformance Failure. A custom button that does not expose its role will be ignored by assistive technologies, rendering it functionally inaccessible.
Compliance and Relationship with Other Standards
ISO 10027-1:2018 does not operate in a silo. It provides the component-level specification that supports higher-level standards:
- EN 301 549 (European accessibility requirements for ICT): Must be mapped to component requirements for procurement compliance.
- WCAG 2.1 / 2.2 (Web Content Accessibility Guidelines): ISO 10027 provides the technical underpinnings for WCAG success criteria related to keyboard control (2.1.1) and name/role/value (4.1.2).
- ISO 9241-171 (Ergonomics of human-system interaction — Guidance on software accessibility): Serves as the general ergonomics framework; ISO 10027 provides the implementation details for software engineers.
Regulatory bodies increasingly require proof of conformance to an international accessibility standard. Demonstrating compliance with ISO 10027-1:2018 is a strong technical step toward meeting procurement regulations like Section 508 in the US and the European Accessibility Act.