Accessibility Statement
Scrollwork is meant for every reader of the Holy Bible's account, including those who use a keyboard, a screen reader, a magnifier or a phone. This statement says what has been done for them, what has been measured, and what is not yet good enough.
Conformance status
WCAG 2.2 Level AA — Partially Conformant
Scrollwork partially conforms to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Partially conformant is the W3C's own term: some parts of the content do not yet fully conform, or have not yet been shown to. What is known to fall short is set out under Honest Disclosure.
Most recent audit: 18 November 2026. On it, axe-core found no violation in 142 of 142 page scans, and Scrollwork's own suite passed 714 of 714 checks.
01 · Scope
Pages Covered
This statement covers the public site and the application. Every page below is opened and measured by both automated suites on every run; this statement is one of them.
- The home page
/ - The home page, with How we compare open
/#compare-open - About
/about.html - Donate
/donate.html - A gift to the Guillory family
/gift.html - What it costs
/costs.html - How this is made
/method.html - The iPhone app
/iphone.html - Licensing and attribution
/licensing.html - Privacy
/privacy.html - Terms of use
/terms.html - This statement
/accessibility.html - Contact
/contact.html - The page shown for an address that does not exist
/404.html - The Bookshelf, the application's front page
/app - The Lineage of Jesus Christ
/app/scrolls/lineage - Family Tree
/app/scrolls/family-tree - The Megiddo Mosaic
/app/scrolls/megiddo-mosaic - The Story in Gold
/app/scrolls/story-in-gold - Biblical Art
/app/scrolls/biblical-art - The Bible Library
/app/charts/library - Your account
/app/account - The Study Reader, at John 3
/app/reader/John.3 - My Notes
/app/notes - Your highlights
/app/notes/highlights - Your bookmarks
/app/notes/bookmarks - Your reading history
/app/notes/history - The Study Reader's start, with the day's verse
/app/reader - About the application
/app/about - /app/roadmap
/app/roadmap - /app/request
/app/request - The Lineage, with a story opened from it
/app/scrolls/lineage#drill-open - The Study Reader, with the original words opened
/app/reader/John.3#original - The Bookshelf behind the one-time licence prompt
/app#licence - The Bookshelf, with What's new open
/app#whats-new
35 pages in all, each opened on a desktop screen 1280 pixels wide and on a phone 390 pixels wide. The application's pages are opened as a signed-in reader would see them.
02 · How it is built
What Was Done
Each measure below is in the site now, and each one the suites can measure is measured on every page before a change is published.
A skip link
The first stop for the Tab key on every page is a link, “Skip to the content”, hidden until it is reached, that passes over the menu to the page's main content.
Landmarks
Every page has one main region, which the skip link leads to. The site's menu is a navigation landmark, and search in the application is a search landmark.
Language declared
Every page declares that it is in English, so a screen reader reads it with the right voice and pronunciation.
A visible focus ring
Every control shows where the keyboard is when it is reached. The suite walks every page with the Tab key and measures the ring on each control it stops on.
Reduced motion
If your device asks for less movement, every animation and transition stops, on every page, and the home page's screens start paused.
Targets of 24 pixels
Every control you tap or click is at least 24 by 24 pixels (WCAG 2.5.8). Where a mark is drawn smaller, such as the grip that moves a tool, the target around it is not.
Contrast
Text meets the WCAG AA contrast level against its background, in light and in dark. A step in the build measures every text colour, and both suites measure the pages as they are drawn.
Text alternatives
Every image carries a description of what it shows, and the drawn marks that only decorate are hidden from screen readers.
The home page's screens
The carousel follows the W3C's carousel pattern: a named region, each screen a named slide, Previous and Next, a dot for each screen, and Pause, which a hover or keyboard focus also holds.
Dialogs
The lineage's welcome, and the stories opened from it, are named dialogs: focus moves into them when they open, and Escape closes the welcome.
Text that scales
Type is set in relative units and the layout reflows, so the browser's zoom and the site's own text size enlarge it without breaking it. Nothing scrolls sideways on a phone.
Reading without JavaScript
Reading, navigation and the donation links work without JavaScript. Three forms need JavaScript, because each is checked for automated use: contact, registration and password reset. Each says so when it is off.
Measured on the last run
Two automated suites open the same 35 pages, on a desktop and on a phone, before every change is published.
The axe-core audit
142 of 142 scans clean
0 with a violation.
acceptance/uat-axe/browser.mjs runs axe-core 4.13.0,
Deque's open-source engine, with its WCAG 2.0, 2.1 and 2.2 Level A and AA
rules and its best-practice rules, in Chromium, Firefox.
- Chromium: 71 of 71 scans clean, 2808 rule checks passed
- Firefox: 71 of 71 scans clean, 2809 rule checks passed
Scrollwork's own checks
714 of 714 checks pass
0 failing.
acceptance/uat-a11y/browser.mjs measures what axe does not: tap targets on a
phone, a keyboard walk through every control with its focus ring, reduced
motion, sideways scrolling and errors in the page.
axe finds nothing to report on any page, in either browser. An automated audit catches only part of what can go wrong, so this is a floor, not a ceiling.
Nothing the suite checks is failing. That is a statement about what it measures, not a claim that every barrier is gone; what it cannot measure is set out under Honest Disclosure.
| What our own suite checks, on every page | Passing |
|---|---|
| The page opens | 70 of 70 |
| Nothing makes the page scroll sideways | 70 of 70 |
| Every image has a text alternative | 70 of 70 |
| Text stands out from its background (WCAG AA) | 70 of 70 |
| One main heading, and the levels in order | 70 of 70 |
| Every form field has a name | 70 of 70 |
| No errors in the page | 70 of 70 |
| A skip link is the first Tab stop, and leads to the content | 60 of 60 |
| Every control reached by keyboard, with a visible focus ring | 70 of 70 |
| Movement stops when your device asks for less | 52 of 52 |
| Every tap target is at least 24 pixels, on a phone | 35 of 35 |
| Nothing covers a row you tap, on a phone | 1 of 1 |
| [D-16] no size modal | 1 of 1 |
| [D-16] no people list or scroll | 1 of 1 |
| [D-16] no Welcome | 1 of 1 |
| [D-16] item has a named Back control | 1 of 1 |
| The lineage's welcome is a named dialog, with focus inside it | 1 of 1 |
| Escape closes the lineage's welcome | 1 of 1 |
These figures are written onto this page by the suites' own run, never typed by hand. The site will not build if this page shows anything other than the last run.
What the audits made us fix
Each of these was found by a suite, failing, and fixed in the product, not switched off in the suite.
- A skip link on every page. There was none; it is now the first Tab stop everywhere, and our own suite checks it on every page.
- Search named a list that was not there. Before anything
was typed, the search field pointed to a list of results that did not yet
exist. The list is now always present, hidden until it has something to
show, and the field says whether it is open (axe:
aria-valid-attr-value). - The home page's screens. Each screen was a figure given
a role a figure may not take; each is now a plain named group, as the
carousel pattern asks (axe:
aria-allowed-role). - The lineage's strip names. The small names of the
strips of events and finds were too faint, 3.48 to 1; they are darker now
and meet 4.5 to 1 (axe:
color-contrast). - The grips that move a tool. They were 14 by 18 pixels;
each is now a 24-pixel target, its mark unchanged (axe:
target-size). - Your initials on the account page. They carried a name a
screen reader could not use; they are now an image named “Your
initials” with the letters themselves (axe:
aria-prohibited-attr). - Earlier, from our own suite: the muted grey darkened to meet AA in light and in dark; the lineage's dates moved clear of their ruler marks; movement stopped everywhere on request; a focus ring on every control; tap targets of 24 pixels; one main heading on each page; and the application's menu moved off the first row of the lineage's list on a phone.
03 · Known limits
Honest Disclosure
These are the limits we know of. They are why the status above is partial, however clean the automated run.
- No testing with a screen reader yet. Scrollwork has not been tried with VoiceOver, NVDA, JAWS or TalkBack. The markup is written for them; that is not the same as having tried it.
- The lineage is drawn, and long. The Lineage of Jesus Christ is a scroll you move across and zoom. Its people, events and finds are real text and controls, and every one is reached by keyboard, but how well a screen reader conveys the shape of the whole, who stands beside whom and across what span of years, is not yet known. The underlying record is structured text, which is what makes a better answer possible.
- The charts are pictures. The Bible Library and the other charts are drawn; a screen reader is given their names, not every figure in them.
- Automated audits find only part of what can go wrong. axe and our own suite check what a script can decide. Whether an image's description is a good one, or a page reads in a sensible order, takes a person.
- No formal third-party audit has been carried out.
Rules switched off in the audit
No axe rule is switched off. Every rule for WCAG 2.2 Level A and AA, and every best-practice rule, runs on every page.
04 · What was run
Tested Environments
Only what was actually run is listed. The automated suites drive these browsers through Playwright on macOS:
| Browser, version | What ran in it | Screens |
|---|---|---|
| Chromium 153.0.8010.12 | The axe-core audit, and Scrollwork's own checks | desktop 1280×800 and phone 390×844 |
| Firefox 155.0 | The axe-core audit | desktop 1280×800 and phone 390×844 |
Not yet tested: any screen reader (VoiceOver, NVDA, JAWS, TalkBack), Safari and other WebKit browsers, Windows and Android, and a person working through the site by keyboard alone. When any of these is done, it will be listed here with what it found.
05 · Measured against
Referenced Standards
- Web Content Accessibility Guidelines (WCAG) 2.2, Level A and AA, a W3C Recommendation: the standard this statement reports against.
- WAI-ARIA 1.2, a W3C Recommendation, for the roles and names given to the application's controls.
- The ARIA Authoring Practices Guide, whose carousel and dialog patterns the home page's screens and the lineage's dialogs follow.
06 · Feedback
Report an Issue
If something stops you reading or using Scrollwork, tell us on the contact page. Say which page, what you were trying to do and what happened, and name the browser and any assistive technology you use. A barrier is treated as a defect, not a request, and goes to the front of the work: a page someone cannot read is broken, whatever else is right about it.
07 · Review
Statement Currency
This statement was last reviewed on 1 October 2026. Its figures are rewritten by every run of the suites, and the site will not build if they differ from the last run. The words are reviewed whenever a page is added, when the status above changes, and at least once a year.