Accessibility Statement
Last updated 1 August 2026
TechTwin is committed to making our website and application usable by as many people as possible, including people who use screen readers, keyboard navigation, magnification, or who have low vision, colour-vision deficiency, or cognitive differences. This statement sets out where we currently stand — including the parts that do not yet meet the standard we are working to.
1. Conformance status
We aim to meet WCAG 2.1 Level AA. TechTwin is currently partially conformantwith that standard. “Partially conformant” means some parts of the service do not yet fully conform; the specific shortfalls we know about are listed in section 3.
We have not claimed full conformance, because we have not completed the testing that would justify it. We would rather tell you that plainly than publish a claim you might rely on.
2. What we have done
The following have been checked and are in place across the service:
- Semantic structure — pages use proper headings and landmark regions, so screen readers and browser reader modes can navigate them.
- Language — the page language is declared, so screen readers use the correct pronunciation.
- Images — decorative illustrations are explicitly hidden from assistive technology rather than being read out as meaningless filenames.
- Icon-only controls — buttons without visible text carry accessible names, so a screen reader announces what they do rather than “button”.
- Forms — inputs are associated with visible labels.
- Reduced motion — if your device is set to reduce motion, animated transitions are suppressed.
- Colour is never the only signal.This matters more here than on most sites: TechTwin displays health information, and a status shown only as a red or green dot is unreadable to many people with colour-vision deficiency. Every status in the app carries a text label (“Favorable”, “Caution”, “Normal”) alongside its colour, and every chart value is available as a number, not only as a line.
3. Known issues
These are real shortfalls we have measured, not hypothetical ones. We are listing them because you may hit them today:
- Text contrast. WCAG AA requires 4.5:1 for normal-size text. Several of the greys we use for supporting copy fall below it. Cards in the app are white and the page behind them is a very light grey, so each colour is measured against both:
Secondary text 4.23:1 on white, 3.95:1 on the page · captions 2.43:1 / 2.27:1 · the lightest icon grey 1.64:1 / 1.53:1 · the slate used for some accents 4.76:1 / 4.44:1.
Primary text and headings measure 17.61:1 and 16.45:1 and are unaffected, as are the numbers on your metric cards, charts and blood panel.
What this affects in practice is labels, captions and hint text — not the readings themselves, and not anything you need in order to operate the app. It is still below the standard. Browser zoom and your operating system’s increased-contrast setting both work throughout TechTwin, and if there is a figure you cannot read we will send it to you in another format — see section 5.
We have not changed these colours. It is a palette-wide change touching several hundred places in the interface, and we would rather record it here as outstanding than give you a date we have not committed to. - Untested with assistive technology. We have not yet completed structured screen-reader testing (VoiceOver, NVDA) or an end-to-end keyboard-only pass. Individual components are built to support both, but we have not verified every journey, so we cannot promise they all work.
- Charts. Forecast and biomarker charts are interactive and read out their values on hover or tap. We have not yet provided an equivalent non-visual summary of a full chart, so a screen-reader user gets the underlying numbers but not the shape of the trend.
- No third-party audit. Everything above is our own assessment. It has not been independently verified.
4. How this was assessed
By self-assessment, most recently on 1 August 2026, combining automated checks (contrast ratios computed across our colour palette against both surface colours it is displayed on, review of markup for landmarks, labels, and alternative text) with manual review. We have not commissioned an external accessibility audit.
5. Tell us if something does not work
If you hit a barrier — anything you cannot read, reach, or operate — please tell us. We treat it as a bug, not a feature request, and reports about accessibility go to the front of the queue. Email team.techtwin@gmail.com and, if you can, include the page, what you were trying to do, and the assistive technology or settings you were using. We aim to respond within five working days.
If you need information that is currently presented in a way you cannot access — a forecast, a blood-panel reading, a report — ask us and we will provide it in another format.
6. Keeping this honest
We will update this page when the issues above are fixed, and when new ones are found. A statement that lists nothing is usually a statement nobody has checked.