An accessible website is one that people with disabilities can use fully: the content, the features and the forms are available to everyone. Since June 2025 this is no longer just good practice for many companies in the EU, but a legal requirement.
What does an accessible website mean in practice?
- Text alternatives: images and other non-text content have descriptions, so blind and low-vision users with screen readers understand them too.
- Contrast: text and key elements have enough contrast against the background.
- Navigation and structure: logical heading order, descriptive links, visible focus, full keyboard operation.
- Video and audio: captions and transcripts for deaf and hard-of-hearing users.
- Forms: every field has a label, clear instructions and understandable error messages.
What is WCAG?
WCAG (Web Content Accessibility Guidelines) is the internationally accepted guideline for digital accessibility. The European standard (EN 301 549) is based on WCAG 2.1 level AA, so that is the practical benchmark. The newer version 2.2 adds a few criteria, and new projects should already aim for it.
Who has to comply?
Public sector websites and mobile apps have had accessibility rules for years. The European Accessibility Act (EAA), transposed in Hungary by Act XVII of 2022, came into force on 28 June 2025 and extends the requirements to certain products and services of businesses. For websites the most important is e-commerce: if consumers can enter into a contract through your website or app, for example buy, book or subscribe, the law applies to you. Consumer banking, electronic communications, some transport services and e-books are covered too.
Microenterprises providing services are exempt: companies with fewer than 10 employees and an annual turnover or balance sheet total of no more than 2 million euros. If you are unsure, ask for legal advice: this article is for information and is not legal advice.
How can you check your existing website?
- Automated tools: WebAIM WAVE, axe (also as a browser extension) and Google Lighthouse flag typical issues for free.
- Contrast check: for example with the WebAIM Contrast Checker.
- Manual test: go through the site without a mouse, using only the keyboard, and try it with a screen reader (VoiceOver on macOS, NVDA on Windows).
- Content: are there alt texts, captions and clear form labels?
Automated tools find only part of the issues; a full picture needs an expert audit.
Does an accessibility plugin solve it?
No. The "accessibility toolbars" (overlays) added with one line of code are surface add-ons: screen reader users report that they often get in the way, and they do not ensure WCAG conformance. The lasting solution is to build accessibility into the design and the code: semantic HTML, proper contrast, keyboard operation, alt texts. An existing site can be improved step by step after an audit.
How is an accessible new website built?
In design we check the colour system for contrast and design components to work in focus, in error states and when zoomed. In development we use semantic HTML and keyboard operation, and run automated and manual tests before handover.
Updated: 4 November 2026
