WEBSITE
ACCESSIBILITY
COMPLIANCE GUIDE
Complete guide to WCAG 2.1 Level AA compliance for nonprofit websites—legal requirements, technical implementation, and testing frameworks.
Accessibility isn't optional. It's a legal requirement under the ADA and the right thing to do for your community.
Includes: WCAG 2.1 AA checklist, color contrast requirements, keyboard navigation, screen reader compatibility, testing tools, and legal considerations.
WHY ACCESSIBILITY MATTERS
Accessible websites aren't just legally required—they're better for everyone.
Americans with Disabilities
61 million Americans have disabilities. If your website isn't accessible, you're excluding 26% of your potential supporters, donors, and volunteers.
Average ADA Lawsuit Cost
Nonprofit ADA website lawsuits are increasing 20% annually. Legal fees alone typically cost $15,000-$50,000, not including remediation costs.
Better User Experience for All
Accessibility improvements benefit everyone: Better mobile experience, clearer navigation, faster load times, and improved SEO rankings.
WCAG 2.1 AA REQUIREMENTS
WCAG 2.1 Level AA is organized into 4 principles: Perceivable, Operable, Understandable, and Robust.
1. Perceivable
Information must be presentable to users in ways they can perceive.
- →Alt text for all images and non-text content
- →Captions and transcripts for audio/video
- →Color contrast ratio 4.5:1 (normal text) or 3:1 (large text)
- →Text can be resized up to 200% without loss of functionality
- →Content adapts to different screen sizes
Most common violations: Missing alt text and insufficient color contrast
2. Operable
Interface components must be operable by all users.
- →All functionality available via keyboard
- →No keyboard traps (users can navigate away)
- →Sufficient time to read and use content
- →No content that flashes more than 3 times per second
- →Clear focus indicators on interactive elements
Test: Can you navigate your entire site using only Tab, Shift+Tab, Enter, and Arrow keys?
3. Understandable
Information and operation of interface must be understandable.
- →Language of page identified in HTML
- →Pages behave in predictable ways
- →Clear instructions for form inputs
- →Error messages that help users fix problems
- →Consistent navigation across pages
Write at an 8th-grade reading level and provide clear error messages
4. Robust
Content must work with current and future technologies.
- →Valid HTML markup (no major errors)
- →Proper use of HTML semantic elements
- →ARIA labels where needed
- →Compatible with assistive technologies
- →Status messages announced to screen readers
Run your HTML through W3C Validator to catch markup errors
COMPLIANCE CHECKLIST
Use this checklist to audit your website for WCAG 2.1 Level AA compliance:
Images & Media
- →All images have descriptive alt text
- →Decorative images have empty alt=''
- →Complex images have long descriptions
- →Videos have captions
- →Audio has transcripts
- →No auto-playing audio/video
Color & Contrast
- →Text contrast ratio ≥ 4.5:1 (normal)
- →Large text contrast ≥ 3:1 (18pt+)
- →Color not sole means of conveying information
- →Focus indicators visible and high contrast
- →Error messages don't rely on color alone
Keyboard Navigation
- →All interactive elements keyboard accessible
- →Logical tab order follows visual layout
- →No keyboard traps
- →Skip links to main content
- →Focus visible on all interactive elements
- →Keyboard shortcuts documented
Forms & Input
- →All form fields have labels
- →Labels properly associated with inputs
- →Required fields clearly indicated
- →Error messages clear and helpful
- →Instructions provided before input
- →Time limits can be extended
Headings & Structure
- →Proper heading hierarchy (H1, H2, H3...)
- →Only one H1 per page
- →Headings describe content sections
- →Lists use proper HTML elements
- →Tables have proper headers
- →Landmarks (nav, main, aside) used
Links & Navigation
- →Link text descriptive (no 'click here')
- →Links distinguishable from text
- →Consistent navigation across pages
- →Breadcrumbs for deep pages
- →Search functionality (if site >20 pages)
- →Sitemap available
TESTING TOOLS
Combine automated tools with manual testing for comprehensive accessibility audits:
Automated Testing Tools
These catch 30-40% of accessibility issues automatically.
- →WAVE (WebAIM) - Browser extension
- →axe DevTools - Chrome/Firefox extension
- →Lighthouse - Built into Chrome DevTools
- →Pa11y - Command-line tool
- →AccessibilityChecker.org - Free scanner
FREE - Run automated scans weekly during development
Manual Testing
Required to catch the 60-70% of issues automation misses.
- →Keyboard navigation test (Tab, Enter, Arrows)
- →Screen reader test (NVDA, VoiceOver, JAWS)
- →Color contrast checker (WebAIM tool)
- →Text resize test (zoom to 200%)
- →Mobile screen reader test
Budget 8-12 hours for manual testing of a 20-page site
Professional Audits
Comprehensive testing by certified accessibility experts.
- →Full WCAG 2.1 AA compliance audit
- →Detailed remediation recommendations
- →Priority-ranked issue list
- →Written report for legal purposes
- →Typical cost: $3,000-$15,000
Recommended annually or before major site launches
COMMON MISTAKES
These are the most frequent accessibility violations we see on nonprofit websites:
Missing or Poor Alt Text
65% of websites have missing or generic alt text like 'image1.jpg' or 'photo'.
- →Write descriptive alt text that conveys meaning
- →Keep it under 125 characters
- →Don't start with 'image of' or 'picture of'
- →For complex images, provide longer descriptions
- →Decorative images: use empty alt=''
EXAMPLE: Bad: 'woman' | Good: 'Female volunteer serving meals at community kitchen'
Insufficient Color Contrast
70% of websites fail contrast requirements, especially with gray text or overlays on images.
- →Use WebAIM Contrast Checker tool
- →Normal text needs 4.5:1 contrast ratio
- →Large text needs 3:1 contrast ratio
- →Test ALL text, including buttons
- →Don't rely on color alone for information
COMMON FAILURES: Light gray text (#999) on white fails. White text on light images fails.
Keyboard Navigation Failures
80% of websites have keyboard navigation issues—inaccessible dropdowns, modal traps, or invisible focus.
- →Test entire site with keyboard only
- →Ensure visible focus indicators
- →Dropdown menus must be keyboard operable
- →Modal dialogs must trap focus properly
- →Skip links for long navigation menus
TEST: Can you Tab through your site, open dropdowns, and submit forms without a mouse?
Unlabeled Form Fields
Forms are the #1 barrier for screen reader users. 60% have unlabeled or poorly labeled inputs.
- →Every input needs a visible label
- →Use <label> elements, not placeholders alone
- →Clearly mark required fields
- →Provide helpful error messages
- →Group related fields with <fieldset>
Placeholder text (like 'Enter email') is NOT accessible. Use proper labels.
LEGAL CONSIDERATIONS
Understanding the legal landscape of website accessibility:
ADA Title III
Applies to nonprofits that serve the public (places of public accommodation).
- →Courts have ruled websites are 'public accommodations'
- →No specific technical standard cited in ADA
- →WCAG 2.1 AA is the de facto standard
- →Applies to nonprofits, not just businesses
- →DOJ recommends WCAG 2.0 AA minimum
Even if not legally required, accessibility is part of your nonprofit mission
Section 508
Federal law requiring accessibility for organizations receiving federal funding.
- →Applies if you receive federal grants
- →Stricter than ADA in some areas
- →Requires WCAG 2.0 AA conformance minimum
- →Includes electronic documents (PDFs)
- →Non-compliance can affect grant eligibility
If you get federal funding, Section 508 compliance is mandatory
Recommended Legal Protection Steps
- ✓Create and publish an Accessibility Policy page
- ✓Provide clear contact info for accessibility concerns
- ✓Conduct regular accessibility audits (annually minimum)
- ✓Document your remediation efforts and timeline
- ✓Consider accessibility insurance (cyber insurance riders)
- ✓Train content creators on accessibility requirements
Consult with an attorney familiar with ADA digital accessibility for specific legal advice.
FREQUENTLY ASKED QUESTIONS
Answers to common questions about nonprofit website accessibility:
Yes. Title III of the ADA applies to nonprofits that serve the public, and recent court cases (including against nonprofits) have established that websites must be accessible. Additionally, if you receive federal funding, Section 508 compliance is required. Non-compliance can result in lawsuits, Department of Justice complaints, and loss of federal funding.
WCAG (Web Content Accessibility Guidelines) 2.1 Level AA is the internationally recognized standard for web accessibility. Level AA is the recommended conformance level for most organizations and is referenced in ADA compliance lawsuits. It includes requirements for color contrast, keyboard navigation, screen reader compatibility, and more.
For existing sites: $3,000-$15,000 for an audit and remediation of a 10-20 page nonprofit site. For new sites: Building accessibility from the start adds 10-15% to development costs but avoids expensive retrofitting later. Monthly ongoing maintenance typically costs $500-$1,500 for monitoring and updates.
No. Accessibility overlays (like AccessiBe, UserWay) are NOT sufficient for compliance and are widely criticized by the disability community. They don't fix underlying code issues and often create new barriers. The only way to achieve real accessibility is to fix the actual website code.
WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (18pt+ or 14pt+ bold). This ensures text is readable for people with low vision or color blindness. Use tools like WebAIM's Contrast Checker to verify your color choices.
Almost all. Informative images need descriptive alt text. Decorative images should have empty alt attributes (alt='') to avoid cluttering screen readers. Complex images (charts, graphs) need longer descriptions. Missing or generic alt text ('image1.jpg') is one of the most common accessibility violations.
Use a combination of automated tools (WAVE, axe DevTools, Lighthouse) to catch 30-40% of issues, plus manual testing with keyboard navigation and screen readers (NVDA on Windows, VoiceOver on Mac/iOS). Consider hiring professional accessibility auditors for comprehensive testing—automated tools miss 60-70% of real barriers.
ADA lawsuits typically demand website remediation, legal fees ($15,000-$50,000), and sometimes damages. However, most cases settle out of court if you commit to fixing issues within 6-12 months. The best defense is proactive compliance—having an accessibility policy and remediation plan shows good faith effort.
NEED HELP WITH
ACCESSIBILITY?
We build accessible websites from the ground up and audit existing sites for WCAG 2.1 AA compliance.
Let's make your website accessible to everyone.