Accessibility suggestion

  • Howdy,

    From a recent 3rd party audit with credentialed accessibility auditors, they had the following to say about this lightbox plugin:

    Success criteria

    • 4.1.2 Name, Role, Value (WCAG 2.0?A)

    Native Widgets: Link Function & Role

    If an anchor element (<a>) is coded to function as something other than a link, it must have the correct ARIA widget role.

    The image components on this page are coded as links but functions more appropriately as buttons.

    Note: When these components are activated they expose a modal.

    Remediation Recommendation

    Native HTML elements should always be used if possible (eg. use <button> for button functionality).

    If you must use an anchor element to function as a button, for example, add role=“button” to the element and then ensure it can be activated with the spacebar (in addition to the return/enter key)

    —

    For your consideration, since you’re already adding aria labels to the anchor links, could you also consider adding the button role, and possible an event listener for the space button as well to trigger the modal?

    Thank you!

Viewing 1 replies (of 1 total)
  • Plugin Author FirelightWP

    (@firelightwp)

    Hi! Thanks for the input and feedback. We will certainly take a look at this. I know there are some other accessibility improvements we’ve been wanting to make as well.

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