Keyboard
Aim for a logical keyboard order, visible focus, and familiar menu and tab keys. Actual keyboard checks are documented for each release.
09 / ACCESSIBILITY
Built to be used
by everyone it can reach.
How this website and the websites Mado builds are made usable with a keyboard, a screen reader, reduced motion or a small screen; what is checked; and how to report a problem.
PRACTICES
Practices we aim to apply,
in each build.
Screen readers
Use structured headings, meaningful text alternatives or decorative image markings, and field-specific form messages. Screen-reader checks require separate testing.
Reduced motion
Scroll-linked movement is designed to respect your system's reduced-motion preference. Some static dimensional layouts remain; essential content does not rely on animation.
Text and contrast
Use real text and review size, spacing and contrast for smaller screens. Real-device readability remains part of the agreed checks.
Forms
This website sends nothing itself; the forms prepare drafts you review and send, with clear messages when something needs fixing.
Without scripts
Keep core content and navigation available without scripts. Enhanced planners and comparisons need JavaScript and provide a direct email alternative.
LIMITS
Said
plainly.
These are design and review targets. They are not a certification or a legal conformance claim, or proof on every browser, device or assistive technology. Testing is documented separately for each release. The concept websites are demonstrations, and their screenshots are images described in text. Use the email below to report a problem; this website does not send a report itself.
REPORT A PROBLEM
Tell us
what blocked you.
Email jack@madebymado.com with the page, what you were trying to do, and the browser or assistive technology you use. For client websites the same practices are part of every build, and a motion, accessibility and performance review is listed in the Flagship scope.