Honeypot html change now accessible via keyboard

  • Resolved suzannaaltman

    (@suzannaaltman)


    9 months, 2 weeks ago

    The HTML structure for the basic honeypot has changed and is now accessible via keyboard, causing accessibility issues. I see someone pointed this out in the past and it was resolved, but the issue seems to be back.

    Ideally the input would have the aria attribute aria-hidden=”true” and tabindex=”-1″ and NOT have an autocomplete attribute.

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Njones35

    (@njones35)

    Hi there,
    I do apologize for the slow response. I’ll report this to our developers now, and they will look into solutions that can be included in an upcoming update.

    Best,
    Nathanael

    Plugin Support Njones35

    (@njones35)

    I just got some more information from our lead developer that I wanted to pass on. He said:

    “The tabindex=”-1″ is set the first time the tab key is pressed. It’s intentionally not added on load because it would be a dead giveaway to a bot. If we added the tabindex=”-1″ on load we might as well just not have a honeypot feature at all.

    We dropped the aria-hidden attribute to remove the accessibility errors picked up by automated tools like Google PageSight and Axe DevTools.
    If that is an issue, I would recommend disabling the honeypot.

    Honeypot is NOT accessible by keyboard, at least on a normal browser. Also, the autocomplete attribute is set to false if they switch the setting to “basic” and not strict. When using strict, has no autocomplete attribute.”

    I hope that helps!
    Best,
    Nathanael

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Honeypot html change now accessible via keyboard’ is closed to new replies.

Tags