Access is part of the method

Accessibility & privacy

The site is designed so the question remains available across keyboard, touch, screen-reader, reduced-motion, and low-bandwidth contexts—and so private diagnostic notes stay private.

AMIANISM question-mark emblem

Direct answer

What does AMIANISM.com aim to make accessible?

The public philosophy, reports, media context, and interactive tools should remain understandable and operable without requiring a mouse, an account, a framework, or a third-party runtime. Accessibility is treated as an ongoing engineering practice, not a badge or certification claim.

01

Keyboard and focus

Interactive controls are intended to remain reachable by keyboard, with a strong visible focus indicator and no context changes merely because an element receives focus. Navigation can be opened, closed, and escaped without a pointer.

Control sizing and spacing are designed for touch and limited-dexterity use, while skip navigation lets keyboard and assistive-technology users move directly to the main content.

02

Readable, semantic structure

Pages use server-rendered HTML, landmarks, one primary page heading, descriptive section headings, associated form labels, breadcrumbs, and contextual links. Core reading content remains available without JavaScript.

Images that carry meaning receive descriptive alternative text. Decorative imagery is excluded from the accessibility tree. Long reports include an on-page table of contents.

03

Motion, contrast, and layout

The visual system uses high-contrast dark and light surfaces, generous Open Margin spacing, stable image dimensions, and responsive layouts. The site honors the operating system’s reduced-motion preference and avoids making animation necessary to understand content.

04

Private by design

The AMIAN Field Guide, Four Rights Request Generator, 11-Question Epistemic Audit, and AMIAN Claim Lens run entirely in the visitor’s browser. User-entered labels, case references, impacts, beliefs, and notes are not submitted to AMIANISM.com, sent to analytics, or stored in cookies or browser storage.

Copy, text download, print, and PDF-generation actions for those tools are created locally in the browser. The Four Rights Request is a civic/ethical template, not jurisdiction-specific legal advice.

05

An ongoing target, not a certification claim

The implementation is informed by current WCAG 2.2 practices, including focus visibility, target sizing, labels, instructions, and predictable interaction. This page does not claim formal third-party accessibility certification or universal conformance across every assistive technology.

If a future feature conflicts with accessibility, privacy, or the ability to read the core philosophy without JavaScript, the default project rule is to fix the feature rather than weaken those boundaries.