L E G A L · A C C E S S I B I L I T Y
Accessibility Statement
Effective May 24, 2026. We want every visitor to be able to use this site, including people who use assistive technology like screen readers, switch devices, or voice control. If something doesn’t work for you, tell us and we’ll fix it.
What we are aiming for
Sisu Development is committed to digital accessibility for everyone. We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium. WCAG 2.1 AA covers a wide range of recommendations for making web content more accessible to people with disabilities, visual, auditory, motor, and cognitive.
What we have done
- Semantic HTML. Pages use proper heading levels (one H1 per page, logical H2 to H4 structure), landmark regions (
main,nav,footer), and labeled forms. - Keyboard navigation. Every interactive element, links, buttons, form fields, accordions, is reachable and operable with the Tab and arrow keys. Visible focus indicators are styled with a 2px gold outline.
- Color contrast. Body text and primary UI meet or exceed the WCAG AA contrast minimums (4.5:1 for normal text, 3:1 for large text). We test new pages with automated contrast tools.
- Image alternatives. Meaningful images have descriptive
alttext. Decorative images are markedalt=""so screen readers skip them. - Skip links. Every page begins with a “Skip to content” link for keyboard users.
- Resizable text. Content reflows down to mobile widths and supports 200% browser zoom without loss of functionality.
- Bilingual structure. Spanish pages use
lang="es"so screen readers pronounce them correctly. - Reduced motion. We honor the
prefers reduced motionmedia query on animated elements.
Known issues we are working on
The site is a work in progress and there are places we know we still need to improve:
- Some legacy journal posts use color combinations that pass AA for normal text but fall short for thin or small text. We’re updating older posts as we go.
- PDF downloads (Planning Guide, plan sheets) are being re exported as tagged, screen reader friendly PDFs. Until then, if you need an alternative format, email Daniel and we’ll send you an accessible version.
- Video content (when we add it) will include captions and a transcript.
How we test
- Automated testing with axe DevTools and Lighthouse on every page before publish.
- Manual keyboard testing on every page template.
- Screen reader spot checks with VoiceOver (macOS / iOS) and NVDA (Windows).
- Color contrast checks against WCAG AA thresholds.
If something does not work, tell us
If you can’t access a page, can’t complete a form, can’t read content because of a contrast or sizing issue, or run into anything else that gets in the way, we want to know about it. We respond inside two business days and we will work with you to provide the information you need in another format.
When you reach out, it helps if you can tell us the page URL, the assistive technology or browser you’re using, and what you were trying to do. Don’t worry about being technical, describe it in your own words.
Third party content
Some content on the site is provided by third parties, embedded videos, fonts from Google Fonts, partner lender prequalification forms. If one of those tools gets in your way, contact us and we’ll get you the information another way.
Formal complaints
If you’ve contacted us about an accessibility issue and aren’t satisfied with the response, you can also file a complaint with the U.S. Department of Justice Civil Rights Division, or your state attorney general’s office. We’d much rather hear from you directly and fix it, but you have the right to escalate.