The story should be readable.
Useful journalism should not be hidden behind difficult navigation, cramped type, or controls that only work one way. Tell us when the site gets in your way.
Readable pages. Clear controls. Better access.
The Salty RagIndependent Gulf Coast Journalism
The approach.
The site is designed around readable pages, meaningful headings, visible focus, and controls that can be reached without a mouse.
The design target is WCAG 2.2 Level AA. That is a working target, not a claim that every requirement has been independently audited. Accessibility also needs testing with real readers, assistive technology, and the final deployed site.
Tools already in the build.
Keyboard navigation
A skip-to-content link, standard links and buttons, a keyboard-operated section menu, and an Escape-to-close search dialog.
Readable story pages
Adjustable article text size, print styling, semantic headings, and layouts that reflow for smaller screens.
Clear form labels
Visible labels, required-field wording, native input types, draft previews, and status messages that do not depend only on color.
Less interruption
No autoplay video, flashing ad creative, remote chat overlay, or forced account signup is part of this build.
Known limits and areas to keep testing.
The current edition has not undergone a full assistive-technology evaluation across screen readers, voice control, browser combinations, and devices. The logo is an image with alternative text rather than live type. Downloaded artwork is an image asset, not a substitute for the text-based publication information on the Press page.
Some interactions—local search, the reading list, and draft tools—need JavaScript. Ordinary page reading and section links do not. Browser security settings may block local storage, clipboard access, or mail-app handoff; those actions have status or fallback messages rather than a claim of success.
External documents and sites may have different accessibility support. The single-file offline preview may also behave differently from a normal website in a phone’s document viewer. A full browser is needed to assess its interactive controls.
Statement guidance: W3C Web Accessibility Initiative.
Tell us where the barrier is.
Give the page, what you were trying to do, and what happened instead. The device, browser, and assistive technology can be useful, but a diagnosis or other sensitive health information is not needed.
For an alternate-format request, identify the story or document and the format that would help. No response deadline or accommodation outcome is promised by this page; use the contact address above for feedback.
Accessibility feedback
Start with the essentials. Fields marked required help make the draft useful.