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

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 16 Dec 2011 23:54:05 +0000
To: public-html-a11y@w3.org
Message-Id: <E1RbhbJ-0002SY-HT@jessica.w3.org>

Cynthia Shelly <cyns@microsoft.com> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #3 from Cynthia Shelly <cyns@microsoft.com> 2011-12-16 23:54:04 UTC ---
screen reader users do know what the DOM order is, because screen readers
present content in DOM order, not visual order.  So, these use cases will
become confusing for these users.

Similarly, tab order is based on DOM order.  It can be adjusted with
incrementing tabindexes, but that is a strategy that is well known to get
broken over time, and also difficult to implement in dynamic and composited

Wouldn't it make sense in the use cases below to just use one big form, around
all the elements?  This feature seems to encourage overly complex and
inaccessible authoring practices, when we should be developing techniques to
avoid that.

Configure bugmail: https://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 Friday, 16 December 2011 23:56:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:25 UTC