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 17929 - 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 INVALID
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://dev.w3.org/html5/spec/commands...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 07:18 UTC by contributor
Modified: 2012-07-27 02:06 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2012-07-18 07:18:48 UTC 
This was was cloned from bug 16783 as part of operation convergence.
Originally filed: 2012-04-18 16:21:00 +0000
Original reporter: steve faulkner <faulkner.steve@gmail.com>

================================================================================
 #0   steve faulkner                                  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?
================================================================================
 #1   steve faulkner                                  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?
================================================================================
Comment 1 Ian 'Hixie' Hickson 2012-07-27 02:06:14 UTC 
Please file just one issue per bug.