Web accessibility (WCAG): a 2025 guide
What are WCAG and web accessibility? Who the requirements in force since 28 June 2025 apply to, how to check your site and how much it costs to adapt it.
Web accessibility is no longer a topic just for public offices. Since 2025 more and more private companies have had to make sure that everyone can use their website, and WCAG says how to do it. This guide explains the principles, the requirements and the costs in plain language.
What web accessibility is (and what WCAG is)
Web accessibility means that people with various limitations can also use your site: limitations of sight, hearing, movement, concentration or understanding of content. WCAG is a set of rules that help you design, build and check such a site.
In practice it comes down to simple situations. Someone enlarges the text because their sight is weaker. Someone moves around the site with the keyboard alone because they do not use a mouse. Someone uses a screen reader, a program that reads the content of the page aloud. Someone watches a video without sound and needs captions.
Website accessibility concerns the content, the design, the code and the whole user path. A site can look good and still block some people as early as the contact form. It can have nice colours but contrast that is too low. It can have an extensive menu that cannot be operated with a keyboard.
WCAG, the Web Content Accessibility Guidelines, puts these requirements in order. You will most often come across level AA, because it is a sensible standard for business websites, stores and service sites. Legal and tender documents usually refer to WCAG 2.1, although newer versions of the guidelines exist. If you have a duty to comply, the first thing to establish is which version and which level are required in your case.
Why website accessibility is now compulsory: the legal position in 2025
In 2025 web accessibility became a duty not only for public institutions but also for many private companies in the EU. For public bodies the accessibility requirements for websites and apps have been in force for several years, and on 28 June 2025 part of the business world joined them.
For a long time accessibility was associated mainly with public offices, universities and public institutions. That is changing. EU rules on the accessibility of products and services also cover part of business, especially where the customer buys, books, pays, logs in or uses a service online.
For a business owner this means something concrete: a website is more and more often part of legal compliance. If you run a store, a service platform, a booking system, online payments or a site with a customer account, website accessibility should be in the work plan just like GDPR, the terms and conditions, payments and security.
Who it applies to
The basis is the European Accessibility Act (Directive (EU) 2019/882), implemented in Poland by the Act of 26 April 2024 on ensuring that certain products and services meet accessibility requirements (ustawa o zapewnianiu spełniania wymagań dostępności niektórych produktów i usług). The requirements cover companies offering specific products and services to consumers. The ones mentioned most often are e-commerce, financial services, banking, transport, e-books, apps and sites with a login. The current scope of duties for businesses is described on biznes.gov.pl, the Polish government’s portal for entrepreneurs.
Not every small business website has the same scope of duties. A simple psychologist’s website with a description of services and a contact form is one thing, a WooCommerce store with payments, a basket, a customer account and terms and conditions is another. Microenterprises (usually fewer than 10 people) providing services may benefit from exemptions, but that depends on the type of business and on national law.
Even when the law does not require full compliance from you, accessibility still affects sales and service. If a customer cannot read the offer, get through the form or complete a purchase, the company loses contact with a real person.
When it applies from and what the risks of non-compliance are
The duties under the European Accessibility Act came into force on 28 June 2025. The technical standard for websites is usually WCAG 2.1 at level AA, and for the wider range of products and services the EN 301 549 standard.
The consequences can include user complaints, an inspection, an order to fix the problems, administrative fines or restrictions on offering the service. There is also business risk: abandoned baskets, fewer enquiries, poorer service and a higher cost of fixes later. The exact scope for your company is best confirmed with a lawyer, because the rules provide for exemptions and transition periods.
The most sensible approach is to treat WCAG as a standard for working on the site. First you check where you are. Then you fix the barriers that really block users. Finally you make sure that new content, forms and features do not undo the result.
The four WCAG principles in plain language (POUR)
WCAG rests on four principles: a site should be perceivable, operable, understandable and technically robust. The abbreviation is written as POUR, from the English words Perceivable, Operable, Understandable and Robust.
Perceivable means that the user can take in the content of the page. Text should have good contrast. Images that carry meaning should have alternative text, a short description read out by a screen reader. A video should have captions if it contains speech needed to understand the content.
Operable means that an action can be carried out. The user should be able to get through the menu, the form, the basket and the buttons with the keyboard alone. Focus, the visible marking of the current element, must be clearly visible. If someone presses Tab, they should know where they are on the page.
Understandable concerns language, layout and messages. A form should say clearly what it expects: a first name, an email address, a phone number. If an error appears, the message should explain the problem in plain language. “Validation error” on its own does nothing for a person who wants to send an enquiry.
Robust means that the site works well with browsers, screen readers and other assistive tools. The code should use the right HTML elements. A button should be a button, a link should be a link, and a form field should have a label that is visible to a person and understandable to a program.
The most common barriers on websites and how to spot them
AI-generated image
The most common barriers are contrast that is too low, missing image descriptions, forms without labels, keyboard problems, unclear error messages and videos without captions. Some of them you will see straight away, and some only come out in testing.
Contrast is the first signal. Light grey text on a white background may look delicate, but for many people it will be hard to read. In WCAG 2.1 at level AA normal text should have a contrast of at least 4.5:1 . Large text has more lenient requirements, but it still has to be legible.
Missing alternative text concerns photos, icons and graphics. If a photo is decorative, a screen reader can skip it. If it shows important information, a description is needed. For a product photo the description can be specific: “Black leather ankle boots with a low heel”. For a basket icon the description should say what will happen after a click.
Keyboard support shows whether the site is really usable without a mouse. Open the page, put the mouse aside and use Tab, Shift+Tab, Enter, Space and Escape. If you cannot enter the menu, close a window, click a button or get through a form, that is a barrier.
Forms often fail on labels. A placeholder, the text shown in an empty field, is not enough as a label. It can disappear after a click or after autofill. A person using a screen reader should hear which field they are filling in and what error has occurred.
Video captions are needed by people who are deaf or hard of hearing. They also help when someone watches a video in the office, on a train or without headphones. If a video contains instructions, a customer review or an important description of a service, the lack of captions limits access to the content.
Links such as “click here” are a problem too. When a screen reader reads out only the links on a page, the user hears the same phrase several times and does not know where it leads. A better link says it directly: “See the consultation price list” or “Download the store’s terms and conditions”.
How to make a website accessible, step by step
An accessible website is easiest to make when WCAG is there from the start of the project. That is how I design and build websites, from the mockup in Figma to the code. With an existing site, you start with an audit, a list of barriers and fixes ordered by their impact on the user.
The first step is checking the scope. Working on a brochure site is different from working on a store, and different again from a portal with user accounts. You need to write out the most important paths: arriving on the site, reading the offer, getting in touch, booking an appointment, buying, paying, downloading a document, logging in.
The second step is the design. Already in Figma you can check contrast, text sizes, button states, error messages and the layout on a phone. Accessibility starts before coding, because many problems come from design decisions: a font that is too small, weak contrast, hidden labels or unclear button names.
The third step is the content. Headings should be in a sensible order. Paragraphs should be short. Links should say where they lead. Form messages should be specific. If you use industry abbreviations, explain them the first time they appear.
The fourth step is the code. The developer should use semantic HTML, that is, elements that have meaning for the browser and for assistive tools. A page heading should be a heading, a list a list, a button a button. With more complex elements, such as tabs, accordions, modals or menus, you have to take care of the right roles, names and keyboard support.
The fifth step is testing. Automated tools help, but they do not catch everything. They can point out a missing label, weak contrast or an error in the structure. They will not tell you, though, whether the text is understandable, whether the keyboard order makes sense, or whether an error message really helps the user.
The sixth step is maintenance. Web accessibility can break after a new section, form, banner or plugin is added, or after the colours are changed. That is why it is worth setting a simple rule: every bigger change on the site goes through a quick test of contrast, keyboard, forms and screen reader.
How to check the accessibility of your site
AI-generated image
You check the accessibility of your site by combining automated tools, a keyboard test and a test with a screen reader. The result from a single tool is not enough to assess WCAG compliance.
To start with you can use WAVE. This tool shows errors, warnings, the heading structure, alternative text and contrast problems. It works well for a quick review of a single page, for example the home page, the contact form or a product page.
Lighthouse in the Chrome browser gives an accessibility report. It shows selected technical problems, such as buttons without names, contrast errors or incorrect form elements. Treat the percentage score as a signal, not a certificate. A site can have a high score and still have a serious problem in the basket or a form.
Screen readers let you check how the site works for people who are blind or partially sighted. On Windows, NVDA is often used. On Mac and iPhone there is VoiceOver. The test consists of going through the site without relying only on the visual layout: you listen to the headings, links, buttons, forms and messages.
The keyboard test is simple and very effective. Go through the whole user path without a mouse. Check whether you can see which element is selected, whether the order is logical, whether you can open and close the menu, whether a modal traps you in place, and whether the form can be sent.
For colours, use contrast tools, for example the browser’s built-in features or design add-ons. Check normal text, text on buttons, links, error messages and elements on a coloured background. Judging “by eye” easily fails, especially with shades of grey, green and light pastels.
The best picture comes from a combined audit: automated checks, manual tests, a code review, a walk through the most important processes and a list of fixes with priorities. That way you know which errors are cosmetic and which block contact, a purchase or access to information.
How much it costs to adapt a site to WCAG
The cost of adapting a site to WCAG depends on the size of the site, the technology, the number of forms, the quality of the code and the scope of compliance required. Indicative ranges are helpful, but without an audit only an order of magnitude can be given.
A small brochure site with a few subpages and a simple form may need fixes costing from a few hundred to a few thousand zloty, if there are not many problems. This applies when you need to fix contrast, alternative text, headings, field labels and a few interactive elements.
A larger business website on WordPress can cost from a few thousand to between ten and twenty thousand zloty, if there are custom sections, many types of subpages, integrations, a search engine, forms and PDF documents. In this kind of work more time goes on testing, fixing components and checking that a change in one place does not break another part of the site.
An online store is usually more demanding. You have to check the product list, filters, the product page, the basket, the customer account, payment, error messages, terms and conditions and transactional emails. With WooCommerce or another store platform the cost can run from a few thousand to a few tens of thousands of zloty, depending on the scale and the quality of the current build.
Content and documents have to be counted separately. Alternative text for hundreds of photos, fixing PDFs, video captions and simplifying difficult messages is editorial work, not just a change in the code. On a large site it is the content that can take the most time.
The cheapest way is to include WCAG in a new project. Then the designer chooses contrast, element states and form layouts from the start, and the developer builds the components to a good standard. Repairing a finished site tends to cost more, because it means undoing earlier decisions.
The most common mistakes and myths about accessibility
The most common mistake is treating accessibility as a one-off checklist to tick off. WCAG helps check quality, but web accessibility also needs good design, sensible content, sound code and regular testing.
The first myth says that an accessibility plugin is enough. Such a plugin can add a contrast switch, text enlargement or a settings panel, but it will not fix a badly built form, missing labels, a wrong heading order or a basket that cannot be operated with a keyboard.
The second myth says that accessibility spoils the look of a site. A well-designed site can be attractive, modern and WCAG-compliant. It needs decisions based on legibility: adequate contrast, clear button states, a logical layout and predictable interactions.
The third myth says that accessibility concerns only blind people. They are one group of users, but the scope is wider. Accessibility helps people who are partially sighted, people who are deaf, people with limited mobility, with dyslexia, with cognitive difficulties, after injuries and with temporary limitations, for example after breaking an arm.
The fourth myth says that an automated report is enough. Tools such as WAVE and Lighthouse are needed, but they detect only part of the problems. They cannot fully assess the sense of a message, the quality of alternative text, how comfortable it is to get through a purchase or whether the content is understandable to someone outside the industry.
The fifth myth says that WCAG concerns only large companies. The scope of legal duties varies, but barriers on a site affect customers regardless of the size of the company. A small practice, a local restaurant, a wedding photographer or a store with a niche product can also lose an enquiry because of a form that cannot be used.
The sixth myth says that a site fixed once stays accessible for ever. A new banner, plugin, promotional section, popup or change of colours is enough for new barriers to appear. That is why website accessibility should become part of the ordinary process of maintaining a site.
FAQ
Does my small company have to have a WCAG-compliant website?
It depends on the type of business, the services and the rules that apply to you. Since 2025 accessibility requirements have applied to many services and products on the EU market, but the scope for a specific company has to be checked separately. Even without a legal duty it is worth removing the barriers that block contact or a purchase.
Does WCAG 2.1 mean a site has to be ugly and very simple?
No. A site can be attractive, extensive and accessible. You have to watch contrast, legibility, keyboard support, clear forms, image descriptions and correct code. Good design helps meet WCAG without giving up the character of the brand.
Does an automated score of 100 in Lighthouse mean WCAG compliance?
It does not give full certainty. Lighthouse checks part of the technical problems, but it will not replace a manual keyboard test, a screen reader and an assessment of the content. A high score is a good signal, but it is not a full accessibility audit.
Which matters more: fixes in the code or in the content?
Both. The code decides whether forms, buttons, menus and messages are understandable to assistive technologies. The content decides whether a person understands the offer, the error, the instructions and the next step. With WCAG 2.1 these areas have to work together.
Where do I start if I have no budget for a full implementation?
Start with the most important paths: the home page, the offer, contact, the form, the basket, payment and login, if you have them. Check contrast, headings, keyboard support, form labels and error messages. These fixes often remove the most painful barriers.
Does accessibility have to be checked after every change on the site?
After a bigger change, yes. A new section, form, popup, banner, plugin or a rebuilt menu can introduce new problems. A short test after a release is cheaper and quicker than a big audit only once users start reporting errors.