Accessibility statement

This English version is a translation provided for information. Only the Hungarian text is legally binding: the Hungarian original.

What we have done, what we have not, and where we actually stand. This is a description of the current state, not a certificate of conformity.

1. Scope of this statement

This statement applies to the pages of the adatka.hu website intended for users: the home page with the address search, the result card and the API access request window, the four service pages, the page for online shops, the API documentation, the “Prices” page and the legal pages, and the English-language version of these pages (/en/), where there is one.

It does not apply to:

• the responses of the API — these are JSON data intended for machine processing, not a user interface (see section 9);
• your email program, which the API access request window and the email links open;
• the external pages we link to (for example the websites of the data sources) — their operators are responsible for their accessibility.

2. Legal situation: what is mandatory and what is voluntary

adatka.hu is currently operated by a private individual — not as a sole trader and not through a company — as a free-of-charge beta service. The API is used by developers and organisations; the search on the home page is a demonstration that anyone can try. The assessment below is our own reading; it has not been reviewed by a lawyer. If you think another law also applies to us, please let us know — we will reply as described in section 7.

If the situation changes — for example, if the operator continues the activity as a sole trader or through a company, if the service becomes chargeable, or if we launch a service aimed at consumers — we will repeat the assessment and update this page with a date.

3. Benchmark and compliance status

The benchmark we have voluntarily adopted is WCAG 2.1 level AA (version 2.1 of the W3C's Web Content Accessibility Guidelines, conformance level AA). According to the European standard EN 301 549 V3.2.1 (2021-03), conformance with WCAG 2.1 level AA is equivalent to conformance with clauses 9.1–9.4 of the standard and with the conformance requirements of clause 9.6 (clause 9.0). The reference of this standard was published in the Official Journal of the European Union as a harmonised standard for public sector websites (Commission Implementing Decision (EU) 2018/2048, as amended by Implementing Decision (EU) 2021/1339). For web pages, the standard also contains further, conditional requirements outside clause 9; we have not assessed these separately.

According to the European Commission's list, the reference of the harmonised standard for Directive (EU) 2019/882 had not been published in the Official Journal of the European Union by 2 October 2026. If it is published, we will review the benchmark.

Compliance status: partially compliant. Because of the deficiencies listed in section 5, the website is only partially compliant with WCAG 2.1 level AA. The content listed there is not accessible because of non-compliance with the benchmark: the fix has not yet been completed, and a fix for the contrast of the brand colour is not scheduled (see there). For none of the deficiencies do we invoke a disproportionate burden or the content falling outside the scope of the applicable rules.

4. What we have solved

• Keyboard. The search, the list of matches and every link can be reached with the keyboard. You can move between the suggestions with the up and down arrows, choose with Enter and close with Escape. Nothing requires a mouse.
• Skip to content. On every page, the first press of Tab shows the “Skip to content” link: with Enter it skips the menu and takes you to the main content of the page. On every page, the main content is marked as a main region.
• Access request window. While the window is open, Tab and Shift+Tab move only within the window; the page behind the window cannot be reached. It can be closed with Escape; focus then returns to where you opened the window from. After sending, focus moves to the window's message.
• Announcements. The search writes the number of matches and the list messages (for example: no matches, search is not available right now) into a role="status" region, which the screen reader announces.
• Visible focus. Focus is visible on every focusable element: an outline appears around links and buttons, and the border of the search field turns blue. In the suggestion list, the item selected with the keyboard is marked not only by a light background but also by a blue bar on the left.
• The empty-field mark. On the result card, the mark for an empty field (—) has been given the colour of the labels; its contrast with the white background is 4.8:1.
• Field borders. The border of the search fields (on the home page and on the Address autocomplete page) and of the email field in the API access request window is visible even when the field is not in focus: the contrast between the border and the background behind the field is, in the light appearance, 4.2:1 for the search fields and 4.8:1 for the email field, and in the dark appearance 3.5:1 for the search fields and 3.6:1 for the email field (WCAG success criterion 1.4.11 requires 3:1).
• Source window. If you point at the source mark on the result card, move to it (Tab) or tap it, a small window opens with a description of the source and the “Sources and licences” link. The window and the link can be reached with both the mouse and the keyboard; the window can be closed with Escape.
• Language marking. Hungarian pages are marked lang="hu" and English pages lang="en", so that the screen reader reads them aloud in the language of the page. The language switcher in the header (HU, EN) takes you to the version of the page in the other language; from the legal pages that have no English version (both texts of the General Terms and Conditions and the Data Processing Terms), to the English home page.
• Structure. Real headings, real tables with headers, real buttons and links — not boxes made clickable.
• Width and zoom. The pages can be used in views 320 and 640 pixels wide, without scrolling the page horizontally; wide tables and long lines of code can be scrolled within their own frame. A view 640 pixels wide corresponds to a window 1280 pixels wide zoomed to 200%.
• Motion. There is no automatically starting animation, video or slider.
• No time limit and no action that has to be done in a hurry.
• Dark appearance. The pages follow the device setting: with a dark setting they are displayed with a dark background. The appearance can also be switched with the theme button in the header; the choice is not stored and remains valid until the page is reloaded. The contrast of text is at least 4.5:1 in the dark appearance too — also on hover and in focus —, except for the white text on the brand-coloured buttons (section 5).

5. Known deficiencies

We list these rather than keep quiet about them.

Accessible alternative. If you run into an obstacle using the search or the API access request window, write to info@adatka.hu: we will also send you the match for the address you are looking for by email, and we accept your access request by email in the same way as one sent through the window. It is enough to write the address you are looking for: do not add a name or any other personal data. Nor do you need to tell us about your disability or state of health.

6. Preparation of this statement

This statement was prepared on 20 September 2026. Last review: 21 October 2026.

Method: self-assessment (the method referred to in Article 3(1)(a) of Implementing Decision (EU) 2018/1523). We carried out the checks on 2 October 2026, in the Chromium browser:

• on the 11 pages the website had at the time (home page, four service pages, six legal pages) we stepped through with the Tab key and checked, for every focusable element, whether the focus indicator is visible;
• we viewed all 11 pages in views 320 and 640 pixels wide: none of them needs to be scrolled horizontally;
• on the result card we reached the source window and the link in it with both the keyboard (Tab, Enter) and the mouse; we chose from the suggestion list with the keyboard (arrow, Enter);
• we checked the headings in the browser's accessibility tree on the home page and on the “Address autocomplete” („Címkiegészítés”) page;
• we examined the roles of the fields and lists (combobox, listbox), the keyboard handling and the contrast of some colour pairs on the basis of the source code and the stylesheet.

On 3 October 2026 we checked in the same way — with the Tab key and in views 320 and 640 pixels wide — the two new legal pages (the Data processing terms and the text of the Terms of service in force from 2 November 2026), as well as the notice shown at the top of the home page.

On the same day, after the fixes, we checked all 13 pages in the Chromium browser with an automated check: on each of them, the first press of Tab gives focus to the “Skip to content” („Ugrás a tartalomra”) link, and each of them has a main region; Tab and Shift+Tab do not lead out of the API access request window; the number of matches and the list messages go into the role="status" region; the selected suggestion is marked by a blue bar. We measured contrast from the colours computed in the browser; this is also how we found the low contrast of the field borders. We fixed this the same day and measured the fix again with the same automated check on every page that has an input field: the contrast between the border and the background behind it is at least 4.2:1.

On 4 October 2026, in the same way, with an automated check in the Chromium browser, we checked the new page for online shops: in views 320 and 640 pixels wide no horizontal scrolling is needed; stepping through with the Tab key, the focus indicator is visible on every focusable element; the first press of Tab gives focus to the “Skip to content” link, the page has a main region, and the heading levels follow one another without skipping. On the same day we tried the header's new “Solutions” („Megoldások”) drop-down menu with the mouse and the keyboard (Enter, Tab, Escape), and checked that the header fits at every width tested between 761 and 1440 pixels; up to a width of 960 pixels the menu items can be reached via the “Menu” („Menü”) button.

On the same day, with the same automated check, we also checked the new API documentation: in views 320 and 640 pixels wide the page does not need to be scrolled horizontally (long lines of code can be scrolled within the code sample's own frame, and this frame can also be reached with the Tab key); in views up to 600 pixels wide the tables are displayed as cards, while in the browser's accessibility tree they remain tables; stepping through with the Tab key, the focus indicator is visible on every focusable element; the first press of Tab gives focus to the “Skip to content” link, the page has a main region, and the heading levels follow one another without skipping; the “Copy” („Másolás”) button of the code samples puts exactly the text of the code sample on the clipboard.

On 20 October 2026, with an automated check in the Chromium browser, we measured on every page of the website — in the light and dark appearance, in views 1280 and 390 pixels wide — the contrast of all visible text against the background behind it, with the pages as loaded (without hover or focus): the colour pairs below 4.5:1 are the brand-coloured buttons and text (section 5); all other text reaches 4.5:1. On the same day we checked the English-language version of the pages in the same way: in views 320 and 640 pixels wide no horizontal scrolling is needed; stepping through with the Tab key, the focus indicator is visible on every focusable element; the first press of Tab gives focus to the “Skip to content” link, and every page has a main region.

On 21 October 2026, in the same way, with an automated check in the Chromium browser, in the light and dark appearance, we also measured the contrast of text on hover and in focus. On every page we pointed the mouse at every visible link and button (in a view 1280 pixels wide; on the home page also in the drop-down menus, the API access request window, the list of suggestions and the result card), and stepped with the Tab key through every focusable element (in views 1280 and 390 pixels wide; also in the API access request window and in the phone menu). In both states the only colour pair below 4.5:1 is the white text on the brand-coloured buttons (section 5). On the same day we tried the header's language switcher and theme button with the keyboard (Tab, Enter, Space) and with the mouse on the Hungarian and English pages, in views 1440 and 390 pixels wide, and the “Sign in” („Belépés”) button in a view 1440 pixels wide (in narrower views it is reached behind “Menu”). We checked that the header of the Hungarian and of the English home page fits at every width tested between 761 and 1440 pixels, and measured the contrast of the field borders in both appearances (section 4).

Not done: an external expert audit, certification, testing with a screen reader, testing with users with disabilities, checking in another browser, and separately trying out the browser's built-in zoom (for example 200%).

We review this statement at least once a year, and also after every change that affects the search, the result card or the structure of the pages.

7. Feedback and contact

If you run into an obstacle, please write to info@adatka.hu. A concrete description — on which page, on what device (computer, phone) and in which browser, and what does not work — is worth more than any self-assessment. You do not need to tell us about your disability or state of health; it is enough to describe what does not work.

At the same address you can also ask us to send you the content of a page — for example the text of the legal pages — in another format that suits you (for example as plain text).

• We will reply on the merits, in writing (by email), within 30 days of receiving your message: we will tell you what we will fix and by when, or — if we are not fixing something — why not.
• Keep our reply: if you turn to an authority, you can attach it (section 8).
• We have no telephone customer service. If written contact is an obstacle for you, someone helping you can also write on your behalf; please let us know if you need another way.
• We handle your messages in accordance with the Privacy notice; there you can also read what happens if a message contains data concerning health.

8. Remedies: where you can turn

If you are not satisfied with our reply, or we do not reply within 30 days, the following routes are open to you. Turning to an authority or a court does not require that you write to us first; if you have written, it is worth attaching the correspondence.

An application to an authority and a statement of claim usually also have to state the name and address of the party against whom you are requesting proceedings. We do not publish the operator's name and place of residence on the site, but we will give them to you if, in a message to info@adatka.hu, you indicate that you intend to start administrative or court proceedings, and to the authority or the court if it formally contacts us. The content of the request and the deadline are described in section 9 of the Terms of service (in Hungarian).

For discrimination — the Commissioner for Fundamental Rights

In the event of a breach of the requirement of equal treatment, the Commissioner for Fundamental Rights conducts administrative proceedings upon application (Section 13(1), Section 14(1)(a) Ebktv.). Within the Office of the Commissioner for Fundamental Rights (Alapvető Jogok Biztosának Hivatala), this task is performed by the unit designated for it, the Directorate-General for Equal Treatment (Egyenlő Bánásmódért Felelős Főigazgatóság) (Act CXI of 2011 on the Commissioner for Fundamental Rights, Ajbt., Section 39/M(7)). The former Equal Treatment Authority (Egyenlő Bánásmód Hatóság) ceased to exist on 1 January 2021; its general legal successor is the Commissioner for Fundamental Rights (Section 45/D(1) of the Ajbt.).

You can submit the application as follows:

• by post, signed;
• electronically, through the e-Papír service;
• in person: at the Office's customer service, after booking an appointment in advance on the phone numbers above, or at the ombudsman's regional offices.

An application submitted by email does not start administrative proceedings.

According to the Office's guidance, the application should include:

• your name and place of residence (postal address);
• the name and address of the party against whom you request proceedings (see above);
• when and what happened, with the documents available to you (for example your correspondence with us);
• on account of which of your characteristics (for example your disability) you were harmed;
• whether you have started proceedings in the matter before a court or another authority;
• that you are requesting administrative proceedings, specifically proceedings by the Directorate-General for Equal Treatment;
• for an application submitted on paper, your signature; if a representative acts on your behalf, proof of their authority to represent you.

Worth knowing about the proceedings:

• It is enough for you to show as probable that you suffered a disadvantage and that you have such a characteristic; it is then for us to prove that this was not the case, or that we complied with the requirement of equal treatment (Section 19 of the Ebktv.).
• Proceedings can be started within one year of becoming aware of the infringement, but no later than three years after the infringement (Section 17 of the Ebktv.); the time limit for dealing with the case is 75 days (Section 14(4) of the Ebktv.).
• The costs of the proceedings are advanced by the authority; the person subject to the proceedings — that is, us — advances the costs related to its own participation. If your application is rejected, you only have to bear the costs if the authority establishes that you acted in bad faith (Section 16(3)–(4) Ebktv.).
• If you are visually impaired, you can ask to receive the minutes of the hearing and the decision closing the proceedings in Braille as well (Section 16(2) of the Ebktv.).
• On the basis of your authorisation, a civil society organisation or an interest representation organisation can also represent you (Section 18(1) of the Ebktv.).
• If the authority establishes an infringement, it may order the infringing situation to be ended, prohibit the infringing conduct, order its decision to be made public, and impose a fine (Section 17/A(1) Ebktv.).
• An administrative lawsuit can be brought against the authority's decision; it is heard by the Budapest-Capital Regional Court (Fővárosi Törvényszék), and legal representation is mandatory (Section 13(2) Ebktv.).

As a consumer — the consumer protection authority

If you are a consumer — you use the site as a natural person, not for business or professional purposes — you may, at your choice, turn to the consumer protection authority instead of the Commissioner for Fundamental Rights over a breach of the requirement of equal treatment: the consumer protection authority also monitors compliance with the requirement of equal treatment in the provision of services (Act CLV of 1997 on consumer protection, Fgytv., Section 45/A(3)(f); Section 15(1) of the Ebktv.). If proceedings have already been started before one of the authorities, the other does not act on the same infringement against you (Section 15(3) of the Ebktv.). The Fgytv. covers the activities of businesses affecting consumers (Section 1(1)); whether we, as a private individual operating a free-of-charge beta service, fall within it is for the authority to decide.

The consumer protection authority also monitors the accessibility of e-commerce services (Government Decree 605/2022 (XII. 28.), Section 1(1)(f)); to enforce the accessibility requirements, a consumer may start proceedings before the authority or before a court (Section 8(6) of the Aktv.). In our reading (section 2), the Aktv. does not apply to us; if you see it differently, you can choose this route as well.

The Budapest and county government offices (fővárosi és vármegyei kormányhivatal) act as the general consumer protection authority (Government Decree 326/2024 (XI. 14.), Section 2). Consumer protection contact details of the government offices: nkfh.gov.hu/hova-fordulhatok.

Court

You can also enforce your claim arising from a breach of the requirement of equal treatment in a lawsuit for the enforcement of personality rights (Section 12 of the Ebktv.); discrimination constitutes a violation of personality rights (Act V of 2013 on the Civil Code, Ptk., Section 2:43(c)). If proceedings are also started before a court in the same matter, the authority suspends its own proceedings until the court case has been decided with final and binding effect (Section 15/B(1) of the Ebktv.).

9. Information about the service (voluntary)

Annex 3 of the Aktv. requires service providers within the scope of the Aktv. to provide the information below. It is not mandatory for us (section 2), but we provide it because it may be useful to our users and clients.

• General description of the service. Adatka is used for completing, validating and geocoding addresses in Hungary. The search on the home page is a demonstration: for the part of an address you type it gives a list of suggestions, and for the selected address it shows a result card. The same is available through the API (/suggest, /reverse, /clean), in JSON format.
• Description needed to understand how it works. When you type in the search field, the suggestions appear below the field; you can move between them with the up and down arrows, choose with Enter and close with Escape. The result card shows the result as text, structured with headings; if you move to or click the source mark, a small window shows the description of the source. There is no time limit.
• How the requirements are met. The requirements met are listed in section 4, those not met in section 5; the benchmark is set out in section 3.
• For our API clients. The API is not a user interface: the accessibility of how the responses are displayed depends on your interface. If the Aktv. applies to your service, you are responsible for compliance even if a third party provides the service or part of it as a subcontractor (Section 3(4) of the Aktv.). On request, we will describe how the suggestion list on the home page is built (combobox and listbox roles, keyboard handling), so that it can serve as a model for your own interface.

10. What happens to this statement

Whenever one of the listed deficiencies is fixed, this page is updated as well, with a date. If the list gets shorter, it is because we have fixed something — not because we deleted it. We keep the earlier versions. If you need one of them, write to info@adatka.hu stating the date for which you are requesting the text in force, and we will send it to you by email within 8 days.

Prepared: 20 September 2026, based on self-assessment · Amended: 24 September 2026 (the paragraph on the legal situation) · Reviewed: 2 October 2026 (headings, reaching the source window with the keyboard and the mouse, the focus indicator, the list of known deficiencies) · Amended: 3 October 2026 (revised: the scope of the statement, the legal situation, the benchmark and the compliance status, the reason for the deficiencies and the accessible alternative, the method of preparation, feedback, remedies and the description of the service; checks of the new legal pages and of the notice on the home page; the API's automatic description — /docs, /redoc, /openapi.json — discontinued, removed from the exceptions; fixed and removed from the known deficiencies: skip to content and a main region on every page, focus handling of the API access request window, announcements of the list of matches, marking of the selected suggestion, contrast of the empty-field mark; contrast of the field borders: added as a known deficiency that day, then fixed and removed from the list — the borders of the search fields and of the email field have a contrast of at least 4.2:1 even without focus) · Amended: 4 October 2026 (scope of the statement extended: the page for online shops and the API documentation; preparation of the statement: checks of the new pages and of the “Solutions” menu; section 4: scrolling of long lines of code; spelling correction in section 9) · Amended: 20 October 2026 (scope of the statement supplemented with the English-language version of the pages; in section 3: the contrast of the brand colour; in section 4: language marking for both languages and the language switcher in the header, new item: dark appearance; in section 5: the missing dark appearance removed — implemented —, new row on the contrast of the brand-coloured buttons and text; in section 6: the checks of 20 October 2026, the date of the last review; formatting: emphasis removed from running text) · Amended: 21 October 2026 (scope of the statement supplemented with the “Prices” page; in sections 3 and 5: the description of the contrast of the brand colour — a fix is not scheduled; in section 4: the language switcher on the legal pages without a translation, the contrast of the field borders in the dark appearance, the contrast of the dark appearance on hover and in focus; in section 5: the contrast of brand-coloured text by appearance; in section 6: the description of the checks of 20 October 2026 made more precise, the checks of 21 October 2026, the date of the last review)