Representative home, living-study, library, contribution, and accessibility pages are rendered at 1440 px, a short 1339×590 laptop viewport, 390 px mobile, and 320 px reflow widths with no horizontal page overflow.
A Accessibility
Target WCAG 2.2 AA. Publish evidence, not a badge.
Accessibility is a release requirement and an ongoing review practice. Automated and browser checks are evidence about specific behaviors, not a substitute for full manual and assistive-technology review.
Target2.2 AAnot a conformance claim
Implemented baseline
Keyboard, focus, structure, reflow, reduced motion, and clear errors work together.
The site uses semantic headings, a skip link, a strong author-supplied focus outline, labeled controls, responsive layouts, text alternatives for functional images, status messages, and a reduced-motion media query. Core research remains readable without JavaScript. Search and library filters remain standard server-rendered controls; the site no longer operates contribution forms.
Current staging evidence
The homepage test requires its explanatory lede, primary action, and current-state card to begin or complete inside a short 1339×590 first viewport rather than hiding the next step below a poster-sized hero.
The mobile menu opens from the keyboard, exposes its state, closes with Escape, and returns focus to the menu button.
Keyboard-tab checks verify the project focus style remains visible across representative interactive controls.
Visible search, filter, menu, disclosure, and button controls are checked for programmatic labels or accessible names and minimum effective target sizing.
A mobile stress pass applies enlarged line height, letter spacing, word spacing, and paragraph spacing to the homepage and representative research/community routes and verifies critical content remains available without horizontal scrolling.
Published comparative dossiers now include a keyboard-accessible sticky section navigator. Automated checks verify every jump target exists, the selected location is exposed, and mobile navigation remains touch-sized at 320 px reflow.
Dossier source appendices use native disclosure controls so titles remain scannable while citations and annotations remain available without JavaScript. Keyboard opening, minimum target height, and 320 px metadata containment are covered by the browser harness.
The browser harness emulates prefers-reduced-motion: reduce and verifies nonessential transition duration collapses.
Local Apache staging proves private repository paths are denied and PHP is executed rather than served as source.
What remains
Automated evidence does not close the accessibility review.
Manual keyboard review should still cover the complete route set and real production content. Representative screen-reader or other assistive-technology checks, 200% text-size review, production-browser testing, and user-reported barriers remain release evidence to collect.
The project therefore targets Level AA but does not claim full WCAG conformance.
Feedback route
Found an accessibility barrier?
Use the correction route and label the issue “Accessibility.” Include the page, control, browser or assistive technology if relevant, and the barrier you encountered.
Report an accessibility issue