The FAForever Patchnotes website is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards.
This website aims to conform to WCAG 2.1 Level AAA standards. Our accessibility features have been implemented based on:
- WCAG 2.1 (Web Content Accessibility Guidelines)
- Section 508 compliance
- ARIA 1.2 (Accessible Rich Internet Applications)
- Web accessibility best practices
We meet AAA criteria for most guidelines and are actively working toward full compliance.
- Skip to main content link appears on Tab key press
- Direct navigation to primary content area
- High contrast focus indicator
Press ? or Alt+H to view all available shortcuts:
Ctrl/Cmd+K- Focus search inputAlt+T- Toggle theme (light/dark)Alt+A- Enable auto-theme syncEsc- Close modals and dialogsTab- Navigate forward through interactive elementsShift+Tab- Navigate backward through interactive elementsEnter/Space- Activate buttons and links
- 3px solid outline with 3:1 contrast ratio (WCAG 2.1 AAA)
- Enhanced focus boxes with shadow effects
- Only visible for keyboard navigation (
:focus-visible) - High contrast mode support
All interactive elements have descriptive ARIA labels:
<button aria-label="View latest patch notes">Latest</button>
<input aria-label="Search through patch notes">
<nav aria-label="Footer navigation">Dynamic content updates are announced:
<div role="status" aria-live="polite">
Showing 5 of 30 patches
</div>- Proper heading hierarchy (H1→H2→H3)
- Landmark regions:
<main>,<nav>,<header>,<footer> - Role attributes:
role="banner",role="contentinfo",role="list"
Hidden Decorative Content
Icons are hidden from screen readers:
<i class="fas fa-search" aria-hidden="true"></i>All color combinations meet WCAG AAA standards (7:1 for normal text, 4.5:1 for large text):
- Text on background: 9.2:1 contrast ratio ✓
- Links: Underlined + color differentiation ✓
- Buttons: High contrast borders and fills ✓
- Focus indicators: 3:1 contrast ratio ✓
- System preference detection
- Manual toggle with
Alt+T - Auto-sync option with
Alt+A - Smooth transitions with
prefers-reduced-motionrespect
- Relative units (rem, em) throughout
- Zoomable to 200% without horizontal scrolling
- Minimum font size: 14px (0.875rem)
- Maximum line length: 80 characters
WCAG 2.1 AAA compliance (2.5.5):
- Desktop: Minimum 44×44px touch targets
- Mobile: Minimum 48×48px touch targets
- Adequate spacing between interactive elements
Automatically detects and respects prefers-reduced-motion:
@media (prefers-reduced-motion: reduce) {
* {
animation-duration: 0.01ms !important;
transition-duration: 0.01ms !important;
}
}- No flashing content (max 3 flashes per second)
- No auto-playing animations
- User-controlled theme transitions
<html lang="en">Ready for right-to-left languages:
[dir="rtl"] { direction: rtl; }Run Lighthouse in Chrome DevTools:
- Open Chrome DevTools (
F12) - Go to Lighthouse tab
- Select Accessibility category
- Run audit
Target Score: 95+ (current: varies by page)
Install axe DevTools browser extension:
1. Install axe DevTools extension
2. Open DevTools → axe tab
3. Click "Scan ALL of my page"
4. Review and fix violationsUse WAVE:
- Visit https://wave.webaim.org/
- Enter site URL
- Review errors and alerts
- Start at top of page
- Press
Tabkey repeatedly - Verify:
- Skip link appears first
- All interactive elements are reachable
- Focus order is logical (top → bottom, left → right)
- No keyboard traps
- Visible focus indicators on all elements
NVDA (Windows - Free)
1. Download: https://www.nvaccess.org/download/
2. Install and launch NVDA
3. Navigate site with keyboard
4. Verify all content is announced properlyJAWS (Windows - Commercial)
1. Install JAWS
2. Navigate site with keyboard
3. Test forms, buttons, and dynamic contentVoiceOver (macOS - Built-in)
1. Press Cmd+F5 to enable VoiceOver
2. Use VoiceOver commands (VO+Arrow keys)
3. Navigate through landmarks and headingsTalkBack (Android - Built-in)
1. Settings → Accessibility → TalkBack
2. Enable TalkBack
3. Navigate with swipe gestures- Test foreground and background color combinations
- Ensure 4.5:1 for normal text (AA)
- Aim for 7:1 for enhanced contrast (AAA)
- Browser zoom to 200% (
Ctrl/Cmd + +) - Verify no horizontal scrolling
- Check all content remains readable
- Test up to 400% for AAA compliance
- Test on real devices (iOS, Android)
- Enable accessibility features:
- iOS: VoiceOver, Zoom, Larger Text
- Android: TalkBack, Magnification, Font Size
- Test touch targets (should be 48×48px minimum)
- Verify gestures work with assistive tech
- Some third-party embedded content (Font Awesome CDN) may not be fully accessible
- Historical patch HTML files may have legacy accessibility issues
- External links open in new tabs (deliberate UX decision, but noted)
- Full WCAG 2.1 AAA audit completion
- Screen reader testing with all major tools
- User testing with people with disabilities
- Add custom focus indicators per component type
- Implement focus trap for modals
- Add keyboard shortcut legend to footer
- Improve search result announcements
- Multi-language support (i18n)
- Custom font size selector
- High contrast theme option
- Voice navigation support
Use this checklist before each release:
- Lighthouse accessibility score 95+
- axe DevTools: 0 violations
- WAVE: 0 errors
- HTML validation passes
- Skip link works
- All interactive elements reachable
- No keyboard traps
- Logical tab order
- Focus indicators visible
- Keyboard shortcuts functional
- NVDA: All content announced
- VoiceOver: Landmarks navigable
- Content order makes sense
- Form labels properly associated
- Status updates announced
- Color contrast meets AAA (7:1)
- Zoom to 200% works
- No horizontal scrolling
- Dark mode accessible
- Text resizable
- Touch targets 48×48px minimum
- VoiceOver/TalkBack compatible
- Pinch zoom works
- Orientation changes handled
- Forms have labels and error messages
- Images have alt text
- Videos have captions (if applicable)
- Links have descriptive text
- Reduced motion respected
# Install Lighthouse CLI
npm install -g lighthouse
# Run audit
lighthouse https://your-site-url --view --only-categories=accessibility
# Generate report
lighthouse https://your-site-url --output html --output-path ./accessibility-report.html# Install Pa11y
npm install -g pa11y
# Test single page
pa11y https://your-site-url
# Test with specific WCAG level
pa11y --standard WCAG2AAA https://your-site-url
# Generate report
pa11y --reporter html https://your-site-url > accessibility-report.html# Install axe-cli
npm install -g @axe-core/cli
# Run test
axe https://your-site-url
# Save results
axe https://your-site-url --save results.json| Tool | Platform | Status | Notes |
|---|---|---|---|
| NVDA | Windows | ✅ Tested | Latest version |
| JAWS | Windows | Not regularly tested | |
| VoiceOver | macOS/iOS | ✅ Tested | Built-in |
| TalkBack | Android | Periodic testing | |
| Narrator | Windows | Basic support |
- Chrome 90+ ✅
- Firefox 88+ ✅
- Safari 14+ ✅
- Edge 90+ ✅
- Opera 76+ ✅
We welcome feedback on the accessibility of the FAForever Patchnotes site.
- GitHub Issue: Open an issue with label
accessibility - Email: accessibility@faforever.com
- Discord: Message a moderator on FAForever Discord
- Page URL where you experienced the issue
- Assistive technology you're using (name and version)
- Browser and version
- Operating system
- Description of the problem
- Expected behavior
- Steps to reproduce
- Critical issues: 24-48 hours
- Major issues: 3-5 business days
- Minor issues: 1-2 weeks
Contributors focused on accessibility:
- Lead: Community contributor
- Testing: Community volunteers
- Development: Open source contributors
Want to help? See CONTRIBUTING.md for guidelines.
This accessibility statement was last updated on February 5, 2026.
We are committed to maintaining and improving the accessibility of this website. If you encounter any barriers, please let us know.
This website aims to comply with:
- Americans with Disabilities Act (ADA)
- Section 508 of the Rehabilitation Act
- European Accessibility Act (EAA)
- EN 301 549 European standard
Questions or feedback? Contact us through the methods listed above. We appreciate your help in making our site accessible to everyone.