A website UX checklist for 2026

A website UX checklist is a short, repeatable set of checks a marketing team can run on its own site without a developer. The 2026 version below has 12 checkpoints. They cover readability, accessibility, speed, clarity and relevance, and each one ends in a number or a yes/no answer you can act on.

We wrote the first version of this post with three tips. Good contrast, a clear call to action, and less text. All three still hold. What changed is that the rules behind them are now written down, and in the EU some of them are law. So we rebuilt the list around measurable checks. Run it once a quarter, or before a big campaign lands.

Why does a UX checklist matter more in 2026?

Because most websites still fail the basics, and the cost of failing went up. WebAIM's 2026 scan of one million home pages found detectable WCAG 2 failures on 95.9% of them, with an average of 56.1 errors per page, up 10.1% from the 2025 scan (WebAIM, 2026). The same six error types have topped the list for seven years. Low contrast text alone appears on 83.9% of home pages.

Since 28 June 2025, the European Accessibility Act has applied across the EU. It covers e-commerce, banking services, smartphones, computers and passenger transport services (European Commission, 2025). Service providers that are microenterprises, meaning fewer than 10 staff and under 2 million EUR in annual turnover, are exempt (EUR-Lex, 2019). Everyone else selling online to EU customers is in scope. We covered the business case in 7 reasons why it's good for business to invest in web accessibility. This post is the practical follow-up.

Can everyone read and use the page?

Start here. These four checks catch the most common failures on the web, and most of them take minutes to run.

1. Normal text passes the 4.5 to 1 contrast ratio

WCAG 2.2 at level AA requires a contrast ratio of at least 4.5:1 for text, and 3:1 for large text, meaning 18 point or 14 point bold (W3C, 2024). Paste your brand colors into WebAIM's contrast checker. Check text over photos too. A hero image behind white text often fails in its light areas. If it fails, add a darker overlay or move the text off the image.

2. Buttons, icons and input borders pass 3 to 1

The same spec asks for at least 3:1 between a user interface component and the colors next to it (W3C, 2024). Light gray input borders on white are the usual offender. So are icon-only buttons in a pale brand tint. Check the states as well. If your active button looks like a disabled one, people will not press it.

3. Tap targets are at least 24 by 24 CSS pixels

WCAG 2.2 added Target Size (Minimum) at level AA. Interactive targets need to be at least 24 by 24 CSS pixels, or have enough space around them that they do not overlap a neighbor's 24 pixel zone (W3C, 2024). Open the site on a phone and try the footer links, the cookie banner, carousel dots and the menu close icon. Those are where we find failures most often.

4. Images have alt text and inputs have labels

Missing alt text was on 53.1% of home pages in the WebAIM scan, and missing form labels on 51% (WebAIM, 2026). Both are simple to fix in a CMS. In Webflow, alt text lives on the asset, so you fix it once and it follows the image. If you have hundreds of CMS images, we described a way to generate alt text automatically. Decorative images should be marked decorative, not given a caption. Every form field needs a visible label. Placeholder text does not count, because it disappears the moment someone starts typing.

Is it obvious what the visitor should do?

Clarity is where the original post started, and it is still where most conversion problems live.

5. Each page has one primary action

Pick the single thing you want the visitor to do on each page. Make that the only filled button above the fold, and give everything else a secondary style. When we audit sites, the pages that convert worst usually have four or five competing buttons in the first screen. Ask someone outside the team to look at the page for five seconds and say what it wants them to do. If they hesitate, the page is not clear.

6. The headings tell the story on their own

Read only the H1 and the H2s and skip the body text. If that outline still makes sense, the hierarchy works. If it does not, the important points are buried in paragraphs nobody reads. Walls of text were the third tip in the original post, and the fix is the same now. Cut, then order what is left by importance, and let the headings carry the message.

7. Forms ask for the minimum

Every extra field is a reason to leave. Go through each form and defend every field. If sales does not use it in the first call, drop it. Keep error messages next to the field they belong to, in plain words. "Enter a valid email address" beats "Error 422". We go deeper in our conversion optimization work, but the field audit alone is worth an afternoon.

8. Links and buttons say where they go

Empty links were found on 46.3% of home pages and empty buttons on 30.6% (WebAIM, 2026). An empty link has no text a screen reader can announce, which usually means an icon or image with no label. Sighted visitors suffer a milder version. "Learn more" repeated eight times on a page is a weak signal. Write the destination into the link. "See pricing" tells people more than "Click here".

Does the page load and respond fast enough?

9. Core Web Vitals pass at the 75th percentile

Google's thresholds are a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads across mobile and desktop (Google web.dev, 2024). Check them in PageSpeed Insights or Search Console, and read the field data rather than the lab run. Field data is what your visitors see. The usual causes of failure are oversized hero images, third-party scripts, and embeds that push content around while they load. In our own project data, clients who migrated to Webflow saw about a 40% average Lighthouse improvement with no design changes, mostly because the plugin and script load disappeared.

10. The site works on a real phone

Emulators miss things. Open the site on an actual phone over mobile data. Look for text that needs pinch-zoom, a sticky header that eats a third of the screen, a cookie banner that hides the primary button, and any horizontal scroll. Most marketing teams look at their site on a large monitor all day. Most visitors never will.

Does the page speak to the person in front of it?

11. The first screen names the audience

Generic pages convert generically. When we built sport-specific landing pages for Veo, the personalized versions converted 17% better than the generic page, in our own project data. The mechanics were simple. Same offer, same layout, but the headline, the hero footage and the proof points matched the sport the visitor came in for. You do not need a personalization engine to start. One version per key segment, linked from the right campaigns, gets most of the value. This is the kind of work that sits inside digital experience design, and it is measurable.

12. The page declares its language

13.5% of home pages had no document language set (WebAIM, 2026). It is one attribute on the HTML tag. Without it, screen readers guess the pronunciation, and browsers may offer to translate a page that is already in the visitor's language. For a Danish company with an English site, or a site in both, this is an easy one to get wrong. Check it in your CMS page settings, and check it per locale if you run more than one.

How do the numbers fit together?

Seven of the twelve checks have a hard threshold. Here they are in one place.

‍

The other five checks are judgment calls. One primary action, headings that stand alone, minimal forms, descriptive links, and a page that names its audience. They need a person, not a tool, and they are where the conversion gains usually hide.

What does this checklist not cover?

Quite a lot, on purpose. It does not replace an accessibility audit. WCAG 2.2 AA has dozens of criteria beyond the handful here, and automated tools only catch the detectable failures. Keyboard-only navigation, focus order and screen reader flow need a person to test them. It does not cover content strategy, or whether the page answers the visitor's question at all. And it does not cover AI search visibility, which we wrote about in how to get your website cited by AI search.

The list also assumes a site you can edit yourselves. If every change goes through a developer ticket, the bottleneck is the platform, not the checklist. One more honest note. Webflow makes most of these checks easier, but it does not do them for you. It will happily publish a page with 2:1 contrast and no alt text. The Designer's audit panel flags some issues. The rest is on the team.

What should we do with the results?

Fix the fails in the order above. Contrast, targets and alt text are usually a day of work for a content team. Vitals may need a developer. Personalization needs a plan. If you want a second pair of eyes on the list, or a full audit against WCAG 2.2, get in touch. We run this checklist on our own site too, and we still find things.

Sources

• WebAIM, The WebAIM Million 2026
• W3C, Web Content Accessibility Guidelines (WCAG) 2.2
• WebAIM, Contrast Checker
• Google web.dev, Web Vitals
• European Commission, European Accessibility Act
• EUR-Lex, Directive (EU) 2019/882

All Kvalifik client figures are our own project data.