accessibility problem with SVG

  • Resolved Christine SIEMBIDA

    (@chris1511)


    3 years, 3 months ago

    Hello, I tested my site with accessScan and I have an accessibility problem.

    It tells me that “Non-functional icons/spacers should be excluded from assistive technology” for <svg xmlns=”… svg” viewBox=”0 0 448 512″ height=”18″ ><path d=”M224 416c-8.188 0-16.38-3.125-22.62-9.375l-192-192c-12.5-12.5-12.5-32.75 0-45.25s32.75-12.5 45.25 0L224 338.8l169.4-169.4c12.5-12.5 32.75-12.5 45.25 0s12.5 32.75 0 45…

    Requirement: Font icons, SVG or images that are being used as spacers, decorations or their purpose is already described by the content should include a “role” attribute that equals to “presentation” or “none”.

    I searched and found it was in Complianz code.

    Could you help me to resolve this problem, please ?

    Regards, Christine

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Jarno Vos

    (@jarnovos)

    3 years, 3 months ago

    Hi @chris1511,

    You can replace the entire Cookie banner HTML with your own template, and replace the default “close icon SVG” to conform with the requirements of your accessibility tool.

    The details are outlined here in section 3.1 & 3.3, in short, you will end up with the following files:

    /wp-content/mu-plugins/banner.php (a filter to override the current template HTML)

    /wp-content/mu-plugins/cookiebanner/cookiebanner.php (the new cookie banner HTML, which you can now edit to adjust/replace the SVG).

    Kind regards, Jarno

    Plugin Author Aert

    (@aahulsebos)

    3 years, 3 months ago

    Hi @chris1511,

    Do you mean? https://accessibe.com/accessscanv

    If they consider the toggle icons or close icons as non-functional, I would understand the reasoning, but I wouldn’t categorize them as such. I will run the scan to see what they say.

    Thanks, regards Aert

    Thread Starter Christine SIEMBIDA

    (@chris1511)

    3 years, 3 months ago

    Thank you for your prompt response @jarnovos, I’ll look at that, but it bothers me, because your extension is supposed to be WCAG compliant…

    Yes, @aahulsebos this is the test tool here : https://accessibe.com/accessscan

    Plugin Author Aert

    (@aahulsebos)

    3 years, 3 months ago

    Hi @chris1511,

    I fully understand, and we will see what we can do.

    But we’re looking at compliance with WVAG AA based on their documentation, but it’s an ongoing process while we keep optimising our plugin. The SVG icon mention does not hurt WCAG AA, and seems to suggest it has no role for a user. But it does signify a purpose as a toggle, and there is where interpretation comes in play. Especially if you look at the amount of WCAG scans available, and different results that are reported.

    I will have a look at how to remove this mention from your scan, without alarming another. We’re always happy with feedback, it gives us information we didn’t have before:-)

    Thanks, regards Aert

    Thread Starter Christine SIEMBIDA

    (@chris1511)

    3 years, 3 months ago

    Thank you for your involvement @aahulsebos.
    Friendly good evening from France 😊, Christine

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

The topic ‘accessibility problem with SVG’ is closed to new replies.