Hidden field in form

[Divisive Cotton]

I've been adding a field into forms and then hiding it with display: none

If a spam bot comes across the form it automatically fills in the field and which is then rejected after validation

For the purpose of stopping spam bots it seems to be pretty successful

However, how does this level with accessibility? Any advice is welcome.

[stonedeft]

Wow thats a good idea to fight spam bots.

[felgall]

I've been adding a field into forms and then hiding it with display: none

If a spam bot comes across the form it automatically fills in the field and which is then rejected after validation

For the purpose of stopping spam bots it seems to be pretty successful

However, how does this level with accessibility? Any advice is welcome.

display:none will only impact people using browsers that don't process the stylesheet. For those people displaying a label for the field explaining that they should leave the field blank as it is there as a trap for spammers should ensure accessibility for those users.

[AlexDawson]

It should be fine, screen readers tend to ignore anything using display: none so they would skip over the hidden field (which is of no use to them anyway).

[Stomme poes]

Uh, no. JAWS can ignore display: none when it comes to labels and other special circumstances. I hate they did that, but whatever. Labels get read out... I'd have to go back and check Juicy Studio to see if Window Eyes did that too.

*edit only problem with it is the age, but my JAWS10 reads out display: none labels still: http://juicystudio.com/article/scree...splay-none.php

For those people, displaying a label for the field explaining that they should leave the field blank as it is there as a trap for spammers should ensure accessibility for those users.

Amen, nothing more frustrating for humans than to be accidentally considered a spammer : )

If I make a post on the Fronteers site, they use Javascript to hide a question. Since i don't have that on, I get an extra field. The label says "NEE invullen" (fill in NO) but I misread it and thought it said "NIET invullen" (don't fill in) so I kept triggering the spam filter, lawlz. This can also work since most bots don't process Javascript.

On a moving site I haz:

<label for="spamz" id="spamvraag"><span>AUB <strong>Niet invullen</strong>, dit is een anti-spam vraag:</span>
<input type="text" id="spamz" name="spamz" title="aub niet invullen!"></label>

Title is an extra to really catch any screen reader users who have titles on, though it does trigger that old W-E bug where inputs inside labels aren't focussable... then again, for this question, that's just fine : )

One thing I might want to look out for are smarter bots who might be scanning the label for the word "spam" though. I mean, if I made such bots I'd consider adding something like that : )