ACTION-282: Write a response to Simon's post to action 153 http://lists.w3.org/Archives/Member/w3c-wai-pf/2008JulSep/0591.html

Reassign to Al.

Al review this wording, proposed by Rich, with Aaron to ensure it addresses the "access to the scrollable region" scenario. Wording proposed by Rich is as follows (taken from: http://lists.w3.org/Archives/Member/w3c-wai-pf/2008OctDec/0015.html:

Modify section 4.1 of the Best Practices Guide to append the following
paragraphs to step 6:

When a document element that uses role="application" receives focus,
focus must be set to a widget descendant within
the element's document subtree. This is to provide a "point of regard" for
the user. Tabindex="0" should never be applied
to a document element with role="application."


When an element (other than the document element) that uses
role="document" receives focus, the author
should determine the desired user experience
when navigating to the document area. If the user should browse from the
start of the document subtree,
having role="document," then a tabindex="0" should be set on this element
and there should be a visual indication
that it has received focus. Otherwise, focus should be allowed to flow
normally as defined by the host language, such as to a link or
form element within the subtree. By allowing focus to move to the element
with role="document" a screen reader
can begin reading the document area from the beginning rather than from
an embedded link or form element within.


The above logic should be applied for all elements that have
role="document" including those that are descendents
of an element with role="application."

Modify per this post to the pf-editors working group list:

http://lists.w3.org/Archives/Member/member-pf-editors/2009JanMar/0007.html

Close after.

Closed in 14 January 2009 Editor's Draft. Closes 282 and Issue 57

Changed to pending review

See CVS history 1.58