The standard
The target is the Web Content Accessibility Guidelines 2.1, Level AA. SOVRINT Inc. is one person with no accessibility team, and this statement is its own account of its own tests.
The US Department of Justice names the same standard in its web rule for state and local governments under Title II of the Americans with Disabilities Act. An interim final rule of April 20, 2026 set the compliance dates at April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller governments and special districts. This is information for readers, not legal advice.
What was tested
The tests ran on November 7, 2026, on the code of that date, and covered:
- The public site: all 41 pages in the site map, the briefing request page, the page shown when a form cannot send, the page shown for an address that does not exist, and the sign-in page.
- The workspace: 16 screens, run on a local copy with made-up test accounts as a customer and as the owner. They cover search, a watched phrase, an audit, a report, an assessment request, an order, the writing screens and the owner’s accounts and inbox.
- The one PDF on the site, the sample briefing, for its structure only.
The analytics choice panel and the frozen demo were tested on a local copy with test settings. A delivered assessment was tested only as the read-and-sign proof of the same document. Pages or screens added after this date are not covered.
How it was tested
| Test | How | Where |
|---|---|---|
| Automated rules | axe-core 4.14 with its WCAG 2.0 and 2.1 A and AA rules, in Chrome | Every page and screen, at 1280 and 320 pixels wide |
| Keyboard | A script pressed Tab through each page and recorded the order, whether the focus ring showed, its contrast, and whether anything covered it | Every public page and 10 workspace screens, at both widths |
| Keyboard actions | Scripted use of the skip links, the sorted table, the chart arrow keys and Escape, and sending forms | Trends, a topic page, Contact, sign-in and the audit screen |
| Text contrast | The ratio worked out for every piece of text against the colour behind it, including text over the yellow column | Every page and screen, at 1280 pixels wide |
| Reflow and zoom | Pages loaded at 320 and 640 pixels wide, which match 400 and 200 percent zoom on a 1280 pixel screen, and checked for sideways scrolling | Every public page; workspace screens at 320 |
| Text spacing | The WCAG 1.4.12 line, letter and word spacing forced on, then checked for overflow | Every page and screen, at both widths |
| Accessibility tree | Chrome's own tree compared with the page: table rows, and names on links, buttons and fields. This shows what a screen reader is given, not what it says | Every page and screen |
| Forms | Labels, required fields, autofill names, error messages and where focus goes on an error and on success | Contact, briefing request and sign-in |
| Checked for tags, a title, a language, headings and tables | The sample briefing |
Software ran these tests, including AI tools working under SOVRINT’s direction. A person has not repeated them by hand. On the final run, axe-core found no failure of a WCAG A or AA rule, every piece of text measured at 5.4 to 1 or better, and no page scrolled sideways at 320 pixels. That is a good sign and nothing more: automated tools catch only part of what WCAG asks.
What was not tested
- No real screen reader. VoiceOver, JAWS and NVDA have not been used on any page.
- No voice control, switch device, or magnifier software.
- No testing by people with disabilities.
- No browser but Chrome on a Mac. Safari, Firefox, Edge and real phones are untested. The 320 pixel tests were a narrow window in Chrome.
- No outside audit of any kind.
Fixed on November 7, 2026
- The sign-in and invitation screens had no main landmark.
- The workspace had no skip link past its search and side panel.
- Sending a form dropped keyboard focus to the top of the page. Focus now stays on the button, on the public forms and in the workspace.
- Workspace tables pushed the whole page sideways on a narrow screen. They now scroll in their own box, and a keyboard can scroll it. One table on Trends had the same fault. The wide tables on the filings and state bills pages now take keyboard focus too.
- Workspace charts gave a single figure as text and every other count only on hover. Each chart now has its counts as a table.
- The date field had no focus ring on its calendar button.
- The workspace bar stayed fixed on phones and could cover what had focus.
- At 400 percent zoom on a short screen, the top of the analytics choice panel ran off the screen and could not be reached.
- A link inside a table caption on the fourth case file broke that table’s structure.
- A long cookie name, the phone navigation and the chart range buttons overflowed at 320 pixels, or once text spacing was widened.
- The reading on a trend chart can now be dismissed with Escape. A new invitation link is now announced to assistive technology.
Known gaps
| Gap | Plan |
|---|---|
| Nobody has listened to the site with a screen reader, so the results above may hide real problems. | A VoiceOver pass by hand first, then a paid test with JAWS and NVDA before any agency relies on the workspace. |
| The concordance on the case files sets each line as one long link. It works by keyboard and reflows at 320 pixels, but how a long line sounds is unknown, and its two column heads are hidden from assistive technology. | Listen to it in the VoiceOver pass, then shorten the link or restore the heads if it reads badly. |
| Trend charts can be read by arrow key, but the table under each covers only the last 52 weeks. Older weeks are in the CSV download. | Add a full table or a plainer route to the older weeks. |
| In the workspace, a finished action such as keeping a line is not announced. The change can only be found by reading on. | Add one status message that says what changed. |
| Workspace form errors are announced, but focus stays on the button and the field in error is not marked. The public forms rely on the browser's own required-field messages. | Mark the field and move focus to the error. |
| Accepting the cost and timing of an assessment takes one click, with no separate check step (WCAG 3.3.4). | Add a confirming step before the order starts. |
| In the workspace, the side panel's headings come before the page's main heading, and all audits share one page title. | Move the panel after the main content in the page order, and name each audit in its title. |
| In the workspace, long quoted lines are cut off at the sides on a wide screen. The full line reaches assistive technology and is at its source. | Let the line wrap, as it does on a narrow screen. |
| With the wider text spacing forced on at 320 pixels, five pages scroll sideways by up to 55 pixels, because a long word or a date kept on one line no longer fits. Nothing is hidden. | Let those words break or shrink at that width. |
| The public site has menus and page lists but no search and no page listing every address, so a few pages can be reached only one way (WCAG 2.4.5). | Add a plain index of all pages. |
| The sample briefing PDF is tagged, with a title, language, headings and tables. Its reading order has not been checked, and it has not been through a PDF accessibility checker. | Check it with PAC and a screen reader, or point readers to the web page, which holds the same text. |
| Scanned documents on the case files are images. Each has a written description, and the words that matter are quoted as text, but the full page is not transcribed. | Provide a transcript on request, and add more as they are asked for. |
Report a problem
If a page does not work for you, use the contact form and choose the topic An accessibility problem. Say which page, what you were trying to do, and what you use to read or move around the site. If you are a workspace customer, the same form works.
If the form itself is the barrier, write to privacy@sovrint.com and put the word accessibility in the subject. SOVRINT is one person and has set no response time, but every report is read, and SOVRINT will try to get you the content another way.
Changes
The date at the top is the date of the last test. When the tests are run again or a gap closes, this page changes with a new date.