Open StephDriver opened 4 months ago
the bracketed email address to evade scraping is awkward when read aloud by screen reader - consider how to handle that. without putting the email address into the HTML.
This is user content.
Need to fix Clean theme, others fix if easy, if not create new issue for later.
i.e. fix: Clean Invalid entries are not reported to the user (try entering random text in the email field, it doesn't react). They are reported to the screen reader user, but only if they navigate back having left the item. They are reported on landing, not on exiting.
Following discussion I am retesting these and reviewing the changes required.
could this be solved by putting the error fixing messages into a sibling of the input, and using something like input:invalid ~ .error-fix
in the css to show/hide the error fixing messages?
this may be useful: https://design-system.service.gov.uk/patterns/validation/
The contact us form is the only part of the front end which requires user input. It does not currently comply with WCAG 3.3 Input Assistance., among other areas of WCAG.
Non-exhaustive list of issues found so far:
*
which gets read out as 'star' - this should either be marked as decorative and the field marked-up as required, or it should be described.Note: the Clean contact form works well with voiceover, but doesn't indicate required fields visually (does tell the screen reader!).