Features intended to support access
The site uses text headings, labelled form fields, keyboard-operable links and buttons, and responsive layouts. The standalone validator and status decoder provide text results. The guide search announces the number of matching resources without requiring a page reload.
The tracking popup uses a native dialog. Its close control has a text label, and focus returns to the triggering link when it closes. These implementation choices support access; they are not a claim that every page has passed a comprehensive accessibility audit.
Ways to use the pages
Use your browser’s zoom and text controls to adjust the display. The guides include section links for navigating longer explanations. Search and topic filters narrow the resource library; without JavaScript, its links remain available.
Tools need JavaScript to calculate their results. The UETR validator includes a written format explanation when scripting is unavailable. A copied bank-enquiry template can also be selected and copied manually if clipboard access is blocked.
Current limitations
Some existing guides contain dense diagrams and wide message examples or tables. At high zoom or on a narrow display, parts of these may require horizontal scrolling or be harder to interpret than the surrounding prose. External documents and videos may have accessibility limitations outside our control.
We have not completed a comprehensive independent audit across assistive technologies. We therefore do not claim full WCAG conformance or certification. Browser checks of selected tasks do not establish compatibility with every screen reader, device or browser combination.
Report a barrier
Email [email protected] with the page URL, the task you were attempting and what prevented it. If useful, include the browser, device and assistive technology. You do not need to disclose a diagnosis.
Please exclude passwords, signed transaction links and full payment documents. Tell us whether an alternative text explanation would help. We will use the report to investigate the affected task; no fixed resolution deadline is promised here.
Scope and preparation
This statement covers the public UETR.io site and was prepared on 22 October 2026 from the implemented features and identified limitations. It follows the transparency approach described in W3C’s guidance on accessibility statements.
For general website support, use Contact. For a factual content correction, see the editorial policy.