1. Our commitment
Infold builds this website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We treat readability and keyboard access as requirements, not nice-to-haves, and we check them on phone, tablet and desktop screens as we build.
2. How we build this website
- Readable text Body text is at least 18px and secondary text at least 15px, with a contrast target of 4.5:1 against the real background.
- Keyboard first Every link, button and control can be reached with a keyboard, with a clearly visible focus ring and a “Skip to content” link on every page.
- Motion you control Animations respect your device’s “reduce motion” setting, and animated sample calls have Pause and Replay controls.
- Sound only when asked Audio samples play only when you press play. Nothing starts talking on its own.
- Clear structure Pages use real headings, landmarks and lists, the language is set to Canadian English, and questions use native expand-and-collapse controls.
- Text alternatives Meaningful images have written descriptions; decorative ones are hidden from screen readers.
3. On the phone
For many people, calling is the easiest way to reach a business — and Infold means those calls get answered instead of going to voicemail. Callers can ask the receptionist to repeat something, and can ask for a person at any time; it transfers the call or takes a message, following the business’s rules.
4. Standards and laws
- WCAG 2.2 Level AA is our target for every page. It goes further than the WCAG 2.0 AA level that Ontario’s web accessibility rules refer to.
- Ontario’s Accessibility for Ontarians with Disabilities Act (AODA). Where the AODA applies to us, we follow its requirements — including providing accessible formats and communication supports on request, and a way to give feedback.
We don’t claim any accessibility certification. Instead, we describe what we do and list what we haven’t fixed yet.
5. Known limitations
- Some steps, such as online booking and payment, may run on our providers’ pages, which we don’t control. If you can’t complete one, email us and we’ll set things up with you directly.
- The recorded greeting has a written transcript under “Read the greeting” wherever it plays. Sample calls are written conversations, not audio.
- When we publish video, it will have captions and a transcript before it is linked.
6. How do I report an accessibility barrier?
Email hi@infold.ai with “Accessibility” in the subject line. Tell us:
- the page or feature,
- what you were trying to do and what got in the way, and
- the device, browser or assistive technology you use, if you’re comfortable sharing it.
We’ll reply by email, tell you how and when we’ll fix it, and help you get what you need in the meantime.
7. Accessible formats
You can ask for any page or document — including our privacy notice and terms of service — in an accessible format, such as plain text or a format that works with your screen reader, at no extra cost. Email hi@infold.ai and we’ll agree a format and a timeline with you.
8. How we check
We test pages during development with automated checks and by hand, at phone, tablet and desktop widths. We’ll review this statement whenever the site changes significantly.
Latest check, 30 October 2026: Google Lighthouse’s accessibility audit scored 100 out of 100 on 14 of our main pages, including the home page, pricing, sample calls, booking, sign-up, industry and comparison pages, after we fixed the two issues it found. Our build also checks every page at three screen widths for text size, reduced-motion settings and the cookie bar. Automated tools catch only some barriers, so please tell us about anything that gets in your way.
- Draft 0.2 · 30 October 2026 · Added the latest check results.
- Draft 0.1 · 27 October 2026 · First draft.