Accessibility
How we try to be reachable.
Aperture is built to meet WCAG 2.2 AA. Some things still need work, and we'd rather name them than not.
01What we target.
-
WCAG 2.2 Level AA.
Our target across the marketing site and the Studio app. This includes the 2.2 additions for focus appearance (2.4.11 and 2.4.13).
-
A practitioner audience that includes people in their fifties and beyond.
Type size, contrast, and tap-target discipline are calibrated for readability across the actual range of the audience, not against a young-eyes default.
-
Keyboard-first navigation.
Every interactive control is reachable by keyboard. Skip links land. Focus rings are visible. Tab order is logical.
02What we've done.
-
We target WCAG 2.2 AA contrast across body, prose, and small text.
Paper-cream tokens are calibrated against the charcoal ground; a token pass to bring every small-text use to ≥4.5:1 is in progress. Small mono labels held to a higher floor for sub-14px sizes.
-
Visible focus indicators on every focusable element.
A site-wide :focus-visible rule renders an umber 1px outline with a 2px offset on keyboard focus. Mouse focus stays clean so the rings don't read as design accident.
-
Skip links as the first body element.
"Skip to content" lands every page, keyboard-reachable on first Tab.
-
Touch targets at 44 by 44 minimum.
Tap targets meet WCAG 2.2 minimum target size. Generous spacing between adjacent controls reduces mis-taps on mobile.
-
Reduced-motion respected.
The prefers-reduced-motion media query collapses all motion to static end-states across the site. No vestibular triggers.
-
Semantic HTML throughout.
Real headings, real lists, real buttons. ARIA used only where semantics fall short. SVG diagrams carry role="img" with title and description.
-
Form labels and error states.
Every input has a visible label. Error messages are programmatically associated. Required fields are indicated.
03Known limitations.
-
Native browser controls in some checkout and date-picker flows.
The Paddle checkout overlay and the native datetime-local input use vendor and browser default chrome at v1. Both pass WCAG AA via the vendor and browser; replacement with custom components is scoped for Phase 2.
-
Some decorative diagrams use aria-hidden.
The iris wordmark glyph is decorative-only and marked aria-hidden. Conceptual diagrams that carry information have proper labels and descriptions.
-
Image-protection on deck images.
Drag, save, and right-click are disabled on deck images via CSS and a context-menu blocker. This does not interfere with click or keyboard activation. Screen-reader announcement of image content uses alt text where set by the curator.
-
Color-only signals are minimized but exist.
Active states use color plus shape (umber underline plus border-bottom thickness). One or two places still rely on color alone; surfaced in the next audit pass.
04How to report.
-
Write to us.
Email hello@aperturedeck.com with "Accessibility" in the subject. Tell us the page, the device, the browser, and what you ran into. We respond within seven days.
-
Specific is helpful, lived is enough.
A precise reproduction is great. So is "the form on the pricing page felt cramped on my phone." We don't gatekeep what counts as a real accessibility issue.
05Review cadence.
-
Annual review.
Once a year, a written accessibility review. Findings and remediation tracked in the annual transparency report.
-
Ad-hoc when reports come in.
Reported issues are triaged on receipt, not held for the next review cycle. Material fixes ship promptly.
Run into something that isn't reachable? Write to hello@aperturedeck.com.