This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16783 - no clear information on expected or desirable keyboard/focus interaction behaviour with new dialog element
Summary: no clear information on expected or desirable keyboard/focus interaction beha...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/commands...
Whiteboard: whatwg-resolved
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2012-04-18 16:21 UTC by steve faulkner
Modified: 2016-04-18 21:30 UTC (History)
10 users (show)

See Also:

Attachments

Description steve faulkner 2012-04-18 16:21:54 UTC 
One of the reason why a dialog feature was asked to be added in HTML5 is that the interaction behaviour for keyboard and AT users with pseudo dialogs sucks. Can you provide some description in the spec to allow us mortals to understand what the expected behaviours in browsers should be?
Comment 1 steve faulkner 2012-04-18 16:37:01 UTC 
For example when a non modal dialog is displayed and receieves focus it is still expected that the tab order will cycle through the dialog content only until the user either dismisses the dialog or moves focus back to the page via a defined action.

There is also an expectation that the focus will move to the first focusable element in the dialog when it is invoked and that the focus will move back to the same position in the document once the dialog is dismissed or the user moves focus awaya from the dialog.

None of this type of information appears to be specified?
Comment 2 contributor 2012-07-18 07:18:51 UTC 
This bug was cloned to create bug 17929 as part of operation convergence.
Comment 3 Robin Berjon 2013-02-18 11:48:04 UTC 
Steve, do you want to take this one up and make a proposal? Or is there a specific other action that you'd like to see?
Comment 4 Travis Leithead [MSFT] 2016-04-18 21:30:52 UTC 
HTML5.1 Bugzilla Bug Triage: Works for me.

I'm pretty sure much of this logic has since been specified, e.g., in: http://w3c.github.io/html/editing.html#control-group

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!