Skip to content
Pier Gorelli / web & AI dev
  • 01Work
  • 02Services
  • 03About
  • 04Blog
Let's talk
Home / Legal / Accessibility

Accessibility.

This site is built to be usable with a keyboard, a screen reader, zoom or the motion turned off. Here is what that means in practice, how it is checked, and how to tell me when something doesn't work.

Last updated
29 September 2026
Standard
WCAG 2.1 AA
Reference
EN 301 549 · EAA
Applies to
piergorelli.com

fig. 00 · at a glance

  • TargetAAWCAG 2.1 level AA on every page, in every theme and accent.
  • Keyboard100%Everything works without a mouse, with a visible focus ring.
  • MotionOptionalTurn on reduced motion in your system and every effect stops.
  • Reply≤ 5 daysReport a barrier and I answer within five working days.

Contents

  1. 01 The short version
  2. 02 Standard and status
  3. 03 What you can count on
  4. 04 Motion and animation
  5. 05 How it is tested
  6. 06 Known limitations
  7. 07 Feedback and contact

The short version

Every page is designed and tested to meet WCAG 2.1 level AA.

That is the level the European standard EN 301 549 and the European Accessibility Act refer to. The blueprint look, the animations and the three accent colours were all tuned to stay within it, and the checks run again every time the site changes.

Standard and status

Target: WCAG 2.1 AA. Status: conformant, with the limits listed below.

The Web Content Accessibility Guidelines (WCAG) are the international reference for accessible websites. Level AA is the one required across the European Union by EN 301 549. Where it was simple to go further (for example on contrast of focus rings, or on motion), the site does.

What you can count on

  • Keyboard. Every link, button and form field is reachable with Tab, in reading order, with a clearly visible focus ring. A “Skip to content” link is the first stop on every page.
  • Contrast. Text meets 4.5:1 (3:1 for large text) and controls and focus rings meet 3:1, in light and dark mode and with every accent colour.
  • Screen readers. Pages use real headings, landmarks and lists. Decorative graphics are hidden from assistive technology; figures and images carry text alternatives.
  • Zoom and reflow. Text can be enlarged to 200% and the layout works down to 320 px wide without scrolling sideways.
  • Forms. Every field has a visible label. Errors are described in words next to the field and read out by screen readers, not shown by colour alone.
  • Shortcuts. ⌘K or Ctrl K opens a searchable menu. The grid overlay uses ⌥G or Alt G. No shortcut is a single letter, so nothing fires by accident while dictating.
  • Links. Links inside sentences are underlined, not only coloured.

Motion and animation

All motion is decoration, and all of it can be switched off.

If your system has “reduce motion” turned on (macOS, iOS, Windows and Android all have it), the site shows every page in its final state: no intro, no smooth scrolling, no page transitions, no animated background, no custom cursor.

With motion on, nothing moves on its own for more than five seconds: the animated contour lines behind the page titles settle after a few seconds and only react to your pointer, and blinking cursors stop. Nothing flashes more than three times per second.

How it is tested

Automated checks on every page, plus manual keyboard and zoom testing.

CheckHow
Automated auditaxe-core on every page, light and dark theme, all three accent colours, desktop and mobile
KeyboardEvery page tabbed through end to end: focus always visible, never hidden under the header, no traps
Reflow and zoomEvery page at 320 px wide and with increased text spacing, without horizontal scrolling
Reduced motionEvery effect checked with the system setting on: content is visible at once, nothing moves

Automated tools find only part of the possible problems, which is why keyboard, zoom and motion are also checked by hand.

Known limitations

  • Code samples in the blog scroll sideways on narrow screens instead of wrapping, so that commands stay copyable as written.
  • Some older blog posts use screenshots of interfaces; the text around them explains the steps, but the screenshots themselves may contain details that are only visual.

Feedback and contact

Found a barrier? Tell me and I'll fix it.

Write to me@piergorelli.com with the page address and what went wrong (and, if you like, the browser and assistive technology you use). I reply within five working days and, if the problem is on my side, I send you the content in a format that works for you in the meantime.

Questions about your data?

Write to me, a human replies.

me@piergorelli.com →
Also read · what happens to the data you send mePrivacy policy →

Got a brief that needs to move? Let's talk.

Site

  • Work
  • Services
  • About
  • Blog

Elsewhere

  • LinkedIn ↗
  • GitHub ↗
  • RSS

Contact

  • Send a brief
  • Book a call ↗

I do dev.

Cookies
0
Banners
0
Ads
0

Privacy spec · rev. 2026Read the cookie policy →

© 2026 Pier GorelliDesigned and built in Valencia

Press ⌥G for the grid · ⌘K for everything else
PrivacyCookiesAccessibility
Plotting rev. 2026
Pier Gorelli · web & AI dev0%