• Resolved JohnStaples

    (@johnstaples)


    I have a site where the dropdown menu trigger links were set up with #. Accessibility Checker finds those and flags them as “Improper Use of Link”. I then go into my menu and change the offending link to an actual URL but Accessibility Checker continues to flag this as an issue both in the WordPress View Page mode and Edit Page mode. When I click the Show Code option Accessibility Checker show the old code before I changed it.

    • I confirmed that old code is no longer anywhere in my page.
    • I have cleared my site cache over and over.
    • I have cleared my browser cache over and over.
    • I have tried logging out and then back in.

    Is there an Accessibility Checker cache I can clear to make this work properly?

    • This topic was modified 1 week, 1 day ago by JohnStaples.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author williampatton

    (@williampatton)

    Hey @johnstaples,

    I’m not totally certain why that issue would not get cleared out for you when you have fixed the issue. Can you visit one of the pages that has the issue and resave it to trigger a rescan? Let me know if this solves it for you.

    if that doesn’t solve it we recently added a ‘Clear Issues’ button at the top of the Accessibility Checker metabox in the editor. That will clear all issues for a specific page or post and then if you resave the page it will scan it fresh and should find only current issues.

    The ‘Clear Issues’ button is in the top right of the metabox.

    Thread Starter JohnStaples

    (@johnstaples)

    Thanks for your fast response @williampatton ! I first tried the Clear Issues button and that fixed the issue. Then I went to another page and tried just Updating it and that too resolved the issue. Great to know 2 ways to deal with this in the future. Thanks again!

    Plugin Author williampatton

    (@williampatton)

    Happy to have helped!

    If you have other questions or plugin feedback feel free to reach out and we will get back to you ASAP. Also, if you have a few minutes to spare to rate our plugin and support that would be great. These ratings are really helpful to the plugin.

    Thread Starter JohnStaples

    (@johnstaples)

    Well, after using this for a day I have come to realize that using the Clear Issues button has undesired consequences! I had gone through the errors and warnings on my page and marked several as Ignored since they did not apply to my situation. But after clicking Clear Issues I found those Ignores had been reset too so I lost that work! So, for me, updating the page is the only viable option to refresh the score.

    Generally I am finding this very cumbersome. Each time I make a change I have to resave all pages in order to see the effect on the score. Where this really slows me down is when I apply a global change to functions.php or styles.css and then simply opening pages will not show the effect of those changes. Instead I must go to each page, open it for editing and save it again (even though nothing on the page was changed) just to see the new score. Maybe there is a better way I have just not discovered yet? I hope so!

    I remain impressed with this tool and I was ready to buy the pro version but if it works this way too I may need to rethink that decision.

    Plugin Contributor Amber Hinds

    (@alh0319)

    @johnstaples an important thing to understand about the plugin is that it’s not routinely scanning your site. It has triggered scans at certain points.

    • In the free plugin, post scans are triggered on post save.
    • In the paid plugin, you can also run a full site scan, where the website crawls all posts and rescans them.

    When you fix something in your header, you either need to save each post it’s on (in the free plugin) or run a full site scan (in the paid plugin) for Accessibility Checker to see that you have fixed the item and no longer show it in reports.

    I have noted what your point about the “clear issues” button also clearing ignores. We’ll need to think about whether that’s the correct behavior or not for that button and possibly adjust how it works to give people the choice of keeping ignores or not for the post.

    Thread Starter JohnStaples

    (@johnstaples)

    Thank you for your detailed response, Amber!

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.