London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
XFORMS Accessibility Report failure
Hi Jonathan,
Xforms elements do get rendered out with labels (whether these labels are output correctly from an accessiblity perspective is another matter). If you look at this example:
http://alloy.uk.episerver.com/About-us/Become-a-reseller/
The Radio buttons have Label elements, and there's also mark-up relating to validation messages.
In terms of making Mandatory fields highly visible, I'm not sure what would be acceptable from a Screen-reader perspective, but I'm guessing you could:
- Hook into the BeforeLoadingForm event and modify the mark-up, as per this example: http://www.frederikvig.com/2010/11/semantic-markup-with-episerver-xforms/
- Apply css to all fields with validation (the validation message is output in a span tag with class "xformvalidator"
- Supply a custom css class when adding the form field within the xform builder.
Hope this helps
Mark
Aug 21, 2013 20:00
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
Hi,
Our site which uses XForms has failed an accessibility report as it says controls such as a Radio button isnt Labelled appropriately and that Mandatory fields are not flagged as mandatory. Is there something that we can set up to:
Many thanks
Jonathan