Support » Plugin: MC4WP: Mailchimp for WordPress » Small change for accessibility

  • Resolved brucelawson

    (@brucelawson)


    Great plugin.

    The sign up form fails Web Content Accessibility Guidelines (WCAG 1.3.1, WCAG 3.3.2) because the input field for the email address isn’t associated with a label. Simply tweak the current code so that the input field is a child of the label element:

    Currently:
    [label]Email address: [/label]
    [input type=”email” name=”EMAIL” placeholder=”Your email address” required=””]

    improved:
    [label]Email address:
    [input type=”email” name=”EMAIL” placeholder=”Your email address” required=””]
    [/label]

    I’d make the change myself if it were GitHub rather than Subversion.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hey Bruce,

    Thanks for reaching out to us.

    We are aware of this, but because our plugin adds code and not some UI element, we decided to keep this as simple as possible so the admin can update the code as required.

    I understand this might not be the response you are looking for. We do want to make our plugin as accessible as possible but we are currently also trying to have a balance between what we automatically do and how simple it can stay to allow easy editing.

    Thanks Harish.

    I’m delighted to hear “We do want to make our plugin as accessible as possible”/

    My proposal adds not 1 byte to the plugin’s payload, but merely changes the nesting of the default. Anyone able to update the code now would be easily able to update my suggested change, because it’s the same code.

    How is making it not accessible “making it as accessible as possible”? The current code is completely inaccessible and probably used on thousands of sites. (Congratulations for having a highly successful product!)

    Please make it accessible by default. Make the web a better place.

    michaelspellacy

    (@michaelspellacy)

    I think accessibility should come before conviencence and as was said above, the proposed change seems simple enough as to not be a hardship for editors.

    I also saw the same error. I previously tinkered with the code, but it is not convenient with every plugin update.

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