accessibility
Accessibility
What works, what is limited, and how to report a barrier.
Commitment
AegeanWorks aims to meet WCAG 2.2 Level AA on the public site. The static pages are tested with keyboard navigation and an automated axe-core audit at desktop and mobile widths.
What is in place
- Semantic landmarks, one main heading per page, a visible skip link and a logical heading order.
- Keyboard-operable navigation, filters, topic chips, project dossiers and the verifier form.
- Visible focus indicators, a focus-contained mobile menu, Escape to close, and inert background content while the menu is open.
- Reduced-motion support: reveal transitions and the orbit are disabled or effectively frozen when the viewer asks for less motion.
- Text alternatives for decorative SVG, labelled form controls and announced verification results.
- No color-only status: verification results use words, not only badge colours.
- The home, verifier and dossier pages had zero WCAG A/AA axe violations at the last review.
Known limitations
Project README excerpts are simplified to headings, paragraphs, lists, quotes and code and may omit images, tables and inline links. The original README on GitHub remains the complete source.
Third-party GitHub availability and rate limits can make the live atlas fall back to the built-in snapshot or make a README excerpt unavailable. The static atlas remains usable without JavaScript.
Feedback
If something is hard to use or blocks an assistive technology, email aegean-licensing@proton.me with the page, the assistive technology and what happened. Accessibility is reviewed with each material site change.