PragaWeb

Websites

Web accessibility

In short

Web accessibility makes a website usable by everyone, including people with disabilities. PragaWeb audits and fixes websites and online stores to WCAG 2.1 and 2.2 level AA, including for the European Accessibility Act.

Talk about your project

Web accessibility is what makes a website, online store or application usable by everyone, including people with visual, hearing, motor or cognitive disabilities and those who use screen readers or only a keyboard. PragaWeb helps companies and organisations audit and fix their websites to WCAG 2.1 and 2.2 level AA, the international reference standard, including in light of the European Accessibility Act.

An accessible website is not just a box to tick: it is clearer for everyone, works better on mobile and is better understood by Google and AI engines. The PragaWeb website itself is designed to WCAG 2.1 AA.

Web accessibility: what the law says

Here is a brief overview for information only. It is not legal advice: to assess your specific situation, we recommend also speaking to a lawyer or your own adviser.

  • European Accessibility Act (EAA): Directive (EU) 2019/882 sets accessibility requirements for a range of digital products and services, including e-commerce services, banking services, e-books and some transport services. EU countries have transposed it into national law (in Italy with Legislative Decree 82/2022), and the obligations have applied since 28 June 2025, with some transitional periods. Microenterprises providing services, meaning fewer than 10 employees and annual turnover or balance sheet total of no more than 2 million euros, are generally exempt from the service obligations.
  • Italy’s Stanca Law (Law 4/2004): it applies to public administrations and, under more recent rules, to private organisations with average turnover above 500 million euros over the last three years that offer services through websites or apps. Among other things, it requires an accessibility statement following the AgID guidelines.
  • Technical standards: the European reference is EN 301 549, which for the web refers to the WCAG 2.1 level AA criteria. WCAG 2.2 adds useful criteria, for example on visible focus and target size, and is worth taking into account now.

Signs your website has accessibility issues

  • You cannot complete a purchase or a form using only the keyboard.
  • Images have no alternative text describing their content.
  • Some text has poor contrast against its background.
  • Form fields lack clear labels, or error messages are not announced by screen readers.
  • You use an “accessibility toolbar” or a plug-in that promises automatic compliance: on their own they do not fix problems in the code.
  • You have never published an accessibility statement.

What our web accessibility service includes

  • Accessibility audit: a review of the site against WCAG 2.1 and 2.2 level AA, with automated tests and, above all, manual checks on the key pages and journeys, such as the checkout or the contact form.
  • Keyboard and screen reader testing: we browse the site as someone using NVDA, VoiceOver or only a keyboard would, to find the barriers automated tools miss.
  • Prioritised report: each issue is explained in plain language, with the relevant WCAG criterion, its impact on users and the recommended fix.
  • Remediation: we fix code, components, contrast, forms and content, on your current site or on your new one.
  • Accessibility statement: we help you draft the statement and the information on your service’s accessibility, including any known limitations and a contact channel for feedback.
  • Editor training: the people who update your site learn to write alternative text, use headings correctly, create descriptive links and publish accessible documents.

How we work

  1. Initial review: we look at what kind of site you have, which services you offer and which pages are critical.
  2. Audit: automated and manual tests on a representative sample of pages and journeys.
  3. Action plan: priorities, timelines and costs, split into phases.
  4. Fixes: changes to code and content, starting with the issues that block users.
  5. Final check: we repeat the tests to confirm the fixes.
  6. Statement and training: publishing the statement and supporting your editors.
  7. Monitoring: periodic checks, because every new piece of content can introduce new issues.

Check Accessibile, our tool in development

We are developing Check Accessibile, our product for checking website accessibility and keeping issues under control over time. We use it to support manual testing, which remains essential.

Timelines and costs: what they depend on

  • the size of the site and the number of different page templates;
  • the technology used and whether the code can be changed;
  • complex features such as a cart, private area or payments;
  • the amount of PDF documents and multimedia content;
  • whether the work concerns an existing site or a new corporate website.

An audit usually takes from a few days to a few weeks; remediation time depends on the findings. For online stores we start with the purchase journey, which is at the heart of the EAA obligations.

Why choose PragaWeb

  • Accessibility built into the code, not left to plug-ins or overlay toolbars.
  • One contact for audit, development and training.
  • Continuity over time through our maintenance and support service.
  • Plain language: we explain what to change and why, without jargon.

Want to know where your website stands? Request a web accessibility audit and we will tell you where to start.

Frequently asked questions

Does my online store have to comply with the European Accessibility Act?
Generally yes, if you sell online to consumers in the European Union and are not a microenterprise. There are exceptions and transitional periods, however, so it is worth checking your case with a lawyer; we take care of the technical side.

Is installing an accessibility plug-in or toolbar enough?
No. These tools may help some people, but they do not fix problems in the code such as missing labels, focus order or forms that cannot be used with a keyboard. WCAG conformance requires changes to the site itself.

What is the difference between WCAG 2.1 and WCAG 2.2?
WCAG 2.2 includes almost all the 2.1 criteria and adds new ones, for example on visible focus, target size and authentication. The European standard currently refers to 2.1 AA, but working to 2.2 makes your site more robust.

What is an accessibility statement?
It is a public document describing the site’s level of accessibility, any known limitations and how to report problems. In Italy it is mandatory for public bodies and organisations covered by the Stanca Law, and it is good practice for everyone.

How long does an accessibility audit take?
Usually from a few days to a few weeks, depending on the size of the site and the number of journeys to test. At the end you receive a report with priorities and fixes.