diff --git a/css/kb.css b/css/kb.css index 6632725d..2aed7a68 100644 --- a/css/kb.css +++ b/css/kb.css @@ -161,6 +161,12 @@ a.permalink { border-bottom: none !important; } +a.breadcrumb, +a.breadcrumb:visited{ + color: rgb(0,0,200); + border-bottom: 0.1rem dotted rgb(0,0,200); +} + /* page headers and footers */ header { diff --git a/google27ca3f84685cffe6.html b/google27ca3f84685cffe6.html deleted file mode 100644 index 4f9bc9e1..00000000 --- a/google27ca3f84685cffe6.html +++ /dev/null @@ -1 +0,0 @@ -google-site-verification: google27ca3f84685cffe6.html \ No newline at end of file diff --git a/googlee5bfefdedc6e792a.html b/googlee5bfefdedc6e792a.html new file mode 100644 index 00000000..e2932e68 --- /dev/null +++ b/googlee5bfefdedc6e792a.html @@ -0,0 +1 @@ +google-site-verification: googlee5bfefdedc6e792a.html \ No newline at end of file diff --git a/index.html b/index.html index cf15cd34..9b95ea41 100644 --- a/index.html +++ b/index.html @@ -4,6 +4,7 @@ DAISY Knowledge Bases + + + + + +
+
+

Explanation

+ +

An auditory access mode indicates that there is content that must be heard to + be understood (e.g., audio tracks on their own or as part of a video, or an audiobook). + It is expressed in metadata using the auditory value.

+ +

You do not have to set the auditory value if the audio does not include + information necessary to understand the content (e.g., background noises in an interactive + game or mood music).

+ +

Auditory content added using EPUB 3's media overlays feature is not considered an auditory + access mode unless the auditory content is the only way to read the entire publication.

+ +

For example, a mainstream publisher will typically add a media overlay to the full text of a + novel. In this case, the work would only have a textual access mode. + An accessible content republisher, on the other hand, might publish the same work with only + the chapter headings as text and all the content of the book synchronized to those headings + as audio (to allow users who are blind to move through the audio by heading). In this case, + the work would only have an auditory access mode.

+ +

Note that it is not possible for EPUB 2 publications to have an auditory access mode as the format + does not support embedding audio or have an equivalent to EPUB 3's media overlays.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">auditory</meta>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory"]
+
+
+ +
+

ONIX Mapping

+ +

The auditory value maps to multiple codes in list 81. Some common examples include + code 01 for audiobooks, + code 28 for video, and + code 44 for comics and manga.

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/chartOnVisual.html b/publishing/docs/metadata/schema.org/accessMode/chartOnVisual.html new file mode 100644 index 00000000..08556ff0 --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/chartOnVisual.html @@ -0,0 +1,103 @@ + + + + + chartOnVisual + + + + + + + + +
+
+
+

Caution

+

The application of this value and diagramOnVisual + is currently under discussion. One or both terms may be deprecated and/or replaced in the + future.

+
+ +

Explanation

+ +

A chartOnVisual access mode indicates that a publication contains images of + charts. It is expressed in metadata using the chartOnVisual value.

+ +

As chartOnVisual describes a characteristic of visual content, it is considered + a modifier of the visual access mode value and you should + always pair the two together.

+ +

Charts are graphics that represent data. Common examples include pie charts, bar charts, line graphs, + scatter plots, bubble charts, graphs, etc. For graphics that represent concepts, see diagramOnVisual.

+ +

It is also common to pair the chartOnVisual value with textOnVisual if the chart also contains text + content necessary to its understanding. (If the chart is encoded in a format like SVG + where the text character data is retained in the markup, however, textOnVisual + would not apply.)

+ +

It is also not uncommon to pair chartOnVisual with + colorDependent if color perception is the + only way to differentiate information (e.g., a pie chart without a secondary indicator + to differentiate each slice).

+ +

A chartOnVisual access mode is common in publications produced using the EPUB format + but is less common for audiobooks. It is only potentially relevant when an audiobook also contains + supplementary material beyond the audio.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">visual</meta>
+<meta property="schema:accessMode">chartOnVisual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="visual"/>
+<meta name="schema:accessMode" content="chartOnVisual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "visual", "chartOnVisual"]
+
+
+ +
+

ONIX Mapping

+ +

The chartsOnVisual value maps to list 81 + code 19 ("Figures, Diagrams, Charts").

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/chemOnVisual.html b/publishing/docs/metadata/schema.org/accessMode/chemOnVisual.html new file mode 100644 index 00000000..598b6524 --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/chemOnVisual.html @@ -0,0 +1,92 @@ + + + + + chemOnVisual + + + + + + + + +
+
+

Explanation

+ +

A chemOnVisual access mode indicates that a publication contains images of chemical + equations and formulas. It is expressed in metadata using the chemOnVisual value.

+ +

As chemOnVisual describes a characteristic of visual content, it is considered + a modifier of the visual access mode value and you should + always pair the two values together.

+ +

It is not uncommon to pair chemOnVisual with + colorDependent if color perception is the + only way to differentiate information (e.g., if relationships are color coded).

+ +

It is sometimes also paired with textOnVisual + if text content beyond the equation or formula data itself is also encoded in the image (e.g., + if relationships or descriptions are drawn as text in the image canvas).

+ +

Note that chemistry represented using a text-based markup language like MathML, or a formatting + language like LaTeX, is considered a textual access mode.

+ +

A chemOnVisual access mode is common in publications produced using the EPUB format + as there is no support for rendering chemical markup languages like ChemML. It is only potentially + relevant to audiobooks if there is supplementary material beyond the audio.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">visual</meta>
+<meta property="schema:accessMode">chemOnVisual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="visual"/>
+<meta name="schema:accessMode" content="chemOnVisual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "visual", "chemOnVisual"]
+
+
+ +
+

ONIX Mapping

+ +

The chemOnVisual value maps to list 81 + code 47 ("Chemical content").

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/colorDependent.html b/publishing/docs/metadata/schema.org/accessMode/colorDependent.html new file mode 100644 index 00000000..c02f7151 --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/colorDependent.html @@ -0,0 +1,105 @@ + + + + + colorDependent + + + + + + + + +
+
+

Explanation

+ +

A colorDependent access mode indicates that color is the sole means of conveying some visual + information. It is expressed in metadata using the colorDependent value.

+ +

As colorDependent describes a characteristic of visual content, it is considered + a modifier of the visual access mode value and you should + always pair the two values together.

+ +

A common example of the need to perceive color occurs with graphs and charts. If the bars in + a graph, or the slices in a pie chart, are differentiated by color alone, then users may + not be able understand the data unless they can perceive those color differences.

+ +

Color dependence can also manifest itself in other ways, such as when learning assignments + are color coded to age or difficulty level, or when hyperlinks are colored to indicate + their purpose (e.g., to open external web sites).

+ +

The application of the colorDependent value only applies to the visual reading + experience and the value is not set if a secondary means of differentiating the information + is available. If, for example, graphs and charts include distinct patterns in their data + representations, such as lines going in different directions, then a user can use those + patterns to differentiate the data. Similarly, hyperlinks can use different types of underline + to gives a visual cue to their existence and purpose.

+ +

Note, however, that any secondary means of differentiating the information must also be visual + before this label can be omitted. Affordances provided for non-visual readers, such as through + hidden ARIA attributes, are not generally accessible to visual readers so do not improve the + accessibility for them.

+ +

The colorDependent value is meant to help individuals with, for example, color + blindness and cognitive disabilities determine if the content will be accessible to them. + Whether affordances are provided that non-visual readers to access visual presentations is + declared through the sufficient access modes.

+ +

A colorDependent access mode is common in publications produced using the EPUB format but is + less common for audiobooks. It is only potentially relevant when an audiobook also contains + supplementary material beyond the audio.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">visual</meta>
+<meta property="schema:accessMode">colorDependent</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="visual"/>
+<meta name="schema:accessMode" content="colorDependent"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "textual", "colorDependent"]
+
+
+ +
+

ONIX Mapping

+ +

The colorDependent value does not currently have an ONIX equivalent.

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/diagramOnVisual.html b/publishing/docs/metadata/schema.org/accessMode/diagramOnVisual.html new file mode 100644 index 00000000..c52ba713 --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/diagramOnVisual.html @@ -0,0 +1,106 @@ + + + + + diagramOnVisual + + + + + + + + +
+
+
+

Caution

+

The application of this value and chartOnVisual + is currently under discussion. One or both terms may be deprecated and/or replaced in the + future.

+
+ +

Explanation

+ +

A diagramOnVisual access mode indicates that a publication contains images + of diagrams. It is expressed in metadata using the diagramOnVisual value.

+ +

As diagramOnVisual describes a characteristic of visual content, it is considered + a modifier of the visual access mode value and you should + always pair the two values together.

+ +

Diagrams are graphics that represent concepts, flow and relationships. Common examples include + mind maps, anatomical diagrams, flowcharts, instructions to complete tasks, etc. For graphics + that represent concepts, see chartOnVisual.

+ +

The diagramOnVisual value is also commonly paired with textOnVisual if the diagram also contains text + content necessary to its understanding. (If the diagram is encoded in a format like SVG where + the text character data is retained in the markup, however, textOnVisual would + not apply.)

+ +

It is also not uncommon to pair diagramOnVisual with + colorDependent if color perception is the + only way to differentiate information (e.g., a flow chart that uses colors to represent + different organizational groups).

+ +

The diagamOnVisual value would not be specified if the graphic does not carry + information necessary to understand the publication, although such cases are rare for diagrams.

+ +

A diagramOnVisual access mode is common in publications produced using the EPUB format + but is less common for audiobooks. It is only potentially relevant when an audiobook also contains + supplementary material beyond the audio.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">visual</meta>
+<meta property="schema:accessMode">diagramOnVisual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="visual"/>
+<meta name="schema:accessMode" content="diagramOnVisual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "visual", "diagramOnVisual"]
+
+
+ +
+

ONIX Mapping

+ +

The diagramOnVisual value maps to list 81 + code 19 ("Figures, Diagrams, Charts").

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/mathOnVisual.html b/publishing/docs/metadata/schema.org/accessMode/mathOnVisual.html new file mode 100644 index 00000000..c3e236f6 --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/mathOnVisual.html @@ -0,0 +1,92 @@ + + + + + mathOnVisual + + + + + + + + +
+
+

Explanation

+ +

A mathOnVisual access mode indicates that a publication contains images of mathematical + equations and formulas. It is expressed in metadata using the mathOnVisual value.

+ +

As mathOnVisual describes a characteristic of visual content, it is considered + a modifier of the visual access mode value and you should + always pair the two values together.

+ +

It is not uncommon to pair mathOnVisual with + colorDependent if color perception is the + only way to differentiate information (e.g., if relationships are color coded).

+ +

It is sometimes also paired with textOnVisual + if text content beyond the equation or formula data itself is also encoded in the image (e.g., + if relationships or descriptions are drawn as text in the image canvas).

+ +

Note that math represented using a text-based markup language like MathML, or a formatting + language like LaTeX, is considered a textual access mode.

+ +

A mathOnVisual access mode is common in publications produced using the EPUB format + but is less common for audiobooks. It is only potentially relevant when an audiobook also contains + supplementary material beyond the audio.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">visual</meta>
+<meta property="schema:accessMode">mathOnVisual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="visual"/>
+<meta name="schema:accessMode" content="mathOnVisual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "visual", "mathOnVisual"]
+
+
+ +
+

ONIX Mapping

+ +

The mathOnVisual value maps to list 81 + code 48 ("Mathematical content").

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/musicOnVisual.html b/publishing/docs/metadata/schema.org/accessMode/musicOnVisual.html new file mode 100644 index 00000000..696b55af --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/musicOnVisual.html @@ -0,0 +1,90 @@ + + + + + musicOnVisual + + + + + + + + +
+
+

Explanation

+ +

A musicOnVisual access mode indicates that a publication contains images of + musical scores. It is expressed in metadata using the musicOnVisual value.

+ +

As musicOnVisual describes a characteristic of visual content, it is considered + a modifier of the visual access mode value and you should + always pair the two values together.

+ +

The value is also commonly paired with textOnVisual + if, for example, the lyrics for a musical score also drawn in the image canvas. + +

It is also possible to pair musicOnVisual with + colorDependent if color perception is the + only way to differentiate information (e.g., color coding to help learners read music).

+ +

As support for rendering markup languages that represent musical scores is not generally available, + using images for music compositions is common. Consequently, a musicOnVisual access + mode would be typical for any publications produced using the EPUB format that contains music + scores. It is only relevant to an audiobook if it also contains supplementary material + beyond the audio.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">visual</meta>
+<meta property="schema:accessMode">musicOnVisual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="visual"/>
+<meta name="schema:accessMode" content="musicOnVisual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "visual", "musicOnVisual"]
+
+
+ +
+

ONIX Mapping

+ +

The musicOnVisual value maps to list 81 + code 11 ("Musical notation").

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/tactile.html b/publishing/docs/metadata/schema.org/accessMode/tactile.html new file mode 100644 index 00000000..8ad3035a --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/tactile.html @@ -0,0 +1,88 @@ + + + + + tactile + + + + + + + + +
+
+

Explanation

+ +

A tactile access mode indicates that a publication contains content perceived through touch, + such as braille-formatted text, tactile images, and tactile objects. It is expressed in metadata + using the tactile value.

+ +

The tactile value is typically not applicable to publications outside of accessible + republishing.

+ +

Although digital publications will not contain physical tactile objects, if a publication + provides links to such items (e.g., for download and printing on a 3d printer), you should set + the tactile value.

+ +

Do not use the tactile value to indicate that text content can be + converted to tactile form (e.g., using a refreshable braille display). A fully textual access mode, or a sufficient access mode of textual, + indicates that content can be converted to braille or read aloud using text-to-speech + synthesizers.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">tactile</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="tactile"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "tactile"]
+
+
+ +
+

ONIX Mapping

+ +

The tactile value maps to list 21 + code BRL for a braille edition or list 175 code E146 + for a BRF (braille ready format) file.

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/textOnVisual.html b/publishing/docs/metadata/schema.org/accessMode/textOnVisual.html new file mode 100644 index 00000000..54771b2b --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/textOnVisual.html @@ -0,0 +1,95 @@ + + + + + textOnVisual + + + + + + + + +
+
+

Explanation

+ +

A textOnVisual access mode indicates that a publication contains images of text. It is + expressed in metadata using the textOnVisual value.

+ +

As textOnVisual describes a characteristic of visual content, it is considered + a modifier of the visual access mode value and you should + always pair the two values together.

+ +

Images of text are where the text is part of the image data so can only be read visually. + JPEG and PNG are two common image formats that cannot preserve text separate from the visual + canvas it is drawn on. SVG, on the other hand, has markup elements to contain and present + text content, which allow reading systems and assistive technologies to access the character + data independent from its rendering.

+ +

Do not set the textOnVisual value when the text does not carry information + necessary to understand the publication. Corporate logos and the title on a cover page are a + couple of examples of image text that is considered decorative.

+ +

The value is sometimes paired with colorDependent + if color perception is the only way to differentiate information (e.g., colored text to differentiate + different learning levels or related topics).

+ +

A textOnVisual access mode is common in publications produced using the EPUB format, + particularly for comics and manga, but is less common for audiobooks. It is only potentially relevant + when an audiobook also contains supplementary material beyond the audio.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">visual</meta>
+<meta property="schema:accessMode">textOnVisual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="visual"/>
+<meta name="schema:accessMode" content="textOnVisual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "visual", "textOnVisual"]
+
+
+ +
+

ONIX Mapping

+ +

The textOnVisual value maps to list 81 + code 49 ("Images of text").

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/textual.html b/publishing/docs/metadata/schema.org/accessMode/textual.html new file mode 100644 index 00000000..1bb8a7d9 --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/textual.html @@ -0,0 +1,101 @@ + + + + + textual + + + + + + + + +
+
+

Explanation

+ +

A textual access mode indicates that a publication contains information encoded as text + character data. It is expressed in metadata using the tactile value.

+ +

The value only applies to digital publications (e.g., even though a print book has text content + it is considered to have a visual access mode because you must be able to see the ink on the page).

+ +

Text character data can be rendered and manipulated in a variety of ways to accommodate different user + needs — visually for sighted readers and readers with low vision, as synthetic speech for readers + who are blind, etc. This characteristic makes it the most flexible mode of access.

+ +

If a publication also contains images of text (i.e., where the text is part of the image data), set the + textOnVisual and visual + access mode values. If a publication only consists of images of text (e.g., comics and manga), do not + set a textual access mode value.

+ +

If an image format allows the text content to be retained in text form (e.g., SVG), set a + textual value in addition to visual (assuming there + is more to the image to understand it than just the text). Do not set the textOnVisual + value because it is possible for reading systems and assistive technologies to access and read + aloud the text content for users.

+ +

The textual value is also sometimes paired with colorDependent if color perception is the only way + to differentiate information (e.g., colored text to differentiate different learning levels or + related topics).

+ +

A textual access mode is common in publications produced using the EPUB format but is less common + for audiobooks. It is only potentially relevant when an audiobook also contains supplementary + material beyond the audio.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">textual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="textual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "textual"]
+
+
+ +
+

ONIX Mapping

+ +

The textual value most commonly maps to list 81 + code 10. It can map to other values + such as code 16 for text that is not part + of the main content

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessMode/visual.html b/publishing/docs/metadata/schema.org/accessMode/visual.html new file mode 100644 index 00000000..94a525d8 --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessMode/visual.html @@ -0,0 +1,94 @@ + + + + + visual + + + + + + + + +
+
+

Explanation

+ +

A visual access mode indicates that a publication contains content that must be seen to be + understood, such as images, graphics and video, or that it requires visual perception to fully + access information (e.g., the ability to perceive background or border colors, or to read + text that is encoded in images). It is expressed in metadata using the visual value.

+ +

Do not set the visual value if the visual content does not contain any information + necessary to understand the content (e.g., logos, cover artwork, and visual flair at the start of + chapters).

+ +

A visual access mode is common in publications produced using the EPUB format but is less common + for audiobooks. It is only potentially relevant when an audiobook also contains + supplementary material beyond the audio.

+ +

You should always set the visual value when using any of the visual content + indicators — chartOnVisual, + chemOnVisual, + diagramOnVisual, + mathOnVisual, + musicOnVisual, and + textOnVisual. You should also set it with + colorDependent when the color requirement + is in the visual content (as opposed to, say, colored textual content).

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessMode">visual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessMode" content="visual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessMode": ["auditory", "visual"]
+
+
+ +
+

ONIX Mapping

+ +

The visual value maps to multiple codes in list 81. Some common examples include + code 07 for still images and graphics, + code 28 for video, and + code 44 for comics and manga.

+
+ +
+

Related Links

+ + +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessModeSufficient.html b/publishing/docs/metadata/schema.org/accessModeSufficient.html index a60183ab..4a3bf773 100644 --- a/publishing/docs/metadata/schema.org/accessModeSufficient.html +++ b/publishing/docs/metadata/schema.org/accessModeSufficient.html @@ -4,6 +4,7 @@ accessModeSufficient + + + + + +
+
+

Explanation

+ +

An auditory sufficient access mode indicates that a publication can be + read, in whole or in part, if a user is able to perceive sound. It is expressed + in metadata using the auditory value.

+ +

A single auditory sufficient access mode is, by design, most commonly associated with + audiobooks, but it is also possible for formats like EPUB 3 that provide text and audio + synchronization for an entire work to have a solitary auditory sufficient access mode. + This is because sufficient access modes take into account any accessibility affordances + provided by the publisher.

+ +

Note, however, that unlike an auditory access mode, + an auditory sufficient access mode is always specified when media overlays are used in an EPUB 3 + file to include the full audio of the publication.

+ +

The auditory value is more commonly found in combination with textual + for works that include auditory clips, whether standalone or when the audio is part of a video.

+ +

Note that it is not possible for EPUB 2 publications to have an auditory sufficient access mode as + the format does not support embedding audio or have an equivalent to EPUB 3's media overlays.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessModeSufficient">textual</meta>
+<meta property="schema:accessModeSufficient">auditory</meta>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessModeSufficient": [
+   {
+      "type": "ItemList",
+      "itemListElement": ["auditory"],
+      "description": "Audio"
+   }
+]
+
+
+ +
+

ONIX Mapping

+ +

ONIX currently does not include a means of expressing sufficient access modes.

+
+ +
+

Related Links

+ +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessModeSufficient/tactile.html b/publishing/docs/metadata/schema.org/accessModeSufficient/tactile.html new file mode 100644 index 00000000..cd75b5b1 --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessModeSufficient/tactile.html @@ -0,0 +1,79 @@ + + + + + tactile + + + + + + + + +
+
+

Explanation

+ +

A tactile sufficient access mode indicates that a publication can be + read, in whole or in part, if a user is able to perceive content through touch. It is + expressed in metadata using the tactile value.

+ +

A single tactile sufficient access mode is most commonly associated with braille publications, + such as can be produced using the eBraille format (an specialization of EPUB 3 for braille). + EPUB publications can also entirely consist of braille content although this is not common.

+ +

A tactile sufficient access mode is sometimes found paired with other sufficient access modes. + For example, an audiobook for blind users might also include tactile graphics, in which case + it would have a sufficient access mode set of auditory and tactile.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessModeSufficient">tactile</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessModeSufficient" content="tactile"/>
+
+ + 
"accessModeSufficient": [
+   {
+      "type": "ItemList",
+      "itemListElement": ["auditory", "tactile"],
+      "description": "Audio and tactile graphics"
+   }
+]
+
+ +
+

ONIX Mapping

+ +

ONIX currently does not include a means of expressing sufficient access modes.

+
+ +
+

Related Links

+ +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessModeSufficient/textual.html b/publishing/docs/metadata/schema.org/accessModeSufficient/textual.html new file mode 100644 index 00000000..733a564e --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessModeSufficient/textual.html @@ -0,0 +1,124 @@ + + + + + textual + + + + + + + + +
+
+

Explanation

+ +

A textual sufficient access mode indicates that a publication can be + read, in whole or in part, if the user has a device that can present text character data in a form + they can read. This could be as visual text for sighted readers, or as text-to-speech playback or + refreshable braille for non-visual readers. It is expressed in metadata using the + textual value.

+ +

Any accessibility affordances provided by the author are considered when determining when to specify + a single textual sufficient access is available. For example, a publication might have + textual and visual + access modes if it contains a combination of text and images, but the publisher can state that + there is a single sufficient textual means of reading the content if the images all have + alternative text and/or extended descriptions that fully convey their meaning.

+ +

Similarly, text equivalents, like transcripts, provided for auditory content are considered when + determining if a publication can be read in full using only text character data.

+ + + +

Although a single textual sufficient access mode is generally the most important for users to + be aware of, because it allows the content to be read in a variety of different ways, always include + any other combinations of sufficient access modes that include textual content, especially if the + access modes are not listed.

+ +

For example, an EPUB 3 publication with both textual and visual content that also has a single + textual access mode would list the following possibilities:

+ + 
<meta property="schema:accessModeSufficient">textual, visual</meta>
+<meta property="schema:accessModeSufficient">textual</meta>
+
+ +

A single textual sufficient access mode is common in accessible publications produced + using the EPUB format but would never apply to an audiobook.

+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessModeSufficient">textual,visual</meta>
+<meta property="schema:accessModeSufficient">textual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessModeSufficient" content="textual,visual"/>
+<meta name="schema:accessModeSufficient" content="textual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessModeSufficient": [
+   {
+      "type": "ItemList",
+      "itemListElement": ["auditory", "textual"],
+      "description": "Audio and text"
+   }
+]
+
+
+ +
+

ONIX Mapping

+ +

ONIX currently does not include a means of expressing sufficient access modes.

+
+ +
+

Related Links

+ +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessModeSufficient/visual.html b/publishing/docs/metadata/schema.org/accessModeSufficient/visual.html new file mode 100644 index 00000000..bc7c11dd --- /dev/null +++ b/publishing/docs/metadata/schema.org/accessModeSufficient/visual.html @@ -0,0 +1,123 @@ + + + + + visual + + + + + + + + +
+
+

Explanation

+ +

A visual sufficient access mode value indicates that a publication can be + read, in whole or in part, if the user is able to visually perceive the content. It is + expressed in metadata using the visual value.

+ +

A visual value mostly commonly indicates that a publication contains images + and/or videos, but it is also used if the presentation must be visually perceived to + be understood.

+ +

If only a single visual sufficient access mode is set, it indicates that only sighted readers will + be able to read the content (i.e., the content is not universally accessible). Examples of publications + with only a single visual sufficient access mode include comics, manga, and photo books.

+ +

When combined with other values, a visual sufficient access mode indicates that some essential + content is only readable in visual form. It is most common to find the visual value + paired with textual as one means of reading the content, + with a single textual value to indicate that there are affordances that allow all + the visual content to also be read textually. Any book that is predominantly text-based but + includes images, video, interactive games, or other visual content will have both these values + set.

+ +

For example, an EPUB 3 publication with both textual and visual content that also has a single + textual access mode would list the following possibilities:

+ + 
<meta property="schema:accessModeSufficient">textual, visual</meta>
+<meta property="schema:accessModeSufficient">textual</meta>
+
+ +

A single visual sufficient access mode is common in accessible publications produced + using the EPUB format but would never apply to an audiobook.

+ +

Note that the visual content indicators + that can be specified as access modes are never listed as sufficient access modes. Only the + visual value is specified, as this value should always be paired with the content + indicators.

+ +
+

Note

+

An edge case can arise with the colorDependent indicator when it is + used to specify that textual styling may not be accessible only to users who are color blind (e.g., + hyperlinks may not be perceivable). Such publications are not accessible as they will fail WCAG + success criterion 1.4.1, but they typically + still provide a sufficient textual access mode for non-visual readers.

+ +

When the color perception issue is limited only to visual reading, indicate the problem in an accessibility summary and specify that there is single + textual sufficient access mode in addition to a visual and textual one.

+
+
+ +
+

Examples

+ +
+
+
Example 1 — EPUB 3
+
+ 
<meta property="schema:accessModeSufficient">textual,visual</meta>
+<meta property="schema:accessModeSufficient">textual</meta>
+
+ +
+
+
Example 2 — EPUB 2
+
+ 
<meta name="schema:accessModeSufficient" content="textual,visual"/>
+<meta name="schema:accessModeSufficient" content="textual"/>
+
+ +
+
+
Example 3 — Audiobooks
+
+ 
"accessModeSufficient": [
+   {
+      "type": "ItemList",
+      "itemListElement": ["auditory", "visual"],
+      "description": "Audio and images"
+   }
+]
+
+
+ +
+

ONIX Mapping

+ +

ONIX currently does not include a means of expressing sufficient access modes.

+
+ +
+

Related Links

+ +
+
+ + diff --git a/publishing/docs/metadata/schema.org/accessibilityAPI.html b/publishing/docs/metadata/schema.org/accessibilityAPI.html index 7bcabf1c..a982c6e0 100644 --- a/publishing/docs/metadata/schema.org/accessibilityAPI.html +++ b/publishing/docs/metadata/schema.org/accessibilityAPI.html @@ -4,6 +4,7 @@ accessibilityAPI + @@ -54,7 +55,7 @@

Examples

Explanation

The ARIA value - is used to indicate that ARIA roles are used to organize and improve the structural + indicates that ARIA roles are used to organize and improve the structural navigation of the publication (e.g., to identify key sections of the content and the purpose of hyperlinks).

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/ChemML.html b/publishing/docs/metadata/schema.org/accessibilityFeature/ChemML.html index f1131dfc..e0aa8413 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/ChemML.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/ChemML.html @@ -4,11 +4,12 @@ ChemML + @@ -54,7 +55,7 @@

Examples

Explanation

The ChemML - value is used to indicate that a publication contains chemical information (e.g., molecules + value indicates that a publication contains chemical information (e.g., molecules and reactions) encoded using the ChemML markup language.

This value is not typically used with publications at this time as there is no support for diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/MathML-chemistry.html b/publishing/docs/metadata/schema.org/accessibilityFeature/MathML-chemistry.html index fd1541c3..5b24b5d8 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/MathML-chemistry.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/MathML-chemistry.html @@ -4,11 +4,12 @@ MathML-chemistry + @@ -54,7 +55,7 @@

Examples

Explanation

The MathML-chemistry - value is used to indicate that the MathML markup language has been used to encode the + value indicates that the MathML markup language has been used to encode the chemical formulas and equations. For Web-based formats like EPUB, Presentational MathML is used to encode the content as it can be displayed in a growing number of reading systems and browsers.

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/MathML.html b/publishing/docs/metadata/schema.org/accessibilityFeature/MathML.html index 32d10ee3..b1d895ba 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/MathML.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/MathML.html @@ -4,11 +4,12 @@ MathML + @@ -54,7 +55,7 @@

Examples

Explanation

The MathML - value is used to indicate that the MathML markup language has been used to encode the + value indicates that the MathML markup language has been used to encode the mathematical equations. For Web-based formats like EPUB, Presentational MathML is used to encode the content as it can be displayed in a growing number of reading systems and browsers.

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/alternativeText.html b/publishing/docs/metadata/schema.org/accessibilityFeature/alternativeText.html index 3b0362e4..11263976 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/alternativeText.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/alternativeText.html @@ -4,11 +4,12 @@ alternativeText + @@ -55,7 +56,7 @@

Explanation

The alternativeText - value is used to indicate that all images and other non-text content (e.g., audio and + value indicates that all images and other non-text content (e.g., audio and video) that is relevant to understanding a publication includes a text alternative.

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/audioDescription.html b/publishing/docs/metadata/schema.org/accessibilityFeature/audioDescription.html index a483f8a0..3695c3d2 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/audioDescription.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/audioDescription.html @@ -4,11 +4,12 @@ audioDescription + @@ -55,7 +56,7 @@

Explanation

The audioDescription - value is used to indicate that description tracks are included for any video sources that + value indicates that description tracks are included for any video sources that require them.

Audio descriptions differ from captions and subtitles in that they diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/braille.html b/publishing/docs/metadata/schema.org/accessibilityFeature/braille.html index 196c42b0..5cab3f5d 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/braille.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/braille.html @@ -4,11 +4,12 @@ braille + @@ -54,7 +55,7 @@

Examples

Explanation

The braille - value is used to indicate that either that a publication comes in a preformatted tactile + value indicates that either that a publication comes in a preformatted tactile form or that an alternative rendition in this medium is included.

This value is primarily used by accessible republishers who produce HTML files using braille diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/closedCaptions.html b/publishing/docs/metadata/schema.org/accessibilityFeature/closedCaptions.html index 1e80dbd7..170624f2 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/closedCaptions.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/closedCaptions.html @@ -4,11 +4,12 @@ closedCaptions + @@ -54,7 +55,7 @@

Examples

Explanation

The closedCaptions - value is used to indicate that a publication includes closed captions for auditory content.

+ value indicates that a publication includes closed captions for auditory content.

Closed captions are defined separately from the video stream, allowing users to turn them on or off and control their appearance. Open captions, by contrast, diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/describedMath.html b/publishing/docs/metadata/schema.org/accessibilityFeature/describedMath.html index 213dc781..0cedfb83 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/describedMath.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/describedMath.html @@ -4,11 +4,12 @@ describedMath + @@ -54,7 +55,7 @@

Examples

Explanation

The describedMath - value is used to indicate that a publication includes textual descriptions for math + value indicates that a publication includes textual descriptions for math equations.

Text descriptions can be provided, for example, using language-specific technologies like the diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/displayTransformability.html b/publishing/docs/metadata/schema.org/accessibilityFeature/displayTransformability.html index b0216ec6..44bdf562 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/displayTransformability.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/displayTransformability.html @@ -4,11 +4,12 @@ displayTransformability + @@ -55,7 +56,7 @@

Explanation

The displayTransformability - value is used to indicate that a publication does not restrict the ability of users to + value indicates that a publication does not restrict the ability of users to modify the display of textual content (e.g., to change the font family, font size, line height and word spacing).

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/fullRubyAnnotations.html b/publishing/docs/metadata/schema.org/accessibilityFeature/fullRubyAnnotations.html index 14419387..dc3e8ff5 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/fullRubyAnnotations.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/fullRubyAnnotations.html @@ -4,11 +4,12 @@ fullRubyAnnotations + diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/highContrastAudio.html b/publishing/docs/metadata/schema.org/accessibilityFeature/highContrastAudio.html index 5fa297f3..9508667d 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/highContrastAudio.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/highContrastAudio.html @@ -4,6 +4,7 @@ highContrastAudio + @@ -55,7 +56,7 @@

Explanation

The highContrastDisplay - value is used to indicate that there is at least a 7:1 contrast ratio between the + value indicates that there is at least a 7:1 contrast ratio between the foreground text and the background, including for images of text (see WCAG success criterion 1.4.6).

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/horizontalWriting.html b/publishing/docs/metadata/schema.org/accessibilityFeature/horizontalWriting.html index fd17d808..d26c97e9 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/horizontalWriting.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/horizontalWriting.html @@ -4,11 +4,12 @@ horizontalWriting + diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/index.html b/publishing/docs/metadata/schema.org/accessibilityFeature/index.html index 98ddd5d5..7879d98b 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/index.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/index.html @@ -4,11 +4,12 @@ index + @@ -54,7 +55,7 @@

Examples

Explanation

The index value - is used to indicate that a publication contains one or more indexes of the content (e.g., a + indicates that a publication contains one or more indexes of the content (e.g., a topical index or index of names).

Indexes allow users who cannot see the text or have difficulty following it to find and diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/largePrint.html b/publishing/docs/metadata/schema.org/accessibilityFeature/largePrint.html index 96563805..7e55d2c5 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/largePrint.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/largePrint.html @@ -4,11 +4,12 @@ largePrint + @@ -54,7 +55,7 @@

Examples

Explanation

The largePrint - value is used to indicate that the text of a publication has been formatted to meet large + value indicates that the text of a publication has been formatted to meet large print guidelines. Large print guidelines vary from region to region, but generally require a point size ranging from 14 to 18, use of sans serif fonts, and increased word spacing.

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/latex-chemistry.html b/publishing/docs/metadata/schema.org/accessibilityFeature/latex-chemistry.html index ed62a53f..10156274 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/latex-chemistry.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/latex-chemistry.html @@ -4,11 +4,12 @@ latex-chemistry + @@ -55,7 +56,7 @@

Examples

Explanation

The latex-chemistry - value is used to indicate that a publication contains chemical formulas and equations + value indicates that a publication contains chemical formulas and equations formatted using the LaTeX typesetting system.

LaTeX equations can retain semantic information about formulas that is not always diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/latex.html b/publishing/docs/metadata/schema.org/accessibilityFeature/latex.html index 22509bac..69a50737 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/latex.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/latex.html @@ -4,11 +4,12 @@ latex + @@ -54,7 +55,7 @@

Examples

Explanation

The latex value - is used to indicate that a publication contains math equations formatted using the LaTeX + indicates that a publication contains math equations formatted using the LaTeX typesetting system.

LaTeX equations can retain semantic information about math equations that is not always diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/longDescription.html b/publishing/docs/metadata/schema.org/accessibilityFeature/longDescription.html index e0e53c47..f208fb83 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/longDescription.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/longDescription.html @@ -4,11 +4,12 @@ longDescription + @@ -55,7 +56,7 @@

Explanation

The longDescription - value is used to indicate that all complex content (images, tables, charts, equations, + value indicates that all complex content (images, tables, charts, equations, etc.) include an extended description of their purpose.

Complexity is determined by whether alternative text alone is diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/none.html b/publishing/docs/metadata/schema.org/accessibilityFeature/none.html index 8703129a..eb55570d 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/none.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/none.html @@ -4,6 +4,7 @@ none + @@ -54,7 +55,7 @@

Examples

Explanation

The openCaptions - value is used to indicate that a publication includes open captions for auditory content.

+ value indicates that a publication includes open captions for auditory content.

Open captions are burned directly into the video stream and are always visible in an unchangeable form. Closed captions, by contrast, are defined separately from diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/pageBreakMarkers.html b/publishing/docs/metadata/schema.org/accessibilityFeature/pageBreakMarkers.html index b1568e70..176f3369 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/pageBreakMarkers.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/pageBreakMarkers.html @@ -4,11 +4,12 @@ pageBreakMarkers + @@ -56,7 +57,7 @@

Explanation

The pageBreakMarkers - value is used to indicate that static page break locations are included in the text.

+ value indicates that static page break locations are included in the text.

The inclusion of page break markers from a print source allows users to identify where they are in a digital publication relative to its print equivalent. The page break markers are diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/pageNavigation.html b/publishing/docs/metadata/schema.org/accessibilityFeature/pageNavigation.html index 1c372484..dc623073 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/pageNavigation.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/pageNavigation.html @@ -4,6 +4,7 @@ pageNavigation + @@ -56,7 +57,7 @@

Explanation

The rubyAnnotations - value is used to indicate that a publication includes ruby annotations.

+ value indicates that a publication includes ruby annotations.

Ruby annotations are most commonly used to provide pronunciation guides for Chinese, Japanese and Korean texts.

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/signLanguage.html b/publishing/docs/metadata/schema.org/accessibilityFeature/signLanguage.html index 02a3ea30..e626cfc7 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/signLanguage.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/signLanguage.html @@ -4,11 +4,12 @@ signLanguage + @@ -55,7 +56,7 @@

Explanation

The signLanguage - value is used to indicate that sign language interpretation is included for any auditory + value indicates that sign language interpretation is included for any auditory content.

Although captions and audio diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/structuralNavigation.html b/publishing/docs/metadata/schema.org/accessibilityFeature/structuralNavigation.html index 486ebad3..58681d85 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/structuralNavigation.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/structuralNavigation.html @@ -4,11 +4,12 @@ structuralNavigation + @@ -55,7 +56,7 @@

Explanation

The structuralNavigation - value is used to indicate that all headings are properly marked up.

+ value indicates that all headings are properly marked up.

The use of headings tags, and their correct numbering, allows users of assistive technologies to quickly move through the different levels of the book without having to traverse the diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/synchronizedAudioText.html b/publishing/docs/metadata/schema.org/accessibilityFeature/synchronizedAudioText.html index 07b7b5f5..b1b4f8ba 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/synchronizedAudioText.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/synchronizedAudioText.html @@ -4,11 +4,12 @@ synchronizedAudioText + @@ -55,7 +56,7 @@

Explanation

The synchronizedAudioText - value is used to indicate that synchronized playback of prerecorded audio with text + value indicates that synchronized playback of prerecorded audio with text highlighting is available.

Synchronized playback can help new language learners follow the text and hear how it is diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/tableOfContents.html b/publishing/docs/metadata/schema.org/accessibilityFeature/tableOfContents.html index 88a5c8c0..a9fdd6f5 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/tableOfContents.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/tableOfContents.html @@ -4,6 +4,7 @@ tableOfContents + @@ -55,7 +56,7 @@

Explanation

The tactileGraphic - value is used to indicate that a publication includes access to tactile graphics.

+ value indicates that a publication includes access to tactile graphics.

As EPUB reading systems typically cannot present tactile graphics to users, hyperlinks to downloadable graphics are a common way to make these available. It is not required that the diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/tactileObject.html b/publishing/docs/metadata/schema.org/accessibilityFeature/tactileObject.html index 02c0a15e..eed254fd 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/tactileObject.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/tactileObject.html @@ -4,11 +4,12 @@ tactileObject + @@ -55,7 +56,7 @@

Explanation

The tactileObject - value is used to indicate that a publication includes tactile objects.

+ value indicates that a publication includes tactile objects.

Due to the need to print tactile objects, hyperlinks to downloadable files are the most common way to make these available.

diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/taggedPDF.html b/publishing/docs/metadata/schema.org/accessibilityFeature/taggedPDF.html index dde0e0f0..2538626c 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/taggedPDF.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/taggedPDF.html @@ -4,11 +4,12 @@ taggedPDF + @@ -47,7 +48,7 @@

Examples

Explanation

The taggedPDF - value is used to indicate that a PDF includes accessibility tags to improve its + value indicates that a PDF includes accessibility tags to improve its readability.

Accessibility tags are a way of labeling the components of a PDF to try and retain some of diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/timingControl.html b/publishing/docs/metadata/schema.org/accessibilityFeature/timingControl.html index 5b9bfc8f..cf522b38 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/timingControl.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/timingControl.html @@ -4,11 +4,12 @@ timingControl + @@ -55,7 +56,7 @@

Explanation

The timingControl - value is used to indicate that a publication contains content with timed interactions + value indicates that a publication contains content with timed interactions (e.g., a quiz or game with a time limit) and that the timing can be controlled by the user.

As users with disabilities may require additional time to complete tasks, they need to be diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/transcript.html b/publishing/docs/metadata/schema.org/accessibilityFeature/transcript.html index 4fe3e9b2..4b74284a 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/transcript.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/transcript.html @@ -4,11 +4,12 @@ transcript + @@ -54,7 +55,7 @@

Examples

Explanation

The transcript - value is used to indicate that transcripts are provided for any auditory content.

+ value indicates that transcripts are provided for any auditory content.

Transcripts allow users who cannot hear the audio or have difficulty following the speech to read what was spoken. They are an alternative to embedding audio diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/ttsMarkup.html b/publishing/docs/metadata/schema.org/accessibilityFeature/ttsMarkup.html index 94f852ce..335b95d6 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/ttsMarkup.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/ttsMarkup.html @@ -4,11 +4,12 @@ ttsMarkup + @@ -54,7 +55,7 @@

Examples

Explanation

The ttsMarkup - value is used to indicate that a publication's text has been enhanced with additional + value indicates that a publication's text has been enhanced with additional phonetic markup to improve text-to-speech (TTS) playback.

Synthetic speech engines often struggle to render complex words and heteronyms (words that diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/unknown.html b/publishing/docs/metadata/schema.org/accessibilityFeature/unknown.html index 71ca8f1d..cde379a5 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/unknown.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/unknown.html @@ -4,6 +4,7 @@ unknown + diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/withAdditionalWordSegmentation.html b/publishing/docs/metadata/schema.org/accessibilityFeature/withAdditionalWordSegmentation.html index eacfed1d..f7010164 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/withAdditionalWordSegmentation.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/withAdditionalWordSegmentation.html @@ -4,11 +4,12 @@ withAdditionalWordSegmentation + diff --git a/publishing/docs/metadata/schema.org/accessibilityFeature/withoutAdditionalWordSegmentation.html b/publishing/docs/metadata/schema.org/accessibilityFeature/withoutAdditionalWordSegmentation.html index 34132efd..c9506190 100644 --- a/publishing/docs/metadata/schema.org/accessibilityFeature/withoutAdditionalWordSegmentation.html +++ b/publishing/docs/metadata/schema.org/accessibilityFeature/withoutAdditionalWordSegmentation.html @@ -4,11 +4,12 @@ withoutAdditionalWordSegmentation + diff --git a/publishing/docs/metadata/schema.org/accessibilityHazard.html b/publishing/docs/metadata/schema.org/accessibilityHazard.html index a9b0d72e..6ccaca26 100644 --- a/publishing/docs/metadata/schema.org/accessibilityHazard.html +++ b/publishing/docs/metadata/schema.org/accessibilityHazard.html @@ -4,6 +4,7 @@ accessibilityHazard + @@ -20,7 +21,7 @@

Explanation

-

The flashing values is used to indicate that there is content in the publication +

The flashing values indicates that there is content in the publication that flashes more than three times a second or that the flashing is below the general flash and red flash thresholds.

diff --git a/publishing/docs/metadata/schema.org/accessibilityHazard/motionSimulation.html b/publishing/docs/metadata/schema.org/accessibilityHazard/motionSimulation.html index 98c0d3da..ba0deb36 100644 --- a/publishing/docs/metadata/schema.org/accessibilityHazard/motionSimulation.html +++ b/publishing/docs/metadata/schema.org/accessibilityHazard/motionSimulation.html @@ -4,11 +4,12 @@ motionSimulation + @@ -20,7 +21,7 @@

Explanation

-

The motionSimulation value is used to indicate that there is content that +

The motionSimulation value indicates that there is content that simulates motion.

Motion simulation can cause headaches and nausea in some users. In addition to setting this diff --git a/publishing/docs/metadata/schema.org/accessibilityHazard/noFlashingHazard.html b/publishing/docs/metadata/schema.org/accessibilityHazard/noFlashingHazard.html index 07a7137f..afed11fc 100644 --- a/publishing/docs/metadata/schema.org/accessibilityHazard/noFlashingHazard.html +++ b/publishing/docs/metadata/schema.org/accessibilityHazard/noFlashingHazard.html @@ -4,6 +4,7 @@ noFlashingHazard + @@ -20,7 +21,7 @@

Explanation

-

The sound value is used to indicate that a publication contains auditory content +

The sound value indicates that a publication contains auditory content that can harm sound-sensitive individuals.

Sounds can cause seizures in some users, for example, or may trigger headaches. The causes diff --git a/publishing/docs/metadata/schema.org/accessibilityHazard/unknown.html b/publishing/docs/metadata/schema.org/accessibilityHazard/unknown.html index c1b4c41b..6a541789 100644 --- a/publishing/docs/metadata/schema.org/accessibilityHazard/unknown.html +++ b/publishing/docs/metadata/schema.org/accessibilityHazard/unknown.html @@ -4,6 +4,7 @@ unknown + @@ -20,7 +21,7 @@

Explanation

-

The unknownFlashingHazard value is used to indicate that a publisher has not yet +

The unknownFlashingHazard value indicates that a publisher has not yet checked for flashing hazards or is unsure whether some content might present a hazard.

diff --git a/publishing/docs/metadata/schema.org/accessibilityHazard/unknownMotionSimulationHazard.html b/publishing/docs/metadata/schema.org/accessibilityHazard/unknownMotionSimulationHazard.html index c06f2ae7..ddf599f2 100644 --- a/publishing/docs/metadata/schema.org/accessibilityHazard/unknownMotionSimulationHazard.html +++ b/publishing/docs/metadata/schema.org/accessibilityHazard/unknownMotionSimulationHazard.html @@ -4,11 +4,12 @@ unknownMotionSimulationHazard + @@ -20,7 +21,7 @@

Explanation

-

The unknownMotionSimulationHazard value is used to indicate that a publisher has not yet +

The unknownMotionSimulationHazard value indicates that a publisher has not yet checked for motion simulation hazards or is unsure whether some content might present a hazard.

diff --git a/publishing/docs/metadata/schema.org/accessibilityHazard/unknownSoundHazard.html b/publishing/docs/metadata/schema.org/accessibilityHazard/unknownSoundHazard.html index fc294f2e..7fe353c9 100644 --- a/publishing/docs/metadata/schema.org/accessibilityHazard/unknownSoundHazard.html +++ b/publishing/docs/metadata/schema.org/accessibilityHazard/unknownSoundHazard.html @@ -4,6 +4,7 @@ unknownSoundHazard + + + + +
+
+

About

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Version:WCAG 2.2 and up
Number:3.3.9
Level:AAA
Applicability: +
    +
  • Authentication Forms
    • +
+
Requirement: +

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

+ +
    +
  • Alternative: Another authentication method that does not rely on a cognitive function test.
    • +
  • Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
    • +
+
Guidance: + +
Techniques: + Techniques are not yet available for WCAG 2.2 success criteria. +
+
+
+

Purpose

+ +

The purpose of this success criterion is to ensure that users with cognitive disabilities can + authenticate themselves when cognitive function tests — such as password input, memorization, + puzzle solving, and calculations — are used to prevent unauthorized access.

+
+
+

How to Meet

+ +

This success criterion only differs from 3.3.8 in + that no exception is made for functional tests that require the recognition of objects or content + provided by the user. + +

As it is not common for digital publications to authenticate users, this success criterion rarely + applies (authentication is usually done by the user agent).

+
+
+

Additional Information

+ +

The knowledge base does not currently include information on accessible authentication due to the + lack of implementation in publishing formats. Refer to the WCAG guidance + documents for additional information.

+
+
+ + diff --git a/publishing/docs/wcag/accessible-authentication-minimum.html b/publishing/docs/wcag/accessible-authentication-minimum.html new file mode 100644 index 00000000..f0617c1c --- /dev/null +++ b/publishing/docs/wcag/accessible-authentication-minimum.html @@ -0,0 +1,104 @@ + + + + + Accessible Authentication (Minimum) + + + + + + + +
+
+

About

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Version:WCAG 2.2 and up
Number:3.3.8
Level:A
Applicability: +
    +
  • Authentication Forms
    • +
+
Requirement: +

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

+ +
    +
  • Alternative: Another authentication method that does not rely on a cognitive function test.
    • +
  • Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
    • +
  • Object Recognition: The cognitive function test is to recognize objects.
    • +
  • Personal Content: The cognitive function test is to identify non-text content the user provided to the website.
    • +
+
Guidance: + +
Techniques: + Techniques are not yet available for WCAG 2.2 success criteria. +
+
+
+

Purpose

+ +

The purpose of this success criterion is to ensure that users with cognitive disabilities can + authenticate themselves when cognitive function tests — such as password input, memorization, + puzzle solving, and calculations — are used to prevent unauthorized access.

+
+
+

How to Meet

+ +

As it is not common for digital publications to authenticate users, this success criterion rarely + applies (authentication is usually done by the user agent).

+ +

If authors use authentication forms with cognitive function tests to secure access to some part of + a publication, however, they need to ensure there is an alternative that does not rely on a + functional test, a means of helping users with the test, or the test only requires recognition of + objects or content provided by the user.

+
+
+

Additional Information

+ +

The knowledge base does not currently include information on accessible authentication due to the + lack of implementation in publishing formats. Refer to the WCAG guidance + documents for additional information.

+
+
+ + diff --git a/publishing/docs/wcag/accessible-authentication-no-exception.html b/publishing/docs/wcag/accessible-authentication-no-exception.html index 6927f28c..e2c460cb 100644 --- a/publishing/docs/wcag/accessible-authentication-no-exception.html +++ b/publishing/docs/wcag/accessible-authentication-no-exception.html @@ -3,98 +3,11 @@ Accessible Authentication (Enhanced) - - - - +
-
-

About

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Version:WCAG 2.2 and up
Number:3.3.9
Level:AAA
Applicability: -
    -
  • Authentication Forms
    • -
-
Requirement: -

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

- -
    -
  • Alternative: Another authentication method that does not rely on a cognitive function test.
    • -
  • Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
    • -
-
Guidance: - -
Techniques: - Techniques are not yet available for WCAG 2.2 success criteria. -
-
-
-

Purpose

- -

The purpose of this success criterion is to ensure that users with cognitive disabilities can - authenticate themselves when cognitive function tests — such as password input, memorization, - puzzle solving, and calculations — are used to prevent unauthorized access.

-
-
-

How to Meet

- -

This success criterion only differs from 3.3.8 in - that no exception is made for functional tests that require the recognition of objects or content - provided by the user. - -

As it is not common for digital publications to authenticate users, this success criterion rarely - applies (authentication is usually done by the user agent).

-
-
-

Additional Information

- -

The knowledge base does not currently include information on accessible authentication due to the - lack of implementation in publishing formats. Refer to the WCAG guidance - documents for additional information.

-
+

This page has moved to the accessible-authentication-enhanced.html

diff --git a/publishing/docs/wcag/accessible-authentication.html b/publishing/docs/wcag/accessible-authentication.html index c64d5d53..695d4570 100644 --- a/publishing/docs/wcag/accessible-authentication.html +++ b/publishing/docs/wcag/accessible-authentication.html @@ -3,101 +3,11 @@ Accessible Authentication (Minimum) - - - - +
-
-

About

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Version:WCAG 2.2 and up
Number:3.3.8
Level:A
Applicability: -
    -
  • Authentication Forms
    • -
-
Requirement: -

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

- -
    -
  • Alternative: Another authentication method that does not rely on a cognitive function test.
    • -
  • Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
    • -
  • Object Recognition: The cognitive function test is to recognize objects.
    • -
  • Personal Content: The cognitive function test is to identify non-text content the user provided to the website.
    • -
-
Guidance: - -
Techniques: - Techniques are not yet available for WCAG 2.2 success criteria. -
-
-
-

Purpose

- -

The purpose of this success criterion is to ensure that users with cognitive disabilities can - authenticate themselves when cognitive function tests — such as password input, memorization, - puzzle solving, and calculations — are used to prevent unauthorized access.

-
-
-

How to Meet

- -

As it is not common for digital publications to authenticate users, this success criterion rarely - applies (authentication is usually done by the user agent).

- -

If authors use authentication forms with cognitive function tests to secure access to some part of - a publication, however, they need to ensure there is an alternative that does not rely on a - functional test, a means of helping users with the test, or the test only requires recognition of - objects or content provided by the user.

-
-
-

Additional Information

- -

The knowledge base does not currently include information on accessible authentication due to the - lack of implementation in publishing formats. Refer to the WCAG guidance - documents for additional information.

-
+

This page has moved to the accessible-authentication-minimum.html

diff --git a/publishing/docs/wcag/animation-from-interactions.html b/publishing/docs/wcag/animation-from-interactions.html index 2e1b32f8..209dee60 100644 --- a/publishing/docs/wcag/animation-from-interactions.html +++ b/publishing/docs/wcag/animation-from-interactions.html @@ -4,6 +4,7 @@ Animation from Interactions + + + + +
+
+

概要

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
バージョン：WCAG 2.2以上
セクション番号：3.3.9
レベル：AAA
適用対象： +
    +
  • 認証フォーム
    • +
+
要件： +

認知機能テスト（パスワードの記憶やパズルの解決など） は認証プロセスのどのステップにおいても要求されない。ただし、そのステップが次の少なくとも一つを提供する場合は除く。

+ +
    +
  • 代替手段：認知機能テストに依存しない別の認証方法がある。
    • +
  • メカニズム：認知機能テストを利用者が完遂できるように支援するメカニズムが利用できる。
    • +
+
ガイダンス： + +
達成方法：WCAG 2.2の達成基準に対応する達成方法はまだ利用できない。
+
+
+

目的

+ +

この達成基準の目的は、不正アクセスを防ぐために、パスワード入力、記憶、パズルの解決、計算などの認知機能テストを使用する際に、認知障害のあるユーザーが自分自身を認証できるようにすることです。

+
+
+

要件の満たし方

+ +

この達成基準は、ユーザーが提供するオブジェクトまたはコンテンツの認識を必要とする機能テストについては例外が設けられていないという点でのみ、 3.3.8と異なります。

+

デジタル出版物ではユーザーを認証することが一般的ではないため、この達成基準はほとんど適用されません。（通常、ユーザーエージェントによって認証されます）

+
+
+

追加情報

+ +

出版フォーマットでの実装が不十分であるため、ナレッジベースには現在アクセシブルな認証に関する情報は含まれていません。詳細については、WCAG ガイダンス ドキュメントを参照してください。

+
+
+ + diff --git a/publishing/ja/wcag/accessible-authentication-minimum.html b/publishing/ja/wcag/accessible-authentication-minimum.html new file mode 100644 index 00000000..9e527d1b --- /dev/null +++ b/publishing/ja/wcag/accessible-authentication-minimum.html @@ -0,0 +1,94 @@ + + + + + アクセシブルな認証（最低限） + + + + + + + +
+
+

概要

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
バージョン：WCAG 2.2以上
セクション番号：3.3.8
レベル：A
適用対象： +
    +
  • 認証フォーム
    • +
+
要件： +

認知機能テスト（パスワードの記憶やパズルの解決など）は認証プロセスのどのステップにおいても要求しない。ただし、そのステップで次の少なくとも一つが提供される場合は除く。

+ +
    +
  • 代替手段：認知機能テストに依存しない別の認証方法がある。
    • +
  • メカニズム：認知機能テストを利用者が完遂できるように支援するメカニズムが利用できる。
    • +
  • 物体の認識：認知機能テストは、物体を認識させるものである。
    • +
  • 個人特有のコンテンツ：認知機能テストは、その利用者本人がウェブサイトに提供した非テキストコンテンツを識別させるものである。
    • +
+
ガイダンス： + +
達成方法：WCAG 2.2の達成基準に対応する達成方法はまだ利用できない。
+
+
+

目的

+ +

この達成基準の目的は、不正アクセスを防ぐために、パスワード入力、記憶、パズルの解決、計算などの認知機能テストを使用する際に、認知障害のあるユーザーが自分自身を認証できるようにすることです。

+
+
+

要件の満たし方

+ +

デジタル出版物ではユーザーを認証することが一般的ではないため、この達成基準はほとんど適用されません。（通常、ユーザーエージェントによって認証されます）

+ +

ただし、コンテンツ製作者が出版物の一部へのアクセスを保護するために認知機能テストを含む認証フォームを使用する場合には、認知機能テストに依存しない代替手段、テストでユーザーを支援するメカニズム、物体の認識のみを必要とするテスト、ユーザーが提供したコンテンツによる方法が存在するのを確認してください。

+
+
+

追加情報

+ +

出版フォーマットでの実装が不十分であるため、ナレッジベースには現在アクセシブルな認証に関する情報は含まれていません。詳細については、WCAG ガイダンス ドキュメントを参照してください。

+
+
+ + diff --git a/publishing/ja/wcag/accessible-authentication-no-exception.html b/publishing/ja/wcag/accessible-authentication-no-exception.html index b4854d2d..a3686677 100644 --- a/publishing/ja/wcag/accessible-authentication-no-exception.html +++ b/publishing/ja/wcag/accessible-authentication-no-exception.html @@ -4,87 +4,10 @@ アクセシブルな認証（高度） - - - +
-
-

概要

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
バージョン：WCAG 2.2以上
セクション番号：3.3.9
レベル：AAA
適用対象： -
    -
  • 認証フォーム
    • -
-
要件： -

認知機能テスト（パスワードの記憶やパズルの解決など） は認証プロセスのどのステップにおいても要求されない。ただし、そのステップが次の少なくとも一つを提供する場合は除く。

- -
    -
  • 代替手段：認知機能テストに依存しない別の認証方法がある。
    • -
  • メカニズム：認知機能テストを利用者が完遂できるように支援するメカニズムが利用できる。
    • -
-
ガイダンス： - -
達成方法：WCAG 2.2の達成基準に対応する達成方法はまだ利用できない。
-
-
-

目的

- -

この達成基準の目的は、不正アクセスを防ぐために、パスワード入力、記憶、パズルの解決、計算などの認知機能テストを使用する際に、認知障害のあるユーザーが自分自身を認証できるようにすることです。

-
-
-

要件の満たし方

- -

この達成基準は、ユーザーが提供するオブジェクトまたはコンテンツの認識を必要とする機能テストについては例外が設けられていないという点でのみ、 3.3.8と異なります。

-

デジタル出版物ではユーザーを認証することが一般的ではないため、この達成基準はほとんど適用されません。（通常、ユーザーエージェントによって認証されます）

-
-
-

追加情報

- -

出版フォーマットでの実装が不十分であるため、ナレッジベースには現在アクセシブルな認証に関する情報は含まれていません。詳細については、WCAG ガイダンス ドキュメントを参照してください。

-
diff --git a/publishing/ja/wcag/accessible-authentication.html b/publishing/ja/wcag/accessible-authentication.html index 27973501..4cb81896 100644 --- a/publishing/ja/wcag/accessible-authentication.html +++ b/publishing/ja/wcag/accessible-authentication.html @@ -4,90 +4,10 @@ アクセシブルな認証（最低限） - - - +
-
-

概要

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
バージョン：WCAG 2.2以上
セクション番号：3.3.8
レベル：A
適用対象： -
    -
  • 認証フォーム
    • -
-
要件： -

認知機能テスト（パスワードの記憶やパズルの解決など）は認証プロセスのどのステップにおいても要求しない。ただし、そのステップで次の少なくとも一つが提供される場合は除く。

- -
    -
  • 代替手段：認知機能テストに依存しない別の認証方法がある。
    • -
  • メカニズム：認知機能テストを利用者が完遂できるように支援するメカニズムが利用できる。
    • -
  • 物体の認識：認知機能テストは、物体を認識させるものである。
    • -
  • 個人特有のコンテンツ：認知機能テストは、その利用者本人がウェブサイトに提供した非テキストコンテンツを識別させるものである。
    • -
-
ガイダンス： - -
達成方法：WCAG 2.2の達成基準に対応する達成方法はまだ利用できない。
-
-
-

目的

- -

この達成基準の目的は、不正アクセスを防ぐために、パスワード入力、記憶、パズルの解決、計算などの認知機能テストを使用する際に、認知障害のあるユーザーが自分自身を認証できるようにすることです。

-
-
-

要件の満たし方

- -

デジタル出版物ではユーザーを認証することが一般的ではないため、この達成基準はほとんど適用されません。（通常、ユーザーエージェントによって認証されます）

- -

ただし、コンテンツ製作者が出版物の一部へのアクセスを保護するために認知機能テストを含む認証フォームを使用する場合には、認知機能テストに依存しない代替手段、テストでユーザーを支援するメカニズム、物体の認識のみを必要とするテスト、ユーザーが提供したコンテンツによる方法が存在するのを確認してください。

-
-
-

追加情報

- -

出版フォーマットでの実装が不十分であるため、ナレッジベースには現在アクセシブルな認証に関する情報は含まれていません。詳細については、WCAG ガイダンス ドキュメントを参照してください。

-
diff --git a/publishing/ja/wcag/animation-from-interactions.html b/publishing/ja/wcag/animation-from-interactions.html index 78592a22..7b0599cb 100644 --- a/publishing/ja/wcag/animation-from-interactions.html +++ b/publishing/ja/wcag/animation-from-interactions.html @@ -4,6 +4,7 @@ インタラクションによるアニメーション +