• After adding a button I realized that the result didn’t actually behave as a button. For screen reader users there needs to be a little bit more. I don’t know exactly how this is implemented in the particular button code but it seems to me that the following should be considered.

    About role=button and aria and why it matters.
    (Source https://stackoverflow.com/questions/10403138/what-is-the-purpose-of-the-role-attribute-in-html )

    Reason #1. Overriding the role where no host language element is appropriate or, for various reasons, a less semantically appropriate element was used.

    In this example, a link was used, even though the resulting functionality is more button-like than a navigation link.

    <a href="#">Delete</a>
    <a href="#" role="button" aria-label="Delete item 1">Delete</a>

    Screen readers will hear this as a button (as opposed to a link), and you can use a CSS attribute selector to avoid class-itis and div-itis.

    *[role=”button”] {
    /* style these a buttons w/o relying on a .button class */
    }

    ***
    I post this information to plugin author and others only. In the end I decided that I will create my own accessible button but I would love to be able to use su buttons at some point. ??

    Jen

    https://www.ads-software.com/plugins/shortcodes-ultimate/

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Shortcodes ultimate su_button missing accessibility options’ is closed to new replies.