Steel Cap Digital Buy Upfront →
Accessibility

Accessibility Statement

What we target, what’s in place, and what we’re still working on.

Last reviewed: 15 May 2026

Plain English summary We want this site to work for everyone, including people who use a screen reader, navigate by keyboard, need higher contrast, or rely on assistive tech. We’ve built it against WCAG 2.2 Level AA. Some bits are still being polished. If something’s broken for you, email Shannon and we’ll fix it.

1. The Standard We Target

Steel Cap Digital aims to conform to Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That’s the baseline most Australian government and accessibility advocacy bodies recommend for public-facing websites.

Aim and reality aren’t always the same thing. Where we’ve fallen short of AA, we say so below.

2. What’s in Place Today

The current site (deployed May 2026) ships with the following accessibility features:

  • Keyboard-friendly: every interactive element (links, buttons, form inputs, dropdowns, the FAQ accordion) is reachable and operable by keyboard alone. A “Skip to content” link is the first focusable element on every page.
  • Visible focus: a 3px solid orange focus ring with 2px offset shows on any element you tab to. It’s built into the design language rather than bolted on.
  • Screen reader hooks: the primary nav, mobile menu, dropdown submenus, and FAQ accordion all expose ARIA state (`aria-expanded`, `aria-haspopup`, `aria-controls`). Form success and error messages announce themselves via `role="status"` and `role="alert"`.
  • Region-correct language: every page declares `lang="en-AU"` so Aussie place names and currency are pronounced correctly by screen readers.
  • Reduced motion respected: if your system preferences ask for reduced motion, the parallax hero, the animated PCB circuit, smooth scrolling, and motion-based UI all sit still.
  • Semantic structure: headings step in order (h1, then h2, then h3), landmarks (`
  • Touch targets: buttons and tap zones meet or exceed 44x44px on mobile.
  • Escape closes overlays: the mobile menu and nav dropdown close on `Escape` and return focus to the trigger.
  • No flashing content: no element on the site flashes more than three times per second.

3. What We’re Still Working On

Honest list. None of these are stop-everything emergencies, but each one is on the work board.

  • Per-field form validation: the contact form currently shows one top-level error message if the submission fails. Per-field inline validation (telling you exactly which field needs attention) is queued for the next release.
  • Screen reader walkthrough: a full manual pass with NVDA and VoiceOver across every page hasn’t been completed yet. Automated checks pass, but automated checks miss things a real screen reader user would catch.
  • Contrast spot-checks: the primary palette has been checked, but a few decorative or hover-state colour pairs haven’t been verified to AA explicitly. Anywhere we’ve relied on muted secondary text on dark backgrounds is the place to scrutinise.
  • Lead Engine page: this is the most component-heavy page on the site. Some of its newer FAQ and card components haven’t been through the same accessibility audit as the older pages yet.

Each of these is tracked in the project work board. Updates ship to this page when fixes ship to the site.

4. Compatibility

The site is built and tested against current versions of:

  • Chrome, Firefox, Safari, and Edge (latest two major versions of each)
  • iOS Safari and Android Chrome on mobile
  • NVDA (Windows) and VoiceOver (macOS / iOS) at the basic-navigation level

If you use an older browser or a less common assistive technology and run into problems, please tell us. Older-browser support is a known gap, but specific issues we hear about may be fixable.

5. Known Technical Limitations

  • The parallax hero on the homepage uses scroll-linked motion. It’s disabled when the system requests reduced motion, but on devices without that preference set it may still feel intense. Tell us if it’s a problem and we’ll add a per-site toggle.
  • Some PDF or third-party embedded content (Stripe checkout, Formspree confirmation) is hosted by external services we don’t control. Their accessibility is their own. We pick providers who take it seriously.

6. How to Report a Problem

If anything on this site is hard to use, broken, or excluding you, please reach out. We take accessibility issues seriously and respond quickly.

When you write or call, the most useful information is: which page, what you were trying to do, what got in the way, and what device / browser / assistive tech you were using. We aim to acknowledge within one business day and to ship a fix or a workaround within five.

7. Formal Complaints

If we don’t respond to a reported accessibility issue in a reasonable time, or you’re not satisfied with how we’ve handled it, you can escalate to the Australian Human Rights Commission, which administers the Disability Discrimination Act 1992.

8. How This Page Is Maintained

This statement is reviewed at every release that touches accessibility (and at least every six months otherwise). The “Last reviewed” date at the top of the page reflects the most recent review. The site is built and maintained by Shannon White (Steel Cap Digital) using static HTML, CSS and JavaScript with no framework, deployed via Cloudflare Pages. Accessibility regressions are caught by per-release manual checks and by ongoing user feedback.

9. Contact

For accessibility-specific questions or feedback: