• There are a number of accessibility checker plugins that work like this one does. I tried this one and I liked it, but ended up going with a different choice.

    Pros:

    • accurate and meaningful checks with explanations.
    • very clean and easy to read summary.

    Cons:

    • apparently does not check content until after a post is saved.
    • includes issues in headers and footers, and other plugins (which ultimately are important things to check but not necessarily something the editor of a post or page has any control over).
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Amber Hinds

    (@alh0319)

    Thanks for the review, @kennethrg. We are actually working on a feature right now to limit visibility of issues based on user role so that contributors, authors, and editors will not see issues in the header, footer, or other areas they can’t edit. It’s a bit tricky with our JavaScript-based rules that don’t use WordPress PHP functions to get the content (instead testing the rendered page) but it something we’re actively working on.

    I’d love to get your feedback on that feature when it’s released. Happy to comment here it’s available.

    • This reply was modified 1 month, 4 weeks ago by Amber Hinds.
    Thread Starter kennethrg

    (@kennethrg)

    Amber, that’s great to hear! Without knowing how the technology works, I suspect analyzing the page via JavaScript may have some benefits, if for some reason the published page renders differently than what the PHP functions would provide prior to publishing (e.g. unusual page builders, plugins, or other alterations to the page content).

    I am always happy to see good tools that promote a more accessible web.

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