Accessibility statementAccessibility statement

Conformance status

This website aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. It has not been assessed by an independent auditor, so we describe it as partially conformant: most of the site meets the standard, and we have not verified every success criterion on every page under formal audit conditions.

What we have built in

• Semantic HTML with landmarks and one meaningful heading structure per page.
• A skip link to the main content as the first focusable element.
• Full keyboard operability, with a visible focus indicator on every interactive element.
• A mobile navigation built on the native dialog element, so focus trapping, Escape-to-close and focus restoration come from the platform rather than from hand-written scripting.
• Form fields with programmatic labels, errors associated via aria-describedby, an aria-invalid state, and a status region so submission outcomes are announced.
• Text and interface colours checked against their actual backgrounds. The brand green is used for graphics and decoration; interactive surfaces use a darkened variant so white text on them clears 4.5:1.
• Information never conveyed by colour alone.
• Motion that respects prefers-reduced-motion: reduce: with the preference set, transforms and reveals are dropped rather than shortened.
• Touch targets of at least 44 by 44 CSS pixels.
• Layouts that reflow to a 320 pixel width without two-dimensional scrolling.
• Decorative images and icons hidden from assistive technology; meaningful images given useful alternative text.

How we test

• Automated checks with axe running against every page in our test suite.
• A manual keyboard pass over navigation, forms and interactive components.
• Verification with the reduced-motion preference enabled.
• Zoom and reflow checks at 200% and 400%.

Automated tooling finds roughly a third of accessibility problems. The manual passes exist because the rest are structural. We wrote about why in accessible enterprise web applications.

Known limitations

• The site has not been tested with every screen reader and browser combination. Testing to date covers keyboard operation and automated checks rather than a full assistive-technology matrix.
• Wide data tables, such as the engineer tier table, scroll horizontally on narrow viewports. The scroll container is keyboard focusable, but a table remains a harder reading experience on a small screen than the surrounding content.
• No independent accessibility audit has been carried out yet. We will update this statement when one has been completed.

Tell us about a barrier

If something on this site prevented you from doing what you came to do, we want to know, including if it is something we have listed above as known. Email hello@codentures.eu and describe what happened, the page, and the browser or assistive technology you were using if you know it.

We aim to respond within five working days. If you are not satisfied with our response, you can contact the consumer protection authority in your country.

Accessibility in client work

We build client applications to the same standard, as a default rather than a paid extra. What that means in practice is described on how we work.

This statement

Prepared for Codentures, a trade name of Semântica Nómada Lda. Last reviewed 28 September 2026. It is reviewed whenever the site changes materially.