WCAG for Design

A red triangle with eyes, a mouth and a hearing aid. It wears a crooked cap with blue paint on it and holds a paintbrush in its hand. It symbolises designers.

Filter:

The WCAG criteria

Short description:

A website must also be accessible for people with color vision deficiencies. If information is conveyed only through color (for example, a green dot = active, red = inactive), additional graphical elements or text must be provided.

 

Illustration of a website shown in grayscale with the text 'This design also works in black and white.' Below it is an illustration of a round character looking upward with a questioning expression.

Short description:

All graphical elements that are interactive (e.g., icon buttons) or important for understanding must have a minimum contrast of 3:1 with the background.

 

Illustration comparing poor and good contrast of an icon-like figure. On the left, a pale yellow figure on a white background is marked with an X to show insufficient contrast. On the right, a black figure on a white background is marked with a checkmark to show sufficient contrast.

Short description:

All text, including body text, labels, and placeholders, must have sufficient contrast with the background. The minimum contrast ratio is 4.5:1 for text smaller than 24px and 3:1 for text 24px or larger.

 

Two text samples are shown: one in very light color with insufficient contrast, and one in black with sufficient contrast.

Short description:

Important information shouldn’t be presented solely as text within images. Users can’t adjust this text to their needs, and assistive technologies cannot read it.

 

Text in the image reads: *There shouldn’t actually be any text in this image, sorry!!!* Next to it is a green figure looking confused and saying: Typical!

Short description:

Automatically starting animations lasting longer than 5 seconds must be pausable, stoppable, or able to be hidden.

 

Illustration of a slider on a webpage that includes a pause button to stop the automatic sliding.

Short description:

A website should not include elements that flash more than three times per second, such as rapidly blinking GIFs or flickering videos. Flashing elements that are small enough (around 148×148 px) are considered acceptable.

 

Illustration of a triangular character with swirling eyes and shaking arms, suggesting dizziness from rapid flashing.

Short description:

Users must be able to navigate a website’s content using the keyboard (Tab key) in a logical order. The tab order should generally follow the visual layout.

 

Illustration einer Webseite mit nummerierten Fokus-Stationen: Zuerst wird das Logo fokussiert, danach die Navigation, dann der Button.

Short description:

Subpages of your website must be accessible in multiple ways. In addition to navigation menus, provide options such as a search function or a sitemap.

 

Illustration of a menu icon paired with a magnifying glass icon, and below it another menu icon paired with a sitemap icon.

Short description:

Interactive elements, such as buttons and links, must have a visible focus state. A recommended approach is a two-colored focus outline, with white and black lines, ensuring it is clearly visible on all backgrounds.

 

Illustration of two buttons: the first shows a visible focus outline, and the second has no focus outline, indicating an accessibility error.

Short description:

Interactive elements, such as buttons or links, must have a clickable area of at least 24 × 24 px that does not overlap with the clickable area of other elements.

 

Two icon buttons are shown. The first is 16 by 16 pixels and too small to use comfortably. The second is 24 by 24 pixels and large enough to be accessible.

Short description:

The navigation elements on your website, such as menus, breadcrumbs, and search, must consistently be located in the same place to make navigation between subpages easier.

 

Text on the image says: Navigation isn't at the same place! Below it are two web pages, one showing the navigation at the top and the other showing the navigation at the bottom.

Short description:

If a website provides help, it should be easy to find and consistently located on all subpages. Help can include elements such as chatbot or simple contact information in the footer.

 

Illustration showing two webpages labeled Page 1 and Page 2. Each page displays a chatbot bubble saying How can I help you? with the same friendly face icon beside it, positioned in the same place on both pages. This demonstrates that help features should be easy to find and consistently located across all subpages.

Short description:

If errors occur on a website, they should be easy to identify and not indicated by color alone. Text describing the error must also be provided.

 

A form that displays an error message as text.

Short description:

Form fields should include a clearly visible label, ideally using the <label> tag. This label should always remain visible and not disappear. Placeholder text by itself is not an adequate substitute for a proper label.

 

Two form fields are shown: the first has no label, while the second includes a proper label.

Short description:

Error messages should be as specific as possible, providing clear guidance to help users understand and fix the issue.

 

Illustration of a password change form with an incorrectly entered password. Below it is an error message that says: Password too short. It must be at least 12 characters long!

Short description:

To prevent errors during important interactions or transactions, users should have the opportunity to review their data before sending. Alternatively, they should be able to confirm the action again or have the option to undo it.

 

Modal dialog stating: *You have successfully transferred 1 million to Gehirngerecht.* Below are two buttons: the left one allows undoing the action, and the right one confirms it with *They deserve it!*

Choose your role:

Back to all WCAG criteria