[SOLVED] Cynthia Says....

[minute44]

There's something wrong with my search bar.

Rule: 12.4.1 - Identify all non-hidden INPUT elements that do not have an explicit LABEL association.

• Failure - INPUT Element, of Type TEXT, at Line: 51, Column: 14 in FORM Element at Line: 50, Column: 3

What do I need to do to it? It's the last error before I claim WAI-AA

Cheers

Dan

[karinne]

So ... do you have a <label for="name">Name:</label> <input type="text" name="name"id="name" etc...> ?

You are probably missing the for attribute

[minute44]

All I have is the text input area

go look on minute44.com

[karinne]

Ok ... so ... this

HTML: Select all

<form method="get" id="searchform" label="Find" action="">
        <div><label for="Find"></label><input type="text" alt="Search Box" value="" name="s" id="s" />
        </div>
        </form>

should probably be more like this

HTML: Select all

<form method="get" id="searchform" action="">
        <div><label for="search"></label><input type="text" alt="Search Box" value="" name="s" id="search" />
        </div>
        </form>

I removed the label in your <form> and changed the for= to search instead of Find and fixed the id

See [CSS] Customize your form with CSS

[Rakuli]

Give the input box a title...

I'm pretty sure that's what it's looking for.

[karinne]

That too but the for attribute is his label wasn't matching the id attribute in his input

That's what I get from

"Identify all non-hidden INPUT elements that do not have an explicit LABEL association."

[Rakuli]

Okay, that would fix it then.. I didn't check the page... It only needs a title if there's no label.

[minute44]

Sorted it...

It was me not seeing the wood for the trees.

Cheers

[minute44]

I now have WAI-AA

[karinne]

so ... what was it? the for and the id? or something else?

curious

[Jack Franklin]

*DUMB QUESTION*

Whats WAI-AA?

[minute44]

It was the id.

WAI-AA is an accessibility acreditation. It means I satisfy both priority 1 and priority 2 of the WCAG 1.0 accessibility guidelines.. it's kind of a big deal.

[MikeHopley]

Originally Posted by minute44

WAI-AA is an accessibility acreditation. It means I satisfy both priority 1 and priority 2 of the WCAG 1.0 accessibility guidelines.. it's kind of a big deal.

Which is great!

One thing to bear in mind, however: some of the guidelines are stupid (mainly priority 3 ones).

For example, adding accesskeys actually harms accessibility: site accesskeys override browser shortcuts. Disabled users can be dependent on the very shortcut you take away.

All Anchor, AREA, BUTTON, INPUT, LABEL, LEGEND, and TEXTAREA elements are required to use the 'accesskey' attribute.

What has Cynthia been smoking? Put access keys on every link? Is she insane?

Similarly:

All Anchor, AREA, BUTTON, INPUT, OBJECT, SELECT and TEXTAREA elements are required to use the 'tabindex' attribute.

Why define a tabindex, if the default source order is logical?

The WCAG are in a dreadful state. It's still good to read them, but some of their advice is simply daft. Moreover, the outlook for WCAG 2 is bleak.

[minute44]

I'm not going for AAA standards. Far too many links ot apply access keys to. I'm going to maintain AA and section 508.

[MikeHopley]

Originally Posted by minute44

I'm not going for AAA standards. Far too many links ot apply access keys to. I'm going to maintain AA and section 508.

I wouldn't even consider which standard to choose. For a start, there is no true accreditation: it's self-assessment only.

I just read through the guidelines, and try to satisfy all of them that seem sensible.

Also, I don't believe the WCAG specifies "access keys on every link". I think that's Cynthia being stupid. Automated accessibility checkers are crude.

[minute44]

That's true... Cynthia's a pedantic old bitch.

http://fae.cita.uiuc.edu/

That's another tester. It's not too bad though it does need to be accompanied by a human test to weed out one or two crappy results.