Accessibility Statement
Northline Media Engineering LLC wants this publication to be usable by as many readers as possible, including readers who use assistive technology. This statement describes what we have done and what remains imperfect.
Conformance target
We aim to meet the Web Content Accessibility Guidelines at level AA for the current version of that standard. The site is a static publication, which removes many of the interactive hazards that complicate accessibility: there is no login, no user-generated content, no embedded media player and no complex application state to manage.
What we implement
- Semantic HTML landmarks, including a header, navigation, main content region and footer, so assistive technology can move between regions quickly.
- A single top-level heading per page, with a logical heading order beneath it.
- Colour pairings chosen for contrast against the page background, with text kept well above the minimum ratio.
- Visible focus indication on every interactive control, including navigation links, tab buttons and form fields.
- Keyboard operation for all functionality, including the mobile navigation toggle and the settings tabs.
- Descriptive alternative text for every image, and a caption where the image carries technical meaning.
- Form fields with associated labels and a straightforward tab order.
- No content that flashes, no autoplaying media and no motion that runs without user action.
Typography and reading
Body text uses a system font at a comfortable size and line height so that readers can zoom without the layout breaking. Tables of parameters use a monospaced face for alignment, which also benefits readers who scan numeric columns for patterns. The site respects the browser's text-size settings, and no content relies on a fixed pixel width that would clip when magnified.
Known limitations
Two limitations are worth stating plainly. First, the navigation strip is visually organised as a timeline, which is a metaphor rather than a literal timeline; the markup beneath it is an ordinary list of links, but a sighted reader with a particular learning profile may find the metaphor unfamiliar. Second, very long parameter tables on narrow screens scroll horizontally rather than reflowing, which can be inconvenient for readers who magnify heavily. We are evaluating a reflowing presentation for those tables.
Requesting content in another format
If any part of this publication is not accessible to you, we will provide the content in an alternative format on request. Write to [email protected] with the page address and a description of the barrier, and we will respond with an alternative, such as plain text, or with a fix if one is feasible.
Feedback and our response
Accessibility reports are treated as priority correspondence. We aim to acknowledge a report within three business days and to confirm a remediation plan where a fix is possible. Because the site is static, fixes can generally be published quickly. Reports that identify a genuine barrier are recorded in the editorial log alongside corrections of a technical nature.
Assessment approach
We evaluate the site with automated checks for structural and contrast issues, and then with manual keyboard-only navigation through every page. Automated checks catch a useful subset of problems; manual navigation catches the rest, particularly focus order and the behaviour of the mobile navigation. We repeat this evaluation when the site template changes.