- From: <bugzilla@jessica.w3.org>
- Date: Fri, 13 Jan 2012 00:50:12 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13549 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-01-13 00:50:11 UTC --- There's definitely ways to build them without this feature. Just have the server check which button was pressed, and act accordingly, or put the forms after each other. That's what people do now (e.g. this very page does that — it has the bug form in the middle and search forms at the top and bottom). It makes maintenance difficult. Sometimes people split the other form into an entirely separate page, e.g. the way that the "Add an attachment" feature above opens a separate page instead of being done inline. I don't see why the form="" feature would have any implications on accessibility. Users already have to deal with content intermixed with other content (e.g. ads, sidebars, etc). There's nothing particularly special about AT users here — visual users have to deal with pages with mixed content too. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: no new information since comment 2 -- 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, 13 January 2012 00:52:17 UTC