Steve Jones

Do those linked images have alt text? Also, I’m curious if the image lazy loading is why the Accessibility Checker can’t find the image on the page. It could also be why they are being flagged as issues.

When I do a scan of this page I’m getting a reading level of 10th grade.
https://www.konstnarsnamnden.se/internationella-program-och-residens/artnexus/

Screenshot: https://capture.dropbox.com/ZlMsaqKBJ9b9ANTB

Also, that page has some kind of blocking on it. I can’t scroll or click on anything. Maybe that’s by design.

Hi @anphira,

Thanks so much for the thorough testing and taking the time to provide feedback.

I’ve moved this to a GitHub issue for us to consider for the next release.

https://github.com/equalizedigital/accessibility-new-window-warnings/issues/7

If it’s in a block the text should be evaluated. What is the character count of the text?

Sorry, I posted the wrong issue. This is the correct issue. https://github.com/equalizedigital/accessibility-checker/pull/327

Yes, correct the readability is evaluated on the post content. If your post content is in a meta field the plugin currently will not evaluated it for readability.

Hi @dzulfriday, yes I think this is a bug. It has been fixed but not yet released. It should be in the next release.

https://github.com/equalizedigital/accessibility-checker/issues/304

I believe we’ve looked at this site before. I’ve run an offsite scan of that page, and it returned 15 color contrast issues. You’re correct some are false positives. There are about 5 color contrast errors on the page. See the form labels. Also, side note the form labels are missing the “for” attribute. We are in the process of releasing a feature that will resolve these false positives.

Page builders tend to add more complexity in evaluating color contrast because they generally have more nesting and more advanced CSS variable use.

We are actively working on a fix for this. You can track the process with this GitHub issue: https://github.com/equalizedigital/accessibility-checker/issues/246

Hi @caroline72, Yes, there has been progress on this. We had this fix slated for the next release that is coming out this week but we’ve pushed it out a bit because it needs some more refining. Thanks for your patients and we hope to have this released in the near future.

Hello @kallestonecold,

You’ve identified a bug in the plugin. The reading level will properly update on the summary tab. To get the Readability tab to show you the reading level you’ll need to refresh your browser.

I’ve opened an issue in GitHub to get this issue fixed in the next release. You can follow the progress here: https://github.com/equalizedigital/accessibility-checker/issues/275

Thanks,

Steve

Thanks for testing and letting us know it’s working.

This has been fixed with the latest version 1.5.3. Thanks!

Thanks @nwjames, I’ve opened a GitHub issue for this bug. You can follow progress of it there. https://github.com/equalizedigital/accessibility-checker/issues/261

Hi @ahmedzeidan, Yes, the page needs to be scanned before the issue will show on the frontend. We can look at adding a scan trigger from the frontend to address cases like this.

I’ve opened a ticket on GitHub where you can track progress.
https://github.com/equalizedigital/accessibility-checker/issues/260

Hello @voodoocreative, The plugin doesn’t currently evaluate changes to the page made with javascript. If you confirmed the issue is fixed with javascript then you can mark the issues as ignored.