Accessibility
Accessibility Statement
Everyone should be able to read this site, find what we do and ask for help, whatever device, browser or assistive technology they use.
Last reviewed: October 21, 2026
1. Our goal
We aim for runtulalo.com to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG is the standard published by the World Wide Web Consortium (W3C) and used by the ADA Title II rule for state and local government websites.
We treat accessibility as part of how a page is built, not a feature added at the end.
2. How the site is built
- Plain, semantic HTML with one main heading per page and headings in order.
- A "skip to content" link, visible keyboard focus and controls that work with a keyboard alone.
- Text and background colors chosen to meet WCAG contrast ratios.
- Motion that switches off when your device asks for reduced motion. Every animated section still makes sense without it.
- Pages that resize to phone width and allow zoom, with no sideways scrolling.
3. How we test
Before changes go live we run an automated WCAG 2.2 AA check (axe-core) on the main pages at phone width, with motion both on and off, and we check pages with a keyboard. The latest check on October 21, 2026 found no automated failures on the home, systems, work, pricing, about, resources, audit, contact and privacy pages.
Automated tools catch only part of what matters, so we also fix anything people report to us.
4. Known limits
Our audit form, contact form and booking calendar are provided by our CRM platform (HighLevel) and load inside the page from their servers. We test them, but we don't control all of their code. If one of them doesn't work for you, email us and we'll take your request directly.
Some guides link to other websites. We can't promise those sites are accessible.
5. Report a problem
If something on this site is hard to use, tell us what page you were on and what happened: support@thomasandruntulalo.com. You can also use our contact page.
We'll reply, work on a fix and help you get what you came for in another way in the meantime.
6. Client websites
The websites we build for clients go through the same checks before launch. Each client owns their own site and its accessibility statement.
Also read our Privacy Policy and Terms & Conditions.