Last updated: 27 July 2026
Our commitment
SIAGB audits and remediates websites for accessibility. We hold our own site to the same standard we bill clients against, and we publish what we find rather than only what passes.
Conformance target
siagb.com.au targets WCAG 2.1 Level AA.
We consider the site partially conformant. Partially conformant means most of the site meets the standard and some parts do not. The specific parts that do not are listed below rather than described in general terms.
How and when we test
| Date | Tool | Scope | Result |
|---|---|---|---|
| 27 July 2026 | axe-core 4.12.1 | 44 pages, every page template | First pass: 16 of 44 pages failed. After the fixes listed below: 0 violations on all 44, in the default rule set, under a WCAG 2.1 A and AA tag filter, and with the experimental table rules force-enabled |
| 27 July 2026 | Google Lighthouse 13.4.1 | Homepage, ADA service page | Accessibility 100 / 100 |
| 27 July 2026 | WebAIM WAVE | Homepage, service, contact, case study | 3 contrast errors, 4 on the case study |
| 27 July 2026 | Manual keyboard pass | Homepage, contact | 28 of 28 focusable elements showed a visible indicator |
Automated tools catch roughly a third of accessibility problems. We say this to clients and it applies to us too, so the table above is a floor, not a certificate.
Fixed on 27 July 2026
We found these on our own site and fixed them the same day. They are listed because a vendor that only publishes its passes is not telling you anything.
Footer contrast. The copyright line carrying our ABN rendered at 2.47:1 against the dark footer, well under the 4.5:1 minimum in WCAG 1.4.3, on every page of the site. Caused by a CSS specificity conflict. Now measures 5.21:1. The decorative separators between the legal links measured 1.69:1 and were being read aloud as “vertical line”; they are now drawn in CSS instead of shipped as text.
No skip-to-content link. Keyboard users had to tab through the entire header, including three menu buttons, on every page load. WCAG 2.4.1 Bypass Blocks, Level A. A skip link is now the first focusable element on every page.
In-page anchors moved the viewport but not the focus. Our own smooth-scroll script cancelled the browser’s native behaviour, so every jump link scrolled sighted users to the target while leaving keyboard and screen reader users where they started. WCAG 2.4.3.
Muted text on tinted panels measured between 4.31:1 and 4.45:1, just under threshold. The colour has been darkened so it clears 4.5:1 on every background in use.
A heading level skip on our own ADA case study page, on the very page where we describe fixing heading hierarchy for a client.
Links inside body copy were distinguished by colour alone. On 12 pages, 46 links, a link rendered in #000066 against #495057 body text. That is 2.15:1 where WCAG 1.4.1 requires 3:1 for a non-colour cue, and the links carried no underline. Level A. The underline rule existed but its selector list had never been extended to the service, industries and products templates, which is why our blog posts scanned clean and those pages did not.
Green “after” and “live” text failed contrast. #16a34a measures 3.30:1 on white and 3.12:1 on our green badge background, against the 4.5:1 WCAG 1.4.3 requires at that size. Now #15803d, which clears both at 5.02:1 and 4.75:1.
A struck-through “before” value was rendered at 0.65 opacity, which the browser blends to #94999d, or 2.87:1. The colour underneath was already accessible; the opacity was undoing it.
A heading level skip on the RepFlow case study, h2 straight to h4 in three places.
Two comparison tables shipped an empty first header cell, announced as blank by a screen reader, which also left their data cells with no associated header.
Items 1 to 5 came out of a 12 page sweep, which returned zero violations afterwards. We then widened the sweep to 44 pages covering every template on the site and it did not hold: 16 of the 44 failed, which is where items 6 to 10 came from. A pass on a sample is not a pass on a site, and we would not accept the narrower number from a vendor, so we did not keep it for ourselves. The current result is zero violations across all 44 pages, holding in the default rule set, under a WCAG 2.1 A and AA tag filter, and with axe-core’s experimental table rules force-enabled.
Known limitations
These are still open.
- Contact form error messages are announced as a single summary rather than being programmatically associated with the specific field that failed. WCAG 3.3.1, Level A.
- Homepage load speed on mobile. Largest Contentful Paint measures between 3.3 and 4.3 seconds on a throttled mobile connection, which is slower than we want for anyone on a poor connection. Inner pages measure 1.5 seconds.
- No assistive technology testing has been performed. Everything above is automated tooling, source review and a manual keyboard pass. We have not run a screen reader pass with VoiceOver, NVDA or JAWS on this site. Until we have, we will not claim conformance that automated tools cannot establish. Automated tools catch roughly a third of accessibility problems, and we tell clients the same thing.
- Coverage. The site has around 120 published articles. Our automated sweep covers 44 pages, chosen to hit every template at least once. Individually authored pages can still carry issues that a template-level scan does not surface, which is exactly how we found the heading skip listed above.
What already works
Verified rather than assumed, on 27 July 2026:
- Reduced motion is respected. With
prefers-reduced-motion: reduceset, all 35 background animations stop. - Alt text coverage is complete. All 29 template image calls pass explicit alt text, and none of the 378 images in content ship with empty alt.
- Every contact form input has a properly associated label.
- Landmark structure is correct on every page tested: one main, one header, one footer, one navigation, and a single h1.
Third-party content
Some pages embed content we do not control, including analytics and font delivery. We are responsible for the site around them and we will replace any embed that cannot meet the standard.
Report a barrier
If you hit an accessibility barrier on this site, tell us and we will fix it.
Email [email protected] with the page address and what happened. We aim to acknowledge within two business days and to give you a fix date or a workaround in the first reply.
If you use assistive technology and something here is unusable, that is a defect on our side, not a limitation on yours.
Formal approach
This statement follows the structure recommended by the W3C Web Accessibility Initiative. It covers siagb.com.au only. Client sites we have remediated carry their own statements.