W3C home > Mailing lists > Public > public-html@w3.org > August 2011

[Bug 13549] New: associating form elemnents with forms that do not contain them can cause navigation problems for AT and keyboard users

From: <bugzilla@jessica.w3.org>
Date: Wed, 03 Aug 2011 01:12:29 +0000
To: public-html@w3.org
Message-ID: <bug-13549-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13549

           Summary: associating form elemnents with forms that do not
                    contain them can cause navigation problems for AT and
                    keyboard users
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Keywords: a11y, a11ytf
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: cyns@microsoft.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


What is the use case for associating a form element with a differnt form than
the one that contains it?  The spec says this is to work around lack of support
for nested forms, but what is the use case for nested forms?

When an element is associated with a different form than the one that contains
it, it will cause behavior that the user will not expect.  This will be
particularly problematic for screen reader users, because the screen reader
reading order follows the DOM order, not the specified form relationships. 
Similarly, without significant work by authors, keyboard tab order will not
match either.  

This feature seems likely to introduce author errors, without clear benefit. 
Instead, nested forms should be considered an author error.  Browser behavior
for handling this error can be specified, but we should not add features to
handle it.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 3 August 2011 01:12:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:37 GMT