How this site measures up.

The standard we aim at

brackenmark.com is built to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA — the same standard we assess our customers against, and the standard referenced by the European Accessibility Act and by EN 301 549.

We hold ourselves to it whether or not we're legally required to. As a very small business we would most likely fall inside the microenterprise exemption. We're not relying on that.

What we tested, and what came back

We point our own scanner at this site. The most recent assessment was run on 5 August 2026 using axe-core against every page of the site in a real browser, at WCAG 2.1 A and AA plus axe's best-practice rules.

The result, in full:

• Zero WCAG 2.1 A or AA failures on the home page, the study page and this page, at both desktop and mobile widths.
• Zero best-practice flags.
• Zero items marked as needing manual review by the tool.
• 46 rules passed on the home page, 36 on the study page, 31 on this one — the differences are simply that some pages contain more kinds of element than others.

Beyond the scanner, the site is built to avoid whole categories of problem rather than fix them afterwards. There is no JavaScript at all, so nothing can trap focus, hijack the keyboard or change under you. Every page has a skip link, real landmark elements, headings in order, visible focus outlines, text that reflows to a single column, and a prefers-reduced-motion rule. Colour is never the only way anything is signalled. Nothing is set in a fixed pixel size, so your browser's text-size setting works.

What we are not claiming

We are not claiming full conformance, and we won't. Automated testing reliably catches roughly 30–50% of WCAG issues. A clean automated result means the machine-checkable part is in order. It does not mean a person using a screen reader has an equally good time of it, and we say exactly the same thing to every customer who buys a report from us.

The criteria a tool cannot judge — whether alternative text is genuinely useful, whether the reading order makes sense, whether an interaction is actually operable with assistive technology — need a human, and ideally a human who uses that technology daily. We have not commissioned an independent audit of this site by a third party. When we do, this page will say so and give the date.

The one thing on this site we'd flag ourselves: the sample report is a PDF, and PDFs are harder to make properly accessible than web pages. It has a document title, real headings and text alternatives on its charts, and it is text rather than scanned images, so it can be read aloud and searched. It has not been tagged to PDF/UA. If you need the same content as HTML or in another format, email us and we'll send it — that is not a favour, it's the point.

If something doesn't work for you

Tell us. Email contact@brackenmark.com with whatever detail you can — the page, what you were trying to do, and what happened. The browser and assistive technology you were using helps, but don't let not knowing it stop you writing.

We aim to reply within 5 working days, and to say plainly whether we can fix it, when, or why not. If you need something on this site in a different format, ask and we'll provide it.

If you're not satisfied with how we respond, you can raise it with the Competition and Consumer Protection Commission, which is the enforcement authority for e-commerce accessibility in Ireland, or with the Irish Human Rights and Equality Commission.

The honest bit

A statement like this is easy to write and easy to leave rotting. Ours is dated, it says what tool produced the numbers, and it names what we haven't done. If you find something on this page that turns out not to be true, that is worth telling us about more than anything else on the site — and we'd rather hear it from you than not hear it.

Statement prepared 5 August 2026. Based on an automated assessment of brackenmark.com carried out on 5 August 2026 with axe-core. Reviewed whenever the site changes.