Hi Steve Correct - The web page is a context — but the author does not cause the tabkey to move out of the page (that is browser or OS behavior) —so the author (and the web page) would not fail WCAG. Also - on a broader basis — the browser is actually part of the context of each page. (e.g. the print function of the browser provides the print function of the page) so I would say that it is not really a different context but the broader context. gregg ---------------------------------- Gregg Vanderheiden gregg@raisingthefloor.org > On Apr 21, 2015, at 4:53 PM, Steve Faulkner <faulkner.steve@gmail.com> wrote: > > > On 20 April 2015 at 08:33, Gregg Vanderheiden <gregg@raisingthefloor.org <mailto:gregg@raisingthefloor.org>> wrote: > GV: Hmmm. the dialog box sounds like a context to me. and moving out of the dialog box using standard navigation commands (arrows or tab-key) would seem to be a ‘change of context due to change of focus” which would be a WCAG SC failure. explicit commands (like hot keys or command key combinations ) would not violate it - but moving focus around in a context should not jump them out of that context. At least that is my take. If you want a ruling you might run this past the committee as a whole. I added the chairs to this email for their information. > > Hi Gregg, > > > If a web page is a context, and moving outside of a web page via the tab key is a change of context, then every web page would fail the WCAG 2.0 criteria as the address bar of browsers (if present) recieves focus after the last focusable element in the page. > > -- > > Regards > > SteveF > HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
Received on Wednesday, 22 April 2015 14:17:44 UTC