• Hi,

    Accessibility plugin axe Devtools for Firefox reports two accessibility issues with the floating Pressidium cookie button when scanning the page:

    1. Buttons must have discernible text (Critical)
    <button class="button sm fade-in-up visible">
    <slot name="icon"></slot>
    </button>

    A possible solution would be to add aria-label=”Cookie preferences” to the button.

    2. Interactive controls must no be nested (Serious)

    <pressidium-floating-button role="button">

    It then shows the same code from point 1, saying it is a focusable descendant. The issue is there is a focusable button within a focusable button (due to role=”button” on the outer element). Perhaps the internal element should not be a button, or the role could on the outer element could be widget or none.

    • This topic was modified 5 months, 3 weeks ago by DigitalGdn.
    • This topic was modified 5 months, 3 weeks ago by DigitalGdn.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor overengineer

    (@overengineer)

    Hey, @bkno!

    Thank you so much for taking the time to report this and for providing all the details. That’s very helpful!

    I’ve opened a GitHub issue (#163) to track the accessibility improvements you mentioned. They will be addressed in the next release.

    Thanks for helping us make the plugin more accessible! 🙌

    Plugin Contributor overengineer

    (@overengineer)

    Hey @bkno,

    This was addressed in 1.9.0 which was just released.

    Thanks again for reporting this!

    I’ll go ahead and mark this as resolved. If you run into anything else, let us know 🙂

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

You must be logged in to reply to this topic.