Designer wrote:
Sorry to go over old ground here, but I seem to remember that the
general consensus of opinion on the above two was that it was best if
they weren't used? However, if I try to validate using the WIA
validator,
I've never heard of it, and a quick Google doesn't help.
my stuff validates, but the validator gives me two warnings:
9.4 Create a logical tab order through links, form controls, and objects.
* Rule: 9.4.1 - All Anchor, AREA, BUTTON, INPUT, OBJECT, SELECT and
TEXTAREA elements are required to use the 'tabindex' attribute.
Rubbish. WCAG 1.0 says: "For example, in HTML, specify tab order via the
"tabindex" attribute or ensure a logical page design."
Logical page design is the better option. Tabindex only comes into play
if you're doing something fairly odd.
9.5 Provide keyboard shortcuts to important links (including those in
client-side image maps), form controls, and groups of form controls.
Well, technically it is a requirement of AAA level WCAG 1.0, but a lot
of experts consider accesskeys to do more harm then good since they
interfere with built-in keyboard shortcuts in most browsers.
* Rule: 9.5.1 - All Anchor, AREA, BUTTON, INPUT, LABEL, LEGEND, and
TEXTAREA elements are required to use the 'accesskey' attribute.
This tool really isn't very good. WCAG says "important" (and they quoted
it), not "all".
--
David Dorward <http://dorward.me.uk/>
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************