Back to blog

8 common issues a digital accessibility audit reveals – and you could easily avoid

During an accessibility audit, small technical or design issues often create the biggest barriers to use. This article presents eight typical problems that can be avoided during design and development with the right approach and a few considered decisions.

2025-05-22
3 min read
Három ikon az Accessibility Icon Collection ből
Three icons from the Accessibility Icon Collection

Many people assume that if a website “works” and looks visually polished, it is equally accessible to all users. In reality, most sites are full of barriers that are invisible at first glance – unless you try using them with a screen reader, keyboard or other assistive technology.

The purpose of a digital accessibility audit is precisely to uncover these “invisible issues”. Below, we have collected eight common problems that come up time and again during audits – and that are relatively easy to fix.

1. Inadequate contrast ratio – “ahem, as is well known”

“Is it well known? I’m afraid, Safranek, that you are making fun of me. Come closer!” This excerpt comes from the evergreen animated film Catcatcher, although it was not quite about accessibility’s best-known requirement.

Dove-grey text on an ash-grey background? It can look beautiful, but it is not easy for everyone to read. For visually impaired or older users, as well as people browsing on their phones outdoors, it can be a significant barrier.

The WCAG recommendation: a contrast ratio of at least 4.5:1 for normal text. (Web Content Accessibility Guidelines)

1. ábra: Jó és rossz példák háttér és szöveg kontrasztarányára.
Figure 1: Good and bad examples of background-to-text contrast ratios.

2. Missing or incorrect alternative text (alt text)

Screen readers do not “see” images – only their alt text. If this is missing or uninformative (a classic example of uninformative alt text is “image1.jpg”), visual content is lost to people using screen readers.

Every meaningful image should have concise, informative alt text!

2. ábra: Helyettesítő szöveg nélkül: nincs alt= kiegészítés, így a felolvasó nem tud támpontot adni a programról a látássérülteknek.
Figure 2: Without alternative text: there is no alt= attribute, so the screen reader cannot provide visually impaired users with information about the programme.

3. Missing heading structure or incorrect heading order

Headings are important not only visually, but structurally too. A well-formed H1–H2–H3 hierarchy helps screen-reader users jump between sections of content – much as we scan a page with our eyes.

A common mistake is omitting the H1 or displaying headings in an inconsistent order.

3. ábra: Nem jól használt címsorstuktúra – alcímként megjelenő szöveg kódban nem jelölve
Figure 3: Incorrectly used heading structure – text displayed as a subheading is not marked as such in the code

4. The site cannot be used with a keyboard alone

If it is not possible to navigate through a site using the Tab key, users with motor impairments are effectively excluded. This can be particularly problematic in forms, menus and modal windows.

Tip: try navigating the entire site using only Tab and Enter!

5. No visual focus indicator

When an interactive element (such as a button or link) receives keyboard focus, this should also be indicated visually. If it is not visible, users do not know where they are – this is not only an accessibility issue, but also a usability problem.

In the example below, the Services item in the menu does not receive an outline when focused, while the Sales menu item does receive a visual indicator.

4. ábra: Jó és rossz példa fókuszjelzésre
Figure 4: Good and bad examples of focus indicators

6. Buttons and links are not understandable without context

“Details” or “Continue” – but details of what? A user browsing with a screen reader hears only the link, not the context around it.

Solution: use more informative links, such as “Details about our services”.

5. ábra: Kontextus nélküli gomb szöveg
Figure 5: Button text without context

7. Missing labels for form fields

Form fields often have no proper labels, only placeholder text – which screen readers frequently cannot interpret. This is one of the most common barriers to completing forms.

Tip: always use a properly associated <label> element for every field.

6. ábra: hiányzó label mező a bejelentkezésnél
Figure 6: Missing label field on the login form

8. Error messages communicated by colour alone

For example, if you mark an invalid form field only in red, people with colour vision deficiency or users of screen readers will not notice the issue.

Combine colour with a written error message or icons!

7. ábra: Csak színnel jelölt hiányzó adat a keresztnév mezőben
Figure 7: Missing information in the first-name field indicated by colour alone

Summary

These issues are not technically complex, yet they can easily exclude some users. An accessibility audit is not only about complying with legislation: it also supports a better user experience, reaching a wider audience and building your brand.

If you would like to know how accessible your own website is, get in touch about a digital accessibility audit – we can help you find (and fix) hidden barriers.

Next post

Why do company values matter?

Read more