Skip to main content

Accessibility Statement

Last reviewed: August 8, 2026

We want every part of this site to work for you, including if you use a screen reader, navigate by keyboard, rely on captions, or need larger text. This page sets out what we build to, what is actually in place today, where we know we fall short, and how to reach a person if something on this site blocks you.

We are writing this as a small company that does its own front-end work. We would rather publish an honest list with gaps on it than a badge we did not earn.

The standard we aim for

Our working target is the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We do not claim full conformance with that standard, and we have not commissioned an independent audit. Treat this as a statement of intent and current practice, not a certification.

Call Force Global Inc. is an Ontario company, and we are aware of the information and communications requirements set out under the Accessibility for Ontarians with Disabilities Act. WCAG 2.1 AA is the bar we work toward across the public site.

What is in place today

Each of the items below was checked against the live pages on August 8, 2026, not just against our stylesheets:

  • Semantic structure: pages use real landmarks (header, nav, main, footer), a single h1, and ordered headings, so screen reader users can jump through a page by structure instead of reading it top to bottom.
  • Keyboard navigation: menus, buttons, forms and accordions use native HTML elements. The mobile menu is a native disclosure control that opens with Enter or Space, and there are no keyboard traps in the main navigation.
  • Visible focus: every link, button, input, select, textarea and disclosure gets a site-wide focus ring, a 2 pixel ocean blue outline with a white halo, so the focused element stays visible on both light and dark sections.
  • Skip to main content: the first item you reach with Tab on our main page templates jumps past the navigation straight to the page content.
  • Alt text: all 1,319 images across our public pages carry an alt attribute, and decorative graphics are hidden from assistive technology rather than given filler text.
  • Contrast: we check colour contrast on rendered pages using computed styles rather than the values written in the stylesheet, targeting 4.5:1 for body text and 3:1 for large text and interface elements. Our teal brand colour is used as a fill behind dark text, never as text on white.
  • Reduced motion: when your operating system reports a preference for reduced motion, our scroll-in animations and the cookie notice transition are switched off.
  • Text and zoom: layouts use relative units and reflow down to a 390 pixel viewport, so browser zoom and larger default text sizes do not clip content or force horizontal scrolling.
  • Form labels: form fields on our contact and application pages have real labels, and errors are described in text rather than by colour alone.

Where we know we fall short

These are open gaps, not hypotheticals. They are on our list:

  • Skip link coverage: 49 of our 402 public pages, mostly older single-purpose campaign and tool pages, do not yet carry the skip to main content link.
  • No assistive technology audit: we have not completed a full screen reader pass on every page. Our testing is strongest on the pages people actually land on, and thinnest on deep service and location pages.
  • PDF downloads: the worksheets, blueprints and guides we publish as PDFs are not tagged for screen readers. If you need one of them in an accessible format, email us and we will send the content as plain text or HTML.
  • Decorative typography: some marketing pages use layered gradient graphics and stylised type where we have not finished checking how the page is announced by assistive technology.

Parts of the site we do not control

Some functionality on this site comes from third parties. We choose the vendors, but we do not write their code and we cannot fix their accessibility issues directly:

  • Cal.com supplies the booking calendar used to schedule calls with us.
  • Cloudflare Turnstile supplies the anti-spam check on our forms.
  • Our chat widget and any embedded maps or video players.
  • Google Analytics and Microsoft Clarity run in the background for analytics. Clarity records on-page activity such as clicks and scrolling, and you can turn both off from the cookie notice at the bottom of the page or from the choices described in our Privacy Policy.

If one of these embeds blocks you, we will do the same thing manually. You can book a call, get a written quote, or submit an application entirely by phone or email, and nothing on this site is the only route to reach us.

How we test

Before a new page goes live we run a keyboard-only pass, take screenshots at 1440 and 390 pixels wide, and run a contrast check against the rendered page using computed styles. We also run automated performance and accessibility checks with Lighthouse. Automated tools catch a minority of real problems, which is why the reporting route below matters more than any score we could publish.

Tell us about a problem

If any part of this site is hard or impossible for you to use, tell us and we will fix it or get you the information another way.

It helps if you can include the page address, what you were trying to do, and the browser or assistive technology you were using. We respond within 5 business days. If a fix will take longer than that, we will tell you what we are doing and give you a way to get what you needed in the meantime.

Last reviewed

This statement was last reviewed on August 8, 2026 by Miki Furman, Founder and CEO. We review it whenever we ship a significant change to the site, and at least twice a year.

See also our Privacy Policy, Terms of Service, and Security and Data Protection page.