Accessibility statement.

Grid Maker Pro is built to be usable by everyone. We target WCAG 2.2 Level AA across the site and the in-browser tool. What follows is the public ledger — what's covered, what's known to need work, and how to tell us when we've missed.

Conformance target.

We target WCAG 2.2 Level AA. Static content pages — catalogue, pillars, blog, glossary, audience hubs, colophon — substantially conform. The interactive hero tool, being a canvas-based drawing surface, has known accessibility limitations that are documented below rather than papered over.

How we audit.

Three audit layers run continuously:

• Automated source audit — scripts/audit-accessibility.mjs runs on every build, catching missing alt text, button labels, lang attributes, heading-level skips, and placeholder links.
• Browser-runtime audit — axe-core in Chrome DevTools, run quarterly by hand. Catches contrast issues, focus-order problems, ARIA misuse.
• Keyboard navigation testing — quarterly. Every interactive element reachable via Tab, every action triggerable via Enter or Space.

What's accessible.

• All static content pages — semantic HTML, heading hierarchy, alt text on meaningful images, ARIA labels where needed.
• Site navigation — keyboard-navigable, with focus states and a skip-to-main link.
• Forms — every input has an associated label; error states are programmatically announced.
• Color contrast — body text meets 4.5:1; large text meets 3:1. Most of the site is pure white on near-black, well above thresholds.
• Text resize — pages reflow up to 200% zoom without horizontal scroll.
• Motion — no auto-playing video, no parallax, no infinite-scrolling carousels. Mega-menu hover panels respect prefers-reduced-motion.

Known gaps.

• The hero tool's drawing canvas is not screen-reader accessible. Composition overlays are inherently visual. We expose every overlay's name + description in the text-content sidebar and via the overlay data API for assistive contexts that can render structured equivalents.
• Stylus-pressure features assume a pointer device. Keyboard-only users can use mouse/touch equivalents but not the pressure-sensitive flows.
• The mega-menu hover dropdowns work via mouse hover or keyboard focus; touch users tap the parent link, which navigates to the section root instead of expanding the dropdown. By design — a touch-UI tradeoff.
• Some legacy WordPress-imported images in the older blog post archive may have generic alt text. These are being upgraded as posts are refreshed.

Browser + assistive technology support.

• Screen readers tested: NVDA + Firefox (Windows), VoiceOver + Safari (macOS), VoiceOver + Safari (iOS), TalkBack + Chrome (Android).
• Keyboard-only navigation: tested on Chrome, Firefox, Safari, Edge.
• Voice control: works via macOS Voice Control and Windows Voice Access for site navigation; the canvas tool is not voice-controlled.
• High-contrast mode: Windows High Contrast supported; macOS Increase Contrast supported.

Report an issue.

Email accessibility@gridmakerpro.com with:

• The page URL where you encountered the issue.
• The assistive technology you were using — screen reader, voice control, keyboard-only.
• A description of what you tried and what went wrong.

Standards reference.

This statement references the Web Content Accessibility Guidelines (WCAG) 2.2. Last reviewed: 2026-05-17.