Accessibility statement
Openbox Forge helps training teams make their materials accessible. We give our own website the same care.
On this page
Our goal
We want the openboxforge.com website, and the documents we post on it, to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This is a goal. We don’t claim that every page meets it today.
WCAG 2.2 Level AA includes the Level AA criteria of WCAG 2.1 and WCAG 2.0. Those are the versions that the ADA Title II web rule and the Revised Section 508 Standards refer to.
What we tested and how
We record each test: what we tested, when and how. Automated tools find only some problems. So far our checks have been automated scans and scripted checks, with contrast also measured by hand, in one browser: Microsoft Edge on Windows. Testing by a person with screen readers and with Windows high-contrast themes comes next. We’ll add those results here when we have them.
We first ran the scans and the scripted checks on September 30, 2026, on the five pages the website had then. We ran them again on November 11, 2026, after the website changed. The table shows the latest run of each check.
| Date | What we tested | How | Result |
|---|---|---|---|
| November 11, 2026 | Every page: the homepage, the privacy notice and its two earlier versions, this statement, the terms and their earlier version, and the not-found page | Automated scan with axe-core 4.13, using its rules for WCAG 2.0, 2.1 and 2.2 at Levels A and AA. We ran it at desktop and phone widths, with motion on and off, with scripts switched off, and with the menu open on the pages that have one | No problems found. On the homepage’s first screen, the tool couldn’t measure the contrast of the text against the shaded background. We worked it out from the page’s colors: the lowest ratio is 5.38 to 1, which passes |
| November 11, 2026 | Every page | Keyboard: a scripted pass, forward and backward, through every link, button and form field | Every item can be reached, the focus outline is always visible and on screen, “Skip to content” comes first, and on the pages that have a menu, it opens and closes from the keyboard |
| November 11, 2026 | Every page | Structure: headings, page regions, page language and titles, and text alternatives for images | One main heading per page with no skipped levels, every region named, and every image described or marked as decorative |
| November 11, 2026 | Every page | Zoom to 200%, reflow at 320 pixels wide (the same as 400% zoom), and increased text spacing | No sideways scrolling and no cut-off text |
| November 11, 2026 | Every page | Reduced motion switched on in the browser | Nothing animates, on loading or on scrolling to the end of the page |
| November 11, 2026 | Every page | The browser’s high-contrast mode (forced colors): the focus outline on every link, button and form field | Every item keeps a visible focus outline |
| November 11, 2026 | The homepage | The form, by keyboard: sending with no email, a failed send and a successful send | With no email, focus moves to the email field and the error is written beside it. After a failed send, focus moves to the message and your answers are kept. After a successful send, focus moves to the message |
| November 11, 2026 | Every page | The height of every link or button drawn as a button | Each one is at least 44 pixels tall |
| September 30, 2026 | The five pages the website had then | Contrast of text and form borders against their real backgrounds, measured by tool and by hand | All text meets 4.5 to 1, or 3 to 1 for large text, after one fix listed below |
| September 30, 2026 | Buttons, links and form controls | Target size | Every target met the WCAG 2.2 minimum size |
| Planned | Every page | Screen readers: NVDA on Windows and VoiceOver on iPhone | Not yet tested |
| Planned | Every page | Windows high-contrast themes, checked by a person | Not yet tested |
What we found and fixed
The September 30, 2026 checks found four problems. We fixed each one:
- A very large number in the homepage’s policy example was too faint against its background (2.9 to 1). We darkened it.
- On narrow screens, the privacy notice’s heading pushed the page sideways, because “openboxforge.com” couldn’t wrap. Long words now wrap.
- With larger text spacing on a phone, the homepage buttons and one large number didn’t fit. They now wrap.
- In the homepage’s policy example, the new values were invisible before the animation played. They now show in light text while they wait.
The November 11, 2026 run found nothing new to fix.
Known limits
These are the parts of the website that we know need care. We’ll update this list after each test.
- The form needs JavaScript. Without it, the page shows our email address, and you can send us the same information by email.
-
Motion.
- Two short animations on the homepage play once, for about two seconds each, and don’t repeat on later visits. A few background layers move only as you scroll.
- If your device is set to reduce motion, we show a still version with nothing moving.
- Pictures of slides. The small slide pictures in our examples are decorative. Everything they show is written out in the text beside them.
- Other websites. Links to other websites, such as the standards and studies we cite, go to pages we don’t control.
Tell us about a barrier
If something on this website is hard to use, please tell us. Email hello@openboxforge.com with the subject “Accessibility barrier”, and include as much of this as you can:
- the page address
- what you were trying to do
- what happened
- your device and browser
- any assistive technology you use, such as a screen reader, magnifier or voice control
We’ll reply within 5 business days. The person who runs Openbox Learn LLC reads your message and can fix the website directly.
Getting information another way
If you can’t use part of the website, we’ll give you the same information another way, such as a plain-text email or a Word document. Ask at hello@openboxforge.com.
The training materials we work on
This statement covers our own website. For customer work, we agree on an accessibility target for each project, such as a WCAG version and level, or Section 508.
Our reports record:
- what we checked
- how we checked it
- what needs a person’s judgment
A report is a record of the review. It is not a legal determination that the material complies with any law.
Keeping this statement current
We review this statement at least once a year, and whenever the website changes significantly. The date at the top shows the last review.