Accessibility Statement

1. Our commitment

TrustCheck wants everyone, including people with disabilities, to be able to use the TrustCheck website at trustcheckbot.com, the web application, the Telegram bot @trustcheckcom_bot and the API documentation (the Service).

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium (W3C). We consider accessibility throughout design, development and content work, and not as a one time project.

2. Standards and laws we follow

• WCAG 2.2 Level AA is our target for all web content.
• European Accessibility Act (EAA), Directive (EU) 2019/882, which applies since 28 June 2025 to certain products and services provided to consumers in the EU, including e commerce and consumer banking services. We design the Service to meet the EAA accessibility requirements that apply to it.
• EN 301 549, the harmonised European standard for ICT accessibility, which incorporates WCAG for web content and is used to presume conformity with the EAA.
• Americans with Disabilities Act (ADA) and Section 508 of the US Rehabilitation Act, which we use as guidance for the United States.

3. Local equivalents

Many jurisdictions have their own accessibility laws or standards. Most refer to or are closely aligned with WCAG, so meeting WCAG 2.2 AA is our main way of meeting them. Where relevant to our users we also take into account:

• Canada: the Accessible Canada Act and its principles of identifying, removing and preventing barriers, which we use as guidance, and the Accessibility for Ontarians with Disabilities Act (AODA) and its Integrated Accessibility Standards Regulation, which requires WCAG 2.0 Level AA for websites of covered organisations in Ontario. Our WCAG 2.2 AA target exceeds that level. Quebec standards on web accessibility are also used as guidance.
• United Kingdom: the Equality Act 2010, which requires reasonable adjustments.
• Japan: JIS X 8341-3:2016, which is aligned with WCAG 2.0.
• South Korea: the Korean Web Content Accessibility Guidelines (KWCAG), based on WCAG.
• India: the Rights of Persons with Disabilities Act 2016 and the related standard IS 17802.
• Other countries that reference WCAG or EN 301 549 in their national rules.

4. What we do

• Semantic HTML with landmarks (header, navigation, main content, footer), a single main heading per page and a logical heading order;
• a "Skip to main content" link as the first item on each page;
• full keyboard operation with a clearly visible focus indicator;
• text and interface colours chosen to meet WCAG AA contrast ratios in both the dark and the light theme;
• a page language declared for each language, and correct right to left layout for Hebrew, Arabic, Urdu and Pashto;
• layouts that reflow on small screens down to 320 CSS pixels wide without horizontal scrolling of text, and that support browser zoom up to 200 percent and text spacing adjustments;
• risk levels communicated with text labels, not colour alone;
• decorative images and icons hidden from assistive technology, and meaningful controls given accessible names;
• respect for the operating system "reduce motion" setting on our legal pages; and
• self hosted fonts and no third party scripts, which keeps pages fast on slow connections and assistive devices.

5. Known limitations

We are aware of the following limitations and are working to address them:

• Telegram bot. The bot runs inside Telegram's apps. Its accessibility depends partly on Telegram's clients, which we do not control. We keep bot messages short, structured and text based so that they work with screen readers.
• Risk report visuals. Some visual elements of risk reports, such as the score gauge, are graphical. The score and risk level are always also shown as text, but some visual details may not yet have a complete text alternative.
• Motion on the landing page. The home page uses subtle hover and transition effects that do not yet fully follow the "reduce motion" setting.
• Translations. The website is available in 12 languages. Legal documents, including this statement, are in English only, and some translated interface text may not yet have been reviewed by native speakers.
• Third party content. Links to block explorers, Telegram and other third party sites lead to content whose accessibility we do not control.
• API documentation. Code samples and long tables in the developer documentation have not yet been fully evaluated.

If a limitation prevents you from using the Service, contact us and we will provide the information or result you need in an accessible alternative format, for example by email in plain text.

6. Feedback and contact

We welcome your feedback. If you find an accessibility barrier, need information in an alternative format, or have a suggestion, please contact us:

Please tell us the page or feature, what you were trying to do, the problem you encountered, and the device, browser and assistive technology you use, if you are comfortable sharing it. You may also give feedback anonymously by post.

Response time

We will acknowledge your message within 5 business days and aim to give a substantive response, or a fix or workaround, within 30 days. If we need longer, we will tell you why and when to expect a reply.

7. Enforcement and complaints

If you are not satisfied with our response, you may contact the authority responsible for accessibility in your country. In the EU, each member state designates a market surveillance authority for the European Accessibility Act. In Ontario, you may contact the Accessibility Directorate of Ontario. In Canada at the federal level, the Accessibility Commissioner handles complaints about organisations covered by the Accessible Canada Act. In the United States, you may contact the US Department of Justice.

8. Assessment approach and last review

We assess accessibility through self evaluation, including automated checks, manual keyboard testing, contrast measurement, testing at small screen widths, and screen reader spot checks. We have not yet completed an independent third party audit.

This statement was prepared on 18 October 2026. The Service was last reviewed on 18 October 2026. We will review this statement at least once a year and whenever we make significant changes to the Service.