ISO/IEC 24751
| Field | Value |
|---|---|
| Status | Adopt the vocabulary for the accessibility domain (catalogue entry only) |
| Version pinned | ISO/IEC 24751-2:2008 (with parts 1 and 3:2008 and part 4:2023) |
| Source | https://www.iso.org/standard/43603.html |
| What is taken | Accessibility preference terms, pending a licensed text |
| Why | Avoids inventing accessibility keys |
| What is extended or replaced | Maps to vocabulary keys |
| Specification home | Vocabulary registry |
Version pinned
The ISO/IEC 24751 series, Individualized adaptability and accessibility in e-learning, education and training, from JTC 1/SC 36, read from ISO's open data feed on 4 October 2026 (the catalogue pages refused automated reads):
- ISO/IEC 24751-1:2008, Framework and reference model, catalogue 41521.
- ISO/IEC 24751-2:2008, "Access for all" personal needs and preferences for digital delivery, catalogue 43603, the part relevant to accessibility preferences.
- ISO/IEC 24751-3:2008, "Access for all" digital resource description, catalogue 43604.
- ISO/IEC 24751-4:2023, "Access for all" framework for individualized accessibility and registry server API, catalogue 82901.
What is taken
No licensed copy of the standard was available to the editors; the field-level mapping from the accessibility vocabulary keys to part 2's preference terms is pending a licensed text, and this record cites the catalogue entry only.
Why
Accessibility preferences are among the most sensitive and useful context a person can share; reusing an established information model avoids inventing terms.
What is extended
When the mapping is written, each mapped term becomes a vocabulary key with its disclosure levels and renderings (see the vocabulary registry).
What is replaced or not used
Parts 1, 3 and 4 are recorded for context; only part 2's preference terms are candidates for mapping.
Deviations
The vocabulary registry already states that no semantic compatibility with ISO 24751 is claimed without a separately reviewed mapping. The mapping is pending a licensed text.
Conformance checks
None until the mapping exists; the VOCAB checks will cover any key it adds.
References to other standards and projects describe intended technical alignment only and do not imply endorsement or partnership.