Accessibility Statement

SyncReach Solutions Inc. is committed to making this website usable by as many people as possible, including people who use screen readers, keyboard-only navigation, magnification, or other assistive technology. This statement describes where we actually stand — including what is still not fixed.

01 Our commitment

We build websites for a living, including for clients whose own users depend on accessible design. We consider it reasonable to hold our own site to the standard we recommend to others.

Accessibility is not a one-time certification. It degrades as content is added and features change. We treat it as ongoing maintenance, and this page is where we report on it honestly rather than claiming a level of conformance we have not verified.

02 Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for making web content more accessible. This website is partially conformant with WCAG 2.2 Level AA.

“Partially conformant” is a specific term: it means most of the site meets the standard, but some content does not fully conform. We are using it deliberately rather than claiming full conformance, because we have not completed assistive-technology testing and we know of outstanding issues. Those are listed in section 04.

We are not aware of any remaining Level A or Level AA failures detected by automated testing. That is a meaningful but limited claim — automated tools reliably catch only about a third of real accessibility barriers.

03 What we've done

Measures currently in place across the site:

• Semantic HTML with a single <h1> per page, correct landmark structure, and a “Skip to main content” link on every page
• All colour combinations used for text meet or exceed the WCAG AA contrast minimum of 4.5:1; most substantially exceed it
• Descriptive alternative text on all images
• Every form field programmatically associated with a label, with autocomplete attributes so browsers and assistive technology can identify each field's purpose
• A visible keyboard focus indicator on all interactive elements
• The pricing calculator announces estimate changes to screen readers through a live region, and every control has an accessible name
• Reduced-motion preferences are respected for animation and scrolling
• Language declared on every page for correct screen reader pronunciation

04 Known limitations

Despite the above, we know about the following problems. We are listing them so you are not left guessing, and so you know we are aware rather than oblivious.

• Heading levels skip on some pages. Several blog posts and internal design-study pages jump from one heading level to another without the intermediate level. Screen reader users navigating by heading may perceive a missing section. We are correcting these as we revise each post.
• One blog post contains an empty heading. It is announced as a heading with no text. Fix pending.
• Two elements on one design-study demo page sit outside the main landmark. These pages are portfolio concepts rather than core site content, and are lower in our queue.
• The pricing quote form uses hidden labels. Each field has a programmatic label and a visible placeholder, but no visible persistent label. This meets the standard, but a visible label that stays on screen after you start typing would serve people with cognitive and memory-related disabilities better. We intend to redesign that form.
• We have not yet tested with real assistive technology. No verification has been done with NVDA, JAWS, or VoiceOver, and no full manual keyboard walkthrough has been completed. This is the most significant gap in our testing and the next thing we plan to address.
• Third-party content. Parts of our site rely on services we do not control, including Google Tag Manager, Google Fonts, and our form-delivery provider. We cannot guarantee the accessibility of code these services inject. Where we find a barrier, we will either work around it or replace the provider.
• Older blog content. Posts published before we adopted our current review process have not all been re-audited.

05 How we tested

This statement is based on a self-assessment carried out in August 2026. Our approach:

• Automated testing of all 26 published pages using axe-core against WCAG 2.2 A and AA rules
• A second automated pass with JavaScript executed, to test interactive components that do not exist in the static HTML — this is how we found and fixed unlabelled controls in the pricing calculator that a conventional scan reported as clean
• Manual review of page source for heading structure, landmarks, alternative text, link purpose, and form labelling
• Contrast ratios computed directly from our design tokens rather than sampled visually

We want to be clear about what this does not include: no screen reader testing, no manual keyboard walkthrough, no testing with users with disabilities, and no independent third-party audit. A self-assessment is not certification, and we do not present it as one.

06 Report a barrier

If you encounter something on this site you cannot use, please tell us. You do not need to know why it is broken or use any particular terminology — describing what you were trying to do and what happened is enough.

• Email: [email protected]
• Phone: +1 (289) 270-1009
• Contact form: syncreach.io/contact

Please include the page address, what you were trying to do, and — if you know it — the browser and assistive technology you were using.

We aim to acknowledge accessibility reports within 5 business days and to give you a substantive response, including a timeline for a fix, within 10 business days. If a barrier prevents you from accessing information or completing something on our site, tell us what you needed and we will provide it another way while we work on the fix.

07 Regulatory context

We are an Ontario corporation serving clients in Canada and the United States. For transparency, here is how the relevant regimes actually apply to us:

Ontario — AODA

The Accessibility for Ontarians with Disabilities Act and its Integrated Accessibility Standards Regulation require public-sector organizations and private-sector organizations with 50 or more employees to meet WCAG 2.0 Level AA on public-facing web content. SyncReach is below that employee threshold, so that specific technical requirement does not currently bind us by law. We are working to the newer WCAG 2.2 Level AA standard regardless, because the threshold reflects organizational size rather than whether people need to use the site.

Canada — Accessible Canada Act

The Accessible Canada Act applies to federally regulated entities. SyncReach is not federally regulated, so the ACA does not apply to us. We reference it because clients in regulated sectors sometimes need to know.

United States — ADA

Title III of the Americans with Disabilities Act has been widely interpreted by US courts to cover the websites of businesses serving the public. There is currently no federal regulation specifying a technical standard for private businesses, and no compliance deadline — but WCAG 2.1 and 2.2 Level AA are the benchmarks used in litigation and enforcement. We therefore treat WCAG 2.2 AA as our working standard.

We deliberately avoid describing this site as “ADA compliant.” No such certification exists for private websites, and claiming it would be misleading.

08 Ongoing work

Planned, in rough priority order:

• Screen reader testing of the contact form and pricing calculator with NVDA and VoiceOver
• A full keyboard-only walkthrough of every interactive component
• Correcting heading structure across older blog posts
• Redesigning the pricing quote form to use visible persistent labels
• Adding accessibility checks to our deployment process so regressions are caught before publishing

We will update this page as items are completed, and revise the date at the top. If something here is out of date or inaccurate, please let us know.