sf-agent-framework/sf-core/checklists/accessibility-checklist.md

AI Agent Orchestration Framework for Salesforce Development - Two-phase architecture with 70% context reduction

# Salesforce Accessibility Checklist

## Overview

This checklist ensures Salesforce implementations meet WCAG 2.1 AA standards and
provide accessible experiences for all users.

## Pre-Development Accessibility Planning

### Requirements Gathering

- [ ] Identify users with accessibility needs
- [ ] Document specific accessibility requirements
- [ ] Review WCAG 2.1 AA guidelines
- [ ] Plan for assistive technology testing
- [ ] Include accessibility in user stories
- [ ] Define accessibility acceptance criteria

### Design Phase

- [ ] Ensure sufficient color contrast (4.5:1 for normal text, 3:1 for large
      text)
- [ ] Design for keyboard-only navigation
- [ ] Avoid color as the only means of conveying information
- [ ] Plan for screen reader compatibility
- [ ] Design clear focus indicators
- [ ] Ensure touch targets are at least 44x44 pixels

## Lightning Component Accessibility

### Component Structure

- [ ] Use semantic HTML elements
- [ ] Implement proper heading hierarchy (h1, h2, h3, etc.)
- [ ] Add ARIA labels where needed
- [ ] Include skip navigation links
- [ ] Ensure logical tab order
- [ ] Provide text alternatives for images

### Form Accessibility

- [ ] Associate labels with form controls
- [ ] Group related form fields with fieldset and legend
- [ ] Provide clear error messages
- [ ] Mark required fields clearly
- [ ] Ensure error messages are announced to screen readers
- [ ] Implement inline validation feedback

### Interactive Elements

- [ ] All interactive elements are keyboard accessible
- [ ] Provide visible focus indicators
- [ ] Implement proper ARIA roles
- [ ] Ensure custom components follow ARIA patterns
- [ ] Add keyboard shortcuts documentation
- [ ] Test with keyboard navigation only

## Visualforce Page Accessibility

### Page Structure

- [ ] Include proper DOCTYPE declaration
- [ ] Set appropriate page language
- [ ] Use semantic HTML markup
- [ ] Implement skip navigation links
- [ ] Ensure proper heading structure
- [ ] Add page landmarks (header, nav, main, footer)

### Content Accessibility

- [ ] Provide alt text for all informative images
- [ ] Use null alt text for decorative images
- [ ] Ensure tables have proper headers
- [ ] Add captions for complex tables
- [ ] Provide transcripts for audio content
- [ ] Include captions for video content

## Experience Cloud Accessibility

### Template Accessibility

- [ ] Choose accessible templates
- [ ] Customize with accessibility in mind
- [ ] Ensure navigation is keyboard accessible
- [ ] Test with screen readers
- [ ] Verify color contrast throughout
- [ ] Check responsive design accessibility

### Community Features

- [ ] Forums are screen reader compatible
- [ ] Search functionality is accessible
- [ ] File uploads include accessible alternatives
- [ ] Chat features work with assistive technology
- [ ] Knowledge articles follow accessibility guidelines
- [ ] User profiles are accessible

## Mobile Accessibility

### Salesforce Mobile App

- [ ] Test with device screen readers (VoiceOver/TalkBack)
- [ ] Ensure touch targets meet minimum size
- [ ] Support device accessibility settings
- [ ] Test with voice control
- [ ] Verify gesture alternatives exist
- [ ] Check landscape/portrait accessibility

### Mobile-Responsive Design

- [ ] Test at various zoom levels
- [ ] Ensure horizontal scrolling isn't required
- [ ] Verify touch gestures have alternatives
- [ ] Test with mobile assistive technologies
- [ ] Check form usability on mobile
- [ ] Validate mobile navigation accessibility

## Reports and Dashboards Accessibility

### Report Design

- [ ] Use accessible color schemes
- [ ] Don't rely solely on color to convey meaning
- [ ] Add data tables as alternatives to charts
- [ ] Include descriptive titles and summaries
- [ ] Ensure filters are keyboard accessible
- [ ] Test export formats for accessibility

### Dashboard Components

- [ ] Provide text descriptions for charts
- [ ] Ensure interactive elements are accessible
- [ ] Use patterns in addition to colors
- [ ] Add keyboard navigation support
- [ ] Include data table alternatives
- [ ] Test refresh functionality accessibility

## Testing and Validation

### Automated Testing

- [ ] Run Salesforce Accessibility Scanner
- [ ] Use axe DevTools or similar
- [ ] Check for WCAG violations
- [ ] Validate HTML markup
- [ ] Test color contrast ratios
- [ ] Verify ARIA implementation

### Manual Testing

- [ ] Navigate using only keyboard
- [ ] Test with screen readers (NVDA, JAWS, VoiceOver)
- [ ] Verify with browser zoom at 200%
- [ ] Test with Windows High Contrast mode
- [ ] Check with voice recognition software
- [ ] Validate with mobile screen readers

### User Testing

- [ ] Include users with disabilities in testing
- [ ] Document accessibility feedback
- [ ] Test common user journeys
- [ ] Verify assistive technology compatibility
- [ ] Gather feedback on improvements needed
- [ ] Iterate based on user feedback

## Documentation and Training

### Accessibility Documentation

- [ ] Document accessibility features
- [ ] Create keyboard shortcut guide
- [ ] Provide screen reader tips
- [ ] Include accessibility in user guides
- [ ] Document known limitations
- [ ] Maintain accessibility statement

### Training Materials

- [ ] Ensure training materials are accessible
- [ ] Provide alternative formats (audio, large print)
- [ ] Include accessibility in user training
- [ ] Train support staff on accessibility
- [ ] Create accessible video tutorials
- [ ] Offer multiple training delivery methods

## Ongoing Maintenance

### Regular Reviews

- [ ] Schedule quarterly accessibility audits
- [ ] Test new features for accessibility
- [ ] Monitor accessibility feedback
- [ ] Update based on WCAG changes
- [ ] Review third-party component accessibility
- [ ] Maintain accessibility backlog

### Continuous Improvement

- [ ] Track accessibility metrics
- [ ] Address accessibility bugs promptly
- [ ] Include accessibility in release notes
- [ ] Update accessibility documentation
- [ ] Gather ongoing user feedback
- [ ] Stay current with accessibility standards

## Compliance and Legal

### Standards Compliance

- [ ] Meet WCAG 2.1 AA standards
- [ ] Comply with Section 508 (if applicable)
- [ ] Follow ADA requirements
- [ ] Meet regional accessibility laws
- [ ] Document compliance efforts
- [ ] Maintain audit trail

### Accessibility Statement

- [ ] Publish accessibility statement
- [ ] Include contact information
- [ ] List known issues and workarounds
- [ ] Provide feedback mechanism
- [ ] Update statement regularly
- [ ] Make statement easily findable

## Resources and Tools

### Testing Tools

- [ ] Salesforce Accessibility Scanner configured
- [ ] Screen readers installed and configured
- [ ] Color contrast analyzers available
- [ ] Keyboard navigation tested
- [ ] Browser accessibility tools enabled
- [ ] Mobile accessibility tools ready

### Reference Materials

- [ ] WCAG 2.1 guidelines bookmarked
- [ ] Salesforce accessibility documentation reviewed
- [ ] ARIA authoring practices referenced
- [ ] Team trained on accessibility
- [ ] Accessibility champions identified
- [ ] Support resources documented