Title: Accessibility errors
Last modified: June 2, 2020

---

# Accessibility errors

 *  Resolved [carnets2routards](https://wordpress.org/support/users/carnets2routards/)
 * (@carnets2routards)
 * [5 years, 12 months ago](https://wordpress.org/support/topic/accessibility-errors-6/)
 * 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](https://wave.webaim.org/extension/)
   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 😉
    -  This topic was modified 5 years, 12 months ago by [carnets2routards](https://wordpress.org/support/users/carnets2routards/).

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

 *  [WFGerroald](https://wordpress.org/support/users/wfgerald/)
 * (@wfgerald)
 * [5 years, 12 months ago](https://wordpress.org/support/topic/accessibility-errors-6/#post-12928167)
 * Hey [@carnets2routards](https://wordpress.org/support/users/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
 *  [WFGerroald](https://wordpress.org/support/users/wfgerald/)
 * (@wfgerald)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/accessibility-errors-6/#post-13020413)
 * Hey [@carnets2routards](https://wordpress.org/support/users/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](https://wordpress.org/support/users/maryannkelley/)
 * (@maryannkelley)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/accessibility-errors-6/#post-13106660)
 * 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?
 *  [chadsweb](https://wordpress.org/support/users/chadsweb/)
 * (@chadsweb)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/accessibility-errors-6/#post-13176006)
 * I am having the same problem. Has Wordfence come up with a solution please?
 *  [chadsweb](https://wordpress.org/support/users/chadsweb/)
 * (@chadsweb)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/accessibility-errors-6/#post-13176596)
 * 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](https://wordpress.org/support/users/carnets2routards/)
 * (@carnets2routards)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/accessibility-errors-6/#post-13678478)
 * Hi there,
 * Just to say thanks to [@chadsweb](https://wordpress.org/support/users/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.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [a11y](https://wordpress.org/support/topic-tag/a11y/)
 * [WAI](https://wordpress.org/support/topic-tag/wai/)

 * 6 replies
 * 4 participants
 * Last reply from: [carnets2routards](https://wordpress.org/support/users/carnets2routards/)
 * Last activity: [5 years, 6 months ago](https://wordpress.org/support/topic/accessibility-errors-6/#post-13678478)
 * Status: resolved