[html5] r7264 - [e] (0) Cleanup the dependencies section and related bits Affected topics: Canva [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Aug 23 17:42:20 PDT 2012
Author: ianh
Date: 2012-08-23 17:42:18 -0700 (Thu, 23 Aug 2012)
New Revision: 7264
Modified:
complete.html
index
source
Log:
[e] (0) Cleanup the dependencies section and related bits
Affected topics: Canvas, DOM APIs, HTML, Video Text Tracks, WebSocket API
Modified: complete.html
===================================================================
--- complete.html 2012-08-24 00:23:11 UTC (rev 7263)
+++ complete.html 2012-08-24 00:42:18 UTC (rev 7264)
@@ -3636,8 +3636,7 @@
documents<span class=impl> (relevant to authors and authoring tool
implementors)</span>.</p>
- <p><dfn id=conforming-documents>Conforming
- documents</dfn> are those that comply with all
+ <p><dfn id=conforming-documents>Conforming documents</dfn> are those that comply with all
the conformance criteria for documents. For readability, some of
these conformance requirements are phrased as conformance
requirements on authors; such requirements are implicitly
@@ -3790,7 +3789,6 @@
<p>The term "HTML validator" can be used to refer to a
conformance checker that itself conforms to the applicable
requirements of this specification.</p>
- <!--VERSION-->
<div class=note>
@@ -3841,9 +3839,8 @@
<dd>
<p>Authoring tools and markup generators must generate
- <a href=#conforming-documents>conforming
- documents</a>. Conformance criteria that apply to authors also
- apply to authoring tools, where appropriate.</p>
+ <a href=#conforming-documents>conforming documents</a>. Conformance criteria that apply
+ to authors also apply to authoring tools, where appropriate.</p>
<p>Authoring tools are exempt from the strict requirements of
using elements only for their specified purpose, but only to the
@@ -3943,7 +3940,107 @@
</dd>
+
+ <dt>URIs, IRIs, IDNA</dt>
+
+ <dd>
+
+ <p>Implementations must support the semantics of <a href=#url title=URL>URLs</a> defined in the URI and IRI specifications,
+ as well as the semantics of IDNA domain names defined in the
+ <cite>Internationalizing Domain Names in Applications
+ (IDNA)</cite> specification. <a href=#refsRFC3986>[RFC3986]</a>
+ <a href=#refsRFC3987>[RFC3987]</a> <a href=#refsRFC3490>[RFC3490]</a>
+
+ </dd>
+
+
+ <dt>Cookies</dt>
+
+ <dd>
+
+ <p>The following terms are defined in the Cookie specification: <a href=#refsCOOKIES>[COOKIES]</a></p>
+
+ <ul class=brief><li><dfn id=cookie-string>cookie-string</dfn>
+ <li><dfn id=receives-a-set-cookie-string>receives a set-cookie-string</dfn>
+ </ul></dd>
+
+
+ <dt>CORS</dt>
+
+ <dd>
+
+ <p>The following terms are defined in the CORS specification: <a href=#refsCORS>[CORS]</a></p>
+
+ <ul class=brief><li><dfn id=cross-origin-request>cross-origin request</dfn>
+ <li><dfn id=cross-origin-request-status>cross-origin request status</dfn>
+ <li><dfn id=custom-request-headers>custom request headers</dfn>
+ <li><dfn id=simple-cross-origin-request>simple cross-origin request</dfn>
+ <li><dfn id=redirect-steps>redirect steps</dfn>
+ <li><dfn id=credential-flag>credential flag</dfn>
+ <li><dfn id=resource-sharing-check>resource sharing check</dfn>
+ </ul></dd>
+
+
<!--TOPIC:DOM APIs-->
+
+ <dt>Web IDL</dt>
+
+ <dd>
+
+ <p>The IDL fragments in this specification must be interpreted as
+ required for conforming IDL fragments, as described in the Web IDL
+ specification. <a href=#refsWEBIDL>[WEBIDL]</a></p>
+
+ <p>The terms <dfn id=expose>expose</dfn>, <dfn id=supported-property-indices>supported property
+ indices</dfn>, <dfn id=determine-the-value-of-an-indexed-property>determine the value of an indexed
+ property</dfn>, <dfn id=support-named-properties>support named properties</dfn>,
+ <dfn id=supported-property-names>supported property names</dfn>, <dfn id=determine-the-value-of-a-named-property>determine the value of a
+ named property</dfn>, <dfn id=platform-array-objects>platform array objects</dfn>, and <dfn id=dfn-read-only-array title=dfn-read-only-array>read only</dfn> (when applied to
+ arrays) are used as defined in the Web IDL specification. The
+ algorithm to <dfn id=convert-a-domstring-to-a-sequence-of-unicode-characters>convert a DOMString to a sequence of Unicode
+ characters</dfn> is similarly that defined in the Web IDL
+ specification.</p>
+
+ <p>When this specification requires a user agent to <dfn id=create-a-date-object>create a
+ <code>Date</code> object</dfn> representing a particular time, the
+ milliseconds component of that time, if any, must be truncated to
+ an integer and the time value of the newly created
+ <code>Date</code> object must represent the time after that
+ truncation.</p>
+
+ <p class=example>For instance, given the time 23045 millionths
+ of a second after 01:00 UTC on January 1st 2000, i.e. the time
+ 2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
+ created representing that time would represent the same time as
+ that created representing the time 2000-01-01T00:00:00.023Z, 45
+ millionths earlier.</p>
+
+ </dd>
+
+
+ <dt>JavaScript</dt>
+
+ <dd>
+
+ <p>Some parts of the language described by this specification only
+ support JavaScript as the underlying scripting language. <a href=#refsECMA262>[ECMA262]</a></p>
+
+ <p class=note>The term "JavaScript" is used to refer to ECMA262,
+ rather than the official term ECMAScript, since the term
+ JavaScript is more widely known. Similarly, the <a href=#mime-type>MIME
+ type</a> used to refer to JavaScript in this specification is
+ <code title="">text/javascript</code>, since that is the most
+ commonly used type, <a href=#willful-violation title="willful violation">despite it
+ being an officially obsoleted type</a> according to RFC
+ 4329. <a href=#refsRFC4329>[RFC4329]</a></p>
+
+ <p>The term <dfn id=javascript-global-environment>JavaScript global environment</dfn> refers to the
+ <i title="">global environment</i> concept defined in the
+ ECMAScript specification.</p>
+
+ </dd>
+
+
<dt>DOM</dt>
<dd>
@@ -4086,58 +4183,7 @@
<li><dfn id=dom-outerhtml title=dom-outerHTML>outerHTML</dfn></li>
</ul></dd>
- <dt>File API</dt>
- <dd>
-
- <p>This specification uses the following interfaces defined in the
- File API specification: <a href=#refsFILEAPI>[FILEAPI]</a></p>
-
- <ul class=brief><li><dfn id=blob><code>Blob</code></dfn></li>
- <li><dfn id=file><code>File</code></dfn></li>
- <li><dfn id=filelist><code>FileList</code></dfn></li>
-
- </ul><p>It also uses the following interface defined in the File System
- API specification: <a href=#refsFILESYSTEMAPI>[FILESYSTEMAPI]</a></p>
-
- <ul class=brief><li><dfn id=filecallback><code>FileCallback</code></dfn></li>
-
- </ul></dd>
-
- <dt>Web IDL</dt>
-
- <dd>
-
- <p>The IDL fragments in this specification must be interpreted as
- required for conforming IDL fragments, as described in the Web IDL
- specification. <a href=#refsWEBIDL>[WEBIDL]</a></p>
-
- <p>The terms <dfn id=expose>expose</dfn>, <dfn id=supported-property-indices>supported property
- indices</dfn>, <dfn id=determine-the-value-of-an-indexed-property>determine the value of an indexed
- property</dfn>, <dfn id=support-named-properties>support named properties</dfn>,
- <dfn id=supported-property-names>supported property names</dfn>, <dfn id=determine-the-value-of-a-named-property>determine the value of a
- named property</dfn>, <dfn id=platform-array-objects>platform array objects</dfn>, and <dfn id=dfn-read-only-array title=dfn-read-only-array>read only</dfn> (when applied to
- arrays) are used as defined in the Web IDL specification. The
- algorithm to <dfn id=convert-a-domstring-to-a-sequence-of-unicode-characters>convert a DOMString to a sequence of Unicode
- characters</dfn> is similarly that defined in the Web IDL
- specification.</p>
-
- <p>When this specification requires a user agent to <dfn id=create-a-date-object>create a
- <code>Date</code> object</dfn> representing a particular time, the
- milliseconds component of that time, if any, must be truncated to
- an integer and the time value of the newly created
- <code>Date</code> object must represent the time after that
- truncation.</p>
-
- <p class=example>For instance, given the time 23045 millionths
- of a second after 01:00 UTC on January 1st 2000, i.e. the time
- 2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
- created representing that time would represent the same time as
- that created representing the time 2000-01-01T00:00:00.023Z, 45
- millionths earlier.</p>
-
- </dd>
-
<dt>Typed Arrays</dt>
<dd>
@@ -4151,102 +4197,51 @@
</dd>
- <dt>JavaScript</dt>
+ <dt>File API</dt>
+
<dd>
- <p>Some parts of the language described by this specification only
- support JavaScript as the underlying scripting language. <a href=#refsECMA262>[ECMA262]</a></p>
+ <p>This specification uses the following interfaces defined in the
+ File API specification: <a href=#refsFILEAPI>[FILEAPI]</a></p>
- <p class=note>The term "JavaScript" is used to refer to ECMA262,
- rather than the official term ECMAScript, since the term
- JavaScript is more widely known. Similarly, the <a href=#mime-type>MIME
- type</a> used to refer to JavaScript in this specification is
- <code title="">text/javascript</code>, since that is the most
- commonly used type, <a href=#willful-violation title="willful violation">despite it
- being an officially obsoleted type</a> according to RFC
- 4329. <a href=#refsRFC4329>[RFC4329]</a></p>
+ <ul class=brief><li><dfn id=blob><code>Blob</code></dfn></li>
+ <li><dfn id=file><code>File</code></dfn></li>
+ <li><dfn id=filelist><code>FileList</code></dfn></li>
- <p>The term <dfn id=javascript-global-environment>JavaScript global environment</dfn> refers to the
- <i title="">global environment</i> concept defined in the
- ECMAScript specification.</p>
+ </ul><p>It also uses the following interface defined in the File System
+ API specification: <a href=#refsFILESYSTEMAPI>[FILESYSTEMAPI]</a></p>
- </dd>
+ <ul class=brief><li><dfn id=filecallback><code>FileCallback</code></dfn></li>
-<!--TOPIC:HTML-->
+ </ul></dd>
- <dt>Media Queries</dt>
+ <dt>XMLHttpRequest</dt>
+
<dd>
- <p>Implementations must support the Media Queries language. <a href=#refsMQ>[MQ]</a></p>
+ <p>This specification references the XMLHttpRequest specification
+ to define how the two specifications interact. The terms
+ <dfn id=document-response-entity-body>document response entity body</dfn>,
+ <dfn id=xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</dfn>, and
+ <dfn id=xmlhttprequest-origin><code>XMLHttpRequest</code> origin</dfn> are defined in that
+ specification. <a href=#refsXHR>[XHR]</a></p>
</dd>
-<!--TOPIC:Video Text Tracks-->
- <dt>WebVTT</dt>
-
- <dd>
-
- <p>Implementations may support <dfn id=webvtt>WebVTT</dfn> as a text track
- format for subtitles, captions, chapter titles, metadata, etc, for
- media resources. <a href=#refsWEBVTT>[WEBVTT]</a></p>
-
- <p>The following terms, used in this specification, are defined in
- the WebVTT specification:</p>
-
- <ul class=brief><li><dfn id=webvtt-file>WebVTT file</dfn>
- <li><dfn id=webvtt-file-using-cue-text>WebVTT file using cue text</dfn>
- <li><dfn id=webvtt-file-using-chapter-title-text>WebVTT file using chapter title text</dfn>
- <li><dfn id=webvtt-file-using-only-nested-cues>WebVTT file using only nested cues</dfn>
- <li><dfn id=webvtt-parser>WebVTT parser</dfn>
- <li><dfn id=webvtt-cue-settings>WebVTT cue settings</dfn> and how to <dfn id=parse-the-webvtt-settings>parse the WebVTT settings</dfn>
- <li>The <dfn id=rules-for-updating-the-display-of-webvtt-text-tracks>rules for updating the display of WebVTT text tracks</dfn>
- <li>The <dfn id=webvtt-cue-text-dom-construction-rules>WebVTT cue text DOM construction rules</dfn>
- <li>The <dfn id=webvtt-cue-text-rendering-rules>WebVTT cue text rendering rules</dfn>
- <li>The <dfn id=webvtt-cue-text-parsing-rules>WebVTT cue text parsing rules</dfn>
- </ul></dd>
-
<!--TOPIC:HTML-->
- <dt>URIs, IRIs, IDNA</dt>
+ <dt>Media Queries</dt>
<dd>
- <p>Implementations must support the semantics of <a href=#url title=URL>URLs</a> defined in the URI and IRI specifications,
- as well as the semantics of IDNA domain names defined in the
- <cite>Internationalizing Domain Names in Applications
- (IDNA)</cite> specification. <a href=#refsRFC3986>[RFC3986]</a>
- <a href=#refsRFC3987>[RFC3987]</a> <a href=#refsRFC3490>[RFC3490]</a>
+ <p>Implementations must support the Media Queries language. <a href=#refsMQ>[MQ]</a></p>
</dd>
- <dt>Cookies</dt>
- <dd>
-
- <p>The following terms are defined in the Cookie specification: <a href=#refsCOOKIES>[COOKIES]</a></p>
-
- <ul class=brief><li><dfn id=cookie-string>cookie-string</dfn>
- <li><dfn id=receives-a-set-cookie-string>receives a set-cookie-string</dfn>
- </ul></dd>
-
- <dt>CORS</dt>
-
- <dd>
-
- <p>The following terms are defined in the CORS specification: <a href=#refsCORS>[CORS]</a></p>
-
- <ul class=brief><li><dfn id=cross-origin-request>cross-origin request</dfn>
- <li><dfn id=cross-origin-request-status>cross-origin request status</dfn>
- <li><dfn id=custom-request-headers>custom request headers</dfn>
- <li><dfn id=simple-cross-origin-request>simple cross-origin request</dfn>
- <li><dfn id=redirect-steps>redirect steps</dfn>
- <li><dfn id=credential-flag>credential flag</dfn>
- <li><dfn id=resource-sharing-check>resource sharing check</dfn>
- </ul></dd>
-
<dt>CSS modules</dt>
<dd>
@@ -4305,6 +4300,47 @@
</dd>
+<!--TOPIC:Canvas-->
+
+ <dt>SVG</dt>
+
+ <dd>
+
+ <p>The following interface is defined in the SVG specification: <a href=#refsSVG>[SVG]</a></p>
+
+ <ul class=brief><li><dfn id=svgmatrix><code>SVGMatrix</code></dfn>
+ </ul><!--TOPIC:HTML--><!-- mention that the parser supports it? --></dd>
+
+
+ <!-- mention that the parser supports mathml? -->
+
+
+<!--TOPIC:Video Text Tracks-->
+
+ <dt>WebVTT</dt>
+
+ <dd>
+
+ <p>Implementations may support <dfn id=webvtt>WebVTT</dfn> as a text track
+ format for subtitles, captions, chapter titles, metadata, etc, for
+ media resources. <a href=#refsWEBVTT>[WEBVTT]</a></p>
+
+ <p>The following terms, used in this specification, are defined in
+ the WebVTT specification:</p>
+
+ <ul class=brief><li><dfn id=webvtt-file>WebVTT file</dfn>
+ <li><dfn id=webvtt-file-using-cue-text>WebVTT file using cue text</dfn>
+ <li><dfn id=webvtt-file-using-chapter-title-text>WebVTT file using chapter title text</dfn>
+ <li><dfn id=webvtt-file-using-only-nested-cues>WebVTT file using only nested cues</dfn>
+ <li><dfn id=webvtt-parser>WebVTT parser</dfn>
+ <li><dfn id=webvtt-cue-settings>WebVTT cue settings</dfn> and how to <dfn id=parse-the-webvtt-settings>parse the WebVTT settings</dfn>
+ <li>The <dfn id=rules-for-updating-the-display-of-webvtt-text-tracks>rules for updating the display of WebVTT text tracks</dfn>
+ <li>The <dfn id=webvtt-cue-text-dom-construction-rules>WebVTT cue text DOM construction rules</dfn>
+ <li>The <dfn id=webvtt-cue-text-rendering-rules>WebVTT cue text rendering rules</dfn>
+ <li>The <dfn id=webvtt-cue-text-parsing-rules>WebVTT cue text parsing rules</dfn>
+ </ul></dd>
+
+
<!--TOPIC:WebSocket API-->
<dt>The WebSocket protocol</dt>
@@ -4337,26 +4373,12 @@
</dd>
-<!--TOPIC:Canvas-->
-
- <dt>SVG</dt>
-
- <dd>
-
- <p>The following interface is defined in the SVG specification: <a href=#refsSVG>[SVG]</a></p>
-
- <ul class=brief><li><dfn id=svgmatrix><code>SVGMatrix</code></dfn>
- </ul></dd>
-
-<!--TOPIC:HTML-->
-
-
<dt>ARIA</dt>
<dd>
<p>The terms <dfn id=strong-native-semantics>strong native semantics</dfn> is used as defined
- in the ARIA specification. The term <dfn id=default-implied-aria-semantics>default implied ARIA
+ in the ARIA specification. The term <dfn id=default-implicit-aria-semantics>default implicit ARIA
semantics</dfn> has the same meaning as the term <i>implicit
WAI-ARIA semantics</i> as used in the ARIA specification. <a href=#refsARIA>[ARIA]</a></p>
@@ -4368,19 +4390,6 @@
</dd>
- <dt>XMLHttpRequest</dt>
-
- <dd>
-
- <p>This specification references the XMLHttpRequest specification
- to define how the two specifications interact. The terms
- <dfn id=document-response-entity-body>document response entity body</dfn>,
- <dfn id=xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</dfn>, and
- <dfn id=xmlhttprequest-origin><code>XMLHttpRequest</code> origin</dfn> are defined in that
- specification. <a href=#refsXHR>[XHR]</a></p>
-
- </dd>
-
</dl><p>This specification does not <em>require</em> support of any
particular network protocol, style sheet language, scripting
language, or any of the DOM specifications beyond those required in
@@ -13306,34 +13315,30 @@
and <code title=attr-aria-*>aria-*</code> attributes on <a href=#html-elements>HTML
elements</a>, in accordance with the requirements described in
the ARIA specifications, except where these conflict with the
- <a href=#strong-native-semantics>strong native semantics</a>
-<!--FORK--><!--bug 11557-->
- or are equal to the <a href=#default-implied-aria-semantics>default implied ARIA semantics</a>
-<!--FORK--><!--bug 11557-->
- described below. These exceptions are intended to prevent authors
- from making assistive technology products report nonsensical states
- that do not represent the actual state of the document. <a href=#refsARIA>[ARIA]</a></p>
+ <a href=#strong-native-semantics>strong native semantics</a> or are equal to the
+ <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> described below. These
+ exceptions are intended to prevent authors from making assistive
+ technology products report nonsensical states that do not represent
+ the actual state of the document. <a href=#refsARIA>[ARIA]</a></p>
-<!--FORK--><!--bug 11557-->
<p>Authors must not set the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
conflicts with the semantics described in the following table,
except that the <code title=attr-aria-role-presentation>presentation</code> role may
always be used. Authors must not set the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes to values that match
- the <span>default implicit ARIA semantics</span> defined in the
+ the <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined in the
following two tables.</p>
-<!--FORK--><!--bug 11557-->
<div class=impl>
<p>User agents are required to implement ARIA semantics on all
<a href=#html-elements>HTML elements</a>, as defined in the ARIA specifications.
- The <span>implicit ARIA semantics</span> defined below must be
- recognized by implementations for the purposes of ARIA processing.
- <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
+ The <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below must
+ be recognized by implementations for the purposes of ARIA
+ processing. <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
<p class=note>The ARIA attributes defined in the ARIA
specifications, and the <a href=#strong-native-semantics>strong native semantics</a> and
- <span>default implicit ARIA semantics</span> defined below, do not
+ <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below, do not
have any effect on CSS pseudo-class matching, user interface
modalities that don't use assistive technologies, or the default
actions of user interaction events as described in this
@@ -13345,8 +13350,8 @@
</div>
<p>The following table defines the <a href=#strong-native-semantics>strong native
- semantics</a> and corresponding <span>default implicit ARIA
- semantics</span> that apply to <a href=#html-elements>HTML elements</a>. Each
+ semantics</a> and corresponding <a href=#default-implicit-aria-semantics>default implicit ARIA
+ semantics</a> that apply to <a href=#html-elements>HTML elements</a>. Each
language feature (element or attribute) in a cell in the first
column implies the ARIA semantics (role, states, and/or properties)
given in the cell in the second column of the same row. <span class=impl>When multiple rows apply to an element, the role from
@@ -13354,7 +13359,7 @@
properties from all the rows must be combined.</span></p>
<table id=table-aria-strong><thead><tr><th>Language feature
- <th><a href=#strong-native-semantics>Strong native semantics</a> and <a href=#default-implied-aria-semantics>default implied ARIA semantics</a>
+ <th><a href=#strong-native-semantics>Strong native semantics</a> and <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a>
<tbody><tr><td><code><a href=#the-area-element>area</a></code> element that creates a <a href=#hyperlink>hyperlink</a>
<td><code title=attr-aria-role-link>link</code> role
@@ -13550,7 +13555,7 @@
</table><p>Some <a href=#html-elements>HTML elements</a> have native semantics that can be
overridden. The following table lists these elements and their
- <span>default implicit ARIA semantics</span>, along with the
+ <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a>, along with the
restrictions that apply to those elements. Each language feature
(element or attribute) in a cell in the first column implies, unless
otherwise overridden, the ARIA semantic (role, state, or property)
@@ -13561,7 +13566,7 @@
regardless of the restrictions below.</p>
<table id=table-aria-weak><thead><tr><th>Language feature
- <th>Default implied ARIA semantic
+ <th>Default implicit ARIA semantic
<th>Restrictions
<tbody><tr><td><code><a href=#the-a-element>a</a></code> element that creates a <a href=#hyperlink>hyperlink</a>
@@ -13719,14 +13724,13 @@
</table><p>The entry "<dfn id=concept-role-none title=concept-role-none>no role</dfn>", when
used as a <a href=#strong-native-semantics title="strong native semantics">strong native
semantic</a>, means that no role other than <code title=attr-aria-role-presentation>presentation</code> can be used.
- When used as a <a href=#default-implied-aria-semantics title="default implied ARIA semantics">default
- implied ARIA semantic</a>, it means the user agent has no default
+ When used as a <a href=#default-implicit-aria-semantics title="default implicit ARIA semantics">default
+ implicit ARIA semantic</a>, it means the user agent has no default
mapping to ARIA roles. (However, it probably will have its own
mappings to the accessibility layer.)</p>
<div class=impl>
-
<p>Conformance checkers are encouraged to phrase errors such that
authors are encouraged to use more appropriate elements rather than
remove accessibility annotations. For example, if an <code><a href=#the-a-element>a</a></code>
Modified: index
===================================================================
--- index 2012-08-24 00:23:11 UTC (rev 7263)
+++ index 2012-08-24 00:42:18 UTC (rev 7264)
@@ -3636,8 +3636,7 @@
documents<span class=impl> (relevant to authors and authoring tool
implementors)</span>.</p>
- <p><dfn id=conforming-documents>Conforming
- documents</dfn> are those that comply with all
+ <p><dfn id=conforming-documents>Conforming documents</dfn> are those that comply with all
the conformance criteria for documents. For readability, some of
these conformance requirements are phrased as conformance
requirements on authors; such requirements are implicitly
@@ -3790,7 +3789,6 @@
<p>The term "HTML validator" can be used to refer to a
conformance checker that itself conforms to the applicable
requirements of this specification.</p>
- <!--VERSION-->
<div class=note>
@@ -3841,9 +3839,8 @@
<dd>
<p>Authoring tools and markup generators must generate
- <a href=#conforming-documents>conforming
- documents</a>. Conformance criteria that apply to authors also
- apply to authoring tools, where appropriate.</p>
+ <a href=#conforming-documents>conforming documents</a>. Conformance criteria that apply
+ to authors also apply to authoring tools, where appropriate.</p>
<p>Authoring tools are exempt from the strict requirements of
using elements only for their specified purpose, but only to the
@@ -3943,7 +3940,107 @@
</dd>
+
+ <dt>URIs, IRIs, IDNA</dt>
+
+ <dd>
+
+ <p>Implementations must support the semantics of <a href=#url title=URL>URLs</a> defined in the URI and IRI specifications,
+ as well as the semantics of IDNA domain names defined in the
+ <cite>Internationalizing Domain Names in Applications
+ (IDNA)</cite> specification. <a href=#refsRFC3986>[RFC3986]</a>
+ <a href=#refsRFC3987>[RFC3987]</a> <a href=#refsRFC3490>[RFC3490]</a>
+
+ </dd>
+
+
+ <dt>Cookies</dt>
+
+ <dd>
+
+ <p>The following terms are defined in the Cookie specification: <a href=#refsCOOKIES>[COOKIES]</a></p>
+
+ <ul class=brief><li><dfn id=cookie-string>cookie-string</dfn>
+ <li><dfn id=receives-a-set-cookie-string>receives a set-cookie-string</dfn>
+ </ul></dd>
+
+
+ <dt>CORS</dt>
+
+ <dd>
+
+ <p>The following terms are defined in the CORS specification: <a href=#refsCORS>[CORS]</a></p>
+
+ <ul class=brief><li><dfn id=cross-origin-request>cross-origin request</dfn>
+ <li><dfn id=cross-origin-request-status>cross-origin request status</dfn>
+ <li><dfn id=custom-request-headers>custom request headers</dfn>
+ <li><dfn id=simple-cross-origin-request>simple cross-origin request</dfn>
+ <li><dfn id=redirect-steps>redirect steps</dfn>
+ <li><dfn id=credential-flag>credential flag</dfn>
+ <li><dfn id=resource-sharing-check>resource sharing check</dfn>
+ </ul></dd>
+
+
<!--TOPIC:DOM APIs-->
+
+ <dt>Web IDL</dt>
+
+ <dd>
+
+ <p>The IDL fragments in this specification must be interpreted as
+ required for conforming IDL fragments, as described in the Web IDL
+ specification. <a href=#refsWEBIDL>[WEBIDL]</a></p>
+
+ <p>The terms <dfn id=expose>expose</dfn>, <dfn id=supported-property-indices>supported property
+ indices</dfn>, <dfn id=determine-the-value-of-an-indexed-property>determine the value of an indexed
+ property</dfn>, <dfn id=support-named-properties>support named properties</dfn>,
+ <dfn id=supported-property-names>supported property names</dfn>, <dfn id=determine-the-value-of-a-named-property>determine the value of a
+ named property</dfn>, <dfn id=platform-array-objects>platform array objects</dfn>, and <dfn id=dfn-read-only-array title=dfn-read-only-array>read only</dfn> (when applied to
+ arrays) are used as defined in the Web IDL specification. The
+ algorithm to <dfn id=convert-a-domstring-to-a-sequence-of-unicode-characters>convert a DOMString to a sequence of Unicode
+ characters</dfn> is similarly that defined in the Web IDL
+ specification.</p>
+
+ <p>When this specification requires a user agent to <dfn id=create-a-date-object>create a
+ <code>Date</code> object</dfn> representing a particular time, the
+ milliseconds component of that time, if any, must be truncated to
+ an integer and the time value of the newly created
+ <code>Date</code> object must represent the time after that
+ truncation.</p>
+
+ <p class=example>For instance, given the time 23045 millionths
+ of a second after 01:00 UTC on January 1st 2000, i.e. the time
+ 2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
+ created representing that time would represent the same time as
+ that created representing the time 2000-01-01T00:00:00.023Z, 45
+ millionths earlier.</p>
+
+ </dd>
+
+
+ <dt>JavaScript</dt>
+
+ <dd>
+
+ <p>Some parts of the language described by this specification only
+ support JavaScript as the underlying scripting language. <a href=#refsECMA262>[ECMA262]</a></p>
+
+ <p class=note>The term "JavaScript" is used to refer to ECMA262,
+ rather than the official term ECMAScript, since the term
+ JavaScript is more widely known. Similarly, the <a href=#mime-type>MIME
+ type</a> used to refer to JavaScript in this specification is
+ <code title="">text/javascript</code>, since that is the most
+ commonly used type, <a href=#willful-violation title="willful violation">despite it
+ being an officially obsoleted type</a> according to RFC
+ 4329. <a href=#refsRFC4329>[RFC4329]</a></p>
+
+ <p>The term <dfn id=javascript-global-environment>JavaScript global environment</dfn> refers to the
+ <i title="">global environment</i> concept defined in the
+ ECMAScript specification.</p>
+
+ </dd>
+
+
<dt>DOM</dt>
<dd>
@@ -4086,58 +4183,7 @@
<li><dfn id=dom-outerhtml title=dom-outerHTML>outerHTML</dfn></li>
</ul></dd>
- <dt>File API</dt>
- <dd>
-
- <p>This specification uses the following interfaces defined in the
- File API specification: <a href=#refsFILEAPI>[FILEAPI]</a></p>
-
- <ul class=brief><li><dfn id=blob><code>Blob</code></dfn></li>
- <li><dfn id=file><code>File</code></dfn></li>
- <li><dfn id=filelist><code>FileList</code></dfn></li>
-
- </ul><p>It also uses the following interface defined in the File System
- API specification: <a href=#refsFILESYSTEMAPI>[FILESYSTEMAPI]</a></p>
-
- <ul class=brief><li><dfn id=filecallback><code>FileCallback</code></dfn></li>
-
- </ul></dd>
-
- <dt>Web IDL</dt>
-
- <dd>
-
- <p>The IDL fragments in this specification must be interpreted as
- required for conforming IDL fragments, as described in the Web IDL
- specification. <a href=#refsWEBIDL>[WEBIDL]</a></p>
-
- <p>The terms <dfn id=expose>expose</dfn>, <dfn id=supported-property-indices>supported property
- indices</dfn>, <dfn id=determine-the-value-of-an-indexed-property>determine the value of an indexed
- property</dfn>, <dfn id=support-named-properties>support named properties</dfn>,
- <dfn id=supported-property-names>supported property names</dfn>, <dfn id=determine-the-value-of-a-named-property>determine the value of a
- named property</dfn>, <dfn id=platform-array-objects>platform array objects</dfn>, and <dfn id=dfn-read-only-array title=dfn-read-only-array>read only</dfn> (when applied to
- arrays) are used as defined in the Web IDL specification. The
- algorithm to <dfn id=convert-a-domstring-to-a-sequence-of-unicode-characters>convert a DOMString to a sequence of Unicode
- characters</dfn> is similarly that defined in the Web IDL
- specification.</p>
-
- <p>When this specification requires a user agent to <dfn id=create-a-date-object>create a
- <code>Date</code> object</dfn> representing a particular time, the
- milliseconds component of that time, if any, must be truncated to
- an integer and the time value of the newly created
- <code>Date</code> object must represent the time after that
- truncation.</p>
-
- <p class=example>For instance, given the time 23045 millionths
- of a second after 01:00 UTC on January 1st 2000, i.e. the time
- 2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
- created representing that time would represent the same time as
- that created representing the time 2000-01-01T00:00:00.023Z, 45
- millionths earlier.</p>
-
- </dd>
-
<dt>Typed Arrays</dt>
<dd>
@@ -4151,102 +4197,51 @@
</dd>
- <dt>JavaScript</dt>
+ <dt>File API</dt>
+
<dd>
- <p>Some parts of the language described by this specification only
- support JavaScript as the underlying scripting language. <a href=#refsECMA262>[ECMA262]</a></p>
+ <p>This specification uses the following interfaces defined in the
+ File API specification: <a href=#refsFILEAPI>[FILEAPI]</a></p>
- <p class=note>The term "JavaScript" is used to refer to ECMA262,
- rather than the official term ECMAScript, since the term
- JavaScript is more widely known. Similarly, the <a href=#mime-type>MIME
- type</a> used to refer to JavaScript in this specification is
- <code title="">text/javascript</code>, since that is the most
- commonly used type, <a href=#willful-violation title="willful violation">despite it
- being an officially obsoleted type</a> according to RFC
- 4329. <a href=#refsRFC4329>[RFC4329]</a></p>
+ <ul class=brief><li><dfn id=blob><code>Blob</code></dfn></li>
+ <li><dfn id=file><code>File</code></dfn></li>
+ <li><dfn id=filelist><code>FileList</code></dfn></li>
- <p>The term <dfn id=javascript-global-environment>JavaScript global environment</dfn> refers to the
- <i title="">global environment</i> concept defined in the
- ECMAScript specification.</p>
+ </ul><p>It also uses the following interface defined in the File System
+ API specification: <a href=#refsFILESYSTEMAPI>[FILESYSTEMAPI]</a></p>
- </dd>
+ <ul class=brief><li><dfn id=filecallback><code>FileCallback</code></dfn></li>
-<!--TOPIC:HTML-->
+ </ul></dd>
- <dt>Media Queries</dt>
+ <dt>XMLHttpRequest</dt>
+
<dd>
- <p>Implementations must support the Media Queries language. <a href=#refsMQ>[MQ]</a></p>
+ <p>This specification references the XMLHttpRequest specification
+ to define how the two specifications interact. The terms
+ <dfn id=document-response-entity-body>document response entity body</dfn>,
+ <dfn id=xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</dfn>, and
+ <dfn id=xmlhttprequest-origin><code>XMLHttpRequest</code> origin</dfn> are defined in that
+ specification. <a href=#refsXHR>[XHR]</a></p>
</dd>
-<!--TOPIC:Video Text Tracks-->
- <dt>WebVTT</dt>
-
- <dd>
-
- <p>Implementations may support <dfn id=webvtt>WebVTT</dfn> as a text track
- format for subtitles, captions, chapter titles, metadata, etc, for
- media resources. <a href=#refsWEBVTT>[WEBVTT]</a></p>
-
- <p>The following terms, used in this specification, are defined in
- the WebVTT specification:</p>
-
- <ul class=brief><li><dfn id=webvtt-file>WebVTT file</dfn>
- <li><dfn id=webvtt-file-using-cue-text>WebVTT file using cue text</dfn>
- <li><dfn id=webvtt-file-using-chapter-title-text>WebVTT file using chapter title text</dfn>
- <li><dfn id=webvtt-file-using-only-nested-cues>WebVTT file using only nested cues</dfn>
- <li><dfn id=webvtt-parser>WebVTT parser</dfn>
- <li><dfn id=webvtt-cue-settings>WebVTT cue settings</dfn> and how to <dfn id=parse-the-webvtt-settings>parse the WebVTT settings</dfn>
- <li>The <dfn id=rules-for-updating-the-display-of-webvtt-text-tracks>rules for updating the display of WebVTT text tracks</dfn>
- <li>The <dfn id=webvtt-cue-text-dom-construction-rules>WebVTT cue text DOM construction rules</dfn>
- <li>The <dfn id=webvtt-cue-text-rendering-rules>WebVTT cue text rendering rules</dfn>
- <li>The <dfn id=webvtt-cue-text-parsing-rules>WebVTT cue text parsing rules</dfn>
- </ul></dd>
-
<!--TOPIC:HTML-->
- <dt>URIs, IRIs, IDNA</dt>
+ <dt>Media Queries</dt>
<dd>
- <p>Implementations must support the semantics of <a href=#url title=URL>URLs</a> defined in the URI and IRI specifications,
- as well as the semantics of IDNA domain names defined in the
- <cite>Internationalizing Domain Names in Applications
- (IDNA)</cite> specification. <a href=#refsRFC3986>[RFC3986]</a>
- <a href=#refsRFC3987>[RFC3987]</a> <a href=#refsRFC3490>[RFC3490]</a>
+ <p>Implementations must support the Media Queries language. <a href=#refsMQ>[MQ]</a></p>
</dd>
- <dt>Cookies</dt>
- <dd>
-
- <p>The following terms are defined in the Cookie specification: <a href=#refsCOOKIES>[COOKIES]</a></p>
-
- <ul class=brief><li><dfn id=cookie-string>cookie-string</dfn>
- <li><dfn id=receives-a-set-cookie-string>receives a set-cookie-string</dfn>
- </ul></dd>
-
- <dt>CORS</dt>
-
- <dd>
-
- <p>The following terms are defined in the CORS specification: <a href=#refsCORS>[CORS]</a></p>
-
- <ul class=brief><li><dfn id=cross-origin-request>cross-origin request</dfn>
- <li><dfn id=cross-origin-request-status>cross-origin request status</dfn>
- <li><dfn id=custom-request-headers>custom request headers</dfn>
- <li><dfn id=simple-cross-origin-request>simple cross-origin request</dfn>
- <li><dfn id=redirect-steps>redirect steps</dfn>
- <li><dfn id=credential-flag>credential flag</dfn>
- <li><dfn id=resource-sharing-check>resource sharing check</dfn>
- </ul></dd>
-
<dt>CSS modules</dt>
<dd>
@@ -4305,6 +4300,47 @@
</dd>
+<!--TOPIC:Canvas-->
+
+ <dt>SVG</dt>
+
+ <dd>
+
+ <p>The following interface is defined in the SVG specification: <a href=#refsSVG>[SVG]</a></p>
+
+ <ul class=brief><li><dfn id=svgmatrix><code>SVGMatrix</code></dfn>
+ </ul><!--TOPIC:HTML--><!-- mention that the parser supports it? --></dd>
+
+
+ <!-- mention that the parser supports mathml? -->
+
+
+<!--TOPIC:Video Text Tracks-->
+
+ <dt>WebVTT</dt>
+
+ <dd>
+
+ <p>Implementations may support <dfn id=webvtt>WebVTT</dfn> as a text track
+ format for subtitles, captions, chapter titles, metadata, etc, for
+ media resources. <a href=#refsWEBVTT>[WEBVTT]</a></p>
+
+ <p>The following terms, used in this specification, are defined in
+ the WebVTT specification:</p>
+
+ <ul class=brief><li><dfn id=webvtt-file>WebVTT file</dfn>
+ <li><dfn id=webvtt-file-using-cue-text>WebVTT file using cue text</dfn>
+ <li><dfn id=webvtt-file-using-chapter-title-text>WebVTT file using chapter title text</dfn>
+ <li><dfn id=webvtt-file-using-only-nested-cues>WebVTT file using only nested cues</dfn>
+ <li><dfn id=webvtt-parser>WebVTT parser</dfn>
+ <li><dfn id=webvtt-cue-settings>WebVTT cue settings</dfn> and how to <dfn id=parse-the-webvtt-settings>parse the WebVTT settings</dfn>
+ <li>The <dfn id=rules-for-updating-the-display-of-webvtt-text-tracks>rules for updating the display of WebVTT text tracks</dfn>
+ <li>The <dfn id=webvtt-cue-text-dom-construction-rules>WebVTT cue text DOM construction rules</dfn>
+ <li>The <dfn id=webvtt-cue-text-rendering-rules>WebVTT cue text rendering rules</dfn>
+ <li>The <dfn id=webvtt-cue-text-parsing-rules>WebVTT cue text parsing rules</dfn>
+ </ul></dd>
+
+
<!--TOPIC:WebSocket API-->
<dt>The WebSocket protocol</dt>
@@ -4337,26 +4373,12 @@
</dd>
-<!--TOPIC:Canvas-->
-
- <dt>SVG</dt>
-
- <dd>
-
- <p>The following interface is defined in the SVG specification: <a href=#refsSVG>[SVG]</a></p>
-
- <ul class=brief><li><dfn id=svgmatrix><code>SVGMatrix</code></dfn>
- </ul></dd>
-
-<!--TOPIC:HTML-->
-
-
<dt>ARIA</dt>
<dd>
<p>The terms <dfn id=strong-native-semantics>strong native semantics</dfn> is used as defined
- in the ARIA specification. The term <dfn id=default-implied-aria-semantics>default implied ARIA
+ in the ARIA specification. The term <dfn id=default-implicit-aria-semantics>default implicit ARIA
semantics</dfn> has the same meaning as the term <i>implicit
WAI-ARIA semantics</i> as used in the ARIA specification. <a href=#refsARIA>[ARIA]</a></p>
@@ -4368,19 +4390,6 @@
</dd>
- <dt>XMLHttpRequest</dt>
-
- <dd>
-
- <p>This specification references the XMLHttpRequest specification
- to define how the two specifications interact. The terms
- <dfn id=document-response-entity-body>document response entity body</dfn>,
- <dfn id=xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</dfn>, and
- <dfn id=xmlhttprequest-origin><code>XMLHttpRequest</code> origin</dfn> are defined in that
- specification. <a href=#refsXHR>[XHR]</a></p>
-
- </dd>
-
</dl><p>This specification does not <em>require</em> support of any
particular network protocol, style sheet language, scripting
language, or any of the DOM specifications beyond those required in
@@ -13306,34 +13315,30 @@
and <code title=attr-aria-*>aria-*</code> attributes on <a href=#html-elements>HTML
elements</a>, in accordance with the requirements described in
the ARIA specifications, except where these conflict with the
- <a href=#strong-native-semantics>strong native semantics</a>
-<!--FORK--><!--bug 11557-->
- or are equal to the <a href=#default-implied-aria-semantics>default implied ARIA semantics</a>
-<!--FORK--><!--bug 11557-->
- described below. These exceptions are intended to prevent authors
- from making assistive technology products report nonsensical states
- that do not represent the actual state of the document. <a href=#refsARIA>[ARIA]</a></p>
+ <a href=#strong-native-semantics>strong native semantics</a> or are equal to the
+ <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> described below. These
+ exceptions are intended to prevent authors from making assistive
+ technology products report nonsensical states that do not represent
+ the actual state of the document. <a href=#refsARIA>[ARIA]</a></p>
-<!--FORK--><!--bug 11557-->
<p>Authors must not set the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
conflicts with the semantics described in the following table,
except that the <code title=attr-aria-role-presentation>presentation</code> role may
always be used. Authors must not set the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes to values that match
- the <span>default implicit ARIA semantics</span> defined in the
+ the <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined in the
following two tables.</p>
-<!--FORK--><!--bug 11557-->
<div class=impl>
<p>User agents are required to implement ARIA semantics on all
<a href=#html-elements>HTML elements</a>, as defined in the ARIA specifications.
- The <span>implicit ARIA semantics</span> defined below must be
- recognized by implementations for the purposes of ARIA processing.
- <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
+ The <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below must
+ be recognized by implementations for the purposes of ARIA
+ processing. <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
<p class=note>The ARIA attributes defined in the ARIA
specifications, and the <a href=#strong-native-semantics>strong native semantics</a> and
- <span>default implicit ARIA semantics</span> defined below, do not
+ <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below, do not
have any effect on CSS pseudo-class matching, user interface
modalities that don't use assistive technologies, or the default
actions of user interaction events as described in this
@@ -13345,8 +13350,8 @@
</div>
<p>The following table defines the <a href=#strong-native-semantics>strong native
- semantics</a> and corresponding <span>default implicit ARIA
- semantics</span> that apply to <a href=#html-elements>HTML elements</a>. Each
+ semantics</a> and corresponding <a href=#default-implicit-aria-semantics>default implicit ARIA
+ semantics</a> that apply to <a href=#html-elements>HTML elements</a>. Each
language feature (element or attribute) in a cell in the first
column implies the ARIA semantics (role, states, and/or properties)
given in the cell in the second column of the same row. <span class=impl>When multiple rows apply to an element, the role from
@@ -13354,7 +13359,7 @@
properties from all the rows must be combined.</span></p>
<table id=table-aria-strong><thead><tr><th>Language feature
- <th><a href=#strong-native-semantics>Strong native semantics</a> and <a href=#default-implied-aria-semantics>default implied ARIA semantics</a>
+ <th><a href=#strong-native-semantics>Strong native semantics</a> and <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a>
<tbody><tr><td><code><a href=#the-area-element>area</a></code> element that creates a <a href=#hyperlink>hyperlink</a>
<td><code title=attr-aria-role-link>link</code> role
@@ -13550,7 +13555,7 @@
</table><p>Some <a href=#html-elements>HTML elements</a> have native semantics that can be
overridden. The following table lists these elements and their
- <span>default implicit ARIA semantics</span>, along with the
+ <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a>, along with the
restrictions that apply to those elements. Each language feature
(element or attribute) in a cell in the first column implies, unless
otherwise overridden, the ARIA semantic (role, state, or property)
@@ -13561,7 +13566,7 @@
regardless of the restrictions below.</p>
<table id=table-aria-weak><thead><tr><th>Language feature
- <th>Default implied ARIA semantic
+ <th>Default implicit ARIA semantic
<th>Restrictions
<tbody><tr><td><code><a href=#the-a-element>a</a></code> element that creates a <a href=#hyperlink>hyperlink</a>
@@ -13719,14 +13724,13 @@
</table><p>The entry "<dfn id=concept-role-none title=concept-role-none>no role</dfn>", when
used as a <a href=#strong-native-semantics title="strong native semantics">strong native
semantic</a>, means that no role other than <code title=attr-aria-role-presentation>presentation</code> can be used.
- When used as a <a href=#default-implied-aria-semantics title="default implied ARIA semantics">default
- implied ARIA semantic</a>, it means the user agent has no default
+ When used as a <a href=#default-implicit-aria-semantics title="default implicit ARIA semantics">default
+ implicit ARIA semantic</a>, it means the user agent has no default
mapping to ARIA roles. (However, it probably will have its own
mappings to the accessibility layer.)</p>
<div class=impl>
-
<p>Conformance checkers are encouraged to phrase errors such that
authors are encouraged to use more appropriate elements rather than
remove accessibility annotations. For example, if an <code><a href=#the-a-element>a</a></code>
Modified: source
===================================================================
--- source 2012-08-24 00:23:11 UTC (rev 7263)
+++ source 2012-08-24 00:42:18 UTC (rev 7264)
@@ -2536,11 +2536,7 @@
documents<span class="impl"> (relevant to authors and authoring tool
implementors)</span>.</p>
- <p><dfn>Conforming
-<!--END dev-html--><!--END complete--><!--CONFORMANCE--><!--VERSION-->
- HTML5
-<!--START dev-html--><!--START complete--><!--CONFORMANCE--><!--VERSION-->
- documents</dfn> are those that comply with all
+ <p><dfn>Conforming documents</dfn> are those that comply with all
the conformance criteria for documents. For readability, some of
these conformance requirements are phrased as conformance
requirements on authors; such requirements are implicitly
@@ -2695,15 +2691,9 @@
"MUST" requirement because it has been proven to be impossible. <a
href="#refsCOMPUTABLE">[COMPUTABLE]</a>)</p>
- <!--END dev-html--><!--END complete--><!--VERSION-->
- <p>The term "HTML5 validator" can be used to refer to a
- conformance checker that itself conforms to the applicable
- requirements of this specification.</p>
- <!--START dev-html--><!--START complete--><!--END w3c-html--><!--VERSION-->
<p>The term "HTML validator" can be used to refer to a
conformance checker that itself conforms to the applicable
requirements of this specification.</p>
- <!--START w3c-html--><!--VERSION-->
<div class="note">
@@ -2759,12 +2749,8 @@
<dd>
<p>Authoring tools and markup generators must generate
- <span>conforming
-<!--END dev-html--><!--END complete--><!--CONFORMANCE--><!--VERSION-->
- HTML5
-<!--START dev-html--><!--START complete--><!--CONFORMANCE--><!--VERSION-->
- documents</span>. Conformance criteria that apply to authors also
- apply to authoring tools, where appropriate.</p>
+ <span>conforming documents</span>. Conformance criteria that apply
+ to authors also apply to authoring tools, where appropriate.</p>
<p>Authoring tools are exempt from the strict requirements of
using elements only for their specified purpose, but only to the
@@ -2871,7 +2857,119 @@
</dd>
+
+ <dt>URIs, IRIs, IDNA</dt>
+
+ <dd>
+
+ <p>Implementations must support the semantics of <span
+ title="URL">URLs</span> defined in the URI and IRI specifications,
+ as well as the semantics of IDNA domain names defined in the
+ <cite>Internationalizing Domain Names in Applications
+ (IDNA)</cite> specification. <a href="#refsRFC3986">[RFC3986]</a>
+ <a href="#refsRFC3987">[RFC3987]</a> <a
+ href="#refsRFC3490">[RFC3490]</a>
+
+ </dd>
+
+
+ <dt>Cookies</dt>
+
+ <dd>
+
+ <p>The following terms are defined in the Cookie specification: <a
+ href="#refsCOOKIES">[COOKIES]</a></p>
+
+ <ul class="brief">
+ <li><dfn>cookie-string</dfn>
+ <li><dfn>receives a set-cookie-string</dfn>
+ </ul>
+
+ </dd>
+
+
+ <dt>CORS</dt>
+
+ <dd>
+
+ <p>The following terms are defined in the CORS specification: <a
+ href="#refsCORS">[CORS]</a></p>
+
+ <ul class="brief">
+ <li><dfn>cross-origin request</dfn>
+ <li><dfn>cross-origin request status</dfn>
+ <li><dfn>custom request headers</dfn>
+ <li><dfn>simple cross-origin request</dfn>
+ <li><dfn>redirect steps</dfn>
+ <li><dfn>credential flag</dfn>
+ <li><dfn>resource sharing check</dfn>
+ </ul>
+
+ </dd>
+
+
<!--TOPIC:DOM APIs-->
+
+ <dt>Web IDL</dt>
+
+ <dd>
+
+ <p>The IDL fragments in this specification must be interpreted as
+ required for conforming IDL fragments, as described in the Web IDL
+ specification. <a href="#refsWEBIDL">[WEBIDL]</a></p>
+
+ <p>The terms <dfn>expose</dfn>, <dfn>supported property
+ indices</dfn>, <dfn>determine the value of an indexed
+ property</dfn>, <dfn>support named properties</dfn>,
+ <dfn>supported property names</dfn>, <dfn>determine the value of a
+ named property</dfn>, <dfn>platform array objects</dfn>, and <dfn
+ title="dfn-read-only-array">read only</dfn> (when applied to
+ arrays) are used as defined in the Web IDL specification. The
+ algorithm to <dfn>convert a DOMString to a sequence of Unicode
+ characters</dfn> is similarly that defined in the Web IDL
+ specification.</p>
+
+ <p>When this specification requires a user agent to <dfn>create a
+ <code>Date</code> object</dfn> representing a particular time, the
+ milliseconds component of that time, if any, must be truncated to
+ an integer and the time value of the newly created
+ <code>Date</code> object must represent the time after that
+ truncation.</p>
+
+ <p class="example">For instance, given the time 23045 millionths
+ of a second after 01:00 UTC on January 1st 2000, i.e. the time
+ 2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
+ created representing that time would represent the same time as
+ that created representing the time 2000-01-01T00:00:00.023Z, 45
+ millionths earlier.</p>
+
+ </dd>
+
+
+ <dt>JavaScript</dt>
+
+ <dd>
+
+ <p>Some parts of the language described by this specification only
+ support JavaScript as the underlying scripting language. <a
+ href="#refsECMA262">[ECMA262]</a></p>
+
+ <p class="note">The term "JavaScript" is used to refer to ECMA262,
+ rather than the official term ECMAScript, since the term
+ JavaScript is more widely known. Similarly, the <span>MIME
+ type</span> used to refer to JavaScript in this specification is
+ <code title="">text/javascript</code>, since that is the most
+ commonly used type, <span title="willful violation">despite it
+ being an officially obsoleted type</span> according to RFC
+ 4329. <a href="#refsRFC4329">[RFC4329]</a></p>
+
+ <p>The term <dfn>JavaScript global environment</dfn> refers to the
+ <i title="">global environment</i> concept defined in the
+ ECMAScript specification.</p>
+
+ </dd>
+
+
<dt>DOM</dt>
<dd>
@@ -3034,6 +3132,21 @@
</dd>
+
+ <dt>Typed Arrays</dt>
+
+ <dd>
+
+ <p>The <dfn>ArrayBuffer</dfn> and <dfn>ArrayBufferView</dfn>
+ interfaces and underlying concepts from the Typed Array
+ Specification are used for several features in this specification.
+ The <dfn>Uint8ClampedArray</dfn> interface type is specifically
+ used in the definition of the <code>canvas</code> element's 2D
+ API. <a href="#refsTYPEDARRAY">[TYPEDARRAY]</a></p>
+
+ </dd>
+
+
<dt>File API</dt>
<dd>
@@ -3061,77 +3174,21 @@
</dd>
- <dt>Web IDL</dt>
- <dd>
+ <dt>XMLHttpRequest</dt>
- <p>The IDL fragments in this specification must be interpreted as
- required for conforming IDL fragments, as described in the Web IDL
- specification. <a href="#refsWEBIDL">[WEBIDL]</a></p>
-
- <p>The terms <dfn>expose</dfn>, <dfn>supported property
- indices</dfn>, <dfn>determine the value of an indexed
- property</dfn>, <dfn>support named properties</dfn>,
- <dfn>supported property names</dfn>, <dfn>determine the value of a
- named property</dfn>, <dfn>platform array objects</dfn>, and <dfn
- title="dfn-read-only-array">read only</dfn> (when applied to
- arrays) are used as defined in the Web IDL specification. The
- algorithm to <dfn>convert a DOMString to a sequence of Unicode
- characters</dfn> is similarly that defined in the Web IDL
- specification.</p>
-
- <p>When this specification requires a user agent to <dfn>create a
- <code>Date</code> object</dfn> representing a particular time, the
- milliseconds component of that time, if any, must be truncated to
- an integer and the time value of the newly created
- <code>Date</code> object must represent the time after that
- truncation.</p>
-
- <p class="example">For instance, given the time 23045 millionths
- of a second after 01:00 UTC on January 1st 2000, i.e. the time
- 2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
- created representing that time would represent the same time as
- that created representing the time 2000-01-01T00:00:00.023Z, 45
- millionths earlier.</p>
-
- </dd>
-
- <dt>Typed Arrays</dt>
-
<dd>
- <p>The <dfn>ArrayBuffer</dfn> and <dfn>ArrayBufferView</dfn>
- interfaces and underlying concepts from the Typed Array
- Specification are used for several features in this specification.
- The <dfn>Uint8ClampedArray</dfn> interface type is specifically
- used in the definition of the <code>canvas</code> element's 2D
- API. <a href="#refsTYPEDARRAY">[TYPEDARRAY]</a></p>
+ <p>This specification references the XMLHttpRequest specification
+ to define how the two specifications interact. The terms
+ <dfn>document response entity body</dfn>,
+ <dfn><code>XMLHttpRequest</code> base URL</dfn>, and
+ <dfn><code>XMLHttpRequest</code> origin</dfn> are defined in that
+ specification. <a href="#refsXHR">[XHR]</a></p>
</dd>
- <dt>JavaScript</dt>
- <dd>
-
- <p>Some parts of the language described by this specification only
- support JavaScript as the underlying scripting language. <a
- href="#refsECMA262">[ECMA262]</a></p>
-
- <p class="note">The term "JavaScript" is used to refer to ECMA262,
- rather than the official term ECMAScript, since the term
- JavaScript is more widely known. Similarly, the <span>MIME
- type</span> used to refer to JavaScript in this specification is
- <code title="">text/javascript</code>, since that is the most
- commonly used type, <span title="willful violation">despite it
- being an officially obsoleted type</span> according to RFC
- 4329. <a href="#refsRFC4329">[RFC4329]</a></p>
-
- <p>The term <dfn>JavaScript global environment</dfn> refers to the
- <i title="">global environment</i> concept defined in the
- ECMAScript specification.</p>
-
- </dd>
-
<!--TOPIC:HTML-->
<dt>Media Queries</dt>
@@ -3143,83 +3200,7 @@
</dd>
-<!--TOPIC:Video Text Tracks-->
- <dt>WebVTT</dt>
-
- <dd>
-
- <p>Implementations may support <dfn>WebVTT</dfn> as a text track
- format for subtitles, captions, chapter titles, metadata, etc, for
- media resources. <a href="#refsWEBVTT">[WEBVTT]</a></p>
-
- <p>The following terms, used in this specification, are defined in
- the WebVTT specification:</p>
-
- <ul class="brief">
- <li><dfn>WebVTT file</dfn>
- <li><dfn>WebVTT file using cue text</dfn>
- <li><dfn>WebVTT file using chapter title text</dfn>
- <li><dfn>WebVTT file using only nested cues</dfn>
- <li><dfn>WebVTT parser</dfn>
- <li><dfn>WebVTT cue settings</dfn> and how to <dfn>parse the WebVTT settings</dfn>
- <li>The <dfn>rules for updating the display of WebVTT text tracks</dfn>
- <li>The <dfn>WebVTT cue text DOM construction rules</dfn>
- <li>The <dfn>WebVTT cue text rendering rules</dfn>
- <li>The <dfn>WebVTT cue text parsing rules</dfn>
- </ul>
-
- </dd>
-
-<!--TOPIC:HTML-->
-
- <dt>URIs, IRIs, IDNA</dt>
-
- <dd>
-
- <p>Implementations must support the semantics of <span
- title="URL">URLs</span> defined in the URI and IRI specifications,
- as well as the semantics of IDNA domain names defined in the
- <cite>Internationalizing Domain Names in Applications
- (IDNA)</cite> specification. <a href="#refsRFC3986">[RFC3986]</a>
- <a href="#refsRFC3987">[RFC3987]</a> <a
- href="#refsRFC3490">[RFC3490]</a>
-
- </dd>
-
- <dt>Cookies</dt>
-
- <dd>
-
- <p>The following terms are defined in the Cookie specification: <a
- href="#refsCOOKIES">[COOKIES]</a></p>
-
- <ul class="brief">
- <li><dfn>cookie-string</dfn>
- <li><dfn>receives a set-cookie-string</dfn>
- </ul>
-
- </dd>
-
- <dt>CORS</dt>
-
- <dd>
-
- <p>The following terms are defined in the CORS specification: <a
- href="#refsCORS">[CORS]</a></p>
-
- <ul class="brief">
- <li><dfn>cross-origin request</dfn>
- <li><dfn>cross-origin request status</dfn>
- <li><dfn>custom request headers</dfn>
- <li><dfn>simple cross-origin request</dfn>
- <li><dfn>redirect steps</dfn>
- <li><dfn>credential flag</dfn>
- <li><dfn>resource sharing check</dfn>
- </ul>
-
- </dd>
-
<dt>CSS modules</dt>
<dd>
@@ -3288,7 +3269,59 @@
</dd>
-<!--END dev-html--><!--END w3c-html-->
+
+<!--TOPIC:Canvas-->
+
+ <dt>SVG</dt>
+
+ <dd>
+
+ <p>The following interface is defined in the SVG specification: <a
+ href="#refsSVG">[SVG]</a></p>
+
+ <ul class="brief">
+ <li><dfn><code>SVGMatrix</code></dfn>
+ </ul>
+
+<!--TOPIC:HTML-->
+
+ <!-- mention that the parser supports it? -->
+
+ </dd>
+
+
+ <!-- mention that the parser supports mathml? -->
+
+
+<!--TOPIC:Video Text Tracks-->
+
+ <dt>WebVTT</dt>
+
+ <dd>
+
+ <p>Implementations may support <dfn>WebVTT</dfn> as a text track
+ format for subtitles, captions, chapter titles, metadata, etc, for
+ media resources. <a href="#refsWEBVTT">[WEBVTT]</a></p>
+
+ <p>The following terms, used in this specification, are defined in
+ the WebVTT specification:</p>
+
+ <ul class="brief">
+ <li><dfn>WebVTT file</dfn>
+ <li><dfn>WebVTT file using cue text</dfn>
+ <li><dfn>WebVTT file using chapter title text</dfn>
+ <li><dfn>WebVTT file using only nested cues</dfn>
+ <li><dfn>WebVTT parser</dfn>
+ <li><dfn>WebVTT cue settings</dfn> and how to <dfn>parse the WebVTT settings</dfn>
+ <li>The <dfn>rules for updating the display of WebVTT text tracks</dfn>
+ <li>The <dfn>WebVTT cue text DOM construction rules</dfn>
+ <li>The <dfn>WebVTT cue text rendering rules</dfn>
+ <li>The <dfn>WebVTT cue text parsing rules</dfn>
+ </ul>
+
+ </dd>
+
+
<!--TOPIC:WebSocket API-->
<dt>The WebSocket protocol</dt>
@@ -3324,31 +3357,13 @@
</dd>
-<!--START dev-html--><!--START w3c-html-->
-<!--TOPIC:Canvas-->
- <dt>SVG</dt>
-
- <dd>
-
- <p>The following interface is defined in the SVG specification: <a
- href="#refsSVG">[SVG]</a></p>
-
- <ul class="brief">
- <li><dfn><code>SVGMatrix</code></dfn>
- </ul>
-
- </dd>
-
-<!--TOPIC:HTML-->
-
-
<dt>ARIA</dt>
<dd>
<p>The terms <dfn>strong native semantics</dfn> is used as defined
- in the ARIA specification. The term <dfn>default implied ARIA
+ in the ARIA specification. The term <dfn>default implicit ARIA
semantics</dfn> has the same meaning as the term <i>implicit
WAI-ARIA semantics</i> as used in the ARIA specification. <a
href="#refsARIA">[ARIA]</a></p>
@@ -3361,19 +3376,6 @@
</dd>
- <dt>XMLHttpRequest</dt>
-
- <dd>
-
- <p>This specification references the XMLHttpRequest specification
- to define how the two specifications interact. The terms
- <dfn>document response entity body</dfn>,
- <dfn><code>XMLHttpRequest</code> base URL</dfn>, and
- <dfn><code>XMLHttpRequest</code> origin</dfn> are defined in that
- specification. <a href="#refsXHR">[XHR]</a></p>
-
- </dd>
-
</dl>
<p>This specification does not <em>require</em> support of any
@@ -3391,8 +3393,8 @@
</div>
-<!--START dev-html-->
+<!--START dev-html-->
<!--FIXUP dev-html -1-->
<h4>Extensibility</h4>
<!--FIXUP dev-html +1-->
@@ -13914,16 +13916,12 @@
and <code title="attr-aria-*">aria-*</code> attributes on <span>HTML
elements</span>, in accordance with the requirements described in
the ARIA specifications, except where these conflict with the
- <span>strong native semantics</span>
-<!--END w3c-html--><!--FORK--><!--bug 11557-->
- or are equal to the <span>default implied ARIA semantics</span>
-<!--START w3c-html--><!--FORK--><!--bug 11557-->
- described below. These exceptions are intended to prevent authors
- from making assistive technology products report nonsensical states
- that do not represent the actual state of the document. <a
- href="#refsARIA">[ARIA]</a></p>
+ <span>strong native semantics</span> or are equal to the
+ <span>default implicit ARIA semantics</span> described below. These
+ exceptions are intended to prevent authors from making assistive
+ technology products report nonsensical states that do not represent
+ the actual state of the document. <a href="#refsARIA">[ARIA]</a></p>
-<!--END w3c-html--><!--FORK--><!--bug 11557-->
<p>Authors must not set the ARIA <code
title="attr-aria-role">role</code> and <code
title="attr-aria-*">aria-*</code> attributes in a manner that
@@ -13935,15 +13933,14 @@
title="attr-aria-*">aria-*</code> attributes to values that match
the <span>default implicit ARIA semantics</span> defined in the
following two tables.</p>
-<!--START w3c-html--><!--FORK--><!--bug 11557-->
<div class="impl">
<p>User agents are required to implement ARIA semantics on all
<span>HTML elements</span>, as defined in the ARIA specifications.
- The <span>implicit ARIA semantics</span> defined below must be
- recognized by implementations for the purposes of ARIA processing.
- <a href="#refsARIAIMPL">[ARIAIMPL]</a></p>
+ The <span>default implicit ARIA semantics</span> defined below must
+ be recognized by implementations for the purposes of ARIA
+ processing. <a href="#refsARIAIMPL">[ARIAIMPL]</a></p>
<p class="note">The ARIA attributes defined in the ARIA
specifications, and the <span>strong native semantics</span> and
@@ -13972,7 +13969,7 @@
<thead>
<tr>
<th>Language feature
- <th><span>Strong native semantics</span> and <span>default implied ARIA semantics</span>
+ <th><span>Strong native semantics</span> and <span>default implicit ARIA semantics</span>
<tbody>
@@ -14251,7 +14248,7 @@
<thead>
<tr>
<th>Language feature
- <th>Default implied ARIA semantic
+ <th>Default implicit ARIA semantic
<th>Restrictions
<tbody>
@@ -14446,24 +14443,13 @@
used as a <span title="strong native semantics">strong native
semantic</span>, means that no role other than <code
title="attr-aria-role-presentation">presentation</code> can be used.
- When used as a <span title="default implied ARIA semantics">default
- implied ARIA semantic</span>, it means the user agent has no default
+ When used as a <span title="default implicit ARIA semantics">default
+ implicit ARIA semantic</span>, it means the user agent has no default
mapping to ARIA roles. (However, it probably will have its own
mappings to the accessibility layer.)</p>
<div class="impl">
-<!--END dev-html--><!--END complete--><!-- EDITORIAL: this paragraph is redundant with WAI-ARIA and doesn't really make any sense anyway; see bug 9437 --><!--FORK-->
- <p>The WAI-ARIA specification neither requires or forbids user
- agents from enhancing native presentation and interaction behaviors
- on the basis of WAI- ARIA markup. Even mainstream user agents might
- choose to expose metadata or navigational features directly or via
- user-installed extensions; for example, exposing required form
- fields or landmark navigation. User agents are encouraged to
- maximize their usefulness to users, including users without
- disabilities.</p>
-<!--START dev-html--><!--START complete--><!-- EDITORIAL --><!--FORK-->
-
<p>Conformance checkers are encouraged to phrase errors such that
authors are encouraged to use more appropriate elements rather than
remove accessibility annotations. For example, if an <code>a</code>
More information about the Commit-Watchers
mailing list