Formidable Forms is Not Accessible

  • Resolved Andrew Nevins

    (@anevins)


    WCLDN 2018 Contributor | Volunteer support

    1 month ago

    We’re preparing to publish an article outlining several WCAG accessibility issues we found in Formidable Forms during recent testing. Before we release it publicly, we wanted to give you a respectful heads-up.

    These affect users who rely on screen readers, autofill, keyboard navigation, and clear feedback, especially those with cognitive, visual, or motor disabilities.

    SC 1.3.1 – Info and Relationships
    Error messages like “Checkboxes cannot be blank” are not programmatically linked to fields. Screen readers don’t announce them in context.

    SC 1.3.5 – Input Purpose
    Fields like name and email lack autocomplete support. This excludes users who rely on autofill due to memory, motor, or language impairments.

    SC 1.4.1 – Use of Colour
    Focus indicator on the submit button is too subtle. Colour contrast between default and focused states is only 1.38:1 (minimum is 3:1).

    SC 1.4.3 – Contrast (Minimum)
    Text contrast fails (minimum is 4.5:1):

    • Submit button (white on #4199fd): 2.91:1
    • Focused state: 4.01:1
    • Error text (red on pink): 3.11:1

    SC 1.4.11 – Non-Text Contrast
    Field borders (grey #d0d5dd on white) have a contrast ratio of 1.47:1 (minimum is 3:1). This makes fields hard to perceive for users with low vision.

    SC 3.3.2 – Labels or Instructions
    Validation rules are not explained. For example, phone fields reject brackets or spaces without telling the user.

    SC 3.3.3 – Error Suggestion
    Vague messages like “Please match the requested format” don’t help users correct input. This affects users with cognitive or motor disabilities.

    Our aim is constructive: to support improvement and collaboration. We’ll be sharing the article shortly via tab-able.co.uk, and we’d be glad to discuss any of the findings with your team.

    Best regards,
    Andrew Nevins
    Founder, Tab-able

Viewing 1 replies (of 1 total)
  • Plugin Support Jonathan Martínez

    (@jonathanenlared)

    1 month ago

    Hey @anevins . We take accessibility seriously and we apprecite your time and effort in sharing this with us.

    I escalated this topic to our dev lead. He shared the following:

    SC 1.3.1 – I created a new issue to resolved this on our end.

    SC 1.3.5 – For email fields, setting the autocomplete attribute is a Pro setting. They can set this manually by updating their [input] shortcode in their custom HTML as well in Lite. As for name fields, I’m bringing it up in a discussion with the rest of the leadership team. In Pro, you can set name field autocomplete options in Text fields or use [input] shortcodes manually in Lite.

    SC 1.4.1, SC 1.4.3, SC 1.4.11 – I’m pretty aware of our contrast errors. This should be possible to fix by customizing their style, but we should consider more accessible defaults or an accessible style template.

    SC 3.3.2, SC 3.3.3 – Yeah, this is mostly up to the customer to customize themselves at the moment. Since the formats are often manually entered and can be pretty complex (using any regex), it’s tough to really address this universally.

    Thank you you again for sharing all this information with us. If there is anything else we can do to make Formidable Forms more accessible, please share it with us.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.

Tags