Accessibility Statement

Website Blueprints should work for everyone, including people who use a keyboard, a screen reader, voice control, magnification or high-contrast settings. This page explains what we do, what we know isn't perfect yet, and how to tell us about a problem.

Our commitment

We aim for every page and tool on websiteblueprints.tech to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Accessibility is part of how we build each tool, not a separate project, and we fix reported problems as a priority.

What we do

Structure: pages use semantic HTML with one main heading, headings in order, landmark regions (header, navigation, main, footer) and a page language.
Keyboard access: a "Skip to main content" link is the first item on every page, controls are reachable with the keyboard, and focus is always visible. Visual editors that use dragging, such as the gradient, clip-path and easing tools, also accept keyboard input and typed values.
Color and contrast: text and controls are checked against WCAG contrast ratios, and you can switch between dark and light themes from the gear menu in the header.
Forms and results: form fields have labels. Tools that run a check or lookup, such as the SSL, DNS and accessibility checkers, announce their results to screen readers when they appear, and generators show their output as text you can read and copy.
Motion: animations are reduced or removed when your device is set to reduce motion.
Zoom and reflow: pages work when zoomed to 200 percent and on screens as narrow as 320 pixels, without sideways scrolling.
No overlays: we don't use accessibility overlay widgets. We fix the site itself instead.

How we test

New and updated pages are checked with automated tools (Google Lighthouse and axe-core, the same engine behind our ADA Compliance Checker) and reviewed at phone and desktop sizes before they go live. Automated tools catch only part of what WCAG requires, so we also review new tools with the keyboard and fix issues as we find them or as they're reported.

Known limitations

Visual previews: some tools exist to produce something visual, such as gradients, color palettes, logos and image previews. The previews themselves are images; the code, values and settings that produce them are available as text.
Third-party content: advertising served by Google AdSense, fonts loaded from Google Fonts in the font tools, and pages loaded inside the Responsive Tester come from third parties, and we can't guarantee they meet WCAG.
Downloaded files: files the tools generate for you (PDFs, images, QR codes) are created from what you enter; we can't guarantee their accessibility.

Report a barrier

If something on this site doesn't work for you, or you need information in a different format, please tell us. Email info@websiteblueprints.tech or use the contact page, and include the page address and what happened. We aim to reply within 5 business days.

Technical details