Skip to content
Felipe Sousa

Accessibility

The accessibility level this site aims for, how it is checked on every change and where it still has known limitations.

Target

The goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on every page, in both languages, in the light and dark themes, on desktop and on mobile.

How it is checked

Every pull request runs axe-core, through Playwright, on every public page across the combinations of language, theme and screen size, with the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA. A violation blocks the merge.

End-to-end tests also cover keyboard use: the skip link, the mobile menu closing with Escape and returning focus to its button, and moving through a page with its table of contents.

Automated tests find only part of all accessibility problems. They are the baseline, not the whole proof.

What the site provides

Semantic structure with a header, navigation, main content and footer, a single main heading per page and the language declared on every page.

A link to skip straight to the content, visible focus on controls and touch targets of at least 24 by 24 pixels on small links.

Light and dark themes that follow the system preference, with a manual switch saved only in your browser.

A contact form with a label on every field, errors tied to the field that caused them and messages announced by screen readers.

A breadcrumb trail, a table of contents and direct links to each section on long pages.

Search with Ctrl+K and single-key shortcuts (/ to search, g then p for Projects), listed under "Keyboard shortcuts" in the footer, where the single-key shortcuts can be turned off.

Known limitations

There has not yet been a documented round of testing with screen readers such as NVDA or VoiceOver. It is planned.

The contact form’s bot check is a Cloudflare Turnstile iframe, outside my control. If it gets in your way, write directly to the address at the end of this page.

The release notes in the changelog are in English, like the commits they are generated from.

Found a barrier?

Say which page, what you were trying to do and, if you can, the browser and assistive technology you use. Every reported barrier is treated as a bug, with a reply within 7 days.

To report an accessibility barrier: contact@felpsxp.com