Accessibility / Semantic Form Markup

[tommarshall]

Hi Guys,

Thanks for the plugin, we're getting a lot of use out of it.

Unfortunately one of our sites has just been through an accessibility review and the markup generated by the form builder was flagged as invalid / inaccessible.

They're required to meet Priority 2 (AA) standards across the board - http://www.w3.org/TR/WCAG10/full-checklist.html

..which involves the following requirements in particular for forms:

• http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-unassociated-labels
• http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-associate-labels

At the moment the form builder doesn't appear to be using tags and I can't find a setting to enable them.

Is this something you'd be looking to resolve in the coming releases yourselves? If not, would you potentially accept a pull request?

The client likes using the plugin so we'd both like to keep using it if we can, but if this is something you feel isn't worth resolving then we'll just have to move this site off the formbuilder and look for alternatives.

I'd rather not put us in a position where we're running a modified version from the code that is being released to the wordpress plugin repo.

Thanks again,
Tom

[warkior]

Hi Tom,

We would be happy to accept pull requests. We've actually had a number of people who have pulled and submitted patches already.

I agree, this is something that should be looked into. It may take some time to complete if you wait on us to do it though, as FormBuilder is somewhat of a side project for us. We use it on many of our sites, and have released it for public use, but usually can only devote time to upgrading it when we're not under time crunches for other deadlines.

If you were willing to update it to more accessible code, we'd be happy to review your changes and merge them into the main branch. If you do submit changes, please just be sure they're well documented so that when we review things we know what's been changed and why.

Have a great day,
James W.