├── .gitignore ├── .pr-preview.json ├── w3c.json ├── CODE_OF_CONDUCT.md ├── LICENSE.md ├── common ├── css │ └── custom.css └── js │ ├── css-inline.js │ ├── previousRelease.js │ ├── examples.js │ └── permalink-a11y.js ├── CONTRIBUTING.md ├── latest ├── crosswalk │ └── index.html └── index.html ├── README.md ├── crosswalk ├── indexOld.html └── MARC-UNIMARC │ └── Original-Crosswalk-Schema-ONIX-MARC21-UNIMARC.html └── index.html /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | -------------------------------------------------------------------------------- /.pr-preview.json: -------------------------------------------------------------------------------- 1 | { 2 | "src_file": "index.html", 3 | "type": "respec" 4 | } -------------------------------------------------------------------------------- /w3c.json: -------------------------------------------------------------------------------- 1 | { 2 | "group": [134546] 3 | , "contacts": ["iherman"] 4 | , "repo-type": "cg-report" 5 | } 6 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | All documentation, code and communication under this repository are covered by the [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/). 4 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | All Reports in this Repository are licensed by Contributors 2 | under the 3 | [W3C Software and Document License](http://www.w3.org/Consortium/Legal/2015/copyright-software-and-document). 4 | 5 | Contributions to Specifications are made under the 6 | [W3C CLA](https://www.w3.org/community/about/agreements/cla/). 7 | 8 | Contributions to Test Suites are made under the 9 | [W3C 3-clause BSD License](https://www.w3.org/Consortium/Legal/2008/03-bsd-license.html) 10 | 11 | -------------------------------------------------------------------------------- /common/css/custom.css: -------------------------------------------------------------------------------- 1 | pre, 2 | code { 3 | white-space: break-spaces !important; 4 | } 5 | 6 | fieldset { 7 | border: none; 8 | padding: 0; 9 | margin: 0; 10 | } 11 | 12 | legend { 13 | position: absolute; 14 | left: -9999rem; 15 | overflow: hidden; 16 | } 17 | 18 | div.ex-buttons { 19 | margin: 1rem auto -1rem; 20 | min-width: 45rem; 21 | background-color: rgb(235, 235, 235); 22 | } 23 | 24 | div.ex-buttons input { 25 | background-color: inherit; 26 | border: none; 27 | width: 5rem; 28 | height: 1.6rem; 29 | } 30 | 31 | input.active { 32 | background-color: rgb(250, 250, 250) !important; 33 | } 34 | 35 | p.synonym { 36 | margin-top: -0.5rem; 37 | margin-bottom: 2rem; 38 | padding-top: 0; 39 | font-weight: bold; 40 | font-size: 90%; 41 | } 42 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Schema.org Community Group 2 | 3 | This repository is being used for work in the W3C Schema.org Community Group, governed by the [W3C Community License 4 | Agreement (CLA)](http://www.w3.org/community/about/agreements/cla/). To make substantive contributions, 5 | you must join the CG. 6 | 7 | If you are not the sole contributor to a contribution (pull request), please identify all 8 | contributors in the pull request comment. 9 | 10 | To add a contributor (other than yourself, that's automatic), mark them one per line as follows: 11 | 12 | ``` 13 | +@github_username 14 | ``` 15 | 16 | If you added a contributor by mistake, you can remove them in a comment with: 17 | 18 | ``` 19 | -@github_username 20 | ``` 21 | 22 | If you are making a pull request on behalf of someone else but you had no part in designing the 23 | feature, you can remove yourself with the above syntax. 24 | -------------------------------------------------------------------------------- /common/js/css-inline.js: -------------------------------------------------------------------------------- 1 | 2 | function inlineCustomCSS() { 3 | 4 | var customCSS = getCSS(); 5 | 6 | if (customCSS == '') { return; } 7 | 8 | var style = document.createElement('style'); 9 | style.textContent = customCSS; 10 | 11 | document.getElementsByTagName('head')[0].appendChild(style); 12 | 13 | } 14 | 15 | function getCSS() { 16 | 17 | try { 18 | var xmlhttp = new XMLHttpRequest(); 19 | 20 | xmlhttp.open('GET', 'common/css/custom.css', false); 21 | xmlhttp.send(); 22 | 23 | if (xmlhttp.status == 200) { 24 | return xmlhttp.responseText; 25 | } 26 | else { 27 | console.error('Failed to read CSS file common/css/custom.css. Returned status: ' + xmlhttp.status); 28 | return ''; 29 | } 30 | } 31 | 32 | catch (e) { 33 | console.error(e); 34 | return ''; 35 | } 36 | } 37 | -------------------------------------------------------------------------------- /latest/crosswalk/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 |
4 | 5 |The latest version of the vocabulary is available at 23 | 24 |
25 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /latest/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 |The latest version of the vocabulary is available at 23 | 24 |
25 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /common/js/previousRelease.js: -------------------------------------------------------------------------------- 1 | 2 | function addPreviousRelease() { 3 | 4 | if (!respecConfig.hasOwnProperty('previousPublishDate')) { 5 | console.warn('Missing previousPublishDate in respec metadata. Cannot add link to previous release.'); 6 | return; 7 | } 8 | 9 | // respec converts previousPublishDate to a date object, so need to conver to numeric representation 10 | 11 | var ppd = respecConfig['previousPublishDate'].getFullYear() + 12 | (respecConfig['previousPublishDate'].getMonth() + 1).toString().padStart(2,'0') + 13 | (respecConfig['previousPublishDate'].getDate() + 1).toString().padStart(2,'0'); 14 | 15 | var prevLink = 'This document crosswalks the accessibility metadata for Schema.org, EPUB, and ONIX.
97 |The following table provides a crosswalk between the properties defined in the EPUB Accessibility specification [[EPUB-A11Y-11]] and The EPUB Accessibility exemption property [[EPUB-A11Y-Exemption]] and 105 | the equivalents defined in the ONIX metadata standard [[ONIX]].
106 | 107 |The conformsTo term used in EPUB is drawn from Dublin
110 | Core.
Unless stated otherwise, all code values are from ONIX code list 196: E-publication Accessibility Details.
116 || EPUB | 122 |ONIX | 123 |
|---|---|
| 129 | | Code 90: Compliance certification by (name) |
130 |
| 133 | 135 | | 136 |
137 | Code 94: Compliance web page for 138 | detailed accessibility information 139 |or, if a publisher is self-certifying, 140 |Code 96: Publisher's web page for 141 | detailed accessibility information 142 | |
143 |
| 146 | 148 | | 149 |
150 | Code 93: Compliance certification by (URL) 151 | |
152 |
|
155 |
|
159 |
160 | Code 04: EPUB Accessibility Specification 1.1 161 |Code 80: WCAG v2.0 162 |Code 84: WCAG level A 163 | |
164 |
|
167 |
|
171 |
172 | Code 04: EPUB Accessibility Specification 1.1 173 |Code 80: WCAG v2.0 174 |Code 85: WCAG level AA 175 | |
176 |
|
179 |
|
183 |
184 | Code 04: EPUB Accessibility Specification 1.1 185 |Code 80: WCAG v2.0 186 |Code 86: WCAG level AAA 187 | |
188 |
|
191 |
|
195 |
196 | Code 04: EPUB Accessibility Specification 1.1 197 |Code 81: WCAG v2.1 198 |Code 84: WCAG level A 199 | |
200 |
|
203 |
|
207 |
208 | Code 04: EPUB Accessibility Specification 1.1 209 |Code 81: WCAG v2.1 210 |Code 85: WCAG level AA 211 | |
212 |
|
215 |
|
219 |
220 | Code 04: EPUB Accessibility Specification 1.1 221 |Code 81: WCAG v2.1 222 |Code 86: WCAG level AAA 223 | |
224 |
|
227 |
|
231 |
232 | Code 04: EPUB Accessibility Specification 1.1 233 |Code 82: WCAG v2.2 234 |Code 84: WCAG level A 235 | |
236 |
|
239 |
|
243 |
244 | Code 04: EPUB Accessibility Specification 1.1 245 |Code 82: WCAG v2.2 246 |Code 85: WCAG level AA 247 | |
248 |
|
251 |
|
255 |
256 | Code 04: EPUB Accessibility Specification 1.1 257 |Code 82: WCAG v2.2 258 |Code 86: WCAG level AAA 259 | |
260 |
|
263 |
|
267 |
268 | Code 02: EPUB Accessibility 269 | Specification 1.0 A 270 | |
271 |
|
274 |
|
278 |
279 | Code 03: EPUB Accessibility 280 | Specification 1.0 AA 281 | |
282 |
|
286 |
|
288 |
289 | Code 75: EAA exception 1 - Micro-enterprises 290 | |
291 |
|
294 |
|
296 |
297 | Code 76: EAA exception 2 - Disproportionate burden 298 | |
299 |
|
302 |
|
304 |
305 | Code 77: EAA exception 3 - Fundamental modification 306 | |
307 |
The following table provides a crosswalk between the Schema.org metadata and ONIX standard [[ONIX]].
315 | 316 |Unless stated otherwise, all code values are from ONIX code list 196: E-publication Accessibility Details.
319 || Schema.org | 325 |ONIX | 326 |
|---|---|
| accessibilityFeature | 331 ||
| 335 | | Code 14: Short alternative 336 | descriptions |
337 |
| 341 | | 343 | |
| 347 | | Code 30: ARIA roles provided |
348 |
| 353 | | Code 28: Full alternative audio descriptions |
354 |
|
358 | – |
359 |
| 363 | | List 21: Edition type, Code BRL: Braille edition 365 |or 366 |List 175: Product form detail, Code E146: BRF(Braille-ready file) Electronic Braille file 368 | |
369 |
|
372 |
373 | – 374 | |
375 |
| 379 | |
380 | Code 18: Accessible chem content 381 | |
382 |
| 385 | | 386 | 387 | | 388 |
| 392 | |
393 | Code 14: Short alternative textual descriptions 394 |along with 395 |List 81: Product content type, Code 48: Mathematical content |
397 |
| 401 | | Code 36: All textual content can be modified |
402 |
| 406 | | – |
407 |
| 411 | | Code 27: Use of high contrast between foreground and background audio |
412 |
| 416 | | Code 26: Use of high contrast between text and background color 417 |and 418 |Code 37: Use of ultra-high contrast between text foreground and background |
419 |
| 423 | | – |
424 |
| 428 | |
429 | Code 12: Index navigation 430 | |
431 |
| 435 | | List 21: Edition type, Code LTE: Large type / large print edition 437 |and 438 | |
440 |
| 444 | | Code 35: Accessible math content (as LaTeX) 445 |should be used with 446 |List 81: Product content type, Code 48: Mathematical content 448 | |
449 |
| 453 | | – 454 | |
455 |
| 460 | |
461 | Code 15: Full alternative 462 | descriptions 463 |Code 16: Visualised data also 464 | available as non-graphical data 465 | |
466 |
| 470 | |
471 | Code 17: Accessible math content 472 | |
473 |
| 477 | | Code 34: Accessible chemistry content (as MathML) 478 | |
479 |
| 484 | | Code 09: Inaccessible, or known limited accessibility |
485 |
| 489 | | 490 | 491 | | 492 |
|
494 |
|
498 |
499 | Code 19: Print-equivalent page 500 | numbering 501 | |
502 |
| 506 | | – |
507 |
| 511 | |
512 | Code 13: Reading order 513 | |
514 |
| 518 | | – |
519 |
| 523 | | List 175: Product form detail, Code V213: Sign language interpretation |
525 |
| 529 | | Code 29: Next / Previous structural navigation |
530 |
| 534 | |
535 | Code 20: Synchronised pre-recorded 536 | audio 537 | |
538 |
| 542 | |
543 | Code 11: Table of contents 544 | navigation 545 | |
546 |
| 550 | | Code 05: PDF/UA 551 |Code 06: PDF/UA-2 |
552 |
| 556 | | – |
557 |
| 561 | | – |
562 |
| 566 | | – |
567 |
| 571 | | 573 | |
| 577 | |
578 | Code 21: Text-to-speech hinting 579 | provided 580 |Code 22: Language tagging 581 | provided 582 | |
583 |
| 587 | | Code 08: Unknown accessibility |
588 |
| 592 | | 594 | |
| 598 | | – |
599 |
| 603 | | – |
604 |
| 608 | | – |
609 |
– |
612 |
613 | Code 31: Accessible controls provided 614 | |
615 |
– |
618 |
619 | Code 24: Dyslexia readability 620 | |
621 |
– |
624 |
625 | Code 32: Landmark navigation 626 | |
627 |
– |
630 |
631 | Code 10: No reading system accessibility options disabled 632 | |
633 |
– |
636 |
637 | Code 25: Use of color is not sole means of conveying information 638 | |
639 |
| accessibilityHazard | 645 ||
| 649 | | List 143: US CPSIA or other international hazard warning type, Code 13: WARNING – Flashing hazard |
651 |
| 655 | | List 143: US CPSIA or other international hazard warning type, Code 17: WARNING – Motion simulation hazard |
657 |
| 661 | | List 143: US CPSIA or other international hazard warning type, Code 15: WARNING – Sound hazard |
663 |
| 667 | | List: 143; Code: 00 No known hazards or warnings |
668 |
| 672 | | List 143: US CPSIA or other international hazard warning type, Code 14: No flashing hazard warning necessary |
674 |
| 678 | | List 143: US CPSIA or other international hazard warning type, Code 18: No motion simulation hazard warning necessary |
680 |
| 684 | | List 143: US CPSIA or other international hazard warning type, Code 16: No sound hazard warning necessary |
686 |
| 690 | | – |
691 |
| 695 | | List: 143; Code: 24 Flashing risk unknown |
696 |
| 699 | | List: 143; Code: 26 Motion simulation unknown |
700 |
| 703 | | List: 143; Code: 25 Sound risk unknown |
704 |
| accessibilityAPI | 710 ||
| The metadata accessibilityAPI does not really apply to EPUBs directly but rather to the Reading System itself. Therefore we have not included it here in this crosswalk to ONIX. | 713 ||
| accessibilityControl | 719 ||
| The metadata accessibilityControl does not really apply to EPUBs directly but rather to the Reading System itself. Therefore we have not included it here in this crosswalk to ONIX. | 722 ||
| accessMode | 729 ||
| 733 | | List 81: Product content type, 734 |
plus types of audio content 738 | |
747 |
| 751 | |
752 | List 81: Product content type, Code 19: Figures, Diagrams, 754 | Charts 755 | |
756 |
| 760 | | 762 | |
| 766 | | – |
767 |
| 771 | |
772 | List 81: Product content type, Code 19: Figures, Diagrams, 774 | Charts 775 | |
776 |
| 780 | | List 81: Product content type, Code 48: Mathematical content |
782 |
| 786 | | 788 | |
| 792 | | – |
793 |
| 797 | | 799 | |
| 803 | | 804 | 810 | | 811 |
| 815 | |
816 | List 81: Product content type, 817 |
|
832 |
| accessModeSufficient | 838 ||
| ONIX crosswalks are for instances where accessModeSufficient includes this 841 | vocabulary entry alone; combinations may occur but are more difficult to crosswalk | 842 ||
| 846 | | 847 | 853 | | 854 |
| 858 | | – |
859 |
| 863 | | List 196: E-publication Accessibility Details, Code 52: All non-decorative content supports reading without sight |
865 |
| 869 | | – |
870 |
| accessibilitySummary | 875 ||
|
879 | Human-readable text 880 | |
881 |
882 |
886 | If present, include information from Codes: 887 | 897 | 898 | |
899 |
The editors would like to thank Christopher Saynor (Editeur) for his invaluable help reviewing this document.
907 |This document is a work in progress to extends the existing crosswalk for accessibility metadata for 98 | Schema.org, EPUB, and ONIX to MARC21 and UNIMARC.
99 |It also adds a definition column.
100 |Note : UNIMARC 231i (pdf file) offers a easy mapping to ONIX 196. Some references may be best described by other 102 | UNIMARC codes.
103 |Schema definitions are found here: https://www.w3.org/2021/a11y-discov-vocab/latest/
107 |“ConformsTo” term used in EPUB –drawn from Dublin Core.
108 |Fixed length fields (fixed fields) and variable length fields (very brief summary – fuller details)
111 |MARC 21 fixed field = 3 digit numeric code (except the Leader); no indicators, value in each position has a specific meaning.
112 |MARC 21 variable length field = 3 digit numeric code; each field can have 2 indicators that signify different values; each field can have one or more subfields; convention to designate subfield = $ ; if no subfield, assume $a.
113 |More detailed information about MARC 21 field 341 and MARC21 field 532
114 |The following table provides a crosswalk between the properties defined in the EPUB Accessibility specification [[EPUB-A11Y-11]] and the 123 | equivalents defined metadata standards [[ONIX]], MARC21, UNIMARC.
124 | 125 |The conformsTo term used in EPUB is drawn from Dublin
127 | Core.
| Definition | 133 |EPUB | 134 |ONIX | 135 |EPUB to MARC21 | 136 |ONIX to MARC21 | 137 |UNIMARC | 138 |
|---|---|---|---|---|---|
| Identifies a party responsible for the testing and certification of the accessibility of an EPUB 143 | publication. | 144 |certifiedBy | 145 |List 196: Code 93: Compliance certification
146 | by
147 | ProductFormFeatureDescription carries the URL of a web page belonging to the
148 | organisation responsible for compliance testing and certification of the product – typically a
149 | ‘home page’ or a page describing the certification scheme itself. For use in ONIX 3.0 only
150 | |
151 | 532 8# Accessibility Note (Non-specific) | 152 |532 8# Accessibility Note$a | 153 |231 ##$i93$2onix196 | 154 |
| f the evaluator provides a publicly-readable report of its assessment, provide a link to the 157 | assessment in an a11y:certifierReport property associated with [epub-3] the evaluator's 158 | name.. | 159 |certifierReport | 160 |List: 196; Code: 94: Compliance web page 161 | for detailed accessibility information or, if a publisher is self-certifying, Code: 96: 163 | Publisher's web page for detailed accessibility information | 164 |
165 |
|
171 | 532 8# Accessibility Note$a | 172 |231 ##$i94$2onix196 and/or 231 ##$i96$2onix196 | 173 |
| Identifies a credential or badge that establishes the authority of the party identified in the 176 | associated certifiedBy property to certify content accessible.. | 177 |certifierCredential | 178 |– | 179 |532 8# Accessibility Note (Non-specific) | 180 |181 | | 182 | |
| An established standard to which the described resource conforms. | 185 |
186 | dcterms:conformsTo
188 | with the URL
189 | http://www.idpf.org/epub/a11y/accessibility-20170105.html#wcag-a
190 | |
191 | List: 196; Code: 02: EPUB Accessibility 192 | Specification 1.0 A | 193 |532 8# Accessibility Note (Non-specific) | 194 |532 8# Accessibility Note$a | 195 |231 ##$i02$2onix196 | 196 |
| An established standard to which the described resource conforms. | 199 |
200 | dcterms:conformsTo
202 | with the URL
203 | http://www.idpf.org/epub/a11y/accessibility-20170105.html#wcag-aa
204 | |
205 | List: 196; Code: 03: EPUB Accessibility 206 | Specification 1.0 AA | 207 |532 8# Accessibility Note (Non-specific) | 208 |532 8# Accessibility Note$a | 209 |231 ##$i03$2onix196 | 210 |
The following table provides a crosswalk between the Schema.org metadata and [[ONIX]], MARC21, UNIMARC.
219 | 220 |ONIX: List 196 (specific codes follow)
222 |MARC21: would not map. Mapping of individual properties is possible as reflected in the following table
223 |UNIMARC: Easy mapping thru list 231 allowing reference to any ONIX list and code.
224 | 225 || Definition | 229 |Schema.org | 230 |ONIX | 231 |MARC21 | 232 |UNIMARC | 233 |
|---|---|---|---|---|
| Alternative text is provided for visual content (e.g., via the [HTML] alt attribute). | 240 |alternativeText 241 | | 242 |List: 196; Code: 14: Short alternative 243 | descriptions | 244 |341 0# $avisual$balternativeText$2sapdv or 341 0# $aaudio$bcaptions$2sapdv | 245 |231 ##$i14$2onix196 | 246 |
| The work includes annotations from the author, instructor and/or others. | 249 |annotations | 250 |– | 251 |341 0# $atextual$bannotations $2 sapdv or 532 8# $a This resource includes annotations from the 252 | author, instructor and/or others. | 253 |254 | |
| Audio descriptions are available (e.g., via an [HTML] track element with its kind attribute set 257 | to "descriptions"). | 258 |audioDescription 260 | | 261 |– | 262 |341 0# $avisual$daudioDescription$2sapdv | 263 |264 | |
| (deprecated). The work includes bookmarks to facilitate navigation to key points. 267 | Note: The use of the bookmarks value is now deprecated 268 | due to its ambiguity. For PDF bookmarks, the 269 | tableOfContents value should be used instead. For 270 | bookmarks in ebooks, the annotations value can be used. 271 | | 272 |bookmarks | 273 |N/A (Reading system feature) | 274 |341 0# $atextual$bbookmarks$2sapdv | 275 |276 | |
| [1] The content is in braille format, or [2] alternatives are available in braille. 279 | Note: Information about the type of braille 280 | (e.g., ASCII, unicode, nemeth), whether the braille is 281 | contracted or not, and what code the braille conforms to 282 | should be provided in the accessibility summary. 283 | | 284 |braille | 285 |– | 286 |
287 |
|
293 | 294 | |
| Indicates that synchronized captions are available for audio and video content. | 297 |captions | 298 |– | 299 |341 0# $aauditory$bcaptions$2sapdv or 341 0# $avisual$bcaptions$2sapdv | 300 |301 | |
| Identifies that chemical information is encoded using the ChemML markup language. | 305 |ChemML | 306 |List: 196; Code: 18: Accessible chem 307 | content | 308 |341 0# $avisual$bChemML$2sapdv | 309 |231 ##$i18$2onix196 | 310 |
Textual descriptions of math equations are included, whether in the alt attribute for
313 | image-based equations, using the alttext
315 | attribute for [MathML]
318 | equations, or by other means. |
319 | describedMath | 320 |– | 321 |341 0# $avisual$bdescribedMath$2sapdv | 322 |323 | |
| Display properties are controllable by the user. This property can be set, for example, if 326 | custom CSS style sheets can be applied to the content to control the appearance. It can also be 327 | used to indicate that styling in document formats like Word and PDF can be modified. | 328 |displayTransformability 330 | | 331 |List: 175 ; Code: E200: Reflowable. | 332 |341 0# $atextual$b displayTransformability$2sapdv | 333 |231 ## $iE200$2onix175 | 334 |
| Audio content with speech in the foreground meets the contrast thresholds set out in WCAG 338 | Success Criteria 1.4.7. | 339 |highContrastAudio 341 | | 342 |– | 343 |3410$aauditory$dhighContrastAudio$2sapdv | 344 |345 | |
| Content meets the visual contrast threshold set out in WCAG Success 348 | Criteria 1.4.6. | 349 |highContrastDisplay | 350 |– | 351 |3410#$atextual$b highContrastDisplay$2sapdv or 3410#$avisual$c highContrastDisplay$2sapd | 352 |353 | |
| The work includes an index to the content. | 356 |index | 357 |List: 196; Code: 12: Index navigation | 358 |3410#$atextual$bindex$2sapdv | 359 |231 $i12$2onix196 | 360 |
| The content has been formatted to meet large print guidelines. 363 | The property is not set if the font size can be increased. 364 | See displayTransformability. | 365 |largePrint | 366 |– | 367 |
368 |
|
376 | 377 | |
| Identifies that mathematical equations and formulas are encoded in the LaTeX typesetting system. | 380 |latex | 381 |– | 382 |3410#$avisual$blatex$2sapdv | 383 |384 | |
| Descriptions are provided for image-based visual content 387 | and/or complex structures such as tables, mathematics, 388 | diagrams, and charts. 389 | Note: Authors may set this property independent of the 390 | method they use to provide the extended descriptions 391 | (i.e., it is not required to use the obsolete [HTML] 392 | longdesc attribute). 393 | | 394 |longDescription | 395 |List: 196; Code: 15: Full alternative 396 | descriptions; 16: Visualised data also available as non-graphical data | 397 |
398 |
|
405 | 231 $i15$2onix196 | 406 |
| Identifies that mathematical equations and formulas are encoded in [MathML]. | 409 |MathML | 410 |List: 196; Code: 17: Accessible math 411 | content | 412 |3410#$avisual$bMathML$2sapdv | 413 |231 $i17$2onix196 | 414 |
| Indicates that the resource does not contain any accessibility features. 417 | The none value must not be set with any other feature value. 418 | | 419 |none | 420 |– | 421 |No mapping | 422 |423 | |
| The work includes equivalent print page numbers. This setting is most commonly used with ebooks for which there is a print equivalent. | 426 |printPageNumbers | 427 |List: 196; Code: 19: Print-equivalent page 428 | numbering | 429 |3410#$atextual$bprintPageNumbers$2sapdv | 430 |231 $i19$2onix196 | 431 |
| The reading order of the content is clearly defined in the markup (e.g., figures, sidebars and other secondary content has been marked up to allow it to be skipped automatically and/or manually escaped from. | 434 |readingOrder | 435 |List: 196; Code: 13: Reading order | 436 |3410#$atextual$breadingOrder$2sapdv | 437 |231 $i13$2onix196 | 438 |
Indicates that ruby annotations [HTML] are provided in the content. Ruby
441 | annotations are used as pronunciation guides for the logographic characters for languages
442 | like Chinese or Japanese. It makes difficult Kanji or CJK ideographic characters more
443 | accessible. The absence of rubyAnnotations implies that no CJK ideographic characters have
444 | ruby. |
445 | rubyAnnotations | 446 |– | 447 |3410#$atextual$brubyAnnotations$2sapdv | 448 |449 | |
| Sign language interpretation is available for audio and video content. 452 | Note: Information about the sign language code used should be provided in the accessibility summary. 453 | | 454 |signLanguage | 455 |– | 456 |3410#$aauditory$csignLanguage$2sapdv | 457 |458 | |
| The use of headings in the work fully and accurately reflects the document hierarchy, allowing navigation by assistive technologies. | 461 |structuralNavigation | 462 |– | 463 |3410#$atextual$bstructuralNavigation$2sapdv | 464 |465 | |
| Describes a resource that offers both audio and text, with information that allows them to be rendered simultaneously. The granularity of the synchronization is not specified. This term is not recommended when the only material that is synchronized is the document headings. | 468 |synchronizedAudioText | 469 |List: 196; Code: 20: Synchronised 470 | pre-recorded audio | 471 |3410#$atextual$d sychronizedAudioText$2sapdv | 472 |231 $i20$2onix196 | 473 |
| The work includes a table of contents that provides links to the major sections of the content. | 476 |tableOfContents | 477 |List: 196; Code: 11: Table of contents 478 | navigation | 479 |3410#$atextual$btableofContents$2sapdv | 480 |231 $i11$2onix196 | 481 |
| The contents of the PDF have been tagged to permit access by assistive technologies. | 484 |taggedPDF | 485 |– | 486 |3410#$atextual$btaggedPDF$2sapdv | 487 |488 | |
491 |
|
496 | tactileGraphic | 497 |– | 498 |
499 |
And 336 Content type ; 336 ##$atactile image$2rdacontent 506 | |
507 | 508 | |
511 |
|
516 | tactileObject | 517 |– | 518 |
519 |
336 ##$atactile three-dimensional form$2rdacontent |
528 | 529 | 530 | | 531 |
| For content with timed interaction, this value indicates that the user can control the timing to meet their needs (e.g., pause and reset) | 534 |timingControl | 535 |– | 536 |341$aauditory$dtimingControl$2sapdv or 341$avisual$dtimingControl$2sapdv | 537 |538 | |
| Indicates that a transcript of the audio content is available. | 541 |transcript | 542 |– | 543 |341$aauditory$btranscript$2sapdv | 544 |545 | |
| One or more of [SSML], [Pronunciation-Lexicon], and [CSS3-Speech] properties has been 548 | used to enhance text-to-speech playback quality. | 549 |ttsMarkup | 550 |List: 196; Code: 21: Text-to-speech 551 | hinting provided; Code 22: Language tagging 552 | provided | 553 |341$atext$bttsMarkup$2sapdv and 532 1# $a Text-to-speech has been optimised through provision of 554 | PLS lexicons, SSML or CSS Speech synthesis hints. | 555 |231 $i21$2onix196 and/or 231 $i22$2onix196 | 556 |
| No digital rights management or other content restriction protocols have been applied to the resource. | 559 |unlocked | 560 |– | 561 |532 1# $aNo DRM (digital rights management) or other content restriction protocols have been 562 | applied to the resource. | 563 |564 | |
| ONIX: The language of the text has been specified (eg via the HTML or XML lang attribute) to optimise text-to-speech (and other alternative renderings), both at whole document level and, where appropriate, for individual words, phrases or passages in a different language. | 567 |– | 568 |List: 196; Code 22: Language tagging 569 | provided – helps with TTS in multi-lingual content | 570 |532 1# $aThe language of the text has been specified (eg via the HTML or XML lang attribute) to 571 | optimise text-to-speech (and other alternative renderings), both at whole document level and, 572 | where appropriate,for individual words, phrases or passages in a different language. | 573 |231 $i22$2onix196 | 574 |
ONIX: Specialised font, character and/or line spacing, justification and paragraph spacing, coloring and other options provided specifically to improve readability for dyslexic readers. Details, including the name of the font if relevant, should be listed in ProductFormFeatureDescription |
577 | – | 578 |List: 196; Code 24: Dyslexia readability 579 | | 580 |532 1# $aSpecialised font, character and line spacing, justification and paragraph spacing, and 581 | coloring for dyslexic readers. | 582 |583 | |
| ONIX: Known to lack significant features required for broad accessibility. For use in ONIX 3.0 only | 586 |– | 587 |List: 196; Code 09: Inaccessible | 588 |532 2# $aLacks significant accessibility features. | 589 |231 $i09$2onix196 | 590 |
ONIX: No accessibility features offered by the reading system, device or reading software (including but not limited to choice of text size or typeface, choice of text or background color, text-to-speech) are disabled, overridden or otherwise unusable with the product EXCEPT – in ONIX 3 messages only – those specifically noted as subject to restriction or prohibition in EpubUsageConstraint. Note that provision of any significant part of the textual content as images (ie as pictures of text, rather than as text, and without any textual equivalent) inevitably prevents use of these accessibility options. |
593 | – | 594 |List: 196; Code 10: No reading system 595 | accessibility options disabled (except) | 596 |532 8# $aNo accessibility features offered by the reading system, device or reading software 597 | (including but not limited to choice of text size or typeface, choice of text or background 598 | color, text-to-speech) are disabled, overridden or otherwise unusable with the product. | 599 |231 $i10$2onix196 | 600 |
| Definition | 609 |Schema.org | 610 |ONIX | 611 |MARC21 | 612 |UNIMARC | 613 |
|---|---|---|---|---|
| Indicates that the resource presents a flashing hazard for photosensitive persons. This value should be set when the content meets the hazard thresholds described in Success Criterion 620 | 2.3.1 Three Flashes or Below Threshold [WCAG2]. 621 | | flashing | 622 |– | 623 |532 8# $aThe resource presents a flashing hazard for photosensitive persons. | 624 |625 | |
| Indicates that the resource does not present a flashing hazard. This value should be set when the content conforms to Success Criterion 628 | 2.3.1 Three Flashes or Below Threshold [WCAG2]. 629 | | noFlashingHazard | 630 |– | 631 |532 8# $aThis resource does not present a flashing hazard. | 632 |633 | |
| Indicates that the resource contains instances of motion simulation that may affect some individuals. 636 | Some examples of motion simulation include video games with a first-person perspective and CSS-controlled backgrounds that move when a user scrolls a page. 637 | | 638 |motionSimulation | 639 |List: 143; Code: 17 WARNING – Motion 640 | simulation hazard 641 | Products simulates (via visual effects) the experience of motion, which may cause nausea in 642 | sensitive people | 643 |532 8# $aContains instances of motion simulation that may affect some individuals. | 644 |231 $i17$2onix143 | 645 |
| Indicates that the resource does not contain instances of motion simulation. | 648 |noMotionSimulationHazard | 649 |– | 650 |532 8# $aThis resource does not contain instances of motion simulation. | 651 |652 | |
| Indicates that the resource contains auditory sounds that may affect some individuals. Editor's note: The application of this value is currently under discussion as its application is underspecified. | 656 |sound | 657 |List: 175; Code: A310: Sound effects 658 | Incidental sounds added to the audiobook narration (eg background environmental sounds). (may 659 | not correspond to a hazard) | 660 |532 8# $aContains auditory sounds that may affect some individuals. | 661 |231 $iA310$2onix175 | 662 |
| Indicates that the resource does not contain auditory hazards. 665 | Editor's note: The application of this value is currently under discussion as its application is underspecified. | 666 |noSoundHazard | 667 |– | 668 |532 8# $aThis resource does not contain auditory hazards. | 669 |670 | |
| Indicates that the resource does not contain any hazards. | 673 |none | 674 |– | 675 |676 | | 677 | |
| Indicates that the author is not able to determine if the resource presents any hazards. | 680 |unknown | 681 |– | 682 |532 8# $aThis resource has not been evaluated for hazard risks. | 683 |684 | |
| Definition | 694 |Schema.org | 695 |ONIX | 696 |MARC21 | 697 |UNIMARC | 698 |
|---|---|---|---|---|
| Indicates the resource is compatible with the Android Access API. | 705 |AndroidAccessibility | 706 |– | 707 |532 0# $aResource is compatible with the Android Accessibility API. | 708 |709 | |
| Indicates the resource includes ARIA roles to organize and improve the structure and navigation. The use of this value corresponds to the inclusion of Document Structure, 712 | Landmark, Live Region, and Window roles [WAI-ARIA]. | 713 |ARIA | 714 |– | 715 |716 | | 717 | |
| Indicates the resource is compatible with the Accessibility Toolkit (ATK) API [ATK] for GNOME. | 720 |ATK | 721 |– | 722 |532 0# $aResource is compatible with the Accessibility Toolkit (ATK) API for GNOME | 723 |724 | |
| Indicates the resource is compatible with the Assistive Technology Service 727 | Provider Interface (AT-SPI) API [AT-SPI] for GNOME. | 728 |AT-SPI | 729 |– | 730 |532 0# $a Indicates the resource is compatible with the Assistive Technology Service Provider 731 | Interface (AT-SPI) API for GNOME. | 732 |733 | |
| Indicates the resource is compatible with the BlackBerry Accessibility API. 736 | This value is now obsolete as BlackBerry devices phones and operating systems are no longer developed, sold, or maintained. 737 | Note: After 2016, the BlackBerry name was licensed for phones released using the Android platform. Compatibility with these devices must be indicated using the AndroidAccessibility value. 738 | | 739 |BlackberryAccessibility (obsolete) | 740 |– | 741 |532 0# $aResource is compatible with the Blackberry Accessibility API. | 742 |743 | |
| Indicates the resource is compatible with the iAccessible2 API 746 | [IAccessible2] for Windows. 747 | | 748 |iAccessible2 | 749 |– | 750 |532 0# $aResource is compatible with the iAccessible2 API for Windows. | 751 |752 | |
| Authors should use the NSAccessibility value instead. | 755 |iOSAccessibility (deprecated) | 756 |– | 757 |532 0# $aResource is compatible with the iAccessible2 API for Apple iOS devices. | 758 |759 | |
| Indicates the resource is compatible with the Java 762 | Accessibility API [JAPI]. | 763 |JavaAccessibility | 764 |– | 765 |532 0# $aResource is compatible with the Java Accessibility API (JAAPI). | 766 |767 | |
| Authors should use the UIAccessibility value instead. | 770 |MacOSXAccessibility (deprecated) | 771 |– | 772 |532 0# $aResource is compatible with the iAccessible2 API for Windows. | 773 |774 | |
| Indicates the resource is compatible with the Microsoft Active Accessibility (MSAA) API [MSAA] for Windows. | 777 |MSAA (Microsoft Active Accessibility) | 778 |– | 779 |532 0# $aResource is compatible with the Microsoft Active Accessibility (MSAA) API for Windows 780 | | 781 |782 | |
| Indicates the resource is compatible with the User Interface Automation API for Windows. | 785 |UIAutomation | 786 |– | 787 |532 0# $aCompatible with the User Interface Automation API for Windows. | 788 |789 | |
| Definition | 799 |Schema.org | 800 |ONIX | 801 |MARC21 | 802 |UNIMARC | 803 |
|---|---|---|---|---|
| Users can fully control the resource through keyboard input. | 810 |fullKeyboardControl | 811 |– | 812 |532 0#$a Users can fully control the resource through keyboard input. | 813 |814 | |
| Users can fully control the resource through mouse input. | 817 |fullMouseControl | 818 |– | 819 |532 0#$a Users can fully control the resource through mouse input. | 820 |821 | |
| Users can fully control the resource through switch input. | 824 |fullSwitchControl | 825 |– | 826 |532 0#$a Users can fully control the resource through switch input. | 827 |828 | |
| Users can fully control the resource through touch input. | 831 |fullTouchControl | 832 |– | 833 |532 0#$a Users can fully control the resource through touch input. | 834 |835 | |
| Users can fully control the resource through video input. | 838 |fullVideoControl | 839 |– | 840 |532 0#$a Users can fully control the resource through video input. | 841 |842 | |
| Users can fully control the resource through voice input. | 845 |fullVoiceControl | 846 |– | 847 |532 0#$a Users can fully control the resource through voice input. | 848 |849 | |
The human sensory perceptual system or cognitive faculty through which a person may process or 855 | perceive information.856 |
| Definition | 860 |Schema.org | 861 |ONIX | 862 |MARC21 | 863 |UNIMARC | 864 |
|---|---|---|---|---|
| Indicates that the resource contains information encoded in auditory form. 870 | Note: This value is not set when the auditory content conveys no information. For example, an instructional video might include background music while all the necessary information to complete the task is conveyed visually and/or through text captions. 871 | | 872 |auditory | 873 |– | 874 |341 0#$aauditory; Also: 875 | 336 ##$aperformed music$2rdacontent; 876 | 336 ##$asounds$2rdacontent; 877 | 336 ##$aspoken word$2rdacontent; 878 | 344 ## $i sound | 879 |880 | |
| Indicates that the resource contains charts encoded in visual form. | 883 |chartOnVisual | 884 |List: 81; Code 19: Figures, Diagrams, 885 | Charts | 886 |341 0 $avisual; 532 8# $aResource contains charts encoded in visual form. | 887 |231 $i19$2onix81 | 888 |
| Indicates that the resource contains chemical equations encoded in visual form. | 891 |chemOnVisual | 892 |– | 893 |341 0# $avisual; 532 8# $aResource contains chemical equations encoded in visual form. | 894 |895 | |
| Indicates that the resource contains information encoded such that color perception is necessary. | 898 |colorDependent | 899 |– | 900 |532 2# $aThe resource contains information encoded in such that color perception is necessary. 901 | | 902 |903 | |
| Indicates that the resource contains diagrams encoded in visual form. | 906 |diagramOnVisual | 907 |List: 81; Code 19: Figures, Diagrams, 908 | Charts | 909 |341 0# $avisual; 532 8# $a Resource contains diagrams encoded in visual form. | 910 |231 $i19$2onix81 | 911 |
| Indicates that the resource contains mathematical notations encoded in visual form. | 914 |mathOnVisual | 915 |– | 916 |341 0# $avisual; 917 | 532 8# $aResource contains mathematical notations encoded in visual form. | 918 |919 | |
| Indicates that the resource contains musical notation encoded in visual form. | 922 |musicOnVisual | 923 |– | 924 |341 0# $avisual; 925 | 532 8# $a Resource contains music encoded in visual form. | 926 |927 | |
| Indicates that the resource contains information encoded in tactile form. Note that although an indication of a tactile mode often indicates the content is encoded using a braille system, this is not always the case. Tactile perception may also indicate, for example, the use of tactile graphics to convey information. | 930 |tactile | 931 |– | 932 |341 0#$atactile | 933 |934 | |
| Indicates that the resource contains text encoded in visual form. | 937 |textOnVisual | 938 |– | 939 |341 0# $avisual; 940 | 532 8# $a Resource contains text encoded in visual form. | 941 |942 | |
| Indicates that the resource contains information encoded in textual form. 945 | Note: This value is not set if the only textual content is for navigational purposes. For example, an audiobook might include a table of contents, but it is not necessary to read the table of contents to read the work. Likewise, books with synchronized text-audio playback may only include headings to allow structured navigation. 946 | | 947 |textual | 948 |List: 81; Code: 10 combined with List: 196; Code: 10 means all text is
950 | actual text. Note that List: 81; Code: 10 on its own (without List: 196; Code: 10) admits
951 | the possibility that the "text" is inaccessible because it is an image of text.
952 | Note : on this point ONIX is unclear. Codes 16 and 14 or 15 should also be mobilisedList: 196; Code: 09 Inaccessible 957 | Known to lack significant features required for broad accessibility. Would give a 958 | better indication for "Screen reader friendly" (if code 09 is not found so the publication is 959 | textual). In both cases it's hard for a publisher to figure out how to describe "all content is 960 | accessible thru true text", he must adopt a reasoning by absence. 961 | |
962 | 341 0# $atextual | 963 |964 | |
| Indicates that the resource contains information encoded in visual form. Note: This value is not set if the only visual imagery is presentational or not directly relevant to understanding the content. Examples of this type of imagery include cover images for publications, corporate logos, and purely decorative images. 967 | | 968 |visual | 969 |List: 81; Code: 07: Still images / graphics 970 | or Code: 18: Photographs or Code: 19: Figures, diagrams, charts, graphs or Code: 12: Maps 971 | and/or other cartographic content | 972 |341 0# $avisual; Also:
973 |
|
985 | 231 $i07$2onix81 | 986 |
A list of single or combined accessModes that are sufficient to understand all the intellectual content of a resource.991 |
ONIX crosswalks are for instances where accessModeSufficient includes this vocabulary entry 992 | alone; combinations may occur but are more difficult to crosswalk
993 || Definition | 997 |Schema.org | 998 |ONIX | 999 |MARC21 | 1000 |UNIMARC | 1001 |
|---|---|---|---|---|
| Indicates that auditory perception is necessary to consume the information. | 1007 |auditory | 1008 |List: 81; Code:01 | 1009 |341 0#$aauditory$2sapdv | 1010 |181 #0 $cspw$2rdacontent (may correspond only to human narration) | 1011 |
| Indicates that tactile perception is necessary to consume the information. | 1014 |tactile | 1015 |– | 1016 |341 0#$atactile$2sapdv | 1017 |1018 | |
| Indicates that the resource contains information encoded in textual form. Note: This value is not set if the only textual content is for navigational purposes. | 1021 |textual | 1022 |List: 81; Code: 10 combined with List: 196; Code: 10 means all text is
1024 | actual text. Note that List: 81; Code: 10 on its own (without List: 196; Code: 10) admits
1025 | the possibility that the "text" is inaccessible because it is an image of text.
1026 | Note : on this point ONIX is unclear. List: 196; Code: 09 Inaccessible 1028 | Known to lack significant features required for broad accessibility. Would give a better 1029 | indication for "Screen reader friendly" (if code 09 is not found so the publication is textual). 1030 | In both cases it's hard for a publisher to figure out how to describe "all content is accesible 1031 | thru true text", he must adopt a reasoning by absence. 1032 | |
1033 | 341 0#$atextual$2sapdv | 1034 |1035 | |
| Indicates that visual perception is necessary to consume the information. | 1038 |visual | 1039 |– | 1040 |341 0#$avisual$2sapdv | 1041 |1042 | |
A human-readable summary of specific accessibility features or deficiencies, consistent with the other accessibility metadata but expressing subtleties such as "short descriptions are present but long descriptions will be needed for non-visual users" or "short descriptions are present and no long descriptions are needed." 1048 |1049 |
| Definition | 1053 |Schema.org | 1054 |ONIX | 1055 |MARC21 | 1056 |UNIMARC | 1057 |
|---|---|---|---|---|
| The accessibilitySummary property is a free-form field that allows authors to describe the accessible properties of the resource. As a result, it does not have an associated vocabulary. | 1063 |accessibilitySummary | 1064 |List: 196; Code: 00: 1065 | Accessibility 1066 | Summary | 1067 |532 8# $a [Text] | 1068 |231 $i00$2onix196 | 1069 |
| Definition not found | 1072 |Human-readable text | 1073 |If present, include information from List: 1074 | 196; Codes 95, 96, 98, and 99 (links for further information about 1078 | accessibility) | 1079 |Would not map | 1080 |1081 | |
This document defines the recommended vocabularies for use with the Schema.org accessibility properties 73 | for discoverability of creative works.
74 |The CreativeWork type [[schema-org]]
83 | includes the following accessibility properties for discoverability:
accessibilityAPIaccessibilityControlaccessibilityFeatureaccessibilityHazardaccessibilitySummaryaccessModeaccessModeSufficientAlthough schema.org contains many other properties that describe the accessibility of objects in its 96 | taxonomy, these specific properties were developed together as part of a project to improve the 97 | discoverability of accessible resources headed by Benetech and IMS Global. Many of these properties 98 | were derived directly from the IMS 100 | Global AccessForAll (AfA) Information Model Data Element Specification.
101 | 102 |Part of this work included defining vocabularies of recommended values for use with these properties 103 | to ensure predictability for machine processing. This document represents those vocabularies.
104 | 105 |By defining these vocabularies, not only is it simpler for authors to understand and apply the 106 | properties, but it ensures that search tools, user agents and other machine intelligence can easily 107 | parse and inform users of the information.
108 | 109 |The vocabulary defined in this document is a continuation of the work that was informally hosted 111 | on the WebSchemas wiki (sometimes 112 | referred to as the "version 2.0 accessibility properties"). The project was moved to a W3C 113 | Community Group to better formalize the document and increase the transparency of its update 114 | process.
115 |For more information about the original project, refer to the Accessibility Metadata Project's web site.
117 |For more information on how to use schema.org accessibility properties not covered by 120 | this vocabulary, please refer to their relevant definitions in schema.org.
121 |The values defined in this vocabulary follow a camel casing convention: single words are lowercase, 127 | while compound words are concatenated into a single value with a capital letter indicating the start 128 | of each connected word (e.g., "alternativeText"). This convention is not applied to acronyms, 129 | accessibility APIs, and other values that already have recognized naming conventions (e.g., "MathML" 130 | and "iOSAccessibility").
131 | 132 |Hyphens are used to add additional descriptors to the end of terms. These
133 | descriptors are only added to clarify certain ambiguities with terms and only one descriptor is
134 | allowed at the end of any given term. For example, languages like MathML and latex are typically
135 | associated with encoding math content but are sometimes used to encode chemical equations and
136 | formulas. To ensure users can differentiate when these languages are being used for chemistry, the
137 | "-chemistry" descriptor is defined in this vocabulary for use on the respective
138 | math terms.
To ensure maximum interoperability with user agents that process these properties, use the values 141 | exactly as they are defined in this vocabulary. Alternative case spellings may not be recognized 142 | (e.g., "mathml" or "aria").
143 | 144 |If a user agent does not recognize a term with a descriptor, it should remove the hyphenated 145 | descriptor and attempt to process the base term.
146 | 147 |User agent developers should be aware that these values may not be strictly validated depending on 148 | the context in which they are created and used. Two values that differ only in case should be 149 | treated as identical.
150 |To extend terms with more information, this vocabulary used to recommend the old slash extension syntax employed by 157 | Schema.org until 2015. In this model, extensions of a term are made by adding a slash followed by a 158 | refinement term.
159 | 160 |Authors are no longer recommended to use this extension mechanism, although the use of slashes is not 161 | formally deprecated for backwards compatibility with existing content. The slash syntax was poorly 162 | defined, especially when multiple refinements could be specified, making it difficult for machines 163 | to process.
164 | 165 |When a user may require more information about the characteristics of a resource (e.g., the specifics 166 | of what type of braille it contains), it is better to explain these in 167 | human-readable terms in an accessibility summary.
168 | 169 |If a term in this vocabulary is not be expressive enough, it is now recommended to open an issue in the tracker to consider how 171 | to improve the existing term (e.g., by renaming terms or defining more specialized cases).
172 | 173 |Descriptors are not a general extensibility mechanism. If a term can 175 | benefit from a new descriptor, the resulting combined value must be registered in the 176 | vocabulary.
177 |accessibilityAPI property187 |189 | 190 |Indicates that the resource is compatible with the referenced accessibility API.
188 |
Compatibility with an accessibility API indicates that assistive technologies on the platform should 191 | be able to access the resource.
192 | 193 |The property is not applicable to resources that are not tightly integrated with their user 194 | interface. It can describe whether a word processing document that only opens in a specific 195 | application will work on a given platform, for example, but is not a useful indicator of whether an 196 | HTML document will, as there are numerous user agents a user could use to render it.
197 | 198 |Setting the property means that the resource is compatible with the given API(s). It does not 199 | necessarily mean that the content will be fully accessible to any given user group.
200 | 201 |The expected value of the accessibilityAPI property is a list of the compatible APIs.
202 | For metadata formats incapable of expressing lists, the property should be repeated for each
203 | API.
Indicates the resource is compatible with the Android Access API.
273 |Indicates the resource uses ARIA [[WAI-ARIA]] markup 279 | to improve interoperability with platform APIs.
280 | 281 |The use of the ARIA value is now deprecated as ARIA is not an accessibility API. The
283 | accessibilityFeature property value "ARIA" is now recommended
284 | to use to indicate that a resource makes use of ARIA to improve structural navigation.
Indicates the resource is compatible with the Accessibility Toolkit (ATK) API [[ATK]] for GNOME.
293 |Indicates the resource is compatible with the Assistive Technology Service Provider 300 | Interface (AT-SPI) API [[AT-SPI]] for GNOME.
301 |Indicates the resource is compatible with the BlackBerry Accessibility API.
309 | 310 |This value is now obsolete as BlackBerry devices phones and operating systems are no longer 311 | developed, sold, or maintained.
312 | 313 |After 2016, the BlackBerry name was licensed for phones released using the Android platform.
315 | Compatibility with these devices must be indicated using the AndroidAccessibility value.
Indicates the resource is compatible with the Fuchsia Accessibility Framework.
326 |Indicates the resource is compatible with the iAccessible2 API 333 | [[IAccessible2]] for Windows.
334 |Authors should use the NSAccessibility value instead.
340 |Indicates the resource is compatible with the Java 347 | Accessibility API [[JAPI]].
348 |Authors should use the UIAccessibility value instead.
354 |Indicates the resource is compatible with the Microsoft Active Accessibility (MSAA) API [[MSAA]] for Windows.
362 |Indicates the resource is compatible with the NSAccessibility 369 | API for Apple iOS and tvOS applications built on UIKit.
370 |Indicates the resource is compatible with the UIAccessibility API for macOS applications built on AppKit.
378 |Indicates the resource is compatible with the User Interface Automation API for Windows.
386 |accessibilityControl property396 |399 | 400 |Identifies one or more input methods that allow access to all of the application 397 | functionality.
398 |
The accessibilityControl property is used to describe the ability of users to interact
401 | with the user interface controls that applications provide.
The property is not applicable to resources that are not tightly integrated with their user 404 | interface. It can describe whether users can control a word processing document that only opens in a 405 | specific application, for example, but is not a useful indicator of whether users can control an 406 | HTML document, as there are numerous user agent and assistive technology pairings a user could use 407 | to access it.
408 | 409 |Setting the property means that the specified control method(s) are compatible with the resource.
410 | 411 |The expected value of the accessibilityControl property is a list of the applicable
412 | control methods. For metadata formats incapable of expressing lists, the property should be repeated
413 | for each control method.
Users can fully control the resource through keyboard input.
490 |Users can fully control the resource through mouse input.
496 |Users can fully control the resource through switch input.
502 |Users can fully control the resource through touch input.
508 |Users can fully control the resource through video input.
514 |Users can fully control the resource through voice input.
520 |accessibilityFeature property530 |533 | 534 |Content features of the resource, such as accessible media, alternatives and supported 531 | enhancements for accessibility.
532 |
The accessibilityFeature property provides a list of all the applicable accessibility
535 | characteristics of the content. It allows a user agent to discover these characteristics without
536 | having to parse or interpret the structure of the content.
For ease of reading, this section splits the vocabulary into the following distinct groups:
539 | 540 |alt attribute is one of the most commonly identifiable augmentation
548 | features.The vocabulary also includes the term "none" that authors
571 | can set to indicate that the resource does not contain special enhancements. Similarly, the term
572 | "unknown" exists as a placeholder for marking content that authors need to
573 | review.
The expected value of the accessibilityFeature property is a list of the applicable
576 | features. For metadata formats incapable of expressing lists, the property should be repeated for
577 | each feature.
The adaptation terms identify provisions in the content that enable reading in alternative access 824 | modes.
825 | 826 |Alternative text is provided for visual content (e.g., via the [[HTML]] alt attribute).
Audio descriptions are available (e.g., via an [[HTML]] track element with its kind attribute set to
840 | "descriptions").
Indicates that synchronized captions are available for audio and video content.
847 | 848 |The use of the captions value is now deprecated. Authors should use the more
850 | specific closedCaptions or openCaptions values, as appropriate.
Indicates that synchronized closed captions are available for audio and video content.
859 | 860 |Closed captions are defined separately from the video, allowing users to control whether they 861 | are rendered or not, unlike open captions.
862 |Textual descriptions of math equations are included, whether in the alt attribute for
868 | image-based equations, using the alttext attribute for [[MathML]] equations, or by other means.
Descriptions are provided for image-based visual content and/or complex structures such as 877 | tables, mathematics, diagrams, and charts.
878 | 879 |Authors may set this property independent of the method they use to provide the extended
881 | descriptions (i.e., it is not required to use the obsolete [[HTML]] longdesc attribute).
Indicates that synchronized open captions are available for audio and video content.
891 | 892 |Open captions are part of the video stream and cannot be turned off by the user, unlike closed captions.
894 |Sign language interpretation is available for audio and video content.
900 | 901 | 902 |Information about the sign language code used should be provided in the accessibility summary.
905 |Indicates that a transcript of the audio content is available.
912 |The rendering control values identify that access to a resource and rendering and playback of its 919 | content can be controlled for easier reading.
920 | 921 |Indicates that the display properties of the content are controllable by the user.
925 | 926 |When setting this property, the author must ensure that the following are modifiable (when 927 | applicable to their language and writing mode):
928 | 929 |The preceding list may not capture all needed display transformability characteristics 944 | for all languages. In such cases, authors must ensure the missing characteristics are 945 | also transformable when setting this metadata. To request an addition to the list, 946 | please open an issue in the 947 | vocabulary tracker.
948 |In addition, text must not be represented as images unless it falls under the exceptions of 951 | Success Criterion 1.4.5 952 | [[WCAG2]].
953 | 954 |Note that setting this property does not mean that users will be able to control all the
955 | properties of the display in all user agents. It only indicates that the author has not
956 | limited the ability of users to change the settings (e.g., by using style
957 | attributes [[HTML]] or !important declarations [[css-cascade-4]] that prevent
958 | user agents from altering the properties, or by restricting users from modifying Word or PDF
959 | files).
The property must not be set for content for which no user agents are available that can 962 | transform the appearance and presentation of the text.
963 |Describes a resource that offers both audio and text, with information that allows them to be 969 | rendered simultaneously. The granularity of the synchronization is not specified. This term 970 | is not recommended when the only material that is synchronized is the document headings.
971 |For content with timed interaction, this value indicates that the user can control the timing 977 | to meet their needs (e.g., pause and reset)
978 |No digital rights management or other content restriction protocols have been applied to the 984 | resource.
985 |The specialized markup terms identify content available in specialized markup grammars. These 992 | grammars typically provide users with enhanced structure and navigation capabilities.
993 | 994 |Identifies that chemical information is encoded using the ChemML markup language.
999 |Identifies that mathematical equations and formulas are encoded in the LaTeX typesetting system.
1006 |Identifies that the LaTeX typesetting system is 1012 | used to encode chemical equations and formulas.
1013 |Identifies that mathematical equations and formulas are encoded in [[MathML]].
1019 |Identifies that [[MathML]] is used to encode chemical equations and formulas.
1025 |One or more of [[SSML]], [[Pronunciation-Lexicon]], and [[CSS3-Speech]] properties has been 1031 | used to enhance text-to-speech playback quality.
1032 |The clarity terms identify ways that the content has been enhanced for improved auditory or 1039 | visual clarity.
1040 | 1041 |Audio content with speech in the foreground meets the contrast thresholds set out in WCAG 1046 | Success Criteria 1.4.7 [[WCAG2]].
1047 | 1048 |Information about the how the audio meets the requirement should be provided in the accessibility summary (i.e., there is no background 1051 | noise, at least 20db difference between foreground speech and background noise, or the 1052 | background noise can be turned off.)
1053 |Content meets the visual contrast threshold set out in WCAG Success 1061 | Criteria 1.4.6 [[WCAG2]].
1062 |The content has been formatted to meet large print guidelines.
1068 | 1069 |The property is not set if the font size can be increased. See displayTransformability.
Information about the type of large print (e.g., the font size) should be provided in the 1074 | accessibility summary.
1075 |The tactile terms identify content that is available in tactile form.
1083 | 1084 |The content is in braille format, or alternatives are available in braille.
1088 | 1089 | 1090 |Information about the type of braille (e.g., ASCII, unicode, nemeth), whether the braille 1092 | is contracted or not, and what code the braille conforms to should be provided in the accessibility summary.
1094 |When used with creative works such as books, indicates that the resource includes tactile 1101 | graphics.
1102 | 1103 |When used to describe an image resource or physical object, indicates that the resource is a 1104 | tactile graphic.
1105 | 1106 |Refer to the BANA Guidelines and Standards 1108 | for Tactile Graphics for more information about tactile graphic formats and 1109 | formatting.
1110 |When used with creative works such as books, indicates that the resource includes models to 1117 | generate tactile 3D objects.
1118 | 1119 |When used to describe a physical object, indicates that the resource is a tactile 3D 1120 | object.
1121 |The internationalization terms identify those accessibility characteristics of the content which 1128 | are required for internationalization.
1129 | 1130 |Indicates that ruby annotations 1134 | [[JLreq]] are attached to every CJK ideographic character in the content. Ruby annotations 1135 | are used as pronunciation guides for the logographic characters for languages like Chinese 1136 | or Japanese. They make difficult CJK ideographic characters more accessible.
1137 | 1138 |If some but not all CJK ideographic characters have ruby annotations, use the rubyAnnotations value.
Indicates that the content can be laid out horizontally (e.g, using the
1146 | horizontal-tb writing mode of [[css-writing-modes-3]]). This value should
1147 | only be set when the language of the content allows both horizontal and vertical directions.
1148 | Notable examples of such languages are Chinese, Japanese, and Korean.
Some dyslexic Japanese can read horizontal writing but cannot read vertical writing.
1152 |Indicates that ruby annotations are 1159 | attached to some but not all CJK ideographic characters in the content.
1160 | 1161 |If all CJK ideographic characters have ruby annotations, use the fullRubyAnnotations value.
Indicates that the content can be laid out vertically (e.g, using the
1169 | vertical-rl of [[css-writing-modes-3]]). This value should only be set when
1170 | the language of the content allows both horizontal and vertical directions.
Indicates that the content can be rendered with additional word segmentation.
1178 | 1179 |Although the space character is not typically used for word segmentation in languages 1181 | such as Chinese, Japanese, Thai and Lao, it may be used for accessibility reasons.
1182 |Indicates that the content can be rendered without additional word segmentation.
1189 |Indicates that the resource does not contain any accessibility features.
1196 | 1197 |The none value must not be set with any other feature value.
Indicates that the author has not yet checked if the resource contains accessibility features. 1204 | This value is only intended as a placeholder until an accessibility review can be completed.
1205 | 1206 |The unknown value must not be set with any other feature value.
accessibilityHazard property1217 |1221 | 1222 |A characteristic of the described resource that is physiologically dangerous to some users. 1218 | Related to WCAG 2.0 guideline 1219 | 2.3.
1220 |
Identifying potential hazards that a resource poses allows users to determine if a resource poses a 1223 | risk to them and to potentially filter out content that could be harmful.
1224 | 1225 |The expected value of the accessibilityHazard property is a list of the applicable
1226 | hazards. For metadata formats incapable of expressing lists, the property should be repeated for
1227 | each hazard.
The accessibilityHazard property currently allows three types of hazards to be
1230 | identified: flashing, motion simulation, and sound. These correspond to the values
1231 | flashing, motionSimulation, and sound.
It also allows authors to indicate that each of the hazards is not present. In this case, the values
1234 | follow the pattern "no…Hazard", using the hazard names in place of the ellipsis
1235 | (e.g., noFlashingHazard).
If the author is sure there are no hazards, they are recommended to use the value "none"
1238 | in place of specifying that each individual hazard is not present. When setting this value, no other
1239 | hazard statuses are allowed.
Authors can additionally indicate that they are unable to determine if a hazard is present. In this
1242 | case, the values follow the pattern "unknown…Hazard", using the hazard names in
1243 | place of the ellipsis (e.g., unknownSoundHazard).
Authors can set the value unknown if they are unsure whether any hazards are present
1246 | (e.g., because they do not know how, or are unable, to assess them). When setting this value, no
1247 | other hazard statuses are allowed.
Indicates that the resource presents a flashing hazard for photosensitive persons.
1450 | 1451 |This value should be set when the content meets the hazard thresholds described in Success Criterion 1453 | 2.3.1 Three Flashes or Below Threshold [[WCAG2]].
1454 | 1455 |The flashing value must not be set when any of the noFlashingHazard, unknownFlashingHazard, none, or unknown values is
1459 | set.
Indicates that the resource contains instances of motion simulation that may affect some 1466 | individuals.
1467 | 1468 |Some examples of motion simulation include video games with a first-person perspective and 1469 | CSS-controlled backgrounds that move when a user scrolls a page.
1470 | 1471 |The motionSimulation value must not be set when any of the noMotionSimulationHazard, unknownMotionSimulationHazard, none, or unknown values is set.
Indicates that the resource contains auditory sounds that may affect some individuals.
1482 | 1483 |The application of this value is currently under discussion as its application 1484 | is underspecified.
1485 | 1486 |The sound value must not be set when any of the noSoundHazard, unknownSoundHazard, none,
1489 | or unknown values are set.
Indicates that the resource does not contain any hazards.
1500 | 1501 |It is recommended to use the none value when there are no hazards instead of
1502 | individual statements for noSoundHazard, noMotionSimulationHazard, and noFlashingHazard.
The none value must not be set when specifying either a known hazard or the unknown value. It should not be set when
1508 | negative hazard claims are made.
Indicates that the resource does not present a flashing hazard.
1515 | 1516 |The noFlashingHazard value must not be set when any of the flashing, unknownFlashing, or unknown values is set.
It should not be set when the none value is set.
Indicates that the resource does not contain instances of motion simulation.
1528 | 1529 |The noMotionSimulation value must not be set when any of the motionSimulation, unknownMotionSimulationHazard, or
1532 | unknown values is set.
It should not be set when the none value is set.
Indicates that the resource does not contain auditory hazards.
1541 | 1542 |The application of this value is currently under discussion as its application 1543 | is underspecified.
1544 | 1545 |The noSoundHazard value must not be set when either of the sound, unknownSoundHazard, or unknown values is set.
It should not be set when the none value is set.
Indicates that the author is not able to determine if the resource presents any hazards.
1561 | 1562 |It is recommended to use the unknown value when all hazards are unknown instead
1563 | of individual statements for unknownSoundHazard, unknownMotionSimulationHazard, and unknownFlashingHazard.
The unknown value must not be set when specifying either a known hazard or the
1569 | none value. It should not be set with the
1570 | individual unknown hazard value.
Indicates that the author cannot determine if a flashing hazard exists.
1577 | 1578 |The unknownFlashingHazard value must not be set when any of the flashing, noFlashingHazard, none
1581 | values is set.
It should not be set when the unknown value is
1584 | set.
Indicates that it is unknown if a motion simulation hazard exists within the content.
1591 | 1592 |The unknownMotionSimulation value must not be set when any of the motionSimulation, noMotionSimulationHazard or none values is set.
It should not be set when the unknown value is
1598 | set.
Indicates that it is unknown if an auditory hazard exists within the content.
1605 | 1606 |The unknownSoundHazard value must not be set when either of the sound, unknownSoundHazard, or unknown values is set.
It should not be set when the none value is set.
accessibilitySummary property1620 |1625 | 1626 |A human-readable summary of specific accessibility features or deficiencies, consistent with the 1621 | other accessibility metadata but expressing subtleties such as "short descriptions are present but 1622 | long descriptions will be needed for non-visual users" or "short descriptions are present and no 1623 | long descriptions are needed."
1624 |
The accessibilitySummary property is a free-form field that allows authors to describe the
1627 | accessible properties of the resource. As a result, it does not have an associated vocabulary.
accessMode property1697 |1700 | 1701 |The human sensory perceptual system or cognitive faculty through which a person may process or 1698 | perceive information.
1699 |
The accessMode property describes the ways information is encoded in the resource, where
1702 | information is defined as any content that contributes to the understanding of the resource.
The expected value of the accessMode property is a list of the applicable access modes.
1705 | For metadata formats incapable of expressing lists, the property should be repeated for each access
1706 | mode.
The access modes do not tell users if all the specified modes are necessary to consume the 1710 | information or if only individual modes or combinations are necessary (e.g., in a book with 1711 | audio content, the ability to read textual content may be sufficient if transcripts are 1712 | provided).
1713 | 1714 |The accessModeSufficient property is designed to
1715 | fill this gap of understanding the combinations of modes necessary to fully consume the
1716 | information.
Indicates that the resource contains information encoded in auditory form.
1788 | 1789 |This value is not set when the auditory content conveys no information. For example, an 1791 | instructional video might include background music while all the necessary information to 1792 | complete the task is conveyed visually and/or through text captions.
1793 |Indicates that the resource contains information encoded in tactile form.
1800 | 1801 |Note that although an indication of a tactile mode often indicates the content is encoded using a 1802 | braille system, this is not always the case. Tactile perception may also indicate, for example, 1803 | the use of tactile graphics to convey information.
1804 |Indicates that the resource contains information encoded in textual form.
1810 | 1811 |This value is not set if the only textual content is for navigational purposes. For example, 1813 | an audiobook might include a table of contents, but it is not necessary to read the table of 1814 | contents to read the work. Likewise, books with synchronized text-audio playback may only 1815 | include headings to allow structured navigation.
1816 |Indicates that the resource contains information encoded in visual form.
1823 | 1824 |This value is not set if the only visual imagery is presentational or not directly relevant 1826 | to understanding the content. Examples of this type of imagery include cover images for 1827 | publications, corporate logos, and purely decorative images.
1828 |Caution: Although user agents should infer a visual access mode when any of
1837 | the values defined in this section is set, it is strongly recommended not to rely on this
1838 | behaviour. Always set the value visual in addition to these indicators.
The visual content indicators are not strictly access modes but combine a visual access mode with 1842 | information about the nature of the visual content in a publication, such as whether charts, music, 1843 | or math equations are encoded as images.
1844 | 1845 |Users can then decide whether the content will still meet their needs. For example, if the math 1846 | equations in a textbook are encoded as images, with only text descriptions to make them accessible, 1847 | a user might opt to keep searching for an alternative that uses MathML markup.
1848 | 1849 |Indicates that the resource contains charts encoded in visual form.
1853 |Indicates that the resource contains chemical equations encoded in visual form.
1859 |Indicates that the resource contains information encoded such that color perception is 1865 | necessary.
1866 |Indicates that the resource contains diagrams encoded in visual form.
1872 |Indicates that the resource contains mathematical notations encoded in visual form.
1878 |Indicates that the resource contains musical notation encoded in visual form.
1884 |Indicates that the resource contains text encoded in visual form.
1890 |accessModeSufficient property1900 |1903 | 1904 |A list of single or combined accessModes that are sufficient to understand all the intellectual 1901 | content of a resource.
1902 |
Although the access modes indicate how the information is encoded in its 1905 | default form, knowing the encoding only describes one possible perceptual pathway through the 1906 | content. For example, a book with textual and visual content will, at the most basic level, require 1907 | an individual who can read text and view images.
1908 | 1909 |The author of the content may, however, provide alternatives to a specific access mode that allow the 1910 | content to be wholly consumed in another manner. The use of alternative text and extended 1911 | descriptions, for example, can allow a user who cannot perceive visual content to read all the 1912 | information in textual form (e.g., through text-to-speech playback).
1913 | 1914 |In such a case, a resource with textual and visual access modes could have both a textual and visual 1915 | sufficient access mode and a purely textual access mode — because there are text 1916 | equivalents for the visual content. Specifying there is an additional textual-only pathway through 1917 | the content allows users of screen readers, for example, to recognize that the content will be 1918 | readable by them.
1919 | 1920 |It is for this reason that content that has multiple access modes may have one or more sets of 1921 | sufficient access modes: each listing of sufficient access modes provides users with one possible 1922 | combination of reading modes that allow the content to be read in full.
1923 | 1924 |Although listing the combinations of access modes that allow a user to read all the content is 1925 | helpful, the most important sufficient access modes to list are the single-value ones. Users looking 1926 | for an alternative to the default encoding of the content typically are looking for a single 1927 | presentation mode (e.g., a fully textual pathway to use with a text-to-speech renderer or a fully 1928 | auditory pathway to listen to).
1929 | 1930 |The expected value of the accessModeSufficient property is an ItemList. Each entry in the ItemList must be a list of
1932 | one or more access modes representing one pathway.
For formats incapable of expressing lists, the property should be repeated for each set of sufficient 1935 | access modes. In these cases, it is recommended to use a comma-separated list of values.
1936 | 1937 | 2032 |Indicates that auditory perception is necessary to consume the information.
2041 |Indicates that tactile perception is necessary to consume the information.
2047 |Indicates that the ability to read textual content is necessary to consume the information.
2053 | 2054 |Note that reading textual content does not require visual perception, as textual content can be 2055 | rendered as audio using a text-to-speech capable device or assistive technology.
2056 |Indicates that visual perception is necessary to consume the information.
2062 |The following example shows how accessibility metadata could be used to enhance a library record 2072 | available on the Web.
2073 | 2074 |<div itemscope="" itemtype="http://schema.org/Book"> 2076 | <meta itemprop="bookFormat" content="EBook/DAISY3" /> 2077 | <meta itemprop="accessibilityFeature" content="ARIA" /> 2078 | <meta itemprop="accessibilityFeature" content="largePrint" /> 2079 | <meta itemprop="accessibilityFeature" content="highContrastDisplay" /> 2080 | <meta itemprop="accessibilityFeature" content="displayTransformability" /> 2081 | <meta itemprop="accessibilityFeature" content="longDescription" /> 2082 | <meta itemprop="accessibilityFeature" content="alternativeText" /> 2083 | <meta itemprop="accessibilityFeature" content="readingOrder" /> 2084 | <meta itemprop="accessibilityFeature" content="structuralNavigation" /> 2085 | <meta itemprop="accessibilityFeature" content="tableOfContents" /> 2086 | <meta itemprop="accessibilityControl" content="fullKeyboardControl" /> 2087 | <meta itemprop="accessibilityControl" content="fullMouseControl" /> 2088 | <meta itemprop="accessibilityHazard" content="none" /> 2089 | <dl> 2090 | <dt>Name:</dt> 2091 | <dd itemprop="name">Holt Physical Science</dd> 2092 | <dt>Brief Synopsis:</dt> 2093 | <dd itemprop="description">NIMAC-sourced textbook</dd> 2094 | <dt>Long Synopsis:</dt> 2095 | <dd>N/A</dd> 2096 | <dt>Book Quality:</dt> 2097 | <dd>Publisher Quality</dd> 2098 | <dt>Book Size:</dt> 2099 | <dd itemprop="numberOfPages">598 Pages</dd> 2100 | <dt>ISBN-13:</dt> 2101 | <dd itemprop="isbn">9780030426599</dd> 2102 | <dt>Publisher:</dt> 2103 | <dd itemprop="publisher" itemtype="http://schema.org/Organization" itemscope="">Holt, Rinehart 2104 | and Winston</dd> 2105 | <dt>Date of Addition:</dt> 2106 | <dd>06/08/10</dd> 2107 | <dt>Copyright Date:</dt> 2108 | <dd itemprop="copyrightYear">2007</dd> 2109 | <dt>Copyrighted By:</dt> 2110 | <dd itemprop="copyrightHolder" itemtype="http://schema.org/Organization" itemscope="">Holt, 2111 | Rinehart and Winston</dd> 2112 | <dt>Adult content:</dt> 2113 | <dd><meta itemprop="isFamilyFriendly" content="true" />No</dd> 2114 | <dt>Language:</dt> 2115 | <dd><meta itemprop="inLanguage" content="en-US" />English US</dd> 2116 | <dt>Essential Images:</dt> 2117 | <dd>861</dd> 2118 | <dt>Described Images:</dt> 2119 | <dd>910</dd> 2120 | <dt>Categories:</dt> 2121 | <dd><span itemprop="genre">Educational Materials</span></dd> 2122 | <dt>Grade Levels:</dt> 2123 | <dd>Sixth grade, Seventh grade, Eighth grade</dd> 2124 | <dt>NIMAC:</dt> 2125 | <dd>This book is currently only available to public K-12 schools and organizations in the United 2126 | States for use with students with an IEP, because it was created from files supplied by the 2127 | NIMAC under these restrictions. Learn more in the NIMAC Support Center.</dd> 2128 | </dl> 2129 | 2130 | <div class="bookReviews" itemprop="aggregateRating" itemscope="" 2131 | itemtype="http://schema.org/AggregateRating"> 2132 | <h2>Reviews of Holt Physical Science (<span itemprop="reviewCount">0</span> reviews)</h2> 2133 | <div class="bookReviewScore"> 2134 | <span><span itemprop="ratingValue">0</span> - No Rating Yet</span> 2135 | </div> 2136 | </div> 2137 | </div>2138 |
This example shows how the accessibility metadata could be used to augment a record for a video.
2145 | 2146 |<dl itemtype="http://schema.org/VideoObject" itemscope=""> 2148 | <dt>Title:</dt> 2149 | <dd itemprop="name">Arctic Climate Perspectives</dd> 2150 | <dt>Description:</dt> 2151 | <dd itemprop="description">This video, adapted from material provided by the ECHO 2152 | partners, describes how global climate change is affecting Barrow, Alaska.</dd> 2153 | <dt>Adaptation Type:</dt> 2154 | <dd><span itemprop="accessibilityFeature">captions</span></dd> 2155 | <dt>Access Mode:</dt> 2156 | <dd>auditory, visual</dd> 2157 | <dt>URL:</dt> 2158 | <dd><a itemprop="url" href="http://www.example.org/asset/echo07_vid_climate" 2159 | >http://www.example.org/asset/echo07_vid_climate</a>/</dd> 2160 | <dt>Has Adaptation:</dt> 2161 | <dd>http://www.example.org/asset/echo07_vid_climate_dvs/</dd> 2162 | <dt>Subjects:</dt> 2163 | <dd><span itemprop="about">National K-12 Subject::Science::Earth and Space 2164 | Science::Water Cycle, Weather, and Climate::Structure and Composition of the 2165 | Atmosphere, National K-12 Subject::Science::Earth and Space Science::Water Cycle, 2166 | Weather, and Climate::Climate</span></dd> 2167 | <dt>Education Level:</dt> 2168 | <dd>Grade 6, Grade 7, Grade 8, Grade 9</dd> 2169 | <dt>Audience:</dt> 2170 | <dd><span itemprop="intendedEndUserRole">Learner</span></dd> 2171 | <dt>Resource Type:</dt> 2172 | <dd><span itemprop="genre">Audio/Visual</span>, 2173 | <span itemprop="genre">Movie/Animation</span></dd> 2174 | <dt>Language:</dt> 2175 | <dd><span itemprop="inLanguage">en-US</span></dd> 2176 | <dt>Publication Date:</dt> 2177 | <dd itemprop="datePublished">2007-02-12</dd> 2178 | <dt>Rights:</dt> 2179 | <dd>Download and Share, <a itemprop="useRightsUrl" 2180 | href="http://www.example.org/oerlicense/2/" 2181 | >http://www.example.org/oerlicense/2/</a></dd> 2182 | </dl>2183 |
Note that this change log only identifies substantive changes to the vocabulary — those that add or 2190 | deprecate terms, or are similarly noteworthy.
2191 | 2192 |For a list of all issues addressed (typos, minor definition modifications, etc.), refer to the Community Group's 2194 | issue tracker.
2195 | 2196 | 2200 | 2201 |annotations value for
2205 | accessibilityFeature. Refer to issue 166.taggedPDF is only to be set when a PDF meets
2214 | accepted standards for accessibility. Refer to issue 40.visual. Refer to issue
2219 | 2653 in the EPUB tracker.displayTransformability
2221 | property. Refer to issue 85.MathML-chemistry and latex-chemistry. Refer to
2224 | issue 106.FuchsiaAccessibility to the accessibilityAPI
2238 | values. See issue 24.closedCaptions and openCaptions to replace the more
2240 | generic captions value. See issue 26.unknown feature for placeholder use. See issue 17.pageNavigation feature for indicating that a resource has a page
2245 | list. See issue 6.pageBreakMarkers feature for indicating that a resource includes
2247 | static page break markers. printPageNumbers is retained as a synonym but no longer
2248 | recommended for use. See issue
2249 | 6.bookmarks feature due to its ambiguous definition. The
2270 | tableOfContents and annotations values are recommended in its
2271 | place. See issue 5.accessibilityFeature. See pull request 39.accessibilityAPI value "ARIA" is deprecated. It is replaced by a
2280 | new "ARIA" value for accessibilityFeature for indicating the use of roles of
2281 | enhanced structural and landmark navigation. See issue 4.The editors would like to thank the Accessibility Discoverability Vocabulary for Schema.org Community Group participants for their 2293 | ongoing input and suggestions to improve this vocabulary.
2294 | 2295 |Additional thanks go to the original participants of the Accessibility Metadata Project for their work bringing the properties and vocabularies to 2297 | reality.
2298 |