Askhive

Accessibility Statement

What we have measured, what is in place, and the gaps we know about.

Last updated: 29 September 2026

Written by us, in plain language, and kept true rather than lawyerly: every factual sentence here is one we can show you the mechanism for. If anything looks wrong, tell us at support@bridgeshorelabs.com and we will correct it.

Our position

Askhive should be usable by everyone, including people who use a screen reader, need larger text, or cannot use a mouse. We test this rather than assume it: an automated accessibility check runs against the real rendered app — not the source — and measures contrast, text scaling, heading structure, focus order and accessible names on every control.

Target: WCAG 2.1 Level AA.

What is in place

Contrast. Every text colour we measure meets AA against the background it is actually rendered on. This was measured and fixed: the inactive tab-bar labels had been at 2.28:1, below the 4.5:1 line, and the whole de-emphasis palette was rebuilt to pass.
Larger text. The app respects the text size set in your operating system. At 200% the layout reflows rather than clipping, and nothing scrolls off sideways — a bug we found and fixed, where the send button moved off-screen at large text sizes.
Screen readers. Every visible control has an accessible name. Decorative emoji are hidden from the screen reader rather than read aloud. Section titles are real headings, so VoiceOver's rotor and TalkBack's heading navigation work. The current tab announces itself.
Things that happen without a tap — the app working on your question, clarifying questions appearing, the report becoming ready — are announced through a live region that is always present, because one that appears at the same moment as its text is unreliable in both VoiceOver and TalkBack.
Keyboard. Tab order follows reading order and focus is visible.
Zoom is not disabled. Pinch-to-zoom works; we do not suppress it.

Known gaps

Testing so far is automated plus our own use. We have not yet run a session with a daily screen-reader user, which is the test that finds what automation cannot. We intend to before general release.
Voice input relies on the platform's dictation and is unavailable in the mobile app shell.
Reports rendered to PDF have not been checked for tagged-PDF accessibility.

Tell us

If any part of Askhive is hard to use, write to support@bridgeshorelabs.com and say what you were trying to do and what got in the way. We will reply within five working days and tell you what we can do and when. This is the fastest route to getting something fixed.