---
title: "Why Accessibility Is More Than Contrast and Font Size"
url: "https://www.insideuxdesign.com/en/blog/why-accessibility-is-more-than-contrast-and-font-size"
language: "en"
description: "Accessibility starts with structure, keyboard access and clear language. What matters beyond contrast and how to get started step by step."
published: "2026-10-14T11:46:00+02:00"
updated: "2026-10-14T12:12:20+02:00"
---

# Why Accessibility Is More Than Contrast and Font Size

Contrast and font size are just the tip of the iceberg. Why real accessibility starts with semantics, keyboard access and clear language, and why it benefits everyone in the end.

When people think about accessibility, they usually think of two things: enough contrast and large text. Both matter, no question. But anyone who reduces [accessibility](https://www.insideuxdesign.com/en/glossar/accessibility) to these two misses most of the topic. Real accessibility starts where design becomes invisible: in structure, operability, comprehensibility and the technology underneath.

Accessibility is not a niche topic either. According to the German Federal Statistical Office, just over 7.8 million people in Germany were living with an officially recognised severe disability at the end of 2025, which is 9.4 percent of the population. On top of that, many people without a recognised disability run into barriers in everyday life. This article shows what accessibility is really about and why it benefits everyone in the end.

## The reflex: contrast and size

It is understandable why these two topics are so prominent: they are visible, quick to check and measurable with tools. A contrast checker shows within seconds whether a text meets the minimum ratio. Font size is obvious at first glance.

The problem: if you only optimise contrast and size, you may meet one or two criteria and ignore dozens of others. Accessibility is a system, not a single measure. Understanding the system leads to better websites.

## The four principles of WCAG

The [WCAG](https://www.insideuxdesign.com/en/glossar/wcag) (Web Content Accessibility Guidelines) are the international standard for accessible web content, currently in version 2.2. They are built on four principles that go far beyond the visual. They are abbreviated as POUR, after their initial letters.

### 1. Perceivable

Content must be accessible through more than one sense. Contrast and font size belong here, but so do alternative text for images, captions for videos and a meaningful heading structure. Conveying content through only one sensory channel excludes people.

### 2. Operable

Everything must work without a mouse: via keyboard, switches, eye tracking or voice input. That includes a logical tab order, a visible focus and enough time to read and act.

### 3. Understandable

Text, forms and processes must be clear and predictable. Navigation stays consistent, and error messages explain what went wrong and how to continue.

### 4. Robust

Content must work with current and future technologies, from the [screen reader](https://www.insideuxdesign.com/en/glossar/screen-reader) to the voice assistant. Clean HTML and correctly used ARIA are the foundation for this.

## Semantics: the invisible order

A screen reader doesn’t read pretty layouts, it reads structure. Heading hierarchies, lists, landmarks and properly marked-up forms are to blind people what the visual grid is to sighted people: orientation.

A classic example: a button that exists only as a styled `<div>` is simply not there for many assistive technologies. Only a real `<button>` element, or the right ARIA role including keyboard support, turns a nice-looking click target into something people can actually operate.

Headings are especially important. Many screen reader users jump from heading to heading to get an overview, much like sighted people skim a page. A well-thought-out hierarchy from H1 to H2 to H3 is therefore not SEO fluff but a navigation aid.

## Alternative text: description instead of decoration

Images need a text equivalent. Good alternative text describes what the image conveys, not just what it looks like. A chart needs more than “graphic”: it needs the key message it contains.

Purely decorative images, on the other hand, get an empty `alt` attribute so screen readers skip them. A file name like “image\_123.jpg” as alt text is not a description but a barrier.

## Keyboard and focus: the underestimated classic

Many people use websites without a mouse: because they have motor impairments, because they prefer the keyboard or because their arm happens to be in a cast. A visible focus and a logical tab order determine whether a page can be used at all.

The classic mistake: the focus outline gets removed via CSS because it looks “ugly”. Anyone navigating by keyboard can then no longer see which element is active and loses orientation. A clearly visible, well-designed focus that fits the design is the better way. WCAG requires this in success criterion [2.4.7 Focus Visible](https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html), and the stricter level is described in [2.4.13 Focus Appearance](https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html).

## Forms: labels and error messages

Forms are among the most common barriers on the web. Every field needs a clear, visible label, not just a placeholder that disappears while typing. Error messages explain exactly what is wrong and how to fix it, instead of just saying “error”.

For screen reader users, it is crucial that the label and the field are technically linked. Only then is it clear which text belongs to which input field. The article [Forms Nobody Abandons](https://www.insideuxdesign.com/en/blog/forms-nobody-abandons-12-rules-for-better-form-ux) shows what this looks like in detail. The corresponding WCAG requirement is [3.3.1 Error Identification](https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html).

## Colour: more than contrast

Not everyone perceives colour the same way, and congenital colour vision deficiencies are much more common in men than in women. Colour must therefore never be the only distinguishing feature. A required field marked in red also needs an asterisk or the word “required”. A chart that separates categories only by colour is unreadable for many people. More on this in the article [Color Blindness in UX Design](https://www.insideuxdesign.com/en/blog/color-blindness-in-ux-design-guidelines-and-tools).

Contrast remains important, but it is only part of the colour topic. Just as important is never conveying information through colour alone.

## Motion, animation and time

Animations can be beautiful, but for some people they are a problem. People with a vestibular disorder, meaning a disorder of the sense of balance, can react to large-scale motion with nausea and dizziness. The CSS media query `prefers-reduced-motion` lets you reduce or switch off animations when someone has set this preference in their operating system. The relevant WCAG requirement is [2.3.3 Animation from Interactions](https://www.w3.org/WAI/WCAG22/Understanding/animation-from-interactions.html).

Time limits are another common barrier. Content that disappears automatically after 30 seconds, or a form that resets after two minutes, excludes slow readers, people with cognitive impairments and anyone who gets interrupted along the way.

## Audio and video: captions and transcripts

Videos without captions are useless for deaf and hard-of-hearing people, and for anyone sitting on the train without headphones. Captions are a must, a transcript is a valuable extra. Audio-only content such as podcasts needs a text version.

## Comprehensibility: language can be a barrier too

Accessibility doesn’t end with technology. Clear language, unambiguous form labels and understandable error messages help people with cognitive impairments and learning difficulties, and incidentally everyone who simply wants to get something done quickly.

In practice, that means short sentences, active phrasing, explaining technical terms and spelling out abbreviations on first use. In German-speaking countries, a distinction is made between “Leichte Sprache” (easy-to-read language with strict rules, mainly for people with learning difficulties) and “Einfache Sprache” (plain language with less strict rules). Even plain language makes a big difference.

## Zoom and reflow: flexible layouts

Many people enlarge content significantly. WCAG requires that text can be resized to 200 percent without loss of content or functionality. In addition, content should remain readable without horizontal scrolling at a width of 320 CSS pixels, which roughly corresponds to 400 percent zoom. A good layout then reflows instead of cutting off content. This is not just an accessibility issue but also a matter of responsive design, and it works on smartphones at the same time.

## The legal side

Since 28 June 2025, the Barrierefreiheitsstärkungsgesetz (BFSG), Germany’s implementation of the European Accessibility Act, has been in force. It covers many products and services, including online shops and other digital offerings through which consumers enter into contracts online. Building accessibly from the start saves expensive retrofitting. What the law requires and who it applies to is explained in the article [The BFSG in Practice](https://www.insideuxdesign.com/en/blog/bfsg-in-practice-german-accessibility-act-websites-apps).

## Why this affects everyone

Many impairments are not permanent. Anyone reading on their phone with tired eyes, watching a video without sound on a noisy train or working with a broken arm benefits from accessible design. Experts speak of situational and temporary impairments that sooner or later affect almost everyone.

Accessibility is therefore not a fringe topic but a foundation of good user experience. It forces clarity, structure and simplicity, and that is exactly what benefits everyone in the end, regardless of impairment, device or situation.

## How to start: the most important steps

- **Check the structure:** Are headings logically organised? Are there landmarks and meaningful lists?
- **Test with the keyboard:** Put the mouse aside and navigate using only the Tab key. Can you reach everything, and can you always see where you are?
- **Describe images:** Do all informative images have meaningful alternative text?
- **Check forms:** Are all fields labelled and are error messages understandable?
- **Measure contrast:** Use a contrast checker, but remember that contrast is only the beginning.
- **Add captions:** Do all videos have captions and all audio content a text version?

Which tools help with testing is covered in the article [Accessibility Testing: Tools and Methods for UX Designers](https://www.insideuxdesign.com/en/blog/accessibility-testing-tools-and-methods-for-ux-designers).

## Conclusion

Contrast and font size are important, but they are not the goal. The goal is a web that everyone can use, regardless of impairment, device or situation. Treating accessibility as a system of structure, operability, comprehensibility and technology leads to better products for everyone. And the best time to start is today.

## Sources

- [German Federal Statistical Office (Destatis): 7.8 million severely disabled people live in Germany, press release of 13 July 2026 (in German)](https://www.destatis.de/DE/Presse/Pressemitteilungen/2026/07/PD26_246_227.html)
- [W3C: Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/)
- [W3C: Understanding Success Criterion 1.4.10 Reflow](https://www.w3.org/WAI/WCAG22/Understanding/reflow.html)