We are currently running a site in Umbraco 13.5.2 and Umbraco Forms 13.2.5. Any forms using bootstrap theme which contain single choice radio buttons fail WCAG 2.2 with missing form labels for radio buttons and multiple form labels on the data consent. If i download the theme files i can fix the issue with the radio button having no labels by adding a for attribute to the FieldType.RadioButtonList.cshtml. However it doesn't fix the issue of multiple labels on data consent. Can anyone advise on how i fix this issue please?
Yes! I love to see when people are thinking of accessibility.
It sounds like you're already on the correct track and doing what we do which is - download the forms files and update with custom markup theming.
We have a custom theme with a number of accessibility tweaks (not many actually because Umbraco forms are actually the best we've used from any CMS over the years!) in addition to hooks specific to our front-end styling.
There are rendering files for each fieldtype, as you noted in reference to the radio buttons. There is one in there specific to FieldType.DataConsent.cshtml .
We don't use this particular field so don't have any update to share - but you sound qualified to handle the tech and are just looking for confirmation you're already on the right path.
I will note that I recall there being some overlap with the orchestrating Form.cshtml file as some labels//legends are set there, not only in the FieldType.{*}.cshtml
You are right in the fact that there is an overlap and one of the missing form labels is in Form.cshtml. I have downloaded that file (umbraco-forms-default-theme-13.3.0\Partials\Forms\Themes\bootstrap3-horizontal\Form.cshtml), however I am now unable to run the solution and getting the following error:-
'FormViewModel' does not contain a definition for 'ShowPagingOnMultiPageFormsAtTop' and no accessible extension method 'ShowPagingOnMultiPageFormsAtTop' accepting a first argument of type 'FormViewModel' could be found (are you missing a using directive or an assembly reference?)
I have also tried the default form.cshtml.
Umbraco forms are not WCAG2.2 Compliant
We are currently running a site in Umbraco 13.5.2 and Umbraco Forms 13.2.5. Any forms using bootstrap theme which contain single choice radio buttons fail WCAG 2.2 with missing form labels for radio buttons and multiple form labels on the data consent. If i download the theme files i can fix the issue with the radio button having no labels by adding a for attribute to the FieldType.RadioButtonList.cshtml. However it doesn't fix the issue of multiple labels on data consent. Can anyone advise on how i fix this issue please?
Yes! I love to see when people are thinking of accessibility. It sounds like you're already on the correct track and doing what we do which is - download the forms files and update with custom markup theming. We have a custom theme with a number of accessibility tweaks (not many actually because Umbraco forms are actually the best we've used from any CMS over the years!) in addition to hooks specific to our front-end styling.
There are rendering files for each fieldtype, as you noted in reference to the radio buttons. There is one in there specific to
FieldType.DataConsent.cshtml. We don't use this particular field so don't have any update to share - but you sound qualified to handle the tech and are just looking for confirmation you're already on the right path.I will note that I recall there being some overlap with the orchestrating
Form.cshtmlfile as some labels//legends are set there, not only in theFieldType.{*}.cshtmlHope this helps!
Hi Damian,
You are right in the fact that there is an overlap and one of the missing form labels is in Form.cshtml. I have downloaded that file (umbraco-forms-default-theme-13.3.0\Partials\Forms\Themes\bootstrap3-horizontal\Form.cshtml), however I am now unable to run the solution and getting the following error:- 'FormViewModel' does not contain a definition for 'ShowPagingOnMultiPageFormsAtTop' and no accessible extension method 'ShowPagingOnMultiPageFormsAtTop' accepting a first argument of type 'FormViewModel' could be found (are you missing a using directive or an assembly reference?) I have also tried the default form.cshtml.
Any help would be greatly appreciated. Thanks
is working on a reply...