Accessibility statement
Last reviewed: October 22, 2026
Commitment
I want this site to work for as many people as possible, whatever their device, connection or assistive technology. The goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
Structure and navigation
- Semantic HTML with clear landmarks (header, navigation, main content and footer), one main heading per page and headings in order.
- A “Skip to content” link as the first element of every page.
- Everything can be used with a keyboard, with a visible focus indicator.
- The mobile menu announces whether it’s open or closed and closes with the Esc key.
- The portfolio filters announce which one is active and how many projects are shown.
- The frequently asked questions use native elements that open and close with the keyboard.
Content
- Every informative image has a descriptive alternative text; decorative images are hidden from screen readers.
- Text is set in high contrast on a dark background, and secondary text is kept above the minimum contrast ratio.
- Each page declares its language, and the full site is available in English and Spanish, with a language switch in the header.
Forms
- Every field has a visible label, and optional fields are marked as such.
- Name, email, phone and company fields support browser autocomplete.
- Confirmation and error messages are announced to screen readers.
Motion and display
- If your system is set to reduce motion, animations, parallax and smooth scrolling are turned off.
- There’s no video or sound that plays on its own, and nothing moves automatically.
- The layout adapts from 320 px wide screens to large monitors and supports browser zoom without horizontal scrolling.
Speed
A fast site is also a more accessible one, especially on slow connections or older devices.
- Written in plain HTML, CSS and JavaScript, without frameworks or page builders. The site works without JavaScript; scripts only add enhancements.
- Images in WebP format, with their dimensions declared to avoid layout shifts, and loaded only when they’re about to appear on screen.
- The main image is preloaded, with a lighter version for mobile.
- Fonts are served from the site itself, with no requests to external font services.
- Third-party scripts, like Google Analytics, only load after you give consent.
Findability
- Each page has its own title, description and canonical address.
- Readable addresses, a sitemap and structured data help search engines understand the content.
- Each page is linked to its version in the other language.
Known limitations
- If Formspree, the service that handles the contact form, detects unusual activity, it may ask for a verification step (reCAPTCHA) that can be hard to complete with some assistive technologies. You can always write to martin.malandra@gmail.com instead.
- The case studies show visual work. Their alternative texts describe the main content of each image, but can’t convey every detail of a design.
- Dragging the portfolio carousel is a mouse shortcut; the arrow buttons and the keyboard do the same.
How it’s checked
The site is reviewed with keyboard-only navigation, at different screen sizes and zoom levels, and with the browser’s accessibility tools.
Feedback
If something on this site is hard to use, or you need content in another format, write to martin.malandra@gmail.com and tell me the page and the problem. I’ll reply and fix it, or send you the content in another way.