Accessibility Testing
CodeFrog includes comprehensive accessibility testing tools designed to help you meet WCAG (Web Content Accessibility Guidelines) standards at all three conformance levels: A, AA, and AAA. These tools help identify and fix accessibility issues before your app or website goes live.
Overview
Accessibility testing ensures your application is usable by people with disabilities, including:
- Visual impairments (blindness, low vision, color blindness)
- Motor impairments (limited dexterity, keyboard-only navigation)
- Cognitive impairments (attention disorders, learning disabilities)
- Hearing impairments (deafness, hard of hearing)
Meeting WCAG standards is not just good practice—it’s often required by law in many jurisdictions. Level AA is typically the target for legal compliance, while Level A is the minimum and Level AAA represents enhanced accessibility.
Windows Screen Reader Context
When testing accessibility on Windows, it’s important to understand how screen readers work:
Windows Screen Readers
Windows Narrator (Built-in):
- Pre-installed on Windows 10/11
- Activate with
Win + Ctrl + Enter - Basic screen reading functionality
- Good for initial testing
NVDA (NonVisual Desktop Access):
- Free, open-source screen reader
- Download from: https://www.nvaccess.org/
- More advanced than Narrator
- Recommended for comprehensive testing
JAWS (Job Access With Speech):
- Commercial screen reader
- Industry standard for professional testing
- Most comprehensive feature set
- Available from: https://www.freedomscientific.com/
Testing with Screen Readers
When testing your web applications:
- Install a Screen Reader
- Start with NVDA (free and comprehensive)
- Or use Windows Narrator for basic testing
- Test Navigation
- Use keyboard-only navigation (Tab, Arrow keys, Enter)
- Verify all interactive elements are reachable
- Check that focus indicators are visible
- Test Content Reading
- Verify headings are announced correctly
- Check that form labels are read with inputs
- Ensure images have descriptive alt text
- Verify link text is meaningful out of context
- Test Forms
- Ensure all form fields have labels
- Verify error messages are announced
- Check that required fields are indicated
How to Run Accessibility Tests
- Open your project in CodeFrog
- Navigate to the Analyze tab
- Select Accessibility from the analysis options
- Choose the files or directories to scan
- Click Run Analysis
The accessibility scanner will check:
- Color contrast ratios (text vs. background)
- Keyboard navigation support
- ARIA attributes and roles
- Focus management
- Screen reader compatibility
- Alt text for images
- Semantic HTML structure
Interpreting Results
Color Contrast
The scanner reports contrast ratios for all text elements:
- WCAG AA Standard: 4.5:1 for normal text, 3:1 for large text
- WCAG AAA Standard: 7:1 for normal text, 4.5:1 for large text
Results show:
- Elements that fail contrast requirements
- Current contrast ratio vs. required ratio
- Suggested color adjustments
Keyboard Navigation
The scanner verifies:
- All interactive elements are keyboard accessible
- Tab order is logical
- Focus indicators are visible
- No keyboard traps (can’t escape with keyboard)
ARIA and Semantic HTML
Checks include:
- Proper use of ARIA labels and roles
- Semantic HTML elements (header, nav, main, etc.)
- Landmark regions for screen reader navigation
- Live regions for dynamic content
Windows-Specific Testing Notes
Browser Testing
When testing accessibility in browsers on Windows:
- Chrome: Good screen reader support with NVDA/JAWS
- Edge: Excellent Narrator integration
- Firefox: Good NVDA support
- Test in multiple browsers for comprehensive coverage
Keyboard Testing
Windows keyboard navigation:
Tab: Move forward through interactive elementsShift + Tab: Move backwardEnterorSpace: Activate buttons/linksArrow keys: Navigate within components (menus, lists)Esc: Close dialogs/modals
High Contrast Mode
Test in Windows High Contrast Mode:
- Settings → Ease of Access → High contrast
- Enable high contrast theme
- Verify your application remains usable
- Check that all content is visible
Zoom Testing
Test at different zoom levels:
Ctrl + Plus: Zoom inCtrl + Minus: Zoom outCtrl + 0: Reset zoom- Verify layout doesn’t break and content remains readable
Best Practices
During Development
- Use semantic HTML: Prefer
<button>over<div>for buttons - Provide alt text: All images need descriptive alt attributes
- Label forms: Every input needs an associated label
- Test early: Test accessibility as you build, not just at the end
- Use ARIA wisely: Don’t overuse ARIA - prefer semantic HTML
Testing Workflow
- Automated Testing: Run CodeFrog’s accessibility scanner first
- Manual Testing: Test with actual screen readers
- Keyboard Testing: Navigate entire application with keyboard only
- Color Testing: Check contrast and color-blind accessibility
- User Testing: Get feedback from users with disabilities
Common Issues and Solutions
Low Contrast Text
Problem: Text doesn’t meet contrast requirements
Solution:
- Increase contrast between text and background
- Use darker text on light backgrounds (or vice versa)
- Test with online contrast checkers
- Consider using bold for small text
Missing Alt Text
Problem: Images lack descriptive alt attributes
Solution:
- Add meaningful alt text to all images
- Use empty alt (
alt="") for decorative images - Describe the image’s purpose, not just what it looks like
Keyboard Traps
Problem: Users can’t escape a component with keyboard
Solution:
- Ensure
Esckey closes modals/dialogs - Provide clear “Close” buttons
- Test tab order within components
- Allow focus to move outside component
Missing Focus Indicators
Problem: Users can’t see which element has focus
Solution:
- Add visible focus styles (outline, border, etc.)
- Ensure focus indicators meet contrast requirements
- Don’t remove default browser focus styles without replacement
Resources
Next Steps
- WCAG Levels Explained - Understand A, AA, and AAA levels
- Windows Setup Guide - Configure CodeFrog on Windows
- Windows Troubleshooting - Solve Windows-specific issues