AI Accessibility Checks (What It Finds and What It Doesn't)

Rihario detects common accessibility issues automatically, but it's not a replacement for dedicated accessibility testing tools. The AI finds obvious problems like missing labels and poor contrast, but cannot evaluate screen reader compatibility or keyboard navigation comprehensively. Use it for quick spot checks, not compliance audits.

What AI Can Detect

Missing Labels

• Input fields without labels - Form fields missing associated <label> elements
• Missing ARIA labels - Interactive elements without aria-label or aria-labelledby
• Images without alt text - <img> elements missing alt attributes
• Icons without labels - Icon buttons without text or aria-label

Color Contrast

• Low contrast text - Text that doesn't meet WCAG contrast ratios
• Color-only information - Information conveyed only through color
• Poor button contrast - Buttons with insufficient contrast

Semantic HTML

• Missing headings - Pages without proper heading structure
• Improper heading hierarchy - Skipped heading levels (h1 → h3)
• Non-semantic elements - Buttons implemented as <div> instead of <button>
• Missing landmarks - Missing ARIA landmarks or semantic regions

Form Accessibility

• Unlabeled form fields - Inputs without labels or placeholders
• Error messages not associated - Error messages not linked to fields via aria-describedby
• Required fields not indicated - Required fields without aria-required or visual indicators

Keyboard Navigation Basics

• Missing focus indicators - Elements that can be focused but have no visible focus state
• Non-focusable interactive elements - Clickable elements that aren't keyboard accessible
• Focus traps - Situations where focus gets stuck (basic detection)

What AI Cannot Detect

Screen Reader Compatibility

• Screen reader announcements - Cannot verify what screen readers actually announce
• ARIA live regions - Cannot verify dynamic content announcements
• Screen reader navigation - Cannot test how users navigate with screen readers
• Complex ARIA patterns - Cannot verify complex ARIA implementations work correctly

Keyboard Navigation

• Tab order - Cannot verify logical tab order
• Keyboard shortcuts - Cannot test custom keyboard shortcuts
• Escape key handling - Cannot verify ESC closes modals/menus
• Arrow key navigation - Cannot test arrow key controls (dropdowns, menus)

Complex Accessibility

• Dynamic content updates - Cannot verify ARIA live regions work correctly
• Drag and drop - Cannot test keyboard alternatives for drag-and-drop
• Complex widgets - Cannot verify complex ARIA widgets (accordions, tabs, etc.)
• Focus management - Cannot verify focus is managed correctly in modals

Contextual Issues

• Alternative text quality - Can detect missing alt text, but not if it's descriptive
• Link purpose - Can detect links, but not if "click here" is clear without context
• Reading order - Cannot verify logical reading order for screen readers
• Skip links - May not verify skip links work correctly

Understanding Accessibility Results

When accessibility issues are found, they're categorized as:

Limitations

Not Comprehensive

Rihario finds obvious accessibility issues, not all issues. It's a spot check, not a full audit.

Cannot Verify Experience

The AI can detect missing labels, but cannot verify if the actual screen reader experience is good. Users with disabilities should test your app.

Not a Compliance Tool

Rihario is not designed for WCAG compliance audits. Use dedicated accessibility testing tools (axe, WAVE, Lighthouse) for compliance.

False Positives

Some reported issues might be false positives. Always verify findings manually.

Best Practices

• Use for quick checks - Catch obvious issues before user testing
• Verify manually - Always manually verify reported issues
• Use dedicated tools for compliance - Use axe or WAVE for WCAG audits
• Test with real users - Have users with disabilities test your app
• Fix obvious issues first - Address missing labels and contrast before complex issues

What to Use Instead (For Compliance)

For comprehensive accessibility testing, use:

• axe DevTools - Browser extension for accessibility testing
• WAVE - Web accessibility evaluation tool
• Lighthouse - Built into Chrome DevTools
• Screen readers - Test with NVDA, JAWS, or VoiceOver
• Keyboard testing - Navigate entire app with keyboard only

Rihario complements these tools by catching issues during regular exploration, but doesn't replace them.

Example: What Gets Found

Next Steps

• Learn about testing forms
• Understand test results
• See limitations of AI testing