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

Question

Question

Dinged on submit button and WAVE compliance

Forms
Updated September 6, 2022
asked on September 2, 2022

Hello,

I am having issues with a form meeting compliance with checked with chrome WAVE.

I created an approval form from Design and added a radio button and a few other single fields.  Published it and get an error using WAVE to check ADA compliance.

I get this error on the submit button.  If I hide and build as a custom i still get the error because it's part of the CSS and I also get on the custom built button :(

 

 

The aria-labelledby="submit" was originally "action"

Any assistance would be much needed and appreciated.  The media team is also not understanding why it is not passing :(

Thanks!!

Sue

0 0

Answers

APPROVED ANSWER
replied on September 5, 2022 • Show version history

There is "aria-labelledby="action"" attribute for the submit button in Forms 10.4 and it has been removed in Forms 11 Update 2 already as it is a bug since there is no element with id "action" on the page(The bug ID is 361139 for internal reference), that is why WAVE no longer reports the compliance issue with 11.0.2201.20436. 

We also fixed some other accessibility issues with 11 Update 2: https://support.laserfiche.com/kb/1014352/list-of-changes-for-laserfiche-forms-11-update-2

1 0
replied on September 6, 2022

Thank you so much for responding also!  That was the culprit so I will get with our vendor to schedule upgrade ASAP.  We did go live with the Change Bus Stop form before the weekend and people did use it (YAY Laserfiche) with no issues or Accessibility complaints.   Thanks again and I hope you had a great well deserved long weekend too!!  TTFN!!

0 0
SELECTED ANSWER
replied on September 2, 2022 • Show version history

You're very welcome =)

Forms currently has two designer modes, "Classic" and "Modern" that use meaningfully different UI frameworks with correspondingly different browser code outputs. See the Forms Designer Comparison documentation page for more info. Self-hosted Laserfiche Forms and Process Automation Forms in Laserfiche Cloud also differ slightly, though each has the same two designer modes.

For clarity, I want to quickly note that the "managed cloud" you're referring to is the self-hosted Laserfiche 11 software run and managed by your specific Solution Provider. It's different than "Laserfiche Cloud", our SaaS offering.

I built four versions of a basic form with a form title, description, single line field, radio button field, the default Submit button, and no Theme:

 

None returned any errors or warnings on the Submit button in WAVE for me. I've made all of them Public so you can check them out yourself using the links above.

This would suggest the the issue on your form lies with one or more of the following:

  1. Custom CSS and/or JavaScript currently applied to a Classic form
  2. A Theme (applies CSS) applied to either a Classic or Modern form
  3. Some difference between self-hosted Forms 10.4.x and 11 (Note: this was it, see Xiuhong Xiang's reply)

 

You can also find our latest available product Voluntary Product Accessibility Template (VPAT) reports here: https://www.laserfiche.com/legal/accessibility/

1 0

Replies

replied on September 2, 2022

Hi Sue,

What version of Forms are you using? I checked a few of our internal Forms (11.0.2201.20436) submission pages with the WAVE Chrome extension and it didn't report any findings on the Submit buttons.

0 0
replied on September 2, 2022

Hi Samuel,  Thanks for the quick response!!  Are you on cloud?  And can you send me the code for the button?  This will help us get v11 up quicker.  We are on 10.4 and we are looking at upgrading to 11 however we were considering the managed cloud also and waiting on final numbers.  Just didn't want to change the system to 11 if we were going to the cloud and do it during that down time.  

Thanks bunches!!

0 0
SELECTED ANSWER
replied on September 2, 2022 • Show version history

You're very welcome =)

Forms currently has two designer modes, "Classic" and "Modern" that use meaningfully different UI frameworks with correspondingly different browser code outputs. See the Forms Designer Comparison documentation page for more info. Self-hosted Laserfiche Forms and Process Automation Forms in Laserfiche Cloud also differ slightly, though each has the same two designer modes.

For clarity, I want to quickly note that the "managed cloud" you're referring to is the self-hosted Laserfiche 11 software run and managed by your specific Solution Provider. It's different than "Laserfiche Cloud", our SaaS offering.

I built four versions of a basic form with a form title, description, single line field, radio button field, the default Submit button, and no Theme:

 

None returned any errors or warnings on the Submit button in WAVE for me. I've made all of them Public so you can check them out yourself using the links above.

This would suggest the the issue on your form lies with one or more of the following:

  1. Custom CSS and/or JavaScript currently applied to a Classic form
  2. A Theme (applies CSS) applied to either a Classic or Modern form
  3. Some difference between self-hosted Forms 10.4.x and 11 (Note: this was it, see Xiuhong Xiang's reply)

 

You can also find our latest available product Voluntary Product Accessibility Template (VPAT) reports here: https://www.laserfiche.com/legal/accessibility/

1 0
replied on September 6, 2022 • Show version history

Thank you so very much for taking the time to do all 4 examples, and link the referencing doc.  I have saved that for future reference :)  Oh and cute labels :)

I hope you had a great long weekend and got some very well deserved down time!!  Thank you again and TTFN!! Sue

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

Sign in to reply to this post.

Details
Related Posts
Loading ...