Evidence over assumption
Quality claims with visible boundaries.
This page records what the project verifies, what it targets, and what still depends on production evidence. Last reviewed 21 September 2026.
Automated and inspected
- ESLint and strict TypeScript compilation
- Vitest component, route, privacy-control, contrast, and accessibility checks
- Next.js production compilation and static route generation
- Keyboard focus, named controls, reduced motion, and 390-pixel reflow inspection
- npm advisory scan and high-confidence secret-pattern scan
- Enforced security headers and privacy-preserving contact validation
Explicit limitations
- Automated checks support accessibility work but do not certify WCAG conformance.
- Performance claims require measurements from the final public production URL.
- Live email delivery, provider retention, and public Vercel access require deployed account configuration.
- Legal applicability depends on the owner, audience, activity, and jurisdiction.
For the implementation details, inspect the project source and quality workflow. To report a problem, use the contact section.