[Validation Issue] v263 – WordPress Default 1.6 theme

nilsc
(@nilsc)

17 years, 7 months ago
I get a validation error in two locations for aria-required=’true’ the code is in comment form:
```
<p><input type="text" name="author" id="author" value="<?php echo $comment_author; ?>" size="22" tabindex="1" <?php if ($req) echo "aria-required='true'"; ?> />
<label for="author"><small>Name <?php if ($req) echo "(required)"; ?></small></label></p>
```
The validation error is: there is no attribute “aria-required”.

I see some entries where this was attributed to reCAPTCHA. Because it happens in the default theme and not in the classic I was wondering if there is a work around to keep the name and email required and avoid the error.

Viewing 5 replies - 1 through 5 (of 5 total)

whatsyourrecord
(@whatsyourrecord)

17 years, 6 months ago

Hi nilsc, ara-required is just an WAI ARIA property for more accessibility (for screenreaders etc.). Im sure that these attributes are soon accepted by the xhtml validator

iridiax
(@iridiax)

17 years, 6 months ago

Yes, some validation “errors” can safely be ignored.

Alvaro Degives-Mas
(@nv1962)

16 years, 10 months ago

I’m sure XHTML 7.0 will have some awesome features too, but it’s an error in the current version. Period. (Else, don’t use a doctype declaration that lies about its standards compliance.)

Edited: it’s in the theme code, so it can be whacked out easily – unlike the issue of the nearly impossible to skin the login and registration forms, the code of which seems to change with every point release.

vikingjs
(@vikingjs)

16 years, 9 months ago

I take pride in only inflicting compliant code upon my hapless viewers, and this aria-required prevents it. I have no problem whacking it out, but if it’s performing a valuable function I don’t want to break things. What’s so cool about this thing that its worth breaking standards?

Alvaro Degives-Mas
(@nv1962)

16 years, 8 months ago

It’s cool in that it provides better accessibility. See:
http://www.marcozehe.de/2008/02/29/easy-aria-tip-1-using-aria-required/

It’s totally uncool as it’s yet another non-standard add-on that gets happily slapped into themes with limited support (by some browser).

I don’t have issues with the intent behind ARIA; I have issues with crud that gets crammed onto the intertubes without any regard for standards, and very little in the way of formal coordination with the standards developing entities to get them slotted in properly.

Reeks of thoughtless me-too featuritis, this implementation of aria-required.

Just whack it out. Odds are you and your readers don’t need it and won’t miss it.