Talk to an expert

L/05Legal

Accessibility Statement

We want this website to be usable by as many people as possible, whatever technology they use to read it. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We do not claim full conformance.

Document
Accessibility Statement
Last updated
22 September 2026
Applies to
www.onioninfosec.com
On this page
  1. 1. Our target
  2. 2. Measures taken
  3. 3. Known limitations
  4. 4. How we test
  5. 5. How to report a barrier
  6. 6. What we will do
  7. 7. Status of this statement

1. Our target

We design, build and test this website against WCAG 2.2 level AA. This is a target that guides our work. It is not a statement that every page meets every success criterion.

2. Measures taken

The website has been built with the following measures.

  • Semantic HTML with landmarks, a logical heading order and a skip link to the main content
  • Navigation, menus, accordions and forms built to be operated with a keyboard
  • A visible focus indicator on every interactive element
  • Text colors that meet WCAG AA contrast ratios
  • Animation that is reduced or removed when your device asks for reduced motion
  • Content that reflows without horizontal scrolling at a width of 320 CSS pixels and at 400% zoom
  • Text alternatives for diagrams and other meaningful images
  • Form fields with visible labels, clear instructions and error messages that are announced to assistive technology

3. Known limitations

Our own testing on 22 September 2026 found the following issues.

  • The borders of some controls, on secondary buttons, form fields and topic filters, have a contrast ratio of 1.72:1 against the page. WCAG 2.2 success criterion 1.4.11 asks for at least 3:1.
  • On small screens, a few links that stand on their own in lists are 24 to 28 pixels tall. This meets the 24-pixel minimum in WCAG 2.2 success criterion 2.5.8, but is below the 44-pixel size we aim for.
  • Complex architecture diagrams may be harder to use with some assistive technologies, even where a text alternative is provided. If you need the information in another form, ask us and we will provide it.

4. How we test

We last tested this website on 22 September 2026. Pages were checked at widths from 320 to 1920 CSS pixels for reflow and horizontal scrolling, the contrast of the text and background color pairs used on the site was measured against WCAG 2.2 AA, and the size of links and buttons was measured on small screens.

Full manual testing with a keyboard and with screen readers has not yet been carried out. This statement will be updated when it has.

5. How to report a barrier

If you cannot access part of this website, or you have a suggestion, tell us through the contact page. It helps if you include the following.

  • The address of the page
  • What you were trying to do and what happened
  • The browser, device and any assistive technology you were using

6. What we will do

We will review your report, reply to you and, where we confirm a barrier, plan a fix. If you need information from the website in a different format, we will work with you to provide it.

7. Status of this statement

This statement describes our approach. It is not a claim of full conformance with WCAG 2.2 or with any accessibility law. We will update it as the website changes and as audit results become available.