Resources · Accessibility of this site~2 minutes

Accessibility statement

I want anyone to be able to use this site: people who do not see well, who use only a keyboard, a program that reads the screen aloud, or an old phone. The statement below says honestly what already works and what does not.

Its structure follows the official Romanian model (Decision no. 815/2022 of the Romanian Authority for Digitalisation (ADR), Annex 1). ADR is the government body responsible for digitalising public administration. Its model takes over the European model (Decision (EU) 2018/1523).

Commitment

I am committed to making the site statulonline.ro accessible, in line with the international standard WCAG 2.2, level AA.

This is a personal site, not the site of a public body. Government Emergency Ordinance (OUG) no. 112/2018 on the accessibility of public websites does not apply to it. I still follow the same rules, voluntarily.

The statement covers all pages of the site, including the interactive demonstration in chapter 5.

Compliance status

The site is partially compliant with WCAG 2.2 level AA. I have checked some of the requirements, but not all of them. The list below shows exactly which.

What I have checked and what works

• Contrast. Every text and background colour combination has been calculated with the WCAG formula and passes the 4.5 : 1 threshold, in light mode, in dark mode and in the demonstration.
• Restful colours for reading. The background is not pure white but a warm paper tone, and in dark mode it is not pure black but a warm grey. Text has a contrast of 13–14 : 1. This is above the AAA threshold of 7 : 1, but below the maximum contrast of 21 : 1, which tires the eyes during long reading and “glows” for people with astigmatism.
• Text enlargement. Text can be enlarged up to 150% with the buttons in the header, and the page stays readable. The base size (100%) is also the minimum: at either end, the button concerned appears inactive, and screen readers say that the text is already at its smallest or largest size. Browser zoom, in or out, is also respected.
• Display on phones. At a width of 375 pixels, content does not run off the screen and there is no need to scroll horizontally.
• The header on phones. On small screens, the header takes up a single row, with two buttons: Aa (text size, theme, language) and Menu (all pages). The buttons tell screen readers whether the panel is open, and the Esc key closes it. All touch targets are at least 44 × 44 px. Without JavaScript, the header remains fully visible.
• Structure. Each page has a single main heading, and headings are in order. There is a “Skip to content” link at the start of the page.
• Automatic higher contrast. If the “Increase contrast” option is on in the device settings, the site strengthens its colours by itself: darker text (16.6 : 1 in light mode, 14.7 : 1 in dark mode), thicker borders and more visible link underlines. The warm backgrounds stay.
• Themes. The site automatically follows the device theme, light or dark. In the header you can choose Light or Dark at any time; your choice is remembered.
• Without JavaScript. The texts, the frequently asked questions and the profiles in chapter 4 remain visible. Only the demonstration in chapter 5 needs JavaScript; its steps are also described in the text.
• The forms in the demonstration have labels linked to the fields, error messages linked to the field in error and an error summary, with links to each field.
• No tracking. The site does not use cookies or analytics tools.
• Automated testing. All 72 pages (24 in each language) were checked with axe-core 4.10 (WCAG 2.0–2.2 rules, levels A and AA), in the light theme and in the dark theme, on 22 October 2026. No errors remained, except for the intentional example described below.
• Keyboard-only navigation, on all 72 pages, on desktop and on phones (22 October 2026, with an automated test that presses the keys). The Tab key reaches every interactive element, in visual order, and the active element has a visible outline. There are no keyboard traps, and the first element is the “Skip to content” link. The phone menu and display panel, the theme, the FAQ, the profile filter and the demonstration, from the first step to the last, all work with the keyboard alone. Wide tables can also be scrolled with the keyboard.

What I have not checked yet

• Screen readers, fully. I have tested a large part of the site with VoiceOver, but not all of it. NVDA (Windows) and TalkBack (Android) have not been tested yet.
• Testing with people with disabilities.

Content that is not yet accessible

Known non-compliance:

• Languages. The site exists in Romanian, English and Hungarian. The “RO”, “EN” and “HU” buttons in the header lead to the same page in the other language, and every page declares its language, so that screen readers use the right pronunciation. Romanian is the base text. The translations were made with the help of artificial intelligence, following a written glossary and rules. The Hungarian version has not yet been checked by a native speaker, and the Hungarian pages say so in a band below the header. In the demonstration, Hungarian shows the same notice.
• The contrast example in chapter 3. The “yellow on white” sample intentionally has a contrast of 1.5 : 1, to show why the yellow of the flag is not used for text. The result for each sample is also written in the text, including for screen readers.
• Large tables scroll horizontally on small screens. Only the table scrolls, not the whole page, and this also works with the keyboard.

Content outside the site: links to external sites (the Chamber of Deputies, legislatie.just.ro and others) lead to pages whose accessibility does not depend on me.

How this statement was prepared

• Method: self-assessment (automated and manual checks, carried out by the author).
• Date prepared: 21 October 2026.
• Last reviewed: 22 October 2026.
• I review it at least once a year and after any significant change to the site.

Feedback and contact

If you come across an accessibility problem on this site, write to me at salut (at) statulonline.ro. Tell me:

• which page the problem was on;
• what you were trying to do;
• what device, browser or assistive technology you were using, if you wish.

I will reply within 10 working days at most. This is the deadline I also propose for state services, in chapter 4. If the problem cannot be solved quickly, I will send you the content in a format that is accessible to you.

Enforcement procedure

Because this is not a public site, the Romanian Authority for Digitalisation has no authority over it. For any unresolved problem, write to me again at the same address.