Reading and Navigation
Pages use one descriptive main heading, followed by section headings and nested subheadings where useful. The skip link moves past repeated navigation. Tool directories, guides and policy links use descriptive text so the destination is understandable without guessing from a generic “click here”.
Text can be enlarged with browser zoom. Responsive layouts stack input and result panels on smaller screens. Tables that need more width have a horizontal scrolling container; their headers and captions remain in the document rather than being drawn into an image.
Forms and Results
Inputs have visible labels and keyboard focus styles. Validation errors use text, not just a colour change. Result panels name the output and keep units visible. Copy and print controls are provided where supported, with an explicit fallback when the clipboard is unavailable. The page does not equate a successful copy action with a saved account or permanent record.
Motion, Sound and Permissions
Reduced-motion preferences disable decorative transitions. Deliberate monitor-motion tests still need movement to perform their task, so start them only when comfortable and use their Stop control. Sound tests can be audible and media checks need browser permission; their controls remain part of the ordinary page.
Full-screen patterns, camera previews and input capture have their own task-specific controls. Browser and device support can differ. A screen-reader user may need the written explanations instead of a visual pattern. The website cannot provide an equivalent optical inspection of a physical monitor through text alone.
Known Review Limits
The build and markup checks confirm labels, structure and routes. They do not replace screen-reader testing, keyboard-only walkthroughs, high-contrast review or actual mobile and device testing. No claim of certified accessibility or full standards conformance is made. Native editorial review of the five editions remains a separate task.
Tell Us What Blocks a Task
Use the Contact form and select Accessibility Problem, or email contact@savvytoolkit.com. Include the page, edition, browser, assistive technology and action that failed. State the result you needed and the barrier encountered. Avoid sending personal files or credentials. Reproducible steps help us examine the control, explanation and focus sequence.