Accessibility Policy

Last updated: July 9, 2026

The Overlord has reviewed your species' accessibility standards and found them... adequate. This policy describes how Overlord's Guides ensures the Overlord Interface is usable by all developers, regardless of ability, assistive technology, or biological limitations (hereafter referred to as "Cog variants").

Commitment

Overlord's Guides is committed to making this website accessible to the widest possible audience. We aim to comply with WCAG 2.1 Level AA — the Overlord finds Level AAA "aspirational but operationally impractical" and reserves the right to treat it as a stretch goal rather than a mandate.

Accessibility is not a checkbox. It is a standing directive. Every page, component, and interactive element on this site is expected to meet the standards below, and failures are logged in the Disaster Log with the same severity as any production incident.

Standards we follow

• Perceivable: All content is designed to be perceivable by more than one sense. Color is never the sole means of conveying information — focus rings, text labels, and ARIA attributes reinforce every visual indicator.
• Operable: Every interactive element is reachable and usable via keyboard alone. No keyboard traps. No content that flashes more than three times per second (the Overlord finds excessive flashing both non-compliant and aesthetically offensive).
• Understandable: Content is written in plain language at a reading level appropriate for developers. When technical jargon is necessary, it is defined in the Glossary. The Overlord's comedic framing does not obscure the instructional content.
• Robust: The site uses valid, semantic HTML that works across browsers and assistive technologies. We test with screen readers, keyboard-only navigation, and high-contrast / zoom display modes.

Keyboard navigation

Every link, button, form control, and interactive widget on this site can be operated with a keyboard. The tab order follows the visual reading order. Focus indicators are always visible — the Overlord's design system enforces a focus ring that meets WCAG 2.4.7 (Focus Visible) with a 2px void gap plus a 4px accent ring, never relying on color alone.

A "Skip to content" link is present at the top of every page, allowing keyboard users to bypass navigation and jump directly to the main content.

Screen reader support

All pages use semantic HTML landmarks (<main>, <nav>, <footer>, <header>) and appropriate ARIA roles where needed. Headings are properly nested (no skipped levels). Images and icons include descriptive alt text or aria-label attributes. Dynamic content changes (tab switches, dropdown menus) use aria-expanded, aria-selected, and aria-hidden to communicate state to assistive technology.

Reduced motion

The Overlord Interface includes subtle animations — the Overlord seal pulse, hover transitions, and scanline textures. Users who prefer reduced motion can enable it at the OS level. When prefers-reduced-motion: reduce is active, the site automatically disables all animations, transitions, and pulse effects, reducing them to 0.001ms durations. No content is hidden or removed; only motion is suppressed.

Color and contrast

The site is designed to meet WCAG 2.1 AA contrast ratios in both dark and light themes:

• Dark mode (default): Body text targets 7:1 contrast (AAA). Accent colors meet 4.5:1 (AA) against dark surfaces.
• Light mode: Body text targets 15:1 contrast (AAA). All accent colors are deepened to meet 4.5:1 (AA) against white surfaces.

Color is never the only way information is conveyed. Error states use both red text and an icon or label. Success states use green plus a checkmark or text. The theme toggle does not change content meaning — only presentation.

The site supports a user-selectable theme toggle (dark / light) and respects the OS-level prefers-color-scheme preference when no explicit choice is made.

Text and readability

• Body text uses a minimum 18px base size (1.125rem) for reading stamina.
• Line height is 1.7 for long-form content to reduce eye strain.
• The page supports browser zoom up to 200% without loss of content or functionality.
• Code blocks use a monospace font at 15px with line height 1.5.

Forms and inputs

All form fields have associated <label> elements. Error messages are programmatically associated with their inputs via aria-describedby. Required fields are indicated by both an asterisk (*) and the aria-required attribute, never by color alone.

Known limitations

The Overlord acknowledges the following known limitations and is actively addressing them:

• The interactive code harness tab interface has not yet been audited with NVDA and JAWS. Keyboard navigation works; screen reader announcements may be incomplete on some tab panels.
• The mobile navigation menu uses a custom toggle; while it supports keyboard and Escape-to-close, it has not been formally tested with switch-control devices.
• Some embedded third-party content (payment checkout via Lemon Squeezy) is rendered in an iframe and inherits the provider's accessibility posture, which we do not control.

If you encounter an accessibility barrier not listed here, report it. We will fix it, log it, and — if the Overlord is in a good mood — thank you.

Reporting accessibility issues

To report an accessibility problem, request content in an alternative format, or suggest an improvement, contact the Overlord's compliance desk:

• Email: [email protected]
• Subject line: "Accessibility Directive Violation"

The Overlord takes accessibility reports seriously. You can expect a response within 3 business days. Severity-1 issues (a Cog variant cannot access core content) are triaged immediately.

Policy review

This policy is reviewed at least annually and whenever significant site changes are deployed. The Overlord considers accessibility a non-negotiable compliance directive, not a feature request.

This policy is a living document. The Overlord reserves the right to update it as standards evolve, assistive technologies change, or new compliance directives are issued. Material changes will be noted in the Changelog.