Accessibility issue with honeypot

  • Resolved eimaste

    (@eimaste)


    2 years, 4 months ago

    hey,
    trying to comply a website with WCAG 2.1 getting stuck to Wp Armor’s Honeypot field.

    could have an alternative way to hide the field, without using display:none. something like: aria-hidden=”true”

    thanx

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Dnesscarkey Support

    (@dcsupport)

    @eimaste,

    Thank you so much for your suggestion. I will definitely add this our next release.

    ??

    Thread Starter eimaste

    (@eimaste)

    thanx! very useful plugin so we’ll wait for your next release

    Lyk

    (@lyk-1)

    Hello,

    Having the same issue, I guess it is not added yet right?

    Moreover, there is another edge case that some accessibility tools flag as mistakes.
    When having more than one forms in the same page, the hidden fields from the different form have the same ids.
    So if we try to add labels (some tools require them in order not to show errors), the for="" of the labels have the same ids. This triggers errors for multiple labels for the same ids in some tools live https://wave.webaim.org/

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Accessibility issue with honeypot’ is closed to new replies.