The 103 tips have a general structure. I start with general knowledge of digital accessibility, then move to tips for design and content creation, and finally to development. However, some of the tips are not entirely specific to one role and are relevant to everyone.
These tips are a subjective compilation of accessibility, web design, and user experience criteria. Not all the 103 points are WCAG-relevant. You can find out what actually applies to WCAG here: WCAG criteria.
General tips on accessibility
- Accessibility is mandatory: Be ready! (More on the laws).
- See how people use assistive technologies to strengthen your “why” and increase your motivation. Watch Apple’s video on accessibility. Watch the video series on assistive technologies in action.
- Gain hands-on experience with screen readers, voice control, and tab navigation. (Watch our screen reader demonstration with a blind person).
- Train your team – accessibility is something you can’t finish. (More about accessibility in teams).
- Get the accessibility plan. (Accessibility free plan) (English available on request)
- Know the most important KPI for digital accessibility: fewer bugs in production.
- Make sure everyone knows: fewer bugs, lower costs.
- Understand the opportunity: Becoming accessible (by 2023/2024) strengthens your brand image.
- Make inclusion a core value. (Learn more about why inclusion is the only future).
- Establish an accessibility team within the company.
- Create more empathy for people with disabilities. (See the importance of awareness campaigns).
- Settings in your operating system make overlay tools unnecessary. (Learn more about your operating system settings).
- Overlay tools do not replace accessible programming.
- Don’t waste your money on certifications.
- Never forget: HTML is inherently accessible.
Accessible design tips
- Make accessibility one of your top three priorities when making design decisions.
- Get inspired by other accessible designs. (If you’d like to register for free, there’s a great case study on accessible design by the company Wise on Medium. )
- Maintain a text-to-background contrast of at least 4.5:1.
- Keep the contrast between buttons/controls and the background at least 3:1.
- Use these tools to test contrasts: WebAIM’s contrast check and APCA’s contrast check.
- Give your logo the right contrast (no requirement, but it looks nice anyway!).
- Do not make body text smaller than 16 pixels – 18 pixels is better.
- Do not make buttons and other interactive elements smaller than 24 by 24 pixels – 44 by 44 is better.
- Avoid sliders.
- Avoid modals.
- Make your layouts responsive.
- Maintain consistency in your layout. (Examples: Always place the navigation, chatbot, or help section in the same location.)
- Design buttons with a clearly recognizable focus state.
- Don’t just use color to display important information. (Your design should also work in black and white.)
- In particular, clarify error messages with icons and text, and not just with color.
- Offer an additional search function as an alternative to navigation.
- Label your icons. (Not everyone knows that three lines represent a menu.)
- Avoid flashing elements.
- Choose a font where the letters are easily distinguishable.
- Avoid centering long texts.
- Avoid completely white backgrounds.
- Avoid using all-black text (#000000) on a white background.
- Avoid sticky navigation.
- Avoid strong blue tones.
- Break down complex forms into smaller steps. (More about forms).
- In a form, select only the optional fields. (Learn more about why you should only highlight optional fields.)
- Use links as links and buttons as buttons. (More about links and buttons).
- A dark mode is nice, but not necessary – your laptop can do it automatically. (More on accessibility in operating systems).
- Do not use red-green color to visualize important information (10% of men are red-green colourblind).
- Document your design decisions regarding digital accessibility. (Example: Different element states or different color combinations.)
Tips for creating accessible content
- Give links meaningful labels (e.g., “To the contact form” instead of “Click here” ). More on link text.
- Give images alternative text.
- Write alternative text correctly. (See our article about alt text).
- Label your icons.
- Never write long texts using only capital letters.
- Avoid alt text for purely decorative elements (lines/shapes/images and illustrations without meaning).
- Tag foreign words in the correct language. (More about the HTML lang attribute)
- Give each subpage of your website a meaningful title.
- Avoid using GIFs (yes, I know, sorry!).
- Stick to the correct heading structure (H1, H2, H3, H4, and so on).
- Be consistent in your word choice. (Don’t use “account area” once and “your area” another time .)
- Do not write text on your images – assistive technologies cannot read this text.
- Do not describe elements solely by their appearance (example: the yellow button).
- Do not describe elements solely by visually perceptible properties (example: the button in the bottom left).
- Create a sitemap as an alternative to navigation.
- Use the HTML element “Blockquote” for quotations.
- Write captions for videos.
- Create audio descriptions for videos (if needed).
- Make captions available for live broadcasts.
- Avoid tables. If you must use them, give them the correct HTML structure.
- Give your icons alt text if they trigger an action.
- Make your PDFs accessible. (Learn more about creating accessible PDFs).
- Avoid emojis.
- Avoid placing links directly within paragraphs. This disrupts the reading flow for screen readers. Place links after the paragraph.
- Use <strong> to make text bold.
- Use <em> to italicize text.
- Create an accessibility statement. (More about accessibility statements).
Accessible development tips
- Use HTML landmarks. (More on proper HTML structure).
- Make animations pauseable if they are longer than 5 seconds (this also includes automatic sliders).
- Make sure that text is not obscured by other elements when zooming in.
- Include skip links. (WCAG criterion 2.4.1: Skippable sections).
- If you have multiple navigation devices, name them. (More on ARIA labels for navigation devices)
- Don’t let notifications disappear automatically.
- Do not automatically log users out after a set period.
- Give users enough time to make their decisions.
- Ensure your website/app is fully keyboard accessible. (WCAG criterion 2.1.1: Keyboard).
- Test your page with a screen reader.
- Allow users to undo critical entries.
- Label each form field.
- Use the HTML autocomplete attribute for form fields (WCAG criterion 1.3.5: Determining the purpose of the input).
- Set the correct language for your website. (More about the correct language in HTML).
- If I can do something by moving my finger (example: pulling something), there needs to be an alternative for people who can’t do that (example: a button to click).
- Link your form fields to their labels using code. (More on accessible forms.)
- If you use captchas, give users several alternatives.
- Use the correct ARIA elements for your self-built components. (More about ARIA labels)
- Save user input (e.g., in form fields) so they don’t have to re-enter it later.
- Provide meaningful error messages for forms.
- Avoid making me remember my login details. (Enable autofill or send a login email.)
- Test your digital product with people with different disabilities.
- Do not use HTML tables for your layout.
- In an error message, also describe how to fix the error.
- Make sure that screen readers process your elements in a logical order.
- Use ARIA Live Region to communicate changes. (Learn more about Live Region).
- Use bookmarklets to test HTML. (How to use Bookmarklets).
- Use libraries for development. (Example library from Kolibri).
The most important thing!
- See the WCAG criteria for more explanations. (See WCAG criteria overview).
- Join one of our workshops! (View our workshops) (View our workshops).
- Tell everyone how valuable digital accessibility is and why they should all participate!