Accessibility Statement
Last updated July 17, 2026
The Kingfish Project — kingfish.la · Effective date: July 17, 2026
How to read this statement
Plain language: Every section starts with a short summary in everyday English. The summaries help you understand; the detailed text underneath is the official version.
Each section begins with a plain-language summary, written following the Federal Plain Language Guidelines and ISO 24495-1. Summaries aid understanding; if a summary is ever inconsistent with the full text beneath it, the full text controls.
The short version
Plain language: Public-interest journalism that some of the public can’t access is failing at its job. We build toward WCAG 2.2 AA, we’re honest below about where we fall short — mostly scanned government documents and third-party video players — and if anything on this site is inaccessible to you, we’ll get you the information another way.
Our commitment
Plain language: Accountability journalism is for everyone, including readers using screen readers, keyboard navigation, captions, or magnification.
The Kingfish Project is committed to making its journalism accessible to the widest possible audience, including people with disabilities. Our conformance target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.
What we do
Plain language: The site is built to work with assistive technology: semantic structure, keyboard navigation, alt text, readable contrast, and transcripts for the meeting videos we publish.
- Structure. The site is built with semantic HTML — meaningful headings, landmarks, and link text — so assistive technology can navigate it.
- Keyboard access. Site functionality is designed to work without a mouse.
- Text alternatives. Images that convey information carry alternative text.
- Contrast and scaling. Text is designed to meet contrast standards and to remain usable when resized.
- Transcripts. Public meeting videos we publish are accompanied by transcripts, making hours of government video available as readable, searchable text.
- No motion traps. We avoid auto-playing media and content that flashes.
Current status and known limitations
Plain language: Honesty section: we haven’t had a formal third-party audit yet, scanned government documents are the biggest gap, and embedded video players belong to other companies.
This site has not yet undergone a formal third-party accessibility audit; we evaluate it ourselves on an ongoing basis and consider it partially conformant with WCAG 2.2 AA — most content meets the standard, with known exceptions:
- Scanned documents. Our archives include government records that exist only as scanned images. We add machine-readable text layers where we can, but some historical and low-quality scans resist reliable conversion. This is the nature of the source material — and we will help you get at what’s in it (see below).
- Machine transcripts. Meeting transcripts are machine-generated and may contain errors; they are aids, not certified records.
- Third-party players and embeds. Video embedded from platforms like YouTube and Vimeo uses those platforms’ players, whose accessibility we don’t control.
If something doesn’t work for you
Plain language: Tell us, and we’ll get you the information in a format that works — that’s a promise, not a suggestion.
If any part of this site or its content is inaccessible to you, contact us at [email protected]. We will acknowledge your message within 3 business days and work with you to provide the information in an accessible format — whether that means a text version of a document, a description of visual material, or another reasonable accommodation. Feedback about barriers also tells us what to fix next, and we treat it that way.
Compatibility
Plain language: Built to work with current browsers and screen readers.
The site is designed to be compatible with current versions of major browsers and assistive technologies, including screen readers such as NVDA, JAWS, and VoiceOver. It is a static, lightweight site by design, which also helps it perform on older devices and slow connections.
This statement will improve with the site
Plain language: As we fix gaps and get audited, this page gets updated.
We review this statement as the site evolves, update the date above when it changes, and preserve prior versions.
Contact
[email protected] The Kingfish Project, 1924 Albert St, Alexandria, LA 71301