Service · Accessibility

An accessibility audit that also stands up the statement.

On most sites the accessibility statement is missing, or it says “partially compliant”. The audit tells you what is missing, in what order it can be fixed, and what can go into the statement. To EN 301 549 / WCAG 2.1 AA.

Two routes

Two laws, two separate stories.

We are a public body

Mandatory since 2018, and there is no fine.

Hungarian Act LXXV of 2018 covers municipalities, public institutions and bodies performing public duties. An accessibility statement must be published, and the technical benchmark is EN 301 549, that is WCAG 2.1 AA.

  • Mandatory since 2018
  • Benchmark: EN 301 549 / WCAG 2.1 AA
  • No fine: there are notices, consultations and supervisory signals
  • Proceedings usually start from a complaint
The question here is not the sanction, but whether the people who need the site can actually use it. The gross price of a quick audit stays below procurement thresholds, so it needs no council decision.
We are a company

In force since 28 June 2025, and there is a fine.

Hungarian Act XVII of 2022 covers e-commerce, consumer banking and financial services, passenger transport, e-books and electronic communications. The benchmark is the same: EN 301 549 / WCAG 2.1 AA.

  • In force since 28 June 2025
  • The administrative fine is capped at 5% of net annual revenue
  • An exemption requires a prior, written disproportionate-burden assessment
  • That assessment is a cost-benefit analysis, not a scan
Microenterprises are exempt from the service requirements: fewer than 10 employees, and at most the forint equivalent of EUR 2 million in annual net revenue or balance sheet total. If that is you, there is nothing here for you to buy. Write to us and that is what we will tell you.

What the authority's report shows

In three years, 6 of 121 detailed audits passed.

Public sector checks, 2022–20241123
Detailed audits that passed6 / 121
Checks with no accessibility statement72%
Automated tests in the official audit0

In the detailed audits, 4 of 73 websites and 2 of 48 mobile apps received a certificate of conformity. The work is usually done by the developer who already runs the system, and that is fine, as long as someone tells them what the audit looks at. A simplified check covers at least three and at most five pages of a site; a detailed audit covers eight to twenty.

Even in simplified checks, KIFÜ does not use automated tests; under every audit method the check is carried out manually.

Source: Digital Hungary Agency, three-year report to the European Commission, 25 November 2024 (in Hungarian; quote translated). (opens in a new tab)

Machine and human

Automated checking finds roughly a third of the issues.

What has to be checkedAutomated checkManual audit
Contrast, missing text alternatives, semantic errorsDetectedDetected
Keyboard navigation and focus orderNot detectedDetected
Focus trapsNot detectedDetected
A screen reader walkthroughNot detectedDetected
Whether text alternatives are meaningful, not merely presentNot detectedDetected
Whether a form error message says what to fixNot detectedDetected
Fix order and estimated effortNot detectedDetected
Draft accessibility statementNot detectedDetected

We run the same open-source rule engine the cheap automated reports run, and we give it away for free. What you buy in the audit is the remaining two thirds: everything that only a keyboard, a screen reader and experience will surface.

What we do not sell

We do not sell overlay widgets, and here is why.

An overlay layers font-size and contrast switches on top of the existing page. It does not fix broken semantics, missing labels or a wrong focus order, so it does not solve a compliance problem. User organisations and most of the profession reject it, and abroad proceedings have been started specifically against sites using overlays. If someone sells a widget instead of accessibility, their other claims are hard to believe too.

Steps and prices

Four steps, with a low-risk entry point.

StepNetGross (27% VAT)What it is for
Free automated quick checkHUF 0HUF 0The address of the site is enough. It shows what the machine sees, and what it does not.
Quick auditHUF 150,000–200,000HUF 190,500–254,0001–2 days. Manual review on a sample, with a fix order and estimated effort.
Full audit: small, medium, large siteHUF 350,000 · 700,000 · 1,200,000HUF 444,500 · 889,000 · 1,524,0002–10 days depending on site size. The draft statement is included.
RemediationQuoted separately–Fixed by the same person who audited it.

The price of the quick audit counts towards the full audit. The gross column is not a formality: public bodies and foundations often cannot reclaim VAT, so their decision is about the gross amount. The statement is an output of the audit, not a separate item.

For public bodies

Requesting a quote as a public body.

If you need a price to set the estimated value of a procurement or for a three-quote round, we reply in writing within one working day: net and gross amounts, in a PDF signed on behalf of the company. An email with the subject and the address of the site is enough.

Indicative price within one working day, in writing
Net and gross amounts, signed on behalf of the company
Valid for 60 days, or 6 months for EU-funded projects
Statement of independence; transparency statement on request
ItemValue
Company nameAxeri Labs Betéti Társaság
Registered office2120 Dunakeszi, Brassói út 7.
Company registration number13-06-060656
Tax number22531300-2-13
Enterprise categorymicro-enterprise
Registered activities6210 computer programming · 6220 IT consultancy · 7120 technical testing and analysis
EKR (Hungarian e-procurement system)registered economic operator
Matching CPV codes72800000 computer audit and testing · 72413000 website design · 72267000 software maintenance
Phone+36 70 407 1111
Email

What the result of an audit looks like: made on our own website with the same method, with the issues we found and how we fixed them. Sample report (PDF in Hungarian, 4 pages) (opens in a new tab)

Giving an indicative price does not exclude a supplier from the later procurement procedure (Hungarian Public Procurement Act, section 25 (9) a)).

Which standard

The legal benchmark is WCAG 2.1 AA. We flag 2.2 separately.

The market talks about WCAG 2.2 in 2026, but the benchmark for compliance is the harmonised version of EN 301 549, which requires WCAG 2.1 AA. The audit follows that. The report separately flags those WCAG 2.2 success criteria that are not yet mandatory but will be with the next standard update.

Reference

A municipal website and a municipal institution.

Municipality of Nyáregyháza

The accessible version of the village website. A public-administration environment with real case-handling content, still live today.

nyaregyhaza.hu (opens in a new tab)

Kertvárosi Local History and Remembrance Centre

An institution of the 16th district municipality of Budapest, 2026. After handing over the new website we ran an accessibility check and drafted the accessibility statement. The institution approved the statement and published it in its own name.

helytortenet16.hu (opens in a new tab)

The Nyáregyháza website is earlier work, done against the WCAG version in force at the time; audits today follow EN 301 549 / WCAG 2.1 AA. Accessibility is not a one-off state. A rebuild or a theme change puts a site back where it was before the fixes within days. That is why re-testing is worth it, and why we hand over a findings list and a fix order rather than a certificate.

Who does it

I run the audit myself, not a subcontractor.

The same person writes the findings list and then does the remediation. This work cannot be handed off: most issues are not found by a rule engine but by a keyboard, a screen reader and experience.

What we do not take on

We do not certify, because the statement is a self-declaration.

The accessibility statement is published by the operator, about their own site. We supply evidence, a findings list and draft wording, not a certificate. That is why the report never says “the site complies with WCAG 2.1 AA”. It says which success criteria showed no findings on the sample we tested, and what the methodology and scope of that testing were. That difference matters the moment somebody relies on the statement.

What a statement contains, and how it is made

The first step

What you get in the free automated quick check

An automated check of 5–10 pages of the site
At least one finding the machine cannot make
A short report by email within a few working days
Including what the automated check does not catch

The check needs the address of the site, a name and an email address so we have somewhere to send the result. We do not ask for a call. The crawl is polite: we respect robots.txt, we identify ourselves in your logs, and we never walk the whole site. We never publish the results, neither as a list nor in aggregate.

Next step

Let us start with a free automated quick check.

One site address, and you get what the automated check finds, plus a short manual note on what it cannot see. That is what tells us whether we have anything to do with each other.

Request a free automated quick check