Clear Information Should Be Usable Information.

Our Approach

This site is designed with semantic structure, keyboard access, visible focus indicators, readable contrast, responsive text, labeled controls, and reduced-motion support, with WCAG 2.2 AA as the target.

How We Test Accessibility

Accessibility testing uses multiple layers because automated checks are useful for repeatable defects but cannot determine whether a site is fully accessible on their own.

• Automated browser testing: Playwright and @axe-core/playwright run accessibility scans across the site’s public-route test inventory using WCAG A and AA rule tags, including WCAG 2.2 AA.
• Regression testing: Automated checks cover semantic heading structure, skip navigation, keyboard operation, visible focus, narrow-screen reflow, text-spacing resilience, reduced-motion behavior, form labels and validation, live-status regions, horizontal overflow, and visual regression.
• Human review: Targeted checks include keyboard-only navigation, 200% browser zoom, and Windows Narrator smoke testing of navigation, article reading, and the contact form.

When a reproducible accessibility defect is found, the goal is to fix the barrier and add regression coverage when the behavior can be tested deterministically. Human review remains part of the process for issues that automated tools cannot meaningfully judge.

Known Limitations

No known accessibility barriers are currently documented. That does not mean none exist; feedback and ongoing testing help identify issues that automated checks can miss.

Feedback

If you encounter a barrier or need information in another format, email admin@structured-ink.com. Please describe the page and the problem, and Structured Ink will work to provide an accessible alternative.

Ongoing Work

Accessibility is an ongoing practice. This statement describes the intended approach and does not claim third-party certification.