Accessibility

Apologetics Wiki wants anyone to be able to read and study the Bible and the articles, including people who use screen readers, braille displays, magnifiers, or voice control, people who navigate by keyboard or switch, people with dyslexia or other cognitive or learning disabilities, and people who prefer larger text or less motion.

Our Target

The target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. Where it helps reading, selected Level AAA and W3C cognitive-accessibility guidance are also in view. This page is not a legal document.

Current status: We have not yet completed a full evaluation. Until we do, we make no conformance claim.

What We Do

The Bible text and the articles are server-rendered HTML. Reading the text works without JavaScript.
Each chapter is a numbered list of verses. A verse number’s accessible name includes the full reference.
A Skip to Content link, breadcrumbs, and previous and next chapter links are on the reader pages.
Greek words use lang="grc" on the Greek letters. Hebrew and Aramaic letters use lang="hbo" and dir="rtl" on those letters. English glosses stay in English. A transliteration uses a Latin-script language tag.
The Accessibility panel sets text size, theme (including high contrast), a dyslexia-friendly font, spacing, underlined links, reduced motion, a colorblind-safe palette, and red letters on or off. The operating system’s contrast and reduced-motion settings are honored when the reader has not chosen otherwise. Windows forced-colors keeps focus rings, word boundaries, and verse numbers visible.
A citation preview opens on hover, keyboard focus, or activation, stays open while the pointer is on it, and closes with Escape. The open icon remains the link to the source.
The same pages are available as Markdown (add .md to most addresses) and through the MCP server.

How We Test

Last tested: 11 October 2026. We only describe checks that were actually run.

axe-core, with the WCAG 2.0, 2.1, and 2.2 A and AA tags, on the home page, one article, the Bible index, a chapter, a verse, Connect, and Non-Canonical, in light, dark, high contrast, and high contrast dark. The run fails on a serious or critical finding. Search was opened, and a Greek word card was opened, in each theme.
A contrast script checks text at 4.5:1 and interface colors at 3:1 in those themes, including system dark, system high contrast, and the colorblind palette.
Playwright checks the citation open-icon hit area, Escape returning focus to the Accessibility button, the word-card button state, language on the Greek letters, and that a verse anchor is not covered by the sticky header.

NVDA, VoiceOver, TalkBack, and JAWS were not part of this check. Pa11y and a Lighthouse score of 100 were not used as a gate. Automated tools find only part of the problems.

Known Limitations

Greek and Hebrew speech. Many screen-reader voices cannot pronounce Ancient Greek or Biblical Hebrew. They may spell the letters or use the wrong voice. Each word also has an English gloss and a transliteration.
Interlinear density. On a verse page the Greek or Hebrew accordion is in the page, collapsed until it is opened. On a chapter page it stays inside Study. A screen reader can still reach that text. A mode that keeps the original languages out of the reading order until requested is planned, and is not built yet.
Supplied words. The King James file used here does not mark the translator’s italic words. The Supplied Words control (italic, gray, brackets, or plain) is saved and applies to an italic or a marked supplied word when one is present. It does not yet change the verse text on the page.
Audio. This site does not play a recording. Links to audio Bibles elsewhere are listed below.
Reporting a problem through GitHub or the MCP suggest tool requires an account. The form on this page does not.

Third-Party Content

Links to other sites, including audio Bibles, sign-language Bibles, and GitHub, leave this site. Those sites are not under our control.

Feedback and Help

If you run into a barrier, tell us the page address and what happened. The device and assistive technology are optional. The form does not need an account. A Cloudflare Turnstile check runs with the form. It has no puzzle, and most people never see a challenge. The report waits in a review queue and is not published on the site.

Report a Barrier

From an AI assistant: connect to the MCP server, sign in, and use suggest_article_change. Say that the suggestion is an accessibility report. Signing in requires the suggest permission.
On GitHub: see Contribute once pull requests are open. Until then, the MCP suggestion is the review queue.

A reply time is not promised. If you leave an email, a reviewer can write back. The form is also where to ask for the text in another format.