Support » Plugin: Accessibility Checker by Equalize Digital » Incorreclty loading Google Fonts

  • Resolved Clayton Collie

    (@claytoncollie)


    Hi. I am testing out your plugins and it is throwing errors in Query Monitor on how you are loading google fonts.

    file_get_contents(//fonts.googleapis.com/css?family=Source+Sans+Pro%3A400%2C700&ver=1607456192): failed to open stream: No such file or directory

    Is this my theme loading these or is your plugin? Do we even need these fonts packs?

    I am running Wp 5.5.3 on the latest Genesis version.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Amber Hinds

    (@alh0319)

    Hi @claytoncollie,

    Thanks for testing the plugin and posting here. Our plugin does not load Google Fonts, so this is likely coming from your theme or could possible be from another plugin.

    Plugin Contributor Amber Hinds

    (@alh0319)

    Hi @claytoncollie,

    We looked into this a little further just to confirm. It looks like Query Monitor does throw some warnings (not an error though) if you have a theme that loads fonts without the https:// or http:// on the URL. This comes up when we parse the CSS to check for accessibility errors.

    Our 1.0.1 version released earlier today did include a fix to suppress these warnings, so if you update they should go away. But we’re tracking it as a bug and are going to see how we can better account for themes that include fonts this way.

    Thanks again for your report, we appreciate it!!

    Thread Starter Clayton Collie

    (@claytoncollie)

    Hi @alh0319

    You are correct. I am loading my fonts without the protocol at the beginning of the URL. I updated the plugin to 1.0.1 and do not see the warning anymore. Much appreciated. 🙂

    Nice job on the plugin and on the Equalize Digital website. Both are very polished.

    I typically use SiteImprove for client sites but it is mostly pre-launch work. This plugin could be a nice addition to my those sites to help content creators with writing accessible posts. I see people using <i>, <b>, <u> elements along with improper nesting of headings all the time.

    If we did start using this plugin on client sites, we typically use Composer to bundle plugins inside a platform plugin and it is hard to do this well with premium plugins such as yours. I know I can use wpackagist for this version but we would need the premium version for custom post types. Just something to think about for your roadmap. DeliciousBrains and Metabox have some knowledge about API keys and Composer packages that might be worth checking out. Feel free to shoot me an email if this is too much for right here.

    clayton.collie@contentpilot.com

    Plugin Contributor Amber Hinds

    (@alh0319)

    Thanks, for the thoughts @claytoncollie. We spoke about this in our team meeting today and may add it to our roadmap.

    I’ll reach out via email.

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