<form> <label for="nameField"></label> <input type="text" id="nameField"/> </form>
This is the correct syntax please follow this, some of the validators give errors even when the label tag is after its corresponding input tag. So always have the label tag infront of the respective input elements. Thanks, JC On Sun, Mar 28, 2010 at 3:28 PM, tee <weblis...@gmail.com> wrote: > > On Mar 27, 2010, at 10:04 AM, Micky Hulse wrote: > > > I personally use only the W3C online validator. Personally, I would go > > with what the W3C validator tells you. > > I mostly use W3C validator for markup validation, but Total Validator has > nice features that allows validate markup, accessibility, broken links and > can perform spell check (though I don't use this feature), and this is the > only validator that has both markup and accessibility features I know of. > It does however often pick up something that I never find in other > validators and I find it to be a good learning tool to help me > understand/pay attention to WCAG 2.0 criterions, thus improving the quality > of the site accessibility wise, e.g. I have a voting poll markup with a > group of radio buttons and the label was presented before input and I saw > nothing wrong with it, none of the validators I used picked up any error but > Total Validator gave me this error and I learned something I was not aware. > > E831 - 5 instance(s): Associate labels properly with their controls. See > http://www.w3.org/TR/WCAG20-TECHS/H44.html > Example 3: A group of radio buttons > > > > Were there other errors on your page? > > No. > > I think I found the cause. Susan's question gave me a clue as to why the > validator throws in this error when it shouldn't be. > > > On Mar 27, 2010, at 9:18 AM, Susan Grossman wrote: > > > That would show an error like this > > > > > > <label for="sp3"> > > <form.....> > > <input id="sp3"....> > > </form> > > Well, it's not like that. The label and select attributes are not wrapped > in a form tag. The code was not written by me to begin with but I didn't > think to add the form tag for that I think it's under that type of situation > that judgement call rules because the function for this is an onchange event > to show x number items per page. If I add the form tag, the error does go > away, but it's a vicious circle that does nothing to improve accessibility > for the page, it starts complaining missing button, missing fieldset and > legend. > > tee > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
