Web accessibility: 7 simple fixes so anyone can use your website

WebsitesBy Emiliano Calderón4 min read

Portable braille display: a device with keys and a row of raised dots that shows on-screen text in braille.
Photo: Braille display, which shows on-screen text in raised dots. Gulundin / Wikimedia Commons, CC BY-SA 4.0 (cropped)

An accessible website is one anyone can use: someone who is blind and uses a screen reader, someone who browses with the keyboard only, an older person who enlarges the text, or anyone looking at their phone in bright sunlight. It isn’t an extra for a few people: it’s the difference between someone being able to buy from you or not.

And most websites fall short. The WebAIM Million 2026 report, which analyzes the home pages of the million most visited sites, found detectable accessibility errors on 95.9% of them, with an average of 56 errors per page. Six types of error account for 96% of everything it found, and almost all of them are quick to fix.

1. Increase text contrast

This is the number one error: it shows up on 83.9% of pages. Light gray text on white, or white on soft blue, looks nice in the mockup and is unreadable in real life.

The international WCAG 2.2 guidelines require a minimum contrast of 4.5 to 1 for normal text and 3 to 1 for large text. In how to choose your brand colors we explain how to measure it, and our color palette generator helps you build combinations.

2. Describe your images

53.1% of pages have images without alternative text. That text (the alt attribute) is what a screen reader reads aloud, and what Google sees when it can’t “look” at the photo.

Describe what matters: “Chocolate cake with strawberries, single slice” works; “IMG_2034” or “image” doesn’t. If an image is purely decorative, give it an empty alt so screen readers skip it.

3. Label every form field

51% of pages have fields without labels. A form where the only hint is gray text inside the field (“Your email”) stops working as soon as the person starts typing, and a screen reader may announce it only as “text field.”

Every field needs a visible label tied to it. On a contact form, this decides whether you get the inquiry or not.

Empty links (46.3%) and empty buttons (30.6%) are usually icons without text: the search magnifier, the Instagram logo in the footer, the carousel arrow. Sighted users understand them; to a screen reader they’re just “link” and “button.”

The fix is hidden text or a label that says what they do: “Search”, “Our store’s Instagram”, “Next photo.”

5. Declare the page language

It sounds like a technical detail, but 13.5% of pages don’t do it. If the site doesn’t say it’s in Spanish, a screen reader may read it with English pronunciation and make it unintelligible. It’s a single line of code (lang="es").

6. Test your site with the keyboard only

Put the mouse aside and go through your site with the Tab key. Can you always see where you are? Can you open the menu, fill in the form and press “Send”? Some people always browse this way, and WCAG requires the keyboard focus to be visible.

Many sites hide that focus outline because “it looks ugly.” It can be designed to match the brand, but it shouldn’t be removed.

7. Buttons that are easy to tap

On a phone, a tiny button next to another one is an invitation to tap the wrong one. WCAG 2.2 added a criterion for minimum target size: 24 × 24 pixels. For important buttons, such as “Buy” or “WhatsApp,” it’s worth going well beyond that.

What the law says in Argentina

Law 26,653 requires accessibility standards on the websites of the national government, state companies, private companies holding public service concessions, and providers or contractors of goods and services to the state. It also covers organizations that receive subsidies or donations from the state or provide services to it: if they don’t comply, they can’t renew contracts or receive benefits.

If your company sells to the state, check this with your adviser. If not, it’s still worth it: the fixes on this list improve the experience for everyone, and several of them, such as alt text and clear headings, also help with search rankings.

How to check your site for free

  • WAVE, WebAIM’s tool, flags the errors on your own page. It’s the same basis as the report cited above.
  • Lighthouse, built into Chrome (right-click → Inspect → Lighthouse), has an accessibility category with a score and a list of issues.

No automated tool finds everything: WebAIM points out that detecting no errors doesn’t mean a site is accessible. The keyboard test in step 6 is still necessary.

Wrapping up

Accessibility isn’t added at the end: it’s planned from the design stage. When we build a website we take care of contrast, alt text, forms and keyboard navigation from the start, and if you already have one, we can review it.

← Back to the blog

Shall we talk about your project?

Tell us what you need and we will reply the same day.