- From: <bugzilla@jessica.w3.org>
- Date: Fri, 16 Dec 2011 23:54:05 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13549
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
sites.
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 the QA contact for the bug.
Received on Friday, 16 December 2011 23:54:10 UTC