• Resolved ImageNazar Hotsa

    (@bugnumber9)


    Hello.

    While auditing a website for WCAG conformance, I noticed a number of issues with your plugin.

    I was able to fix contrast issues with custom CSS, so that’s easy.

    I was also able to fix the redundant alt text issue using the following code snippet:

    <script>
    const updateAltText = () => {
    document.querySelectorAll('.ti-profile-img img').forEach(img => {
    const altText = img.getAttribute('alt');
    if (altText && !altText.includes('profile picture')) {
    img.setAttribute('alt',
    ${altText} profile picture);
    }
    });
    };

    // Initial check in case some reviews are already on the page
    updateAltText();

    // Observe DOM changes in case reviews are loaded dynamically
    const observer = new MutationObserver(() => {
    updateAltText();
    });

    observer.observe(document.body, {
    childList: true,
    subtree: true
    });
    </script>

    However, the biggest problem is that “Read more” and “Hide” semantically aren’t buttons, which means they aren’t accessible with keyboard navigation.

    Please consider making these elements accessible by keyboard navigation, this is a big issue in terms of WCAG conformance.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support ImageLaca

    (@lacadev)

    Hi @bugnumber9

    Thank you for your feedback and the helpful suggestions!

    We’ll include these improvements in one of our upcoming updates.
    Could you please share the WCAG checker tool you used? It would help us a lot.

    Best regards,
    Laca from Trustindex

    Thread Starter ImageNazar Hotsa

    (@bugnumber9)

    Hi.

    I use https://chromewebstore.google.com/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh for checking things like contrast issues, redundant links and alt attributes, etc.

    However, this tool won’t catch the issue with keyboard navigation. Check this out: https://webaim.org/techniques/keyboard/

    This article will help you understand the issue and what needs to be fixed. If in doubt – don’t hesitate to contact me, I can help with further testing.

    Plugin Support ImageLaca

    (@lacadev)



    Thank you!

    • This reply was modified 10 months, 1 week ago by ImageLaca.
    Plugin Support ImageLaca

    (@lacadev)

    Hi @bugnumber9

    We have addressed the issues you mentioned. The element now correctly uses role="button", and we have added a meaningful alt attribute to the image. These changes should improve the accessibility.

    If you encounter any further accessibility issues or have additional suggestions, please don’t hesitate to let us know—we’re always looking to improve.

    Best regards,
    Laca from Trustindex

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘WCAG issues’ is closed to new replies.