In relation to ChronoForms 4.0 RC3.11:
For optimal accessibility we need to add "for" attributes to form "label" tags in order to associate labels with their respective input fields. At present there is no "for" attribute.
Similarly, validation error messages need to be displayed above the form (visually and in the markup). At present error messages are being dynamically added to an absolutely positioned div that is added to the end of the html document (rather than in close proximity to the form markup). This means that for people using screen readers there's no direct association between the error message and the form that generated the error.
Can you please suggest the best course of action? Can this be achieved easily in ChronoForms without hacking the component code? Is better accessibility in the development pipeline?
For optimal accessibility we need to add "for" attributes to form "label" tags in order to associate labels with their respective input fields. At present there is no "for" attribute.
Similarly, validation error messages need to be displayed above the form (visually and in the markup). At present error messages are being dynamically added to an absolutely positioned div that is added to the end of the html document (rather than in close proximity to the form markup). This means that for people using screen readers there's no direct association between the error message and the form that generated the error.
Can you please suggest the best course of action? Can this be achieved easily in ChronoForms without hacking the component code? Is better accessibility in the development pipeline?