Steve Jones

Hi @oldrup,

Very sorry for the late follow up on this and thanks for bring it to our attention.

Our rule currently isn’t checking for duplicate alternative text inside of <figcaption> elements.

I’ve opened a GitHub issue for this: https://github.com/equalizedigital/accessibility-checker/issues/732

I’ve also put together a patch for this: https://github.com/equalizedigital/accessibility-checker/pull/733

We’ll do some internal review of this and if it’s a good fix it’ll be released in the next version.

Please keep an eye on the issue for updates.

Hi @oldrup,

We’re targeting sliders specifically. You can find the list of sliders here in our documentation. https://equalizedigital.com/accessibility-checker/slider-is-present/

We’ll have to look into adding the Getwid slider.

Thanks!

Hi @johnstaples,

Glad to hear you resolved the issue with your hosting company! ??

Most server configurations I’ve seen have allow_url_fopen enabled all the time. You can toggle it as you described if you have specific security requirements.

Glad you’re finding the plugin useful. Let us know if you need anything else.

Hi @johnstaples,

If the plugin is unable to scan the page then that is defiantly the root issue here.

Just out of curiosity have you updated the page in the admin after installing the plugin and adding the image with no alt without receiving the password-protected error message?

Thanks,

Steve

Hi @johnstaples,

The password protection message is likely showing because the plugin can’t scan the front-end of the page. This is usually because of password protection but can be several server configuration issues as well. If you can access server logs, a PHP error should be logged. You can also contact your hosting company and see if they can identify if errors are being logged.

Did you try the SSL filter to ensure it’s not an SSL issue?

add_filter( 'edac_no_verify_ssl', '__return_true' );

Let me know if you can identify any errors in the log file.

Thanks,

Steve

Hi @oldrup, Thanks for bring this to our attention. I’m able to reproduce the bug and have opened a GitHub issues to have a patch released.

We’ll notify you when it’s resolved. Follow progress here: https://github.com/equalizedigital/accessibility-checker/issues/697

@ptaubman, thanks for the kind words and I’m delighted to here you’ve found the plugin to be a vital tool in helping to make the web more accessible!

@peaktoplate, actually now that I looked at the plugin there is a checkbox on the widget that says “Open links in new window?”. Uncheck that and your links should open in the same window.

https://capture.dropbox.com/j37Unj6BnqnThWHc

Hello @peaktoplate,

I don’t think the simple social icons plugin has a setting or filter to change the target attribute value.

You could use a bit of JavaScript to modify the link target and set it to open in the same window.

Here is an example:

function modify_simple_social_icons_link_target() {
    ?>
    <script>
        document.addEventListener('DOMContentLoaded', function() {
            var socialIcons = document.querySelectorAll('.simple-social-icons ul li a');
            socialIcons.forEach(function(icon) {
                // Set the target attribute to '_self' to open links in the same window
                icon.target = '_self';
            });
        });
    </script>
    <?php
}
add_action('wp_footer', 'modify_simple_social_icons_link_target');

Hi @7thcircle,

Can you give us a little more information to help use replicate the issue. Are you seeing this on a Post or Page? Does the post/page have any content in the editor. Are you using the block editor or the classic editor?

Thanks!

Hi @sc0ttkclark,

We’ll take a look at this and keep you posted.

Thanks,

Steve

Hi @ryzo67,

The plugin doesn’t currently integrate with Zendesk Guide.

Thanks,

Steve

We’re closing this ticket due to inactivity, but we’re here if you need us in the future. Please open a new ticket for further assistance.

Thanks for reaching out to us!

Hi @binku,

1. allow_url_fopen Disabled: The first part of the warning indicates that the PHP directive allow_url_fopen is disabled in your server’s configuration. This directive allows PHP’s file_get_contents() function (and others) to access files over a network using URLs. When allow_url_fopen is set to 0 (disabled), these functions cannot use URL-based file paths, leading to the warning you’re seeing.
2. Failed to Open Stream: The second warning is a consequence of the first. Because allow_url_fopen is disabled, the file_get_contents() function cannot open the URL you’ve provided, leading to a “Failed to open stream” error.

How to Fix:
Enable allow_url_fopen: To resolve these warnings, you need to enable the allow_url_fopen directive in your PHP configuration. You may need to contact your hosting company to help with this.

@jinsley8, we’ve just release a fix for this with version 1.8.1.