This page is a measurement record rather than a conformance certificate: what was tested, what came out and what was not tested. The automatically testable parts of WCAG 2.2 AA were measured on 42 pages across the three languages, and the last run left no findings.
The criteria that were tested
Testing runs in a real browser and reads the computed style of the page. The criteria looked at are: images without alternative text (1.1.1); skipped heading levels, form fields without labels and data tables without headers (1.3.1); text contrast, 4.5:1 for normal text and 3:1 for large text (1.4.3); the skip link to the main content and the presence of a main landmark (2.4.1); link purpose being clear from the link text (2.4.4); the target size of clickable elements (2.5.8); the language declaration of the page (3.1.1); and buttons or links without an accessible name (4.1.2).
Keyboard and narrow screens
Keyboard operation is tested separately: where the skip link sits and where it leads, the language switcher’s links to the other two languages, the state of the high-contrast button, the menu links, the labelled search field, the visibility of the focus indicator and whether any keyboard trap exists. In three languages, on both the front page and a deep content page, at 1280 and 360 pixels wide, 126 checks were made and all passed. Horizontal overflow is measured separately at 360 pixels: none of the 42 pages scrolls sideways.
A real defect, found and fixed
A genuine defect was found the same day: a cyan text colour gave a contrast of 2.24:1 against white, where the threshold is 4.5:1. Because that colour was used in the breadcrumb links and the “on this page” button, the finding repeated 81 times across 42 pages. The text colours were darkened and the measurement was repeated. The reason it had gone unnoticed was recorded as well: the testing tool used a fixed browser profile and was being served the old stylesheet from cache.
The high-contrast preference
The button at the top of the page turns on a high-contrast theme. The preference is written to your browser’s local storage under the name acte-karsitlik and stays on for the pages you visit afterwards; the record stays on your own device and is not sent to the server. Details are on the cookies and browser storage page.
What was not tested
Automated tools can only see part of what WCAG covers. Not yet done on this site: end-to-end testing with a screen reader, testing with disabled users, checks on audio and video content (there is none) and the accessibility of attachments such as PDFs. If you meet a barrier on a page, write to info@tercu.me with the page and the step where it happened; the report goes into the next round of measurement.