Sequences

Accessibility

What the automated accessibility tests check on each release, what they do not cover yet, and how to report a problem.

What the tests check

Each release's tests open in a browser the search page in the states on their list, from a new search to each step of a case, the docs pages, the sign-in, plans and sample pages, and these public pages. They check each one against WCAG 2.0 and 2.1 at Level A and AA:

  • axe-core 4.14.0 runs its WCAG 2.0 and 2.1 Level A and AA rules at 375, 768 and 1280 px wide, with the contrast of text over gradients and layers worked out to its worst case.
  • A keyboard walk with Tab and then Shift+Tab, at 375 and 1280 px, must reach every control in page order, each with a focus indicator of 3:1 contrast or more.
  • A reading of the browser's accessibility tree checks the names of controls, the headings, the landmarks and the status lines that change.
  • Each page must reflow at 320 and 640 px wide and keep working with wider letter, word and line spacing.
  • Escape closes each form that opens in place, and the focus goes back to the button that opened it. Every footer links to the list of all pages.

The docs pages and these public pages are also checked at 375, 768 and 1440 px wide: no sideways scrolling, and every button and every link outside a sentence at least 44 px tall. axe-core checks these public pages at those widths too.

What is not tested yet

  • No one has used the pages with a screen reader, a screen magnifier or speech input. The tests read the browser's accessibility tree, which these tools read too, but how a page sounds in a screen reader is not tested.
  • The tests run in one browser, Chromium, on Windows 11. Other browsers are not tested.
  • The PDF and Word reports a case saves, and the CSV and FASTA files of the exports, are not tested.
  • The pages where you sign in to your ConductScience Account belong to that service and are not part of these tests.

Known gaps

None are known. The tests find no failures on the pages and states they check. Since no one has used the pages with a screen reader yet, problems that only a screen reader shows may not be known.

Report a problem

If a page does not work for you with your browser or your assistive technology, write to support@conductscience.com. Say which page, what you were doing and what you use, such as a screen reader or zoom.