aklpl

Hi @williampatton ,

Good to know about the lightspeed cache plugin — that seemed to be problematic in multiple ways, unfortunately.

Current reliability of the Accessibility plugin is so-so. I fixed 3 sitewide errors recently; if I create a brand new page, the old errors are gone (I am down to 9 errors I need to address), but on pages that already existed before I made those 3 fixes, the errors still show up in the Summary and Details of the Checker, though attempting to view those errors on the page yields more “element not found on page” errors. To clarify, this error is different from the one that states that an error is “not visible; try disabling styles.”

I hope this makes sense!

Hi @williampatton ,

Thanks for your response and for the Facebook link; I will double check those empty links. Most of them are probably image links, then, that I will need to add alt text or something else to (I will check the documentation suggestions).

I am still seeing some errors, though, that I have either corrected or that are no longer on the page (such as for past events), even after refreshing and rescanning the page.

For example, our Services tool has a mind of its own and uses H6s where H3s should be. I added a find and replace plugin so I could easily adjust the code. If I view the page source, I can see that my replacements worked (the incorrect H6s are replaced with H3s), but I am still getting an error saying that an H6 is present.

I am not sure, though, if it takes a few days for the Accessibility Checker to register some things? I feel like when I did my first trial H6 replacement, the scanner did not “notice” until several days later (I thought my correction had not worked).

This is the current error I am seeing that has already been corrected to be an H3 (as can be seen in the page source code):

<h6 class="sc_services_item_title"><span class="sc_services_item_label">Reserve Rooms / Study Spaces</span></h6>

Hello @williampatton,

I am unfortunately having a hard time contacting WPBakery at the moment — it appears that I need to have purchased a license with them to do so. I am not sure if it came with our theme or if it was purchased separately, and it seems that only a separate purchase will grant me access to support, which is frustrating. I am currently working with the website developer we used a few years ago to set the website up to see if they have the codes I need. I hate to leave you hanging in the meantime; is it possible to close this ticket for now with the possibility that I can reopen it if I am eventually able to contact WPBakery?

Thanks!

No worries, I appreciate your working on this!

If it helps at all, we do use the WPCode Lite Code Snippets plugin; I do not know what type of code snippet this solution will require, but if it is a PHP snippet, it appears that Code Snippets has an option to run a PHP snippet in the wp-admin area only.

Edit: Scratch that thought — I forgot that the issue was WPBakery, not the admin area. Sorry!

• This reply was modified 1 year, 2 months ago by aklpl.

Hello!

Sorry, I forgot to clarify — we use the WPBakery page builder plugin; edits in WPBakery pop up in little windows, so every element/block on the page ends up with external link arrows and the pop-up tool tips stating the link will open in a new window. No one on staff needs the reminders, so they just get in the way. The New Window Warning plugin seems to treat the page builder view as a frontend website page. Is it possible for us to adjust that, or is that just going to be a side effect of using the WPBakery plugin? (I had not realized until you asked for clarification that the only time we are having an issue is when we are on the WPBakery page builders).