Accessibility.

NervaHous aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. I'm not all the way there yet on every page. This statement is the honest version of what's in, what's rough, and how to flag something that's blocking you.

What's built in.

• Keyboard navigation. Every link, button, form field, and dropdown can be reached and operated with the keyboard alone. Tab moves forward, Shift + Tab moves back, Enter and Space activate. Esc closes open menus.
• Skip to main content. The first focusable element on each page is a "Skip to main content" link so screen-reader and keyboard users can bypass the navigation.
• Semantic landmarks. Pages use real <nav>, <main>, <article>, <section>, and <footer> elements, with aria-label on regions where the purpose isn't obvious from the surrounding heading.
• Visible focus rings. Interactive elements show a visible focus outline when keyboarded; we don't suppress browser defaults.
• Reduced motion. If your system is set to "reduce motion," scroll-driven animation, the landing-page video reveal, and decorative parallax are all turned off automatically. The page still works and the video does not rely on motion to expose the main copy.
• Color contrast. Body copy is tuned to clear WCAG AA contrast against the cream canvas. Decorative cards use translucent layers but the text on top is held above AA via tuned text colors and a subtle warm halo behind the text.
• Captions / muted autoplay. The landing-page video plays muted by default with no audio track, so there is no audio content to caption. If a future video has narration, captions will be provided.
• Resizable text. The site uses relative font sizes and respects browser zoom up to 200% without breaking layout.
• Forms with labels. Every form input has an associated <label>, even when the visual design hides it. Required fields are marked in plain text, not by color alone.

What's still rough.

I'd rather say it out loud than dress it up.

• Some translucent card surfaces can read low-contrast in specific scroll positions where the painting underneath happens to be dark. I'm working through these one by one.
• The dropdown menus in the main nav are accessible by keyboard, but the focus order inside an open dropdown could be tightened.
• Long-form prose pages (privacy, terms, accessibility, the approach) are screen-reader friendly, but the marketing pages have decorative corner brackets and frame motifs that are not always marked aria-hidden. Cleaning that up is a known follow-up.
• The landing-page video respects reduced-motion and now loads at its full editorial size. At full motion, the video plays once and then reveals the brand copy without requiring scroll.
• No formal third-party audit has been completed yet. Statements above are based on my own testing with keyboard, VoiceOver on macOS, and the WCAG checklist.

Tools I test with.

• macOS VoiceOver in Safari and Chrome.
• Keyboard-only navigation, no mouse, no trackpad.
• Browser zoom at 100%, 150%, and 200%.
• "Reduce motion" enabled at the OS level.
• Axe DevTools and Lighthouse for automated checks, then hand verification of anything they flag.

If something blocks you.

Email connect@nervahous.com with the subject line "Accessibility" and as much detail as you can share — which page, what you were trying to do, what got in the way, and what assistive technology you were using. I read every message myself. I'll aim to acknowledge within two business days and to fix the issue or explain why it's harder than that within ten business days. If a fix needs more time, I'll keep you in the loop.

Standards this targets.

WCAG 2.1 at level AA. The site is also intended to meet the relevant parts of Section 508 in the United States, and the EN 301 549 standard for European public-sector procurement. Marketplace products and downloadable PDFs are not in scope here — if you need a specific marketplace pack delivered in an accessible format (tagged PDF, plain text, large print), email me and I'll send one.

Changes to this statement.

When the page is updated, the date at the top changes. Significant improvements (or significant new gaps) get noted in a short revision log below.

Revision log.

• May 27, 2026. Original publication.