WordPress.org

Ready to get started?Download WordPress

Forums

Spam Honey Pot
Not suited for blind users (4 posts)

  1. andreasbo
    Member
    Posted 1 year ago #

    Problem: Only a textarea is added without a label. So when blind people with a screenreader use it, the screenreader will show them the textfield even though it's "display:none". Maybe the fill it out, because they don't know what it is used for.

    Suggestion: Add a label like "If you are a human, do not fill in this field."

    http://wordpress.org/extend/plugins/spam-honeypot/

  2. esmi
    Forum Moderator
    Posted 1 year ago #

    the screenreader will show them the textfield even though it's "display:none"

    What screen reader are you using? All of the common screen readers that I know of (JAWS, NVDA, WindowEyes etc) honour CSS display:none;.

  3. andreasbo
    Member
    Posted 1 year ago #

    Hi esmi

    Thanks for your input. You seem to be right. Unfortunately, I have no screenreader, so I cannot test it.

    But in some circumstances screen readers seem to show display:none
    http://juicystudio.com/article/screen-readers-display-none.php

    I tested it with the Firefox Adddon "Fangs" and that shows me the field of the honepot-field: https://addons.mozilla.org/de/firefox/addon/fangs-screen-reader-emulator/

    Anyway I think it's saver if textfield has a label. Just in case the textfield is shown...
    What do you think?
    (I already made the changes and sent a pull request: https://github.com/elazar/wp-spam-honeypot/pull/3 )

  4. esmi
    Forum Moderator
    Posted 1 year ago #

    That's a pretty old article (although everything on juicystudio.com is well worth reading) and the major screen readers have moved on a bit since then. The article also mentions that this issue only occurred when using display:none; with links (anchor elements) - not form inputs. JAWS especially uses a completely different mode to interact with forms compared to plain text & links.

    With regard to Fangs, I'd be really careful about extrapolating anything concrete when using this add-on. It is just a developer tool - not a screen reader in its own right - so there may be some things that it does not emulate correctly.

    I'd agree that adding a descriptive label would be a good idea to cover any edge cases but only if that label too was hidden using display:none; - otherwise the output could be a bit confusing for sighted screen reader users (and, yes, not all screen reader users have sight problems).

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic