Sharing a few accessibility warnings from plugin elements

  • Resolved Marty

    (@bozzmedia)


    10 years, 7 months ago

    As I’m going through a development site testing accessibility requirements, I noticed a couple errors related to this plugin and wanted to check in to see if they are no big deal, or maybe they should be considered for future updates to the plugin. I got these using Squiz’s HTML_CodeSniffer

    1. Regarding the skiplinks section:
    If this element contains a navigation section, it is recommended that it be marked up as a list.
    <div class="wpa-visible-ltr" id="skiplinks" role="navigation"><a href="#content">Skip to cont...</div>

    2. For the toolbar fontawesome icons:
    Semantic markup should be used to mark emphasised or special text so that it can be programmatically determined.
    <i class="icon icon-font"></i>

    I appreciate any insight or thoughts you might have on these. Many thanks!

    https://www.ads-software.com/plugins/wp-accessibility/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Joe Dolson

    (@joedolson)

    1) I disagree that this is valuable in this context, and won’t be making that change. Additionally, using a list in this context would make it vastly more difficult to provide a method for users to customize the display of their own skiplinks, since the CSS required couldn’t be attached to one single HTML element.

    2) These are not emphasized or special text, so the i element is a reasonable choice for the code. That’s a suggestion based on the usage of i in place of an em, which doesn’t apply here.

    Thanks for noting these, however.

    Thread Starter Marty

    (@bozzmedia)

    Joe, thanks a lot for your thoughtful response, the rationale makes sense. Cheers.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Sharing a few accessibility warnings from plugin elements’ is closed to new replies.