- From: Steven Faulkner <faulkner.steve@gmail.com>
- Date: Wed, 15 Apr 2009 21:00:22 +0100
- To: jgraham@opera.com
- Cc: HTMLWG WG <public-html@w3.org>
james, i suggest providing the information in text, as content of the input's associated label element. >But it is not obvious that solution is better than the one in the > spec. why is it not obvious that an authoring practice that involves no implementation changes and ensures the information is available to all by default, is not a better solution? regards steve 2009/4/15 <jgraham@opera.com>: > Quoting Steven Faulkner <faulkner.steve@gmail.com>: > >> Anne wrote: >>> >>> Isn't the idea of new features that implementations have to change as >>> well? >> >> It is not a question of the implementations changing, the question is, >> has this author conformance requirement been thought out in terms of >> what is the best way for AT to provide this information, I don't think >> it has. > > So given that there is a need for authors to provide hints on the allowed > values of form controls and that it must be both available to those who use > AT and those who do not, what would you suggest as a better solution for > providing a hint as to the allowed values of the input element? It seems > like the "simplest thing that could possibly work" solution is to provide no > guidance here and assume that authors will place the relevant hints in the > main content of the page and in the region of the control (maybe even in the > label). But it is not obvious that solution is better than the one in the > spec. > > -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Wednesday, 15 April 2009 20:01:01 UTC