You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>Assistive technologies need semantic information about the structures and expected behaviors of a document in order to convey appropriate information to persons with disabilities. This specification defines a <ahref="" class="specref">WAI-ARIA 1.1</a> [[!WAI-ARIA-1.1]] module of core <adata-lt="role">roles</a><!-- , <a data-lt="state">states</a> and <a data-lt="property">properties</a> Note, if we do include any states & properties in this module, edit this sentence! --> specific to web graphics. These semantics allow an author to express the logical structure of the graphic to assistive technologies in order improve accessibility of graphics. Assistive technologies could then enable semantic navigation and adapt styling and interactive features, to provide an optimal experience for the audience. These features complement the graphics and document structure elements defined by HTML [[HTML52]] and SVG [[SVG2]].</p>
172
+
<p>Assistive technologies need semantic information about the structures and expected behaviors of a document in order to convey appropriate information to persons with disabilities. This specification defines a <ahref="" class="specref">WAI-ARIA 1.1</a> [[WAI-ARIA-1.1]] module of core <adata-lt="role">roles</a><!-- , <a data-lt="state">states</a> and <a data-lt="property">properties</a> Note, if we do include any states & properties in this module, edit this sentence! --> specific to web graphics. These semantics allow an author to express the logical structure of the graphic to assistive technologies in order improve accessibility of graphics. Assistive technologies could then enable semantic navigation and adapt styling and interactive features, to provide an optimal experience for the audience. These features complement the graphics and document structure elements defined by HTML [[HTML52]] and SVG [[SVG2]].</p>
184
173
<p>This document is part of the <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> suite described in the <ahref="https://www.w3.org/WAI/intro/aria.php"><abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> Overview</a>.</p>
185
174
</section>
186
175
<sectionid="sotd">
@@ -197,7 +186,7 @@
197
186
<sectionclass="informative" id="introduction">
198
187
<h1>Introduction</h1>
199
188
<p><abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> is a technical specification that provides a framework to improve the accessibility and interoperability of web content and applications. It enables web browsers to map the accessibility semantics in web content to platform-specific accessibility APIs. This enables web content to be interoperable with platform assistive technologies, similar to native platform applications, without requiring authors to include platform dependencies.</p>
200
-
<p>This specification is a modular extension of <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> [[!WAI-ARIA-1.1]] designed to support graphics. The goals of this specification include:</p>
189
+
<p>This specification is a modular extension of <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> [[WAI-ARIA-1.1]] designed to support graphics. The goals of this specification include:</p>
201
190
<ul>
202
191
<li>Expanding WAI-ARIA to produce semantic extensions to support structured graphics such as charts, graphs, maps, technical drawings and scientific diagrams. It has applicability to both Scalable Vector Graphics as well as HTML 5 Canvas and graphics produced with CSS styling of HTML and other markup languages.</li>
203
192
<li>Align with a new governance model for modularization and extensions to <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr>.</li>
@@ -226,15 +215,15 @@ <h2>Target Audience</h2>
226
215
227
216
<sectionid="ua-support">
228
217
<h2>User Agent Support</h2>
229
-
<p>This module follows the general <ahref="https://www.w3.org/TR/wai-aria-1.1/#ua-support">User Agent support principles</a> defined in WAI-ARIA [[!WAI-ARIA-1.1]].
218
+
<p>This module follows the general <ahref="https://www.w3.org/TR/wai-aria-1.1/#ua-support">User Agent support principles</a> defined in WAI-ARIA [[WAI-ARIA-1.1]].
230
219
The roles defined here do not require any change in behavior by user agents other than in the information exposed to the <a>accessibility API</a>.
231
220
However, the semantics defined here provide the ability for user agents to enhance the general user interface presented to readers.
232
221
For example, a user agent may provide alternative keyboard navigation suitable to a graphical environment, or may allow users to extract a copy of a graphic from a larger document.</p>
233
222
</section>
234
223
235
224
<sectionid="co-evolution">
236
225
<h2>Co-Evolution of <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> and Host Languages</h2>
237
-
<p>The <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics module follows the model for <ahref="https://www.w3.org/TR/wai-aria-1.1/#co-evolution">co-evolution of <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> and host languages</a> defined in WAI-ARIA [[!WAI-ARIA-1.1]]. It is intended to augment semantics in supporting languages like HTML [[HTML52]], SVG [[SVG2]] and EPUB, or to be used as an accessibility enhancement technology in other markup-based languages that do not explicitly include support for ARIA.
226
+
<p>The <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics module follows the model for <ahref="https://www.w3.org/TR/wai-aria-1.1/#co-evolution">co-evolution of <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> and host languages</a> defined in WAI-ARIA [[WAI-ARIA-1.1]]. It is intended to augment semantics in supporting languages like HTML [[HTML52]], SVG [[SVG2]] and EPUB, or to be used as an accessibility enhancement technology in other markup-based languages that do not explicitly include support for ARIA.
238
227
WAI-ARIA <a>roles</a> clarify semantics to assistive technologies when authors create new types of objects, via style and script, or use markup languages which describe the visual appearance of a document rather than its meaning.</p>
239
228
<p>Although markup languages may provide some of these semantics natively, it is expected that there will be a persistent need for the semantics provided by the <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics module.
240
229
Some host languages exist to create semantics for features other than the user interface. For example, SVG expresses the semantics behind production of graphical objects, not of user interface components that those objects may represent. Host languages such as these might, by design, not provide native semantics that map to all of this specification's features. In these host languages, the <abbrtitle="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics module could be adopted as a long-term approach to add semantic information.</p>
@@ -255,7 +244,7 @@ <h3>Testing Practices and Tools</h3>
255
244
256
245
<sectionid="at_support">
257
246
<h2>Assistive Technologies</h2>
258
-
<p>Programmatic access to accessibility semantics is essential for assistive technologies. For more information, refer to the <ahref="https://www.w3.org/TR/wai-aria-1.1/#at_support">Assistive Technologies</a> section in WAI-ARIA [[!WAI-ARIA-1.1]].</p>
247
+
<p>Programmatic access to accessibility semantics is essential for assistive technologies. For more information, refer to the <ahref="https://www.w3.org/TR/wai-aria-1.1/#at_support">Assistive Technologies</a> section in WAI-ARIA [[WAI-ARIA-1.1]].</p>
259
248
<p>For the graphics roles in particular, two categories of assistive technology are particularly relevant, but have different needs:</p>
260
249
<ul>
261
250
<li>Text-based presentations, such as screen readers, braille displays, and text-only displays or printers. These technologies need to replace a complex graphic with semantic text descriptions, preserving any meaningful structure and relationships between components.
<p>The role descriptions suggest which features of an element with that role are considered semantically important and should be conveyed to the reader whenever possible.</p>
266
255
</section>
267
256
</section>
268
-
<sectionclass="normative">
257
+
<sectionclass="normative"id="conformance">
269
258
<h2>Conformance</h2>
270
-
<p>The main content of this specification is <a>normative</a> and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative" and their subsections, diagrams, examples, and notes are <a>informative</a> (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.</p>
259
+
<p>The main content of this specification is <aclass="termref">normative</a> and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative" and their subsections, diagrams, examples, and notes are <aclass="termref">informative</a> (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.</p>
271
260
<p>Normative sections provide requirements that <aclass="termref">user agents</a> must follow for an implementation to conform to this specification. The keywords <emclass="rfc2119">MUST</em>, <emclass="rfc2119">MUST NOT</em>, <emclass="rfc2119">REQUIRED</em>, <emclass="rfc2119">SHALL</em>, <emclass="rfc2119">SHALL NOT</em>, <emclass="rfc2119">SHOULD</em>, <emclass="rfc2119">RECOMMENDED</em>, <emclass="rfc2119">MAY</em>, and <emclass="rfc2119">OPTIONAL</em> in this document are to be interpreted as described in <cite><ahref="http://www.rfc-editor.org/rfc/rfc2119.txt">Keywords for use in RFCs to indicate requirement levels</a></cite> [[!RFC2119]]. RFC-2119 keywords are formatted in uppercase and contained in an element with <code>class="rfc2119"</code>. When the keywords shown above are used, but do not share this format, they do not convey formal information in the RFC 2119 sense, and are merely explanatory, i.e., informative. As much as possible, such usages are avoided in this specification.</p>
272
261
<p>Normative sections provide requirements that authors, user agents and assistive technologies MUST follow for an implementation to conform to this specification.</p>
273
262
<p>Non-normative (informative) sections provide information useful to understanding the specification. Such sections may contain examples of recommended practice, but it is not required to follow such recommendations in order to conform to this specification.</p>
0 commit comments