Accessibility Issue

  • With website accessibility lawsuits on the rise, I decided to run a few different accessibility website scanners. The scanner at accessible ( https://accessibe.com/accessscan ) may be the most picky scanner of them all. It’s returning the following issues with the accordion:

    ISSUE 1 –

    Elements that act as buttons but use non-button tags (e.g., span, div, a) should include a role=”button” attribute.

    10 Code snapshots of failed elements

    • <a class=”collapsed” id=”ea-header-6190″ data-sptoggle=”spcollapse” data-sptarget=”#collapse6190″ aria-controls=”collapse6190″ href=”#” aria-expanded=”false” tabindex=”0″ > <i class=”ea-expand-icon ea-icon-expand-plus”></i>
    • <a class=”collapsed” id=”ea-header-6191″ data-sptoggle=”spcollapse” data-sptarget=”#collapse6191″ aria-controls=”collapse6191″ href=”#” aria-expanded=”false” tabindex=”0″ > <i class=”ea-expand-icon ea-icon-expand-plus”></i>

    ISSUE 2 –

    Font icons, SVGs, or images used as spacers, decorations, or when their purpose is already described by other content, should include a role=”presentation” or role=”none” attribute.

    Code snapshots of failed elements

    • <i class=”ea-expand-icon ea-icon-expand-plus”></i>

    I manually updated the script.js and script.min.js files to add these role attributes, but it would be great if you would consider adding them in when you next update the plugin.

    Thanks!

Viewing 1 replies (of 1 total)
  • Plugin Support Pulak Ahmed

    (@pulak00)

    Hi @q4u2,

    Thanks for pointing out the issues.

    The accessibility issues are noted and forwarded to the development team. We will review the issues and fix them accordingly in the upcoming versions of the plugin.

    Your understanding and cooperation would be highly appreciated.

    Thank you.

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