Honey pot throws WCAG errors

Hi @dtwx

thanks for your report!

The bad value for autocomplete (on the honeypot and the new comment textarea) is due to a chrome bug which is already there, but we found a better way to circumvent it, which will be used in the next version. You can find all the details here:
https://github.com/pluginkollektiv/antispam-bee/issues/280

The aria-required is not coming from our plugin.

The default comment_form is using required="required"
https://github.com/WordPress/WordPress/blob/1c3b5c9dc8224a632c2fd29fe8bcf8b1bf5de113/wp-includes/comment-template.php#L2388

and we do not add something to this form:
https://github.com/pluginkollektiv/antispam-bee/blob/master/antispam_bee.php#L1195-L1223

If you haven’t changed the Scaffold theme, then your theme is not adding this too.

Do you maybe have used some plugins which could add this to the markup?

All the best,
Torsten

Oh, I see! It takes the existing <textarea>s and modifies them. Yes, I probably should have checked my own code first… Thanks for the pointers!

Also, I notice that you have type="text/javascript" declared in some scripts. WCAG warns about that too. Not the end of the world.

Also, I notice that you have type=”text/javascript” declared in some scripts. WCAG warns about that too. Not the end of the world.

Oh, yes, this could be changed in the next release too.

Thanks for the hint!

All the best,
Torsten

I have read some specs now and we shouldn‘t change it. The type is text/javascript per default in HTML5, but for older themes which are not HTML5 we should set this attribute.

We could check if the theme support is set to HTML5 for comments, but I think this a little to much for this minor issue.

All the best,
Torsten