Accessibility Statement | Nick Poole

The Commitment.

Accessibility is personal for me. I have relatives who rely on screen readers, so I know what a skipped heading or an unlabeled button costs someone on the other side of the glass.

It is also a professional signal. A site that gets screen readers right almost always gets user experience right everywhere else, because both come from the same habit: caring about how a page is actually experienced instead of how it looks in a comp. Most organizations treat accessibility as an afterthought, and the consequences are real, from users quietly locked out to lawsuits that were entirely avoidable.

The overlap with technical SEO is nearly total. Semantic headings, real link names, alt text, and a parseable DOM serve screen readers and search crawlers alike. Build honestly for one and you have mostly built for the other, which is why this site treats them as a single discipline.

WCAG 2.1 AA is the standard this site holds itself to. AAA and Section 508 are not every organization's goal, but AA is a reasonable ask for the private sector. Legally blind and dyslexic people don't deserve to be left out in the cold because an organization can't be bothered to invest in proper code.

The Record.

Conformance target

Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the target this site is built and tested against.

Scope

All pages on nickpoole.dev. That is the home page, the SEO expertise page, the portfolio, the credentials page, the resume, the colophon, this statement, and the contact confirmation page.

Third-party sites linked from the portfolio are not in scope. Where a linked site is one I built, it was built to the same standard, but the live version is under its owner's control.

Measures taken

Contrast managed at the token level, with a separate --accent-text token so accent copy clears AA in both the light and dark themes rather than only one
Semantic HTML first: real headings in order, real buttons for controls, ARIA only where the markup runs out
Keyboard navigation tested manually, including focus order and focus return
Automated scans with WAVE
Screen reader testing with NVDA
Contrast checked per theme, in both light and dark

Known limitations

The contact form uses a CAPTCHA. Submissions run through FormSubmit, which presents a CAPTCHA challenge before a message is delivered. CAPTCHAs are a known barrier: WCAG 2.1 asks for an alternative that does not depend on the same sense, and this one does not provide it. If it blocks you, message me on LinkedIn instead. That route has no challenge and reaches me just as fast. I am looking at whether the honeypot field alone is enough to drop the CAPTCHA entirely.

This list is what is known today, not a promise that nothing else exists. If you find something that is not here, the feedback route below is the fastest way to get it fixed and added.

Feedback

If something on this site does not work for you, tell me and I will fix it. Use the contact form, or reach me on LinkedIn.

Useful details, if you have them: the page, what you were trying to do, and the browser or assistive technology you were using. I read every message that comes through the form. I aim to respond to accessibility reports within five business days.

Statement first published: 20 August 2026
Last reviewed: 20 August 2026

This Page Describes Itself.

application/ld+json · live in this page's source

{
  "@type": "WebPage",
  "@id": "…/accessibility/#webpage",
  "isPartOf": {
    "@id": "https://nickpoole.dev/#website" },
  "about": "Accessibility",
  "author": {
    "@id": "https://nickpoole.dev/#nick-poole" }
}

The smallest node on the site, and still a node. It hangs off the same WebSite identifier as every other page. See the entity graph

How It Was Built.

Read the Colophon Report an Issue