Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @annabelt,

    Out of curiosity, why do hyperlinks contained in an <a> HTML element require role=”button” to be added?

    But if you want, you can do this manually; as you’re able to override the entire Cookie Banner HTML with your own, desired HTML, whereby you can add these attributes as well. Following steps 3.1 and 3.3 in this article allow you to do that:

    https://complianz.io/create-your-own-banner-from-scratch/

    Kind regards, Jarno

    • This reply was modified 10 months, 1 week ago by jarnovos.
    Thread Starter annabelt

    (@annabelt)

    Hi Jarno, thanks for answering. This is the explanation for the errors the accessibility checker has flagged up: https://equalizedigital.com/accessibility-checker/improper-use-of-link/ It is to do with telling screenreaders when a link is being used as a button.

    Thanks for the link.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @annabelt,

    I will raise your suggestion for consideration in a future release of the plugin, but can’t confirm if or when it would be included.

    If you require these attributes in the Cookie Banner right away, you would have to use your own banner template for the time being (as described above); allowing you to make those adjustments in your own template.

    Kind regards, Jarno

    Michael

    (@blackvx)

    Hello, I have the same request as @annabelt with the accessibility checker. I’m going to follow this thread. Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Issues raised in accessibility audit’ is closed to new replies.