modified: aria/aria.html: First draft of clarification of application role.

mcking65 · mcking65 · commit 7593ebf363a1 · 2015-10-15T09:43:00.000-07:00
diff --git a/aria/aria.html b/aria/aria.html
@@ -790,9 +790,9 @@ <h2>Definition of Roles</h2>
 		<div class="role" id="application">
 			<rdef>application</rdef>
 			<div class="role-description">
-				<p>A region declared as a web application, as opposed to a web <rref>document</rref>.</p>
-				<p>When the user navigates an element assigned the role of <rref>application</rref>, <a>assistive technologies</a> that typically intercept standard keyboard events SHOULD switch to an application browsing mode, and pass keyboard events through to the web application. The intent is to hint to certain <a>assistive technologies</a> to switch from normal browsing mode into a mode more appropriate for interacting with a web application; some <a>user agents</a> have a browse navigation mode where keys, such as up and down arrows, are used to browse the document, and this native behavior prevents the use of these keys by a web application.</p>
-				<p class="note">Where appropriate, assistive technologies that typically intercept other standard device input events, such as touch screen input, could switch to an application browsing mode that passes some or all of those events through to the web application.</p>
+				<p>A <rref>section</rref> containing interactive elements that must receive user input, such as keyboard or gesture events.</p>
+				<p>Some <a>user agents</a> and <a>assistive technologies</a> have a browse mode where standard input events, such as up and down arrow key events, are used to browse the document. This browse mode behavior prevents a web application from receiving such keyboard and gesture  events and using them to provide interactive functionality. When the user navigates into a <rref>section</rref> with role <code>application</code>, <a>assistive technologies</a> that typically intercept standard input events SHOULD switch to a mode  that passes most or all standard input events through to the web application.</p>
+				<p>Since <a>assistive technologies</a> SHOULD pass standard input events through to any element with a WAI-ARIA <rref>widget</rref> role, authors SHOULD avoid putting elements with standard widget role into an <code>application</code> section.</p>
 				<!-- note: keep the following paragraphs synced with their counterparts in #document -->
 				<p>Authors SHOULD set the <a>role</a> of <code>application</code> on the <a>element</a> that encompasses the entire application. If the application role applies to the entire web page, authors SHOULD set the role of <code>application</code> on the root node for content, such as the <code>body</code> element in <abbr title="Hypertext Markup Language">HTML</abbr> or <code>svg</code> element in SVG.</p>
 				<p>For example, an email application has a document and an application in it. The author would want to use typical application navigation mode to cycle through the list of emails, and much of this navigation would be defined by the application author. However, when reading an email message the content will appear in a region with a <rref>document</rref> <a>role</a> in order to use browsing navigation.</p>
@@ -804,7 +804,7 @@ <h2>Definition of Roles</h2>
 					<!-- note: keep the previous paragraphs synced with their counterparts in #document -->
 				</ul>
 				<p>User agents SHOULD treat elements with the role of <code>application</code> as navigational <a>landmarks</a>.</p>
-				<p>Authors MAY use the <code>application</code> role on the <a>primary content element</a> of the host language (such as the <code>body</code> element in HTML) to define an entire page as an application. However, if the <a>primary content element</a> is defined as having a role of <code>application</code>, user agents MUST NOT use the element as a navigational landmark. If assistive technologies use an interaction mode that intercepts standard keyboard events, when encountering the <code>application</code> role, those assistive technologies SHOULD switch to an interaction mode that passes keyboard events through to the web application.</p>
+				<p>Authors MAY use the <code>application</code> role on the <a>primary content element</a> of the host language (such as the <code>body</code> element in HTML) to define an entire page as an application. However, if the <a>primary content element</a> is defined as having a role of <code>application</code>, user agents MUST NOT use the element as a navigational landmark. </p>
 				</div>
 			<table class="role-features">
 				<caption>Characteristics:</caption>

Original file line number	Original file line	Diff line number	Diff line change
`@@ -790,9 +790,9 @@ <h2>Definition of Roles</h2>`
`790`	`<div class="role" id="application">`	`790`	`<div class="role" id="application">`
`791`	`<rdef>application</rdef>`	`791`	`<rdef>application</rdef>`
`792`	`<div class="role-description">`	`792`	`<div class="role-description">`
`793`	`- <p>A region declared as a web application, as opposed to a web <rref>document</rref>.</p>`	`793`	`+ <p>A <rref>section</rref> containing interactive elements that must receive user input, such as keyboard or gesture events.</p>`
`794`	- <p>When the user navigates an element assigned the role of <rref>application</rref>, <a>assistive technologies</a> that typically intercept standard keyboard events SHOULD switch to an application browsing mode, and pass keyboard events through to the web application. The intent is to hint to certain <a>assistive technologies</a> to switch from normal browsing mode into a mode more appropriate for interacting with a web application; some <a>user agents</a> have a browse navigation mode where keys, such as up and down arrows, are used to browse the document, and this native behavior prevents the use of these keys by a web application.</p>	`794`	+ <p>Some <a>user agents</a> and <a>assistive technologies</a> have a browse mode where standard input events, such as up and down arrow key events, are used to browse the document. This browse mode behavior prevents a web application from receiving such keyboard and gesture events and using them to provide interactive functionality. When the user navigates into a <rref>section</rref> with role <code>application</code>, <a>assistive technologies</a> that typically intercept standard input events SHOULD switch to a mode that passes most or all standard input events through to the web application.</p>
`795`	`- <p class="note">Where appropriate, assistive technologies that typically intercept other standard device input events, such as touch screen input, could switch to an application browsing mode that passes some or all of those events through to the web application.</p>`	`795`	`+ <p>Since <a>assistive technologies</a> SHOULD pass standard input events through to any element with a WAI-ARIA <rref>widget</rref> role, authors SHOULD avoid putting elements with standard widget role into an <code>application</code> section.</p>`
`796`	`<!-- note: keep the following paragraphs synced with their counterparts in #document -->`	`796`	`<!-- note: keep the following paragraphs synced with their counterparts in #document -->`
`797`	`<p>Authors SHOULD set the <a>role</a> of <code>application</code> on the <a>element</a> that encompasses the entire application. If the application role applies to the entire web page, authors SHOULD set the role of <code>application</code> on the root node for content, such as the <code>body</code> element in <abbr title="Hypertext Markup Language">HTML</abbr> or <code>svg</code> element in SVG.</p>`	`797`	`<p>Authors SHOULD set the <a>role</a> of <code>application</code> on the <a>element</a> that encompasses the entire application. If the application role applies to the entire web page, authors SHOULD set the role of <code>application</code> on the root node for content, such as the <code>body</code> element in <abbr title="Hypertext Markup Language">HTML</abbr> or <code>svg</code> element in SVG.</p>`
`798`	`<p>For example, an email application has a document and an application in it. The author would want to use typical application navigation mode to cycle through the list of emails, and much of this navigation would be defined by the application author. However, when reading an email message the content will appear in a region with a <rref>document</rref> <a>role</a> in order to use browsing navigation.</p>`	`798`	`<p>For example, an email application has a document and an application in it. The author would want to use typical application navigation mode to cycle through the list of emails, and much of this navigation would be defined by the application author. However, when reading an email message the content will appear in a region with a <rref>document</rref> <a>role</a> in order to use browsing navigation.</p>`
`@@ -804,7 +804,7 @@ <h2>Definition of Roles</h2>`
`804`	`<!-- note: keep the previous paragraphs synced with their counterparts in #document -->`	`804`	`<!-- note: keep the previous paragraphs synced with their counterparts in #document -->`
`805`	`</ul>`	`805`	`</ul>`
`806`	`<p>User agents SHOULD treat elements with the role of <code>application</code> as navigational <a>landmarks</a>.</p>`	`806`	`<p>User agents SHOULD treat elements with the role of <code>application</code> as navigational <a>landmarks</a>.</p>`
`807`	- <p>Authors MAY use the <code>application</code> role on the <a>primary content element</a> of the host language (such as the <code>body</code> element in HTML) to define an entire page as an application. However, if the <a>primary content element</a> is defined as having a role of <code>application</code>, user agents MUST NOT use the element as a navigational landmark. If assistive technologies use an interaction mode that intercepts standard keyboard events, when encountering the <code>application</code> role, those assistive technologies SHOULD switch to an interaction mode that passes keyboard events through to the web application.</p>	`807`	`+ <p>Authors MAY use the <code>application</code> role on the <a>primary content element</a> of the host language (such as the <code>body</code> element in HTML) to define an entire page as an application. However, if the <a>primary content element</a> is defined as having a role of <code>application</code>, user agents MUST NOT use the element as a navigational landmark. </p>`
`808`	`</div>`	`808`	`</div>`
`809`	`<table class="role-features">`	`809`	`<table class="role-features">`
`810`	`<caption>Characteristics:</caption>`	`810`	`<caption>Characteristics:</caption>`