williampatton

Do you have access to a staging/development version of this site where changes can safely be made to test things and to figure this out?

I have tested accessibility-checker on a local site with the page optimize plugin and it definetly does create some issues. Maybe those issues are not what is causing the panel to fail in the editor page or that blocks yoast from working – but it is causing some issue. You should add this list of JS scripts that are not concatenated to solve that:
edac,edac-editor-app,edac-frontend-fixes,edac-frontend-highlighter-app

You can find that input box by hovering the menu at Settings -> Performance and then the page that loads should have a box lablelled with Comma separated list of strings to exclude from JS concatenating:

I don’t see anything else in your list of plugins that may be causing a conflict. Do you happen to know if there is any error logging enabled on the site which you could share. I know you mentioned you were not technical so I understand if this isn’t something you know how to check.

Hey,

The Page Optimize plugin is the one that is causing the conflicts here. It is doing some thing to optimize performance but that can sometimes cause things to break due to it making certain expectations that are not always true. It is most likely the reason accessibility-checker is not working on your site and also probably why Yoast SEO isn’t working either.

Temporarily could you disable that plugin and see if your issue with both plugins goes away?

I can find the right scripts to exclude from that plugin to make accessibility-checker work for you if disabling it fixes the problem on your site.

Hey @amykristin75,

Thanks for trying the plugin and sorry that you are running into issues.

I took a quick look at your site and I can see that there are quite a few console errors being thrown from the pages, some related to our plugin and some unrelated. It seems like the cache plugin you are using on the site does not work well with our plugin.

Can you let me know what cache plugin you have enabled? I will look and see if there are specific settings that are needed to ensure that the cache does not interfere with how the plugin works.

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.

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.

I am glad that is is working now for you. I am not sure what exact compatibility issues exist between the plugin and Divi but I will make a point to test the plugin with that specific theme to make sure that there are no conflicts from the theme.

Thanks for letting me know about your problem and that it is now working for you. If you have any other questions or issues feel free to reply on this thread and we will help you out as best as we can.

Hey @rcwatson,

Thanks for trying the plugin, and I’m sorry that it isn’t working as intended on your site.

We have some general docs about things to check that you can look through here: https://equalizedigital.com/accessibility-checker/accessibility-checker-not-scanning/

Does this site have pretty permalinks and REST API enabled? The most common reason I have seen this is that sites have disabled their REST API access.

Can you look in the network tab of the console for me and see if there are any failed ajax or fetch requests logged and if so what their response codes are?

Also if you visit the editor page for a post does the scanner run and produce data in the metabox we add in the editor?

I am glad that you got this figured out. I wonder if there is something that we can do to detect maintainance mode and flag it instead of scanning it. I’ll make a note to look into that.

Thanks for reporting it!

Hey @lukeatsayhellotowoo,

Sorry that you are having an issue with the heading order detection.

I can take a look and try see what might be the cause. Is the page publicly accessible for me to take a look at? If you do not want to share the link here in the thread let me know and you can email me the link.

Also can you confirm that the email address you see is exactly [email protected] or is the email address something different and you have changed it in the example?

Hey @alypara18,

I am glad that this is resolved now. If you run into any other issue or have any other questions feel free to reach out.

Hey @alypara18,

Sorry for the long delay between replies here. I tested this and was unable to reproduce the same issue you faced but I have more time today to dedicate towards getting a solution here for you on it.

If you could share those screenshots of the issue that would helpful in me seeing the problem to get more ideas of how to reproduce it and solve it.

I tested a fresh post this morning with a default mailchimp embed form generted following those same instructions you linked to. I placed the embed code inside of an HTML block in the editor and in the preview and on the frontend published post I see the form and a summary that appears only at the end of the post.

Hey @alypara18,

Thank you for using the plugin, and I’m sorry you are having an issue with this.

I haven’t encountered this particular issue before—where the summary is being duplicated or added inside elements that it isn’t expected to be with—but I will dig into the code and see what I can spot.

About the MailChimp embed, are you using a specific plugin to add that to the pages, or does that feature come with the Divi theme by default?

If you have a developer on your team one solution could be to use the code based injection method to set the simplified summary location on your pages: https://equalizedigital.com/accessibility-checker/readability/#16-simplified-summary-position

Once I have had a chance to take a look into this and figure it out for you I will reply here and let you know what I have found.

Hey @johnstaples,

Thanks for getting back to me. I definetely want to help get to the bottom of this and figure it out. Is there any chance that you could reach out to me through a form on our website so that I can get more details about the exact server setup your using and maybe even a backup of the site to test with? If you are ok with that I will provide a link to a form that you can reach me through so we can dig in more deeply on this.

It has been a while since there has been a response on this thread from the opener so I am going to mark it as resolved – but if it still needs some action let me know and I will reopen the thread.

@oldrup good spotting on the http vs https mismatch. I have taken a note to test if that actually was the root of the issue here.

I think that this thread has answers for the questions asked so I am going to mark it as resolved – but if you have any other questions feel free to post them here and I will make sure that they get answers.

Thank you for the question!