• Resolved Amber Hinds

    (@alh0319)


    Hello,

    We did an accessibility audit on a website that uses your plugin and it had many accessibility problems. Do you have GitHub repo where I can open issues or would it be better to list them here?

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author edo888

    (@edo888)

    Hi,

    Please share more info here, so I can check it for you.

    Not all widget look options are optimized for accessibility. For example you can use flags, language names, language codes, dropdown and their variations and it will be fine. If you are using Globe, Popup or Nice dropdown with flags options, most likely you will see many accessibility issues.

    Thanks! ??

    Plugin Author edo888

    (@edo888)

    Hi,

    I have not heard back from you. Please feel free to reopen this topic when you have time.

    Thanks! ??

    Thread Starter Amber Hinds

    (@alh0319)

    The dropdown option does work much better for accessibility, which is very helpful. Our client switched to that view for their site. Thank you for that tip.

    That said, with the number of active installs on your plugin (and thus the large number of end users that would be engaging with it), it would be great if every view could work for people with disabilities. Many site owners may not know to check for these problems.

    At the least, the plugin should have a warning on the admin settings page that the popup view (and any other views) are unusable for people with disabilities and should not be used for this reason.

    Here are the specific issues that we identified on the site we audited. I am happy to answer any questions that you have.

    1. The trigger to open the modal is incorrectly coded as a link when it should be a <button> and is missing aria that announces when the modal is opened.
    2. When the language switching modal is opened, it is possible to tab through and beyond the modal, leaving it and going back to the page content without closing the modal.
    3. The modal does not close with the escape key.
    4. The X to close the modal is coded as a <span> and not a <button> and there is no way to close the modal without the use of a mouse. A keyboard-only user will be trapped with the modal open and forced to refresh the page in order to close the modal.
    5. The flags included with the language selection are decorative and should have aria-hidden=”true” on them so that they are not read out to screen readers.
    6. The buttons for selecting each language in the modal are incorrectly coded as links rather than buttons.
    7. When the modal is closed, the focus is not returned to the button that triggered it to open.

    Here are some resources that you may find helpful:

    Plugin Author edo888

    (@edo888)

    Thanks for the details, it is a huge milestone to make all widget looks accessible.

    Thread Starter Amber Hinds

    (@alh0319)

    It is work, but not a huge amount. Fixing the items outlined above could probably be done in a half day. Certainly, adding a warning discouraging users from using these views in the meantime could be done faster.

    If you want me to test your fixes, I am happy to do so.

    Plugin Author edo888

    (@edo888)

    It is an open source project, so feel free to submit patches. It does not look like a half day job to me.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Accessibility Problems’ is closed to new replies.