Skip to content

Accessibility Statement

Last updated

Graphcast Web Design wants this website to be usable by everyone, including people using a screen reader, a keyboard instead of a mouse, magnification, or reduced-motion settings. This page says what we aim for, what is already in place, what we know is not perfect, and how to tell us when something blocks you.

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is the target we build and test against.

What we do not claim

We do not claim full conformance, certification, or legal compliance. This site has not been independently audited, and no automated tool can confirm conformance on its own. Treating "we ran a checker" as "we are compliant" would be dishonest, so we are telling you where we actually stand instead.

What is in place today

  • A "skip to content" link as the first focusable element on every page.
  • Semantic HTML: real headings in order, real buttons, real links, real lists.
  • Every page has one H1 and a logical heading structure beneath it.
  • Full keyboard operation, including the mobile menu, the FAQ accordions, and every form.
  • Visible focus outlines that are never removed without a replacement.
  • Every form field has a real, associated label — not just placeholder text.
  • Form status messages are announced to screen readers through a live region, so a submission result is not visual-only.
  • Alt text on meaningful images; decorative graphics are hidden from assistive tech.
  • All decorative motion — scroll reveals, drifting background shapes, magnetic buttons, cursor effects — is switched off when your system requests reduced motion, and is skipped entirely on touch devices.
  • Content is present in the HTML before JavaScript runs, so nothing depends on scripting to be readable.
  • Wide comparison tables scroll inside their own container; the page never scrolls sideways.
  • Text reflows and stays readable when zoomed or on a narrow screen.

Known limitations

These are the things we know are imperfect. We would rather list them than hide them.

  • Contrast on decorative surfaces. Some small text over the gradient hero and dark call-to-action panels sits close to the 4.5:1 minimum rather than comfortably above it. We are working through these.
  • The phone button requires JavaScript. Our phone number is behind a click-to-reveal button to keep it away from scrapers, which means it needs JavaScript to appear. If scripting is off, the number is not reachable from the page — email us and we will send it. Our email address is a plain link and always works.
  • No independent audit. Testing to date has been manual keyboard and screen-reader passes plus automated checks, not a formal third-party evaluation.
  • Client screenshots. Portfolio screenshots have descriptive alt text, but the text inside a screenshot image is not machine-readable. Where a screenshot carries important information, we describe it in the caption as well.
  • Linked third-party sites. We link to client websites and external references we do not control and cannot guarantee.

How this site is tested

Before launch and after significant changes, we go through each page by keyboard only, check heading order and landmarks, submit every form, run automated accessibility checks in the browser, and verify pages with reduced-motion settings enabled and with JavaScript disabled.

Reporting a problem

If something on this site blocks you, tell us — it is the fastest way for us to fix it, and we would rather hear about it than not.

Please tell us the page, what you were trying to do, and what happened. We aim to acknowledge reports within two business days and will tell you honestly how long a fix will take. If you need information from a page you cannot use, ask and we will send it in whatever format works for you.

Accessibility in the sites we build

The practices listed above are the ones we apply to client projects too: semantic markup, keyboard operability, labelled forms, alt text and reduced-motion support are part of the build, not an upsell. If accessibility conformance is a formal requirement for your business, say so at the quote stage so it can be scoped and tested properly.