Accessibility errors

  • Resolved carnets2routards

    (@carnets2routards)


    4 years, 9 months ago

    Hi,

    First thank you for your work! Just starting to try out your plugin, seems to do its job for now. ??

    I’m trying to have an accessible website and in order to I’m using the Wave browser plugin to check errors and alerts.

    It detects Empty button (no text or value attribute) in this part of the code (3 button tag):

    <div id="wfboxOverlay" style="display: none;">
ARIA tabindexARIA<div id="wordfenceBox" class="" role="dialog" tabindex="-1" style="display: none;"><div id="wfboxWrapper"><div><div id="wfboxTopLeft" style="float: left;"><div id="wfboxTopCenter" style="float: left;"><div id="wfboxTopRight" style="float: left;"></div><div style="clear: left;"><div id="wfboxMiddleLeft" style="float: left;"><div id="wfboxContent" style="float: left;"><div id="wfboxTitle" style="float: left;"><div id="wfboxCurrent" style="float: left;">
<button type="button" id="wfboxPrevious">
<button type="button" id="wfboxNext">
<button type="button" id="wfboxSlideshow">
<div id="wfboxLoadingOverlay" style="float: left;"><div id="wfboxLoadingGraphic" style="float: left;"></div><div id="wfboxMiddleRight" style="float: left;"></div><div style="clear: left;"><div id="wfboxBottomLeft" style="float: left;"><div id="wfboxBottomCenter" style="float: left;"><div id="wfboxBottomRight" style="float: left;"></div></div><div style="position: absolute; width: 9999px; visibility: hidden; display: none; max-width: none;"></div>

    Thanks in advance for your time ??

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hey @carnets2routards,

    Thanks for sharing this. I’ve shared this with the developers, and I’ll be sure to share their thoughts with you!

    Thanks,

    Gerroald

    Hey @carnets2routards,

    We haven’t heard back from you in a while, so I’ve gone ahead and marked this thread as resolved.

    Please feel free to open another thread if you’re still having issues with Wordfence.

    Thanks,

    Gerroald

    maryannk

    (@maryannkelley)

    I’m having this same issue and I don’t see on this thread where the Wordfence developers ever shared a solution or a path forward for the plugin that conforms to accessibility standards. What do the developers plan to do about the errors caused by the empty buttons?

    I am having the same problem. Has Wordfence come up with a solution please?

    SOLVED!
    One of our team tracked it down to the Wordfence settings option ‘Monitor background requests from an administrator’s web browser for false positives’. If the box is checked it enables logged in administrators to monitor real-time background (Ajax) requests made from the front-end. That’s what adds the non-accessible code to the front end pages. Two ways to avoid the accessibility problem: either
    1) un-check that Wordfence option for the ‘front end website’ and save or
    2 simply log out of the back-end before running the accessibility check. (Using a completely different type of browser for admin logins will avoid the need to keep logging in and out).

    Thread Starter carnets2routards

    (@carnets2routards)

    Hi there,

    Just to say thanks to @chadsweb , I went back on this issue recently and it is correct, I have the error only when I’m connected to the admin. Otherwise no accessibility error.

    Cheers

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Accessibility errors’ is closed to new replies.

Tags