Accessibility

Accessibility

Flight planning is already full of constraints. The publication should not add an avoidable one.

Our standard

Iliamna aims to meet WCAG 2.2 Level AA across released pages and tools. We design for keyboard use, visible focus, semantic structure, sufficient contrast, zoom, reduced motion, useful alternative text, and readable mobile layouts.

Tools

Calculator controls use persistent labels and native form elements. Results are announced to assistive technology, remain printable, and do not use color as the only cue. The main instructions remain available when JavaScript is unavailable.

Images and motion

Content images use meaningful alternative text when the image contributes information. Decorative visuals receive empty alternative text or are hidden from assistive technology. Motion is reduced when the operating system requests reduced motion.

Report a barrier

Check the contact page for the current reporting channel and its launch status. A useful report includes the page URL, device, browser, assistive technology if relevant, and the task that could not be completed. Accessibility reports are treated as product defects and recorded through the correction process when they affect published meaning.

Current limit

This statement describes the intended and tested standard, not a claim that every possible device and assistive-technology combination is perfect. We will investigate verified reports and fix barriers we can reproduce.