Topic cluster
Accessibility statement
This static site is built to align with WCAG 2.2 AA principles where practical: perceivable, operable, understandable, and robust.
Implemented basics
Semantic landmarks, one main H1 per page, skip link, keyboard-accessible links, visible focus, text alternatives, captions for data tables, and readable contrast.
Known limits
Automated checks cannot prove full accessibility. Manual keyboard and screen reader testing should be repeated after adding tracking scripts or new widgets.
Maintenance
When adding images, use meaningful alt text for informative images and empty alt only for decorative assets.
AERIOQ Review
Evaluate AERIOQ with a cautious, evidence-first affiliate review structure.
FAQ
Does this guarantee WCAG compliance?
No. It establishes a strong baseline, but manual review is still required.
What breaks accessibility fastest?
Popups, unlabelled forms, low contrast text, and custom controls without keyboard support.