Access
Accessibility
This site targets WCAG 2.2 Level AA. It has not been certified, and it has not been tested with assistive technology by external users. Known gaps are listed below.
Target
Conformance target
The target is WCAG 2.2 Level AA for this website. The app is a separate Android product; this page is about the site. A target is not a certificate. No third party has assessed this site, and there is no accessibility certification.
Checks
What has been tested
The checks below are built into the site generation or were reviewed in the source. They are not an audit.
- Structure. The build checks for one h1 per page,
lang="en", a unique title, a meta description, a canonical URL, semantic landmarks, a skip link, and table captions. - Scripts and requests. The build rejects executable scripts, inline event handlers, inline style attributes, and third-party requests. There are no forms, cookies, or analytics.
- Contrast. Body text colour pairs are computed at build time. The body text ratio is at least 7:1; links and focus rings are at least 3:1 against their adjacent colours.
- Keyboard. The skip link is first in the tab order, focus-visible rings are not removed, and the FAQ uses native
detailsandsummaryelements. There are no scripted keyboard traps. - Reflow. The layout is mobile-first, uses relative units, wraps long hashes, and was checked at 360 px and desktop widths.
- Motion. There is no essential animation. The only transitions are colour changes, and they are disabled under
prefers-reduced-motion: reduce.
Gaps
Known gaps
- No screen-reader testing with users. TalkBack, NVDA, and VoiceOver have not been used to review this build.
- No third-party accessibility audit or certification. The checks on this page are internal.
- No formal 200% zoom test is recorded. The layout uses relative units and reflows, but the test is not yet part of the release evidence.
- Dark theme only. There is no light theme or separate high-contrast theme; the dark palette is the only presentation.
- English only. The site and the app are not localised.
- Technical content. Commands, header values, and fingerprints are necessary for verification but are hard for non-technical readers. This is a usability gap, not a WCAG failure.
Method
How this was checked
The method is manual source review plus automated static checks in scripts/build-site.mjs. The checks cover semantics, contrast, script removal, third-party requests, and internal links. They do not replace testing with disabled users, and they do not produce a conformance certificate.
Where a gap is known, it is stated on this page rather than omitted. If a page or component fails your needs, tell us and we will say plainly whether it can be fixed.
Contact
Contact
Accessibility feedback: pilot@bitgab.app. Security reports: security@bitgab.app. BitGab does not promise response times.