Accessibility statement

About this statement

Organization

Sixern Software

Website name

Sixern Software

Website address

https://sixern.ca

Date last reviewed

23 September 2026

Standard applied

WCAG 2.2 Level AA. We build toward that target. We do not claim we meet it.

Conformance status

We do not claim conformance. This is a self-evaluation using automated tooling plus a manual keyboard pass. No assistive-technology pass was run in the first assessment. A passing axe run is not a passing review.

We do not claim conformance with EN 301 549, the Accessible Canada Act, the Accessible British Columbia Act, or any other provincial regime. Those names appear only as explicit non-claims.

Feedback

Email hello@sixern.ca if you hit a barrier. That is the only published feedback channel. There is no phone line, postal address, or in-page form for accessibility reports, and no published response-time promise.

Organizational measures

What is true today:

• Accessibility is a named homepage principle.
• The quality harness in CI runs an automated WCAG 2.2 AA subset (axe), keyboard, reflow, no-JS, token contrast, HTML validity, and Lighthouse. That harness is the floor, not the verdict.

We do not have a published accessibility officer, staff training program, or procurement rule.

Assessment approach

Self-evaluation by the builders of this site. Not an external evaluation. Not a third-party audit. Not a certification.

Tested surfaces in the first pass included the live homepage at https://sixern.ca/, the custom 404 in automated tests, and these trust routes once they exist. Chromium on Linux was used for automated and keyboard checks. NVDA, VoiceOver, TalkBack, and Orca were not run.

Technologies

HTML and CSS are required to read the page. JavaScript is not. Nav enhancements and closing the mobile menu after a click are optional. The menu is a native details element.

Known limitations

• Skip link and focus: Activating Skip to content scrolls to #main, but programmatic focus stays on body; the next Tab lands on the first control in main.
• Target size: The house 44×44 CSS pixel bar is met for the hero CTA and mobile menu control, but not for footer mail or desktop primary nav links.
• In-page links that loop: Fixed when dedicated /about, /principles, /products, and /contact routes shipped. The homepage teasers now point at those routes.
• Hero CTA label: "See our work →" lands on the homepage #products teaser while Work is omitted; the label and destination differ on purpose until Work exists.
• Color as a cue: Some in-content links rely on accent color with underline only on hover or focus.
• Footer mailto: Distinguished mainly by color until hover or focus.
• Logo name: Markup adds redundant screen-reader text; no screen reader was run to confirm announcements.
• Products landmark: The #products section is labelled by the long-term thinking heading while the products card has its own h2.
• Terminal overlay: Decorative terminal uses role="img"; announcement was not tested.
• Not covered in the first pass: Screen readers, human zoom at 200% and 400%, text-spacing as a human pass, a second browser family, linked product sites, or a WCAG-EM sample.

These were observed in the first assessment. They are not a backlog of promised fixes.

Formal complaints

None published. Email hello@sixern.ca. There is no separate enforcement or ombudsperson path for this brochure.