Accessibility Statement

Two Oaks Technologies LLC ("Two Oaks," "we," "us," or "our") believes the businesses, patients, contractors, and neighbors who visit two-oaks-technologies.com (the "Site") should all be able to actually use it — including people who navigate by keyboard, use a screen reader, rely on captions, or need larger text and higher contrast. This page describes what we do to make that true, what standard we're aiming for, where the honest limits are, and how to reach us if something on the Site isn't working for you.

1. The standard we aim for

We target the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, published by the W3C. That's the same benchmark used by the U.S. Department of Justice under the Americans with Disabilities Act (ADA), by U.S. federal agencies under Section 508, and by the European Accessibility Act. It covers four principles: content should be perceivable, operable, understandable, and robust.

Aiming at a standard is not the same as guaranteeing every page meets it perfectly on every device, in every browser, for every assistive technology, at every moment. If you find something that doesn't work for you, please tell us — see Section 5.

2. What we've done

Concrete measures in place on the Site today:

• Keyboard-only navigation. Every interactive element — every link, button, form field, and the mobile menu — is reachable and usable with just the Tab, Shift+Tab, Enter, and Space keys. A visible focus ring shows where you are on the page.
• Skip-to-content link. The first thing a keyboard or screen reader user hits on every page is a "Skip to main content" link that jumps past the site header.
• Semantic structure. Pages use real HTML landmarks (<header>, <nav>, <main>, <footer>) and a proper heading hierarchy so screen readers can navigate by section and heading.
• Meaningful alt text. Images that convey information have descriptive alternative text. Purely decorative marks (like the small emblem in the header) are marked as decorative and skipped by screen readers instead of being read aloud pointlessly.
• Labeled forms. Every form field on the contact and quick-lead forms has a visible label that's programmatically tied to its input. Required fields are marked both visually and to assistive technology.
• Color contrast. The forest green + antique gold palette was chosen and then tested — every text-on-background combination the Site uses meets or exceeds WCAG AA (4.5:1 for normal text, 3:1 for large text). Body text and headings clear AAA (7:1) on the primary background.
• Reduced-motion respect. If your operating system is set to "reduce motion," the animated hero canvas, the typed footprint-audit terminal, and the scroll-reveal animations all stop moving. Content stays visible and usable — you just don't have to sit through the animation.
• Responsive layout. The Site reflows down to phone widths and up to large monitors without horizontal scrolling, and stays readable at browser zoom up to 200%.
• Plain language. Copy is written to be read out loud in a conversation, not decoded — no jargon walls, no unexplained acronyms.
• No auto-playing audio or video. Nothing on the Site plays sound or video without you asking for it.

3. Assistive technology we've tested with

The Site is regularly reviewed with the following tools and configurations:

• Keyboard-only navigation in current versions of Chrome, Safari, and Firefox on macOS, Windows, and iOS.
• VoiceOver on macOS and iOS, and NarratorView on Windows, for reading order and landmark navigation.
• Browser zoom to 200% and forced high-contrast mode.
• Automated checks (Lighthouse and axe DevTools) as a baseline — with the caveat that automated tools catch roughly a third of real accessibility issues; human review catches the rest.

4. Known limitations

Being honest about the edges:

• Third-party embeds. The Site currently uses Netlify Forms for the contact form and Google Analytics 4 for optional traffic measurement (with a consent banner — see our Privacy Policy). Both are third-party services whose exact accessibility posture we don't fully control; we picked them because they're the least invasive tools that do the job. If either creates a barrier for you, tell us and we'll route around it.
• The cookie-consent banner itself. The Accept/Decline banner that appears on your first visit is a modal-like element pinned to the bottom of the screen. Both buttons are real buttons and reachable by keyboard, but if you find it fiddly on your particular assistive-technology setup, please let us know.
• PDF or Word documents linked from the Site. If any proposal or reference document linked from a Site page isn't fully tagged for accessibility, ask us and we'll send you an accessible version.
• Ongoing content. New pages and edits go through the same accessibility checks, but a mistake occasionally slips through. Section 5 is the fastest way to get one fixed.

5. Report a problem or ask for help

If you run into anything on this Site that's hard or impossible to use with your assistive technology, or you'd like content in a different format, contact us directly and we'll get it addressed — usually within one to two business days:

Email: mike@two-oaks-technologies.com
Phone: 256-529-0546
Text: send a text

Please include the page URL, what you were trying to do, and (if you're comfortable sharing) the browser and assistive technology you're using. That's usually all we need to reproduce and fix the issue.

6. About accessibility conformance claims

We describe the Site as built to WCAG 2.1 AA, not as "certified compliant." That's a deliberate choice. Accessibility conformance depends on the whole runtime environment — the current version of the code, the browser, the assistive technology, and the individual user — so a static compliance stamp would overpromise. What we can and do commit to is aiming at the standard, testing against it, and fixing what's reported.

7. Assessment approach

This statement is based on a self-assessment using WCAG 2.1 AA as the target, combined with the tools listed in Section 3. It was last reviewed on the "Last updated" date at the top of this page and is refreshed whenever we ship a substantial change to the Site.

8. About accessibility on client sites we build

Every website we build for a client starts from the same accessibility foundation used on this Site — semantic HTML, keyboard operability, meaningful alt text, WCAG AA contrast, visible focus, labeled forms, reduced-motion support. On our Care Plans, the ongoing edits we make on your behalf follow the same rules. This gives you a solid AA baseline, not a compliance guarantee — for the same reason described in Section 6.

9. Related pages

See also our Privacy Policy (including how the cookie banner works) and our Terms & Conditions.