16783 2012-04-18 16:21:54 +0000 no clear information on expected or desirable keyboard/focus interaction behaviour with new dialog element 2016-04-18 21:30:52 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED WORKSFORME http://dev.w3.org/html5/spec/commands.html#the-dialog-element whatwg-resolved a11y P2 editorial --- 1 faulkner.steve faulkner.steve eoconnor falken faulkner.steve hans.hillen mike philipj public-html-admin public-html-wg-issue-tracking robin travil public-html-bugzilla oldest_to_newest 66805 0 faulkner.steve 2012-04-18 16:21:54 +0000 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? 66806 1 faulkner.steve 2012-04-18 16:37:01 +0000 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? 70320 2 contributor 2012-07-18 07:18:51 +0000 This bug was cloned to create bug 17929 as part of operation convergence. 83262 3 robin 2013-02-18 11:48:04 +0000 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? 125895 4 travil 2016-04-18 21:30:52 +0000 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!