Skip to main content

Legal

Accessibility Statement

Accessibility Statement

Codepixel is committed to making codepixel.me usable by everyone, including people with disabilities. This statement describes our conformance target, our current state, known limitations, and how to report a problem.

1. Our commitment

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as a baseline for codepixel.me. This is the standard expected by:

  • The EU European Accessibility Act (Directive 2019/882, enforcement from 28 June 2025) for commercial websites in the EU.
  • The US Americans with Disabilities Act (ADA) Title III, as interpreted for public-accommodation websites.
  • Canadian Accessible Canada Act (ACA) and the BC Accessible British Columbia Act.

2. Conformance status

Status: Partially conformant with WCAG 2.1 Level AA.

"Partially conformant" means that most parts of the site meet the standard, but some content or interaction patterns do not yet fully meet it. We are working to close those gaps.

This declaration is based on:

  • Internal review against WCAG 2.1 AA success criteria.
  • Code-level audit of accessibility patterns (semantic HTML, ARIA usage, keyboard navigation, focus management, reduced-motion handling).
  • An automated audit pass (axe) across key page templates in July 2026, after which all critical- and serious-severity ARIA findings were fixed and focus-ring styles were unified site-wide.
  • Manual testing with VoiceOver (macOS/iOS) and NVDA (Windows).

A formal third-party audit has not yet been performed. We plan one within 12 months of launch.

3. What we do well

  • Semantic HTML with appropriate landmark roles (header, nav, main, footer).
  • ARIA roles and attributes added where native semantics fall short.
  • Keyboard navigation across all interactive elements, with visible focus indicators driven by a dedicated focus-ring design token.
  • prefers-reduced-motion is honored: scroll-linked animations, transitions, and decorative motion are disabled or significantly toned down for users who opt out via their OS setting.
  • Color contrast uses design tokens chosen for WCAG AA conformance on primary text/background pairs.
  • Responsive layout down to 320 px width without horizontal scroll.
  • Form accessibility: visible labels, programmatic associations, meaningful error messages, descriptive autocomplete attributes where appropriate.
  • No motion-triggered content that auto-plays beyond 5 seconds.

4. Known limitations

We are transparent about gaps. Currently we know about:

  • Color contrast on a small number of text/background pairs does not yet meet the AA ratio. We are migrating the affected elements to AA-conformant design tokens.
  • A full manual WCAG 2.1 AA review (beyond automated tooling and targeted screen-reader testing) has not yet been completed across every page template.
  • Scroll-linked GSAP animations are toned down under prefers-reduced-motion, but in some sections the reduced fallback could be more aggressive. We are reviewing case-by-case.
  • Embedded Pipedrive Scheduler iframe: the booking experience inside the iframe is delivered by Pipedrive. Its accessibility is governed by Pipedrive's own conformance statement. We surface a "contact form" fallback path so that users who cannot use the scheduler still have a way to reach us.
  • Brand video content, where present, is currently provided without captions or audio descriptions. We aim to add captions where the video carries spoken information.
  • Long-form blog and documentation pages have not been individually audited for heading structure on every article. We are improving the authoring template.

We update this list as we resolve items and as new ones come up.

5. Compatibility

We test the site on:

  • Browsers: latest Chrome, Firefox, Safari, Edge.
  • Screen readers: VoiceOver (macOS/iOS), NVDA (Windows). Limited testing with JAWS.
  • Operating systems: macOS, Windows 11, iOS, Android.
  • Input methods: mouse, keyboard, touch. Voice control is supported where the browser/OS handles it natively.

If you use an older browser or assistive technology and run into issues, let us know (see Section 8).

6. Technical specifications

The site is built with HTML5, CSS3, and JavaScript (progressive enhancement where feasible). We use WAI-ARIA 1.2 patterns where native HTML does not expose the required semantics. The site requires JavaScript for full interactivity (e.g., the consent banner, scheduler iframe gating, and animation enhancement).

7. Assessment approach

Our internal assessment combines:

  • Manual review against WCAG 2.1 AA success criteria.
  • Automated testing with browser-based accessibility checkers (axe, WAVE) on key page templates.
  • Code review in every pull request, with an accessibility checklist that includes keyboard navigation, focus visibility, color contrast, and reduced-motion handling.

8. Reporting an issue

If you encounter content or functionality on codepixel.me that is not accessible, please tell us. We will respond promptly and work to fix it.

  • Email: privacy@codepixel.me (subject: "Accessibility").
  • Please describe the problem, the page URL, your browser/assistive technology, and (if you can) what you were trying to do.

We aim to acknowledge accessibility reports within 5 business days. Substantive issues are prioritized for a fix in the next deployment cycle.

9. Enforcement procedure

If you are in the EU/EEA, you also have the right to lodge a complaint with the relevant national accessibility ombudsman or supervisory authority if we do not respond satisfactorily.

If you are in Canada, you may contact:

  • Accessibility Standards Canada / Accessibility Commissioner.
  • For BC residents, the appropriate BC accessibility regulator under the Accessible British Columbia Act.

10. Last reviewed

2026-08-19 — v1.1. Next scheduled internal review: 2027-05-22 (annual). We intend to commission a formal third-party WCAG 2.1 AA audit within 12 months of public launch and will update this statement when complete.

Change log

  • v1.1 — August 2026. Updated the known-limitations list after a July 2026 automated audit pass: critical- and serious-severity ARIA findings were resolved and focus rings unified, so the list now leads with a small set of color-contrast pairs and the outstanding full manual WCAG review.
  • v1.0 — Initial publication (May 2026).