Task #75591
closed
Epic #75567: Accessibility: As an editor I want to create accessible content which passes the accessiblity tests from WCAG 2.0.
Form: I want to create a WCAG conform form
Added by Andrea Moroni about 8 years ago.
Updated over 5 years ago.
Sprint Focus:
Remote Sprint
Description
As an editor I want to create a form which must pass the accessibility-tests WCAG 2.0.
Acceptance Criteria:
- A warning is displayed if:
- the label of one of the following Basic form element is empty: Text Field, Text Area, Checkbox, Radio Button, Drop Down, Upload Field, Password Field, Submit Button, Reset Button, Button
- the legend of a Predefined form elements is empty
The warning contains the WGAC rule and a direct link to the WCAG tutorial (WCAG rule 3.3.2 - Levela A - https://www.w3.org/WAI/WCAG20/quickref/#minimize-error-cues ) and the link to the W3C tutorials ( https://www.w3.org/WAI/tutorials/forms/ )
Files
- Subject changed from Form: As an editor I want to create a form to Form: I want to create a form
- Category set to Form Framework
- Status changed from New to Needs Feedback
The new form framework is quite cool - carla, can you find out what is missing for WCAG compliance?
- Subject changed from Form: I want to create a form to Form: I want to create a WCAG conform form
What is the state of checking this?
Spoke with Björn, he doesn't see any relevance to the new Form.
I've checked today several forms made with the new Form EXT and found one critical issue on all forms...
Form elements must have labels see attached image
checked with https://www.deque.com/products/axe/ and WCAG Accessibility Audit chrome Plugins
This is the honeypot field. It is used for spam protection. We don't need it for the user. Maybe we find a solution to hide it for normal users. If the user enters data, the form is classified as spam.
But the honeypot field could also get a random label? But question would be, what does screen reader do with this field?
Okay, valid point. But now the tricky question. What would be the text (either for the label or the title attribute)? Wanna call it "Hey spammers" or "Honeypot" or "Don't fill me"? I think it is rather complicated to find an appropriate label which stops human beings from filling it out without telling the bot "c'mon this is a honeypot".
What about using aria-hidden="true"
?
- Sprint Focus set to On Location Sprint
- Sprint Focus changed from On Location Sprint to Remote Sprint
- Tracker changed from Story to Task
- Status changed from Needs Feedback to In Progress
- Assignee set to Björn Jacob
I am changing this issue to "Task" since I cannot do it for "Stories". On it.
- Status changed from In Progress to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF