Synonyms: Form area
See also: Group, error prevention and correction, required field label, authentication, control elements
Forms have the purpose of the input of data. A form contains one or more form elements.
Presentation
Permalink "Presentation"Only those requirements that are directly related to the form are described below. Requirements regarding interactive elements within the form are described at the respective element.
| No. | Property | Description | Classification | Reference |
|---|---|---|---|---|
| 340 | Resizing | All elements of the form must be perceptible and operable with a font size adjustment of up to 400% (and a resulting display width of 320 px), in the sense that they wrap and do not have to be horizontally scrolled. | Must | EN 301 549: 9.1.4.10, 11.1.4.10 |
| 341 | Error prevention | The form must be designed in such a way that errors can be prevented and corrected (also see Error prevention and correction und Required field label). | Must | EN 301 549: 9.3.3.1 bis 9.3.3.4, 11.3.3.1 bis 11.3.3.4 |
| 342 | Complexity | The form should be clearly designed. The content of complex forms should be grouped programmatically and visually or split into different screens. | Should | DIN EN ISO 9241-125: 5.1.8 |
Operation
Permalink "Operation"| No. | Property | Description | Classification | Reference |
|---|---|---|---|---|
| 343 | Use of the keyboard | It must be possible to access, operate and exit the interactive elements in the form with the keyboard (see Use of the keyboard table). | Must | EN 301 549: 9.2.1.1, 11.2.1.1, 9.2.1.2, 11.2.1.2 |
| 344 | Use of the keyboard | Frequently used buttons on the form (e. g. the Submit button) should be accessible by keyboard shortcut The keyboard shortcuts should be documented in the Help option and application. | Should | DIN EN ISO 9241-171: 9.3.10 |
| 345 | Navigation sequence | The navigation sequence in the form must be designed so that the contents can be perceived in a meaningful sequence and the control elements can be accessed according to their task-appropriate processing sequence. Note: This applies, for example, to the Submit button which must receive the focus at the end of the form. | Must | EN 301 549: 9.2.4.3, 11.2.4.3 |
| 346 | Updates | When focusing and operating the interactive elements within the form, no unexpected change of context may occur. | Must | EN 301 549: 9.3.2.1, 11.3.2.1, 9.3.2.2, 11.3.2.2 |
| 347 | Click area | The click area of the interactive elements in the form should total at least 24 x 24 px (see Use of the pointing device). | Should | WCAG 2.2 |
Use of the keyboard: form
Permalink "Use of the keyboard: form"| Action | Key | Classification |
|---|---|---|
| Focusing of the form (first element) | TAB | Required |
| Desktop: Quick navigation between form areas | F6 | Recommended |
| Submitting the form | ENTER | Recommended |
Programming/interfaces
Permalink "Programming/interfaces"| No. | Property | Description | Classification | Reference |
|---|---|---|---|---|
| 348 | Name | If the form has a visual label, it must be communicated as an Accessible Name. | Must | EN 301 549: 9.4.1.2, 11.4.1.2, 11.5.2.5 |
| 349 | Desktop: Element hierarchy | The parent / child relationships of the elements within the form must be communicated to the Accessibility API. | Must | EN 301 549: 11.5.2.9 |
Information about this article
You are welcome to send feedback by email about our handout!