Our Commitment
Accessibility Statement
BuildWithAccess is an accessibility consulting firm. Our own website must demonstrate the standards we help our clients achieve. This page documents our full conformance commitment, testing methodology, and how to report barriers you encounter.
Last reviewed: June 29, 2026 — reviewed quarterly
1. Conformance Status
This website conforms to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. WCAG 2.1 AA is defined and published by the World Wide Web Consortium (W3C) and is the standard referenced in the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, the European Accessibility Act (EAA), and most national accessibility laws worldwide.
Conformance is assessed and maintained through a combination of automated scanning, manual code review, and hands-on testing with assistive technologies. This is a living document — it is updated each time we publish a material change to any page template or interactive component.
2. Scope of This Statement
This statement covers the primary web application served at buildwithaccess.com, including:
- All static marketing and informational pages
- All service detail pages
- The blog index and all individual blog post pages
- The contact form and free checklist lead magnet
- All interactive components (navigation, accordion FAQ, forms)
Third-party services embedded on this site (such as Google Forms) are subject to their own accessibility policies. We have chosen and configured these services with accessibility as a criterion, but we cannot guarantee third-party conformance.
3. Testing Methodology
We use a layered testing approach that mirrors the methodology we apply to client audits. No single tool or method catches all WCAG failures — the combination below is required for a thorough evaluation.
Automated Scanning
axe-core and Lighthouse are integrated into our CI/CD pipeline. Every build is scanned for detectable WCAG violations. Automated tools catch approximately 30–40% of WCAG issues.
Manual Code Review
Semantic HTML structure, ARIA attribute correctness, focus management, reading order, and color contrast are reviewed by a certified IAAP accessibility professional on every template change.
Screen Reader Testing
Interactive flows are tested with JAWS, NVDA, and VoiceOver across the browsers and operating systems listed below. Testing includes navigation, form completion, and dynamic content.
Keyboard-Only Navigation
All interactions — menus, accordions, forms, links — are verified to be fully operable using only a keyboard, with a visible focus indicator present at all times.
Mobile & Touch Testing
Pages are tested on iOS with VoiceOver and Android with TalkBack. Touch target sizes, gesture alternatives, and zoom behavior are verified on physical devices.
Color Contrast Audit
All text, interactive component boundaries, and informational graphics are measured against WCAG 1.4.3 (text) and 1.4.11 (non-text) contrast thresholds using the APCA and WCAG 2.x algorithms.
Assistive Technologies Used in Testing
| Assistive Technology | Browser | Operating System |
|---|---|---|
| JAWS 2024 | Chrome 124, Edge 124 | Windows 11 |
| NVDA 2024.1 | Firefox 125, Chrome 124 | Windows 11 |
| VoiceOver | Safari 17 | macOS Sonoma |
| VoiceOver | Safari on iOS 17 | iPhone 15 |
| TalkBack | Chrome on Android 14 | Pixel 8 |
| Dragon NaturallySpeaking 16 | Chrome 124 | Windows 11 |
4. WCAG 2.1 AA Criteria Coverage
The following is a summary of how this website addresses the four principles of WCAG 2.1. All Level A and Level AA success criteria listed below are implemented and verified.
Perceivable
- All non-text content has text alternatives (1.1.1)
- Video and audio have captions and audio descriptions (1.2.x)
- Content can be presented without loss of information when structure is changed (1.3.x)
- Color is not the sole means of conveying information (1.4.1)
- Text contrast ratio meets 4.5:1 minimum (1.4.3)
- Large text contrast ratio meets 3:1 minimum (1.4.3)
- Text can be resized to 200% without loss of content (1.4.4)
- Images of text are avoided except where essential (1.4.5)
- Content reflows at 400% zoom without horizontal scrolling (1.4.10)
- Non-text contrast for UI components meets 3:1 (1.4.11)
- Text spacing can be adjusted without loss of content (1.4.12)
- Content on hover or focus is persistent and dismissible (1.4.13)
Operable
- All functionality is available via keyboard (2.1.1)
- No keyboard traps exist (2.1.2)
- No content flashes more than 3 times per second (2.3.1)
- Skip navigation link is provided (2.4.1)
- Pages have descriptive titles (2.4.2)
- Focus order follows logical reading order (2.4.3)
- Link purpose is clear from text alone or context (2.4.4)
- Multiple ways to find pages are provided (2.4.5)
- Headings and labels are descriptive (2.4.6)
- Keyboard focus indicator is visible (2.4.7)
- Pointer gestures have keyboard or single-pointer alternatives (2.5.1)
- Motion-based features have alternative interaction (2.5.4)
Understandable
- Language of the page is set in HTML (3.1.1)
- Language changes within content are marked up (3.1.2)
- Navigation is consistent across pages (3.2.3)
- Identification of components is consistent (3.2.4)
- Error identification is specific and described in text (3.3.1)
- Form labels and instructions are provided (3.3.2)
- Error suggestions are provided where possible (3.3.3)
- Important submissions can be checked, confirmed, or reversed (3.3.4)
Robust
- All UI components have accessible name, role, and value (4.1.2)
- Status messages are programmatically determinable (4.1.3)
5. Known Limitations
Despite our best efforts, some limitations may exist. We are transparent about these and committed to resolving them. If you encounter something not listed here, please report it using the feedback process below.
6. Third-Party Content
This website integrates a limited number of third-party services:
- Google FormsUsed for lead capture. Form fields on our site submit data to Google Forms in the background — users never leave our page. The Google Forms interface itself is subject to Google's own accessibility policy.
- Google FontsWe use the Inter typeface loaded via Next.js font optimization, which self-hosts the font files. No external Google Fonts request is made at runtime.
- No tracking scriptsThis site does not use third-party analytics, advertising, or marketing scripts that could interfere with assistive technologies or create performance barriers.
7. Accessible Features of This Site
The following features have been deliberately implemented to support users of assistive technologies and alternative input devices:
- Skip navigation link allows keyboard users to bypass the main navigation and jump directly to page content
- All interactive elements have a visible focus indicator with at least 3px outline and sufficient contrast
- Landmark regions (header, nav, main, footer) are marked up with semantic HTML for screen reader navigation
- All images are either decorative (aria-hidden) or have descriptive alternative text
- Forms use explicit label associations, inline error messages linked via aria-describedby, and aria-invalid states
- Dynamic content (form success states, FAQ accordion) uses aria-live regions and role=alert where appropriate
- The accordion FAQ uses aria-expanded, aria-controls, and the disclosure pattern — no ARIA is used beyond what is supported
- Color is never the sole means of conveying information (icons and text labels accompany all color-coded states)
- The site is fully functional with JavaScript disabled for all static content
- All page titles are unique and descriptive, matching the page's primary heading
- Structured data (JSON-LD) is provided for SEO but does not affect the accessible experience
- Responsive design ensures content reflows at 400% zoom and at viewport widths as narrow as 320px without horizontal scrolling
8. Legal and Regulatory Context
This accessibility statement is published in accordance with:
- Americans with Disabilities Act (ADA)Title III requires places of public accommodation, including websites, to be accessible to people with disabilities. WCAG 2.1 AA is the accepted technical standard.
- Section 508 of the Rehabilitation ActRequires federal agencies and federally funded organizations to make their ICT accessible. This site meets the equivalent technical requirements.
- European Accessibility Act (EAA)Effective June 2025, the EAA requires digital products and services in EU member states to meet EN 301 549, which references WCAG 2.1 AA.
- W3C WCAG 2.1Published by the World Wide Web Consortium (W3C), WCAG 2.1 is the internationally recognized technical specification for web accessibility. The full specification is available at www.w3.org/TR/WCAG21/.
9. Feedback and Reporting Barriers
We want to hear about accessibility barriers you encounter on this site. Your feedback directly drives our improvement process.
How to report an accessibility issue:
- Email us at accessbuildwith@gmail.com with the subject line “Accessibility Issue”
- Describe the barrier: Which page? What were you trying to do? Which assistive technology were you using?
- We will respond within 2 business days with an acknowledgement and a timeline for resolution
We treat accessibility reports with the same urgency as critical security vulnerabilities. Barriers that prevent task completion are escalated and fixed in the next deployment cycle.