Our target
We aim to meet the Web Content Accessibility Guidelines 2.1 at Level AA. WCAG is the most widely-used accessibility standard for the web; Level AA covers the most common barriers faced by users with vision, hearing, motor, or cognitive disabilities.
Meeting this standard is an ongoing effort rather than a one-time certification. Some pages already exceed it; some corners of the site still fall short. We treat accessibility issues as bugs, with the same seriousness as any other bug.
What we already do
- Semantic HTML. Articles are built from real headings, paragraphs, lists, figures, and captions — not div-soup. Screen readers and reader modes can parse them.
- Keyboard navigation. Every interactive element on the site — navigation, links, audio controls, forms — can be reached and operated with a keyboard. Focus rings are visible and high-contrast.
- Readable contrast. Body text, headlines, and UI labels meet or exceed WCAG AA contrast ratios in both light and dark themes.
- Text resizing. Content reflows cleanly up to 200% zoom without losing functionality or clipping text.
- Alt text. Informative images include descriptive alt text; decorative-only images are marked as decorative so screen readers skip them.
- Reduced-motion support. The site respects
prefers-reduced-motion. Animated elements (visualizer bars, section transitions) go static for users who have requested less motion. - Dark and light themes. Readers can switch between themes, and both are tested for contrast.
- Podcast transcripts. We are progressively publishing full transcripts of every AI Chat network episode. Recent episodes have transcripts on the show page; back-catalog is being filled in.
- Plain-language writing. We avoid jargon where we can and define it where we cannot. Long sentences get broken up on edit.
Known issues we are working on
Because we ship honestly: here are the gaps we are aware of as of this page's last-updated date.
- Some older podcast episodes do not yet have transcripts.
- A handful of embedded media players (for example from YouTube and Spotify, where we reference third-party content) have accessibility behavior we do not fully control; we avoid them where a first-party alternative exists.
- A small number of charts and data visualizations still need accessible text summaries alongside the graphic.
- Our newsletter is delivered through a third-party service. We have chosen a provider that supports accessible templates, but some email clients render newsletters in ways we cannot guarantee.
When an item on this list is resolved, it moves off the list and into the section above.
Assistive technology we test against
We periodically test the site with:
- VoiceOver on macOS and iOS.
- NVDA on Windows.
- TalkBack on Android (spot checks).
- Keyboard-only navigation on desktop and mobile.
- High-contrast and dark-mode OS settings.
If you rely on a different tool — a different screen reader, switch access, voice control, eye tracking, a braille display — and you hit a wall on our site, we want to know about it. Real reports from real users are more useful than any audit.
Report a barrier
Email hello@aichatdaily.com with “Accessibility” in the subject line. A helpful report usually includes:
- The URL of the page you were on.
- What you were trying to do.
- What happened instead.
- The assistive technology, browser, and device you were using, if relevant.
We respond to accessibility reports within one business day. For urgent issues — for example, something that prevents you from reaching published reporting at all — we triage immediately and get back to you with a timeline for the fix.
Alternative formats
If you need a specific piece of reporting in an alternative format — a plain-text transcript, a larger-type export, an HTML version of a PDF — email us and we will do our best to provide it. We cannot always meet every request instantly, but we will always respond and tell you what we can do.
Our editorial style and accessibility
Accessibility is not just a technical checklist — how we write also matters. See our editorial standards for the principles that govern our writing, including our commitment to plain language, linking primary sources, and writing for a general audience rather than insiders.
Feedback on this policy
If any part of this page is unclear, incomplete, or wrong, please let us know. The same address handles feedback on the policy itself: hello@aichatdaily.com.