What the site currently does
- Uses semantic headings, landmarks, labels, and a skip-to-content link.
- Keeps primary navigation usable without JavaScript and provides visible keyboard focus treatment.
- Supports keyboard navigation for menus, links, forms, search, and article utilities.
- Uses responsive layouts that have been checked for horizontal overflow at representative desktop and mobile widths.
- Respects reduced-motion preferences for nonessential animation.
- Keeps long-form text at a constrained reading measure and provides a print/Save-as-PDF stylesheet.
- Uses live HTML for hero headlines and controls instead of embedding essential text only inside images.
Known limits
Automated and local checks cannot prove that every assistive-technology combination behaves perfectly. Browser, operating-system, zoom, font, screen-reader, and hosting differences can expose problems that are not visible in the development environment.
Report an accessibility problem
If a page is difficult to use, include the URL, what you were trying to do, and—if you are comfortable sharing it—the browser or assistive technology involved. Send the report through Contact or email editor@qaeda.org.
Continuous improvement
Accessibility regressions should be treated as product defects. New interactions should preserve semantic fallbacks and should not make JavaScript a prerequisite for reading core editorial content.