Web Accessibility Tutor

Web forms are frequently used. Typical examples are for contact or ordering purposes. In addition to general information that the screen reader reads, additional user interaction is required. For forms to be perceivable, operable, robust, and, above all, understandable, several aspects must be considered during implementation. Form fields that are visually meaningful and can be operated with the mouse are not automatically implemented semantically correctly and can only be accessed using the keyboard. 

The following aspects are particularly important:

• Ensure keyboard operability
• Correct semantic creation of labels that are programmatically linked to the form fields
• Mandatory fields must be labeled accordingly
• Consider groupings (e.g. for radio buttons)
• Provide instructions accordingly and link them to the form fields (e.g., if a specific data format is required)
• Highlight error messages and make them programmatically detectable
• Create extensive forms over several pages
• Name, role, and value should always be programmatically determinable

The ARIA Authoring Practices Guide (APG) provides patterns for correctly implementing various interactive content elements.
An overview of these patterns can be found at the following URL: https://www.w3.org/WAI/ARIA/apg/patterns/

In general, however, ARIA should be used with caution. Please read the ARIA section under Introduction.

The tutorials provided focus primarily on-screen reader-related aspects such as comprehensibility and usability. However, visual criteria are also considered in some cases.