Using the site

Use Tab and Shift+Tab to move between controls. The first link skips navigation. Open search with Ctrl+K or Command+K, or with / when you are not typing in a field, and close it with Escape. In the lab code editors Tab indents the code; press Escape and then Tab to move focus out of the editor. Text follows the font size set in your browser and can be enlarged with zoom; pages reflow to a width of 320 pixels, and code examples and diagrams wider than the screen scroll sideways inside their own frame.

Pages follow the light or dark setting of your device. The theme buttons in the header, or in the menu on small screens, choose light, dark or the device setting.

Results are announced through status messages, and errors receive keyboard focus. Files can be selected with the keyboard as an alternative to dragging. Every guide can be downloaded as Markdown, and every lab can be downloaded and run locally with Node.js, as another way to read lessons and run workshops.

Conformance status

The site aims to meet WCAG 2.2 level AA and partially conforms: some content may not yet meet every success criterion.

Known limitations: on narrow screens, diagrams and long lines of code scroll sideways. Each diagram is followed by numbered steps that give the same information as text. The site has not been tested with screen readers or other assistive technologies, so problems that only they reveal may remain.

How the site is tested

The site’s automated test suite includes these checks:

  • Every page template, from the home page to a lab, the SBOM checker and this page, is loaded in headless Chrome in the light and dark themes, at widths of 1440 and 390 pixels, and checked with axe-core against its WCAG 2.0, 2.1 and 2.2 level A and AA rules and its best practices. Any serious or critical result fails the suite. The open search dialog with results, the open menu, the open contents list and a finished SBOM report are checked the same way.
  • The same run checks what axe does not: that links inside text are underlined or contrast 3:1 with the text around them, that form fields have a boundary with 3:1 contrast and placeholders 4.5:1, and that the sticky header cannot hide the element that has keyboard focus.
  • Every page of the site is loaded at a width of 320 pixels, and any page that scrolls sideways fails (WCAG 1.4.10 Reflow).
  • Keyboard tests, which simulate key presses in a test browser environment (jsdom), check that the search dialog closes on the first Escape and returns focus, that the arrow keys move through search results, that the menu on small screens makes the page behind it inert, closes with Escape and returns focus, that the lab editor’s Tab and Escape behave as described above, that Run and Stop keep focus on a working control, and that finished reports and input errors receive focus.

Automated checks find only some barriers. The site has not been tested with screen readers (such as NVDA, JAWS, VoiceOver or TalkBack), voice control or screen magnifiers, or for accessibility in browsers other than Chrome.

Report a barrier

Email admin@softwaresecurity.com with the page, the task, your browser and any assistive technology, and what prevented you from completing it. Include only information you are comfortable sharing.

We aim to reply within 3 business days. If a barrier stops you from completing a task, the reply says how to get the same information another way while we fix it, and we aim to fix such barriers within 30 days.