You are viewing limited content. For full access, please sign in.

Question

Question

Forms 11 WCAG 2.1 Accessibility For ADA Title II Compliance

asked on August 19

We're in a push to get all of our web content ready for the ADA Title II accessibility requirement on April 24th, 2026.

ADA Title II Fact Sheet

We have many public forms and running an accessibility scan over any of them returns a few A and AA level infractions that I'm not sure how to fix. I've setup a test form which uses the default template and I still get these errors. Are these issues that are fixed in Forms 12 or are there ways to fix them through the template and JS sections?

Here's the list of issues I've found:

## Form Fields Missing Labels

  • Form field missing a label (A 4.1.2 Name, Role, Value)
    • This applies to all textbox type inputs. Labels exist but the markup is not there to tie them to their input elements. Single line, Multiline, "Other" input on checkbox, "Other" input on radio, dropdown combobox, number, currency, rich text, collection pagination text input, and time input spinbutton.

 

## Form Template

  • Header Logo, no way to add alt text
    • Image missing a text alternative (A 1.1.1 Non-text Content)

 

## Rich Text

  • Hidden element has focusable content (A 4.1.2 Name, Role, Value)
    • Insert Link modal
    • Insert Image modal
    • Insert Video modal
    • Help modal
  • Container element is empty (A 1.3.1 Info and Relationships)
    • More button next to underline
    • More Color button
    • Alignment selector
    • Table dimension selector

 

## Signature

  • Signature image, no way to add alt text
    • Image missing a text alternative (A 1.1.1 Non-text Content)
0 0

Replies

replied on August 19

The form designer in Cloud (released) and Forms v12 (Fall release) will contain a suite of WCAG updates that will address these issues. There are still a couple of minor issues related to some third party libraries we use but they do not impact major components of ADA compliance and are on our radar to fix in the near term.

We do not plan to back port fixes to Forms v11 or classic forms. For classic forms you are able to use JS to resolve any issues your form needs yourself.

If you have any additional questions or concerns post/comment here or email accessibility@laserfiche.com

Thanks!

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.