the beginning of the idiots

This commit is contained in:
2025-10-24 14:51:13 -05:00
parent 0b377030c6
commit cb06217ef7
123 changed files with 10279 additions and 0 deletions

63
qwen/php/ACCESSIBILITY.md Normal file
View File

@@ -0,0 +1,63 @@
# Accessibility Guidelines for MerchantsOfHope.org
## Overview
This document outlines the accessibility standards and best practices implemented in the MerchantsOfHope.org recruiting platform to ensure compliance with Section 508 and WCAG 2.1 AA standards.
## Standards Compliance
- **WCAG 2.1 AA**: All interfaces meet Web Content Accessibility Guidelines 2.1 Level AA standards
- **Section 508**: Compliance with Section 508 accessibility standards for federal procurement
- **ADA Compliance**: Adherence to Americans with Disabilities Act requirements
## Key Accessibility Features
### Semantic HTML
- Proper use of HTML5 semantic elements (`header`, `nav`, `main`, `footer`, `article`, `section`)
- Correct heading hierarchy (H1, H2, H3, etc.) for content structure
- Use of ARIA labels and roles where necessary
### Keyboard Navigation
- All interactive elements accessible via keyboard
- Clear focus indicators for all interactive elements
- Logical tab order matching visual flow
- Skip links to bypass repetitive content
### Color and Contrast
- Minimum 4.5:1 contrast ratio for normal text, 3:1 for large text
- Color not used as the sole means of conveying information
- Adequate color contrast for all UI elements
### Screen Reader Support
- Proper ARIA labels and descriptions
- Alternative text for all images
- Landmark roles for easy navigation
### Forms and Inputs
- Proper labels for all form controls
- Clear error identification and suggestions
- Accessible validation messages
### Media
- Captions for all video content
- Transcripts for audio content
- Text alternatives for images
## API Accessibility Features
- All JSON responses include proper semantic structure
- Error messages are clear and descriptive
- Alternative text available for image-related data
## Testing
- Regular automated accessibility testing with tools like axe-core
- Manual keyboard navigation testing
- Screen reader testing with tools like NVDA and JAWS
- Color contrast validation
## Maintenance
- Accessibility review part of every feature development cycle
- Regular accessibility audits
- Staff training on accessibility best practices
## Additional Resources
- [WebAIM WCAG 2.1 Checklist](https://webaim.org/standards/wcag/checklist)
- [Section 508 Standards](https://www.section508.gov/)
- [W3C Accessibility Tutorials](https://www.w3.org/WAI/tutorials/)