As requested #1645420-63: Use @aria-describedby for fieldset descriptions here is a list of all open D8 accessibility issues related to the Forms API.
Most of them are about cementing in semantic relationships where possible into FAPI. Checking that there are titles, ensuring form labels are properly managed, allowing customized validation messages, using aria to link descriptive text. Ideally we'd also be able to change the location of the description although I don't think that's required before beta/release of D8.
The FAPI open issues I'm aware of at the moment are:
- #933004: Test that all form elements have a title for accessibility
- #1493324: Inline form errors for accessibility and UX
- #742344: Allow forms to set custom validation error messages on required fields
- #1797438: HTML5 validation is preventing form submit and not fully accessible
- #314385: Make position of #description configurable via the API
- #1645420: Use @aria-describedby for fieldset descriptions
- #2192419: Use a WCAG-compliant fieldset (fieldgroup) for #type radios/checkboxes
- #2126761: The body field summary textarea indicates it has a description with aria-describedby attribute, but the DOM id value points to a non-existent node
- #2124397: Keyboard focus is lost after an AJAX page update
- #1918994: Improve Datetime and Daterange Widget accessibility
- #1734716: File field form label has incorrect id in @for attribute
- #2503453: Increase contrast on inline form error text
I think I've got too many here, but they can be weeded out. I'm not sure which are critical for WCAG 2.0 AA at this point.
Comments
Comment #1
mgiffordComment #2
mgiffordComment #3
mgiffordComment #4
kattekrab CreditAttribution: kattekrab commentedadded #2503453: Increase contrast on inline form error text
Comment #5
tim.plunkettComment #6
mgifford