Accessibility Statement
On this page
1. Our commitment
Orbitfy Inc. is committed to making orbitfy.com accessible to everyone, including people with disabilities. We treat accessibility as a build requirement rather than a remediation task, and we hold this website to the same standard we hold the software we are developing.
An accessible site is not a concession — it is a site that works. If any part of this one does not work for you, we want to hear about it, and we will treat it as a defect.
2. The standard we build to
This website is designed and built to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C — the standard referenced by the Americans with Disabilities Act in US Department of Justice guidance, Section 508 of the Rehabilitation Act, the European Accessibility Act and EN 301 549, the UK Equality Act 2010, the Accessible Canada Act and Ontario’s AODA, and Australian, New Zealand and other national frameworks that adopt WCAG.
We aim to meet Level AA in full and adopt Level AAA criteria where practical without harming clarity for other users.
3. Conformance status
Partially conformant with WCAG 2.2 Level AA.
“Partially conformant” means most content meets the standard but we have not completed an independent third-party audit and do not claim full conformance on self-assessment alone. We consider it more useful to tell you exactly where we stand than to make a claim we cannot yet evidence.
Basis of this claim: self-evaluation by the team that built the site, using the methods at §5. What would change it: an independent audit, which we intend to commission and whose outcome we will publish here — including anything it finds that we missed.
4. What we have built in
4.1 Structure and navigation
A skip link to the main content, first in the tab order on every page · proper landmark regions so screen-reader users can jump directly · a single correctly ordered heading hierarchy with no skipped levels · descriptive, unique page titles naming the page first · link text that makes sense out of context · consistent navigation order and component labelling · an HTML sitemap in addition to the navigation.
4.2 Keyboard and pointer
Everything operable by keyboard alone in a logical order · a high-contrast dual-ring focus indicator visible on both light and dark backgrounds · focus never hidden behind the sticky header · the mobile menu moves focus into itself, keeps it there, closes on Escape, and returns focus to the button that opened it · no keyboard trap anywhere else · all pointer targets at least 24×24 CSS pixels, primary controls 48×48 · no drag gesture, path-based gesture or device motion required anywhere · no function depends on a mouse.
4.3 Presentation and readability
Text contrast at least 4.5:1, large text at least 3:1, UI components and meaningful graphics at least 3:1, each pairing individually measured · colour is never the only way meaning is conveyed · text resizable to 200%, page reflows at 400% zoom on a 320px viewport with no horizontal scrolling · the layout survives increased line height, letter spacing, word spacing and paragraph spacing without clipping or overlap · body text never smaller than 16px · line length limited to a comfortable measure · works in portrait and landscape, never locked.
4.4 Motion and time
No content flashes more than three times per second · nothing auto-plays, auto-scrolls, loops or moves without your action · no time limits anywhere · when your device requests reduced motion, every transition and animation is switched off, including the mobile menu slide, the cookie notice appearance, and smooth scrolling.
4.5 Forms and spam protection
This section changed in version 1.1 and describes exactly what protects our contact form.
Every field has a visible, permanent label — we never use a placeholder as the only label · required fields are marked in text, not by colour · errors are described in words, listed in a summary at the top of the form which receives focus, and each error is programmatically linked to its field · fields carry autocomplete attributes so browsers and assistive technology can fill them · no field asks for information you have already given.
On CAPTCHA — the part that matters most.
We use Google reCAPTCHA v3, and we chose it specifically because of what it does not do:
- There is no puzzle. No checkbox, no image grid, no “select all the buses”, no audio alternative to struggle with. There is nothing for you to do at all.
- It never blocks you. reCAPTCHA v3 gives each submission a score. A low score does not stop your message reaching us. It is recorded alongside your enquiry, flagged for our attention, and the enquiry is delivered anyway.
- We made that a rule, not a setting. Score-based systems assign low scores disproportionately to people using screen readers, keyboard-only navigation, privacy browsers, VPNs, older devices and shared corporate networks — which is to say, disproportionately to the people this site works hardest to include. Discarding those submissions would exclude them silently, with no error message and no way for anyone to notice. So blocking on score is not an option in our system; the threshold controls labelling only.
- You can refuse it entirely. reCAPTCHA loads only if you accept spam-protection cookies. If you decline, it never loads, and the form works identically — protected instead by measures that involve no third party, no cookie and no assessment of you.
- It works without JavaScript. If JavaScript is unavailable or switched off, the form still submits, still validates and still reaches us. Requiring JavaScript to contact a company is a barrier, and we do not impose one.
The visible reCAPTCHA badge is hidden, and the attribution notice Google requires appears as text within the form instead — partly for clarity, and partly because the badge would otherwise sit on top of the accessibility panel button.
4.6 The cookie notice
New in version 1.1. The cookie notice is designed to the same standard as everything else:
- It is not a modal. It does not trap focus, does not block scrolling, and does not prevent you reading or using the page. You can ignore it entirely and nothing loads while you do.
- Accept, Reject and Manage preferences are equally prominent — same size, same shape, same row.
- It is fully keyboard operable, announced to assistive technology when it appears, and dismissible with Escape.
- The preferences panel uses real checkboxes with visible labels, not styled
<div>elements. - Under reduced motion it appears without animation.
- The Cookie preferences link in the footer reopens it on any page, so withdrawing consent is as easy as giving it.
4.7 Images and media
Images conveying meaning have text alternatives; purely decorative images are hidden from assistive technology · no meaningful text is baked into an image except the logo · there is no video or audio on this site, and if we add any it will ship with captions, a transcript and audio description where needed — not afterwards.
4.8 Language and technology
The page language is declared and updated if you change language in the accessibility panel · content is served over well-formed HTML that parses cleanly and works with assistive technology · the site does not require JavaScript to read the content or to contact us.
5. How we test
| Method | Detail |
|---|---|
| Automated scanning | axe DevTools and Lighthouse on every page template. A clean automated scan is a floor, never a result — automated tools detect roughly a third of accessibility barriers |
| Manual keyboard testing | Every page operated end to end with the mouse unplugged, including the cookie notice and the contact form’s error recovery |
| Screen reader testing | NVDA with Firefox on Windows; VoiceOver with Safari on macOS and iOS; TalkBack with Chrome on Android |
| Zoom and reflow | 200% text resize and 400% page zoom at a 320px viewport |
| Text spacing | The WCAG 1.4.12 bookmarklet applied to every template |
| Reduced motion | Every page reviewed with the operating-system setting enabled |
| Contrast measurement | Every colour pairing measured, including text over gradients |
| JavaScript disabled | The contact form is tested and must work |
| Regression testing | The whole matrix is re-run before any release touching a template, the cookie notice or the form |
6. The accessibility preferences panel
Every page carries an accessibility preferences panel, reachable by the floating button in the corner or by pressing Shift twice.
It offers text sizing and spacing, readable and dyslexia-friendly fonts, contrast and colour adjustment including colour-blindness filters, a reading guide and reading mask, a text magnifier, motion and animation control, cursor and focus options, tooltips, a page-structure browser, and a screen-reader text-to-speech mode. Your choices are remembered on your own device and can be reset at any time.
The panel is a supplemental comfort and personalisation tool. It does not make an inaccessible website accessible, and we do not present it as doing so. It sits on top of a site built to conform at the code level. Anyone who tells you a widget alone delivers compliance is selling you something. If you find yourself needing the panel to work around a barrier here, that is a bug — please report it under §7.
Privacy note. The panel stores your preferences in your own browser and transmits nothing to us. Its optional page-translation and dictionary features, which would send page content to third-party services, are switched off on this site. See the Cookies Policy §3.4.
7. Feedback — and what we will do with it
If any part of this website is difficult or impossible for you to use, please tell us.
Email: info@orbitfy.com — subject “Accessibility”.
The page address, what you were trying to do, what happened, and your browser and assistive technology all help us reproduce it faster — but please do not let missing any of that stop you writing.
| Commitment | Target |
|---|---|
| We acknowledge every accessibility report | Within 5 business days |
| We tell you what we found and what we intend to do | Within 10 business days |
| We fix barriers preventing access to information or functionality | As a priority defect, ahead of feature work |
| If a fix will take time, we provide the information or service another way meanwhile | Immediately |
| We do not ask you to justify your request or explain your disability | Ever |
If you are not satisfied, say so and it will be escalated within Orbitfy Inc. Your right to complain to a regulator or enforcement body is unaffected, and you need not contact us first.
8. Known limitations
| # | Limitation | Impact | Status |
|---|---|---|---|
| 1 | No independent audit yet. The conformance claim rests on self-assessment | Undetected barriers may exist | An audit is intended; we will publish the result, including anything it finds |
| 2 | Third-party content. We cannot control the accessibility of sites we link to | Linked sites may not conform | We check links we rely on and prefer accessible sources |
| 3 | The accessibility panel’s own interface is third-party code we configure rather than author | Defects in it are not entirely within our control | Tested every release; defects reported upstream |
| 4 | Screen-reader and voice features in the panel depend on browser capabilities that differ, and voice recognition is unavailable in some browsers | Some panel features may not work in your browser | Unsupported features degrade quietly; the site remains fully usable without them |
| 5 | Google reCAPTCHA is third-party code (new in v1.1) | It runs on the contact page when you consent, and we cannot audit its internals | It is invisible, presents no challenge, never blocks a submission, and can be refused entirely without losing the form. If you would rather not run it at all, decline spam-protection cookies or simply email us at info@orbitfy.com |
| 6 | Google Analytics is third-party code (new in v1.1) | It runs only with your consent and displays nothing | It adds no interactive element and no visible content, so it introduces no barrier. It can be refused entirely with no loss of function |
| 7 | Insight articles may contain complex tables or diagrams | Complex content is harder to convey non-visually | Every diagram carries a text description and tables use proper header markup. Tell us if one does not work |
We do not currently claim any content is exempt as a disproportionate burden.
9. Assessment and approval
- Approach: self-evaluation by Orbitfy Inc.
- Standard: WCAG 2.2 Level AA
- Scope: all pages of
https://orbitfy.compublished at the date of this statement, including the cookie notice and the contact form - Statement prepared: 20 August 2026 · Last reviewed: 20 August 2026 · Next review: 20 November 2026, and on any release changing a page template, the cookie notice or the form
This statement follows the structure recommended by the W3C Web Accessibility Initiative and is intended to satisfy the statement requirements of EN 301 549 and equivalent national frameworks.
10. Accessibility in Orbit itself
The software we are developing is built to the same standard. WCAG 2.2 Level AA is a condition of a screen being considered finished — not a phase after it. Frontline interfaces must additionally be operable by touch, by keyboard and by barcode scanner without a pointing device, because that is how the work is done in a shop, a warehouse or a service bay. High-frequency tasks are measured in interaction count and deliberately reduced.
We will publish a separate accessibility conformance report for Orbit when it becomes available.
11. Change history
| Version | Date | Change |
|---|---|---|
| 1.0 | 20 August 2026 | Initial publication |
| 1.1 | 20 August 2026 | §4.5 rewritten — the site now uses reCAPTCHA v3, and the previous statement that it used no CAPTCHA is superseded. Records that no challenge is presented, that a low score never blocks a submission, that reCAPTCHA can be refused entirely, and that the form works without JavaScript. §4.6 added for the cookie notice. §5 extended with JavaScript-disabled testing. Known limitations 5 and 6 added for the two Google components. Scope at §9 extended |
12. Contact
Orbitfy Inc.
Email: info@orbitfy.com — subject “Accessibility”
