Work / Northern Neck Regional Jail
Case study · Regional jail authority
How did a Virginia regional jail authority launch a new site with its accessibility on the record from day one?
Northern Neck Regional Jail is a regional jail authority in Warsaw, Virginia, and a public body. Its old site ran on Dreamweaver and cPanel. Voyager built a new WordPress site on a custom block theme, migrated the content, and tested it by machine and by hand before launch. On 10 August 2026 the site was certified to WCAG 2.1 Level A and AA: 61 pages scanned, 0 accessibility problems.
Case file
Conformance report dated 2026-08-10
Client
Northern Neck Regional Jail
Industry
Regional jail authority
Location
Warsaw, VA
Practice
WordPress
Services
WordPress build, accessibility, managed WordPress
Built on
WordPress, from Dreamweaver and cPanel
Certified
10 August 2026, at launch
Measured
Launch story
Built
Tested
Certified
Figures from the Accessibility Conformance Report (VPAT 2.5, WCAG edition) for www.nnrj.state.va.us, report date 10 August 2026.
01 At a glance
Before against after, on the three things that mattered.
| What mattered | Before | After · WordPress |
|---|---|---|
| Platform | Dreamweaver, run through cPanel | WordPress on a custom block theme |
| Content | On the old site | Migrated to the new one |
| Accessibility | Required on the record, page by page, by launch day | Certified to WCAG 2.1 Level A and AA: 61 pages, 0 problems |
The new site as delivered on 10 August 2026, from its Accessibility Conformance Report.
02 The problem
A site built in Dreamweaver, run through cPanel.
A public body needs its accessibility on the record. Northern Neck Regional Jail is a regional jail authority in Warsaw, Virginia, and a public body. Virginia law expects public bodies to obtain accessibility conformance documentation from their vendors; the conformance report for this site cites the Virginia Information Technology Access Act.
The new site had to arrive with that documentation, not add it after launch.
The old site ran on Dreamweaver and cPanel. Moving it meant a new platform, migrated content, and accessibility that could be shown, page by page, on the day the site went live.
03 What we did
Built accessible, then tested by machine and by hand.
A new WordPress site on a custom block theme, with the content migrated, scanned in full and reviewed by hand before launch.
Built a new WordPress site on a custom block theme
And migrated the content from the old site.
Scanned the full site automatically before launch
All 61 pages, with Equalize Digital Accessibility Checker Pro 2.2.0.
Reviewed by hand what tools cannot test
Keyboard-only traversal, focus, contrast of the full palette, 200% resize, 320px reflow, headings and landmarks, forms, and screen reader spot checks.
Left Accessibility Checker installed
So editors are prompted on every save.
04 What we left off
What the certification does not cover.
Two things this case study deliberately does not claim, and why.
| Left off | Why |
|---|---|
| Every criterion tested by automated tools | Automated tools cannot test every criterion, so manual review covered the rest. |
| Linked PDF documents and third-party vendor services | They are outside the certification, which describes the site as delivered on 10 August 2026. |
05 On screen
The accessibility statement shipped with the site.
The old site ran on Dreamweaver and cPanel. The new home page is WordPress on a custom block theme, and the accessibility statement was published with the site, not after it.
Home page
Built in Dreamweaver, run through cPanel
Before · the old site

nnrj.state.va.us · home
Accessibility statement
Conformance documentation, expected of the vendor by Virginia law
The requirement

The accessibility statement · published with the site
Screenshots of the live pages at 1200 by 800, captured September 30, 2026. There is no capture of the old site, so its side is a text panel.
06 Results
Certified to WCAG 2.1 AA at launch.
61 pages scanned. 0 accessibility problems. The launch scan checked 61 pages and found 0 accessibility problems, and the site was certified to WCAG 2.1 Level A and AA on 10 August 2026.
| Measure | Scope | Result | Source |
|---|---|---|---|
| Accessibility problems | 61 pages scanned | 0 problems found | Conformance report |
| Contrast problems | 61 pages scanned | 0 contrast problems | Conformance report |
| Pages at 100% of passed checks | 61 pages scanned | All 61 | Conformance report |
| WCAG 2.1 Level A and AA | Report date 10 Aug 2026 | Certified | Conformance report |
Automated tools cannot test every criterion, so manual review covered the rest. Linked PDF documents and third-party vendor services are outside the certification. The certification describes the site as delivered on 10 August 2026.
Figures from the Accessibility Conformance Report (VPAT 2.5, WCAG edition) for www.nnrj.state.va.us, report date 10 August 2026, and Equalize Digital Accessibility Checker Pro 2.2.0. Published with client permission.
Your turn
Could your site show its accessibility, page by page, today?
In Virginia, public bodies are expected to get accessibility conformance documentation from their vendors. We build the site accessible, test it by machine and by hand before launch, and deliver the conformance report with it.