Keyboard access
Navigation and interactive controls should work without a mouse, with visible focus and no keyboard traps.
Accessibility
DotMoose is building the public storefront toward WCAG 2.2 Level AA and treats accessibility barriers as product defects.
Our approach
Navigation and interactive controls should work without a mouse, with visible focus and no keyboard traps.
Semantic landmarks, descriptive headings, useful links, Canadian-English language metadata, and straightforward content help people and assistive technology understand each page.
Controls are designed for touch and keyboard use, reduced-motion preferences are respected, and sticky interface elements should not obscure keyboard focus.
Automated checks catch regressions, while production launch testing still includes keyboard, zoom/reflow, screen-reader, mobile, reduced-motion, and high-contrast checks.
Standard
That is our engineering target, not a claim that every production page has already passed an independent conformance audit.
Information should not depend on one sensory channel, tiny text, low contrast, or unexplained imagery.
People should be able to navigate and activate the site with keyboard, touch, and assistive input without being trapped.
Pages should use predictable interaction and semantic HTML that works across browsers and assistive technologies.
Include the page, what you were trying to do, and any browser or assistive-technology details you are comfortable sharing.
We use accessibility reports to identify and fix problems in the public site and customer paths.
Report an accessibility barrier