Sitemap

How to Evaluate Any Website in 10 Minutes: My Go-To Accessibility Checklist

5 min readMay 23, 2025
Close up of a checkout button on a Shopify website.

If you’ve ever opened a website and wondered, “Is this accessible?” — you’re not alone. I get asked this all the time, and honestly, most people think they need fancy tools or deep expertise to find out.

You don’t.

In fact, I’ve taught complete beginners how to spot accessibility issues with just a browser, a timer, and a checklist — and you can too. Whether you’re a small business owner, a UX designer, or just someone who wants their work to be usable by more people, this is the place to start.

Here’s my 10-minute website evaluation process — broken down into simple checks you can perform right now.

Ready? Set a Timer for 10 Minutes

This isn’t a deep audit — it’s a quick pulse check to spot the most common accessibility issues that could frustrate users or lead to legal risks. Think of it as a red-flag detector: if you find problems here, it’s a sign that deeper remediation is needed.

Open any webpage and follow along.

My Quick Accessibility Checklist

1. Color Contrast: Can you easily read the text against the background?

Use a browser extension like WAVE or the built-in dev tools to check color contrast. You’re looking for a contrast ratio of at least 4.5:1 for body text. If you’re squinting, users with low vision or color blindness are probably struggling even more.

Fix: Lighten text or darken backgrounds, or add solid color backgrounds behind text on images.

2. Skip Link Presence: Can keyboard users skip straight to the main content?

Hit Tab as soon as the page loads. Do you see a “Skip to content” link appear? If not, the site is missing a critical navigation aid for screen reader and keyboard-only users.

Fix: Add a skip link that becomes visible on focus and links to the main content region.

3, 4 and 5. Alt Text on Images

Let’s break this down:

  • Active/linked images: Do these images have meaningful alt text describing what clicking them does?
  • Decorative images: Do purely decorative graphics (like background flourishes or borders) have alt=””?
  • Meaningful images: Are product photos, charts, or content-supporting images described clearly?

Red Flag: Complex images like infographics with no meaningful alt text or captions.

Fix: Add helpful, concise alt text — or mark images as decorative when appropriate.

6. Complex Images Without Meaningful Descriptions: Do charts, graphs, or infographics have detailed explanations nearby?

If a visual contains information you can’t get by reading surrounding text, that’s an issue. Users who can’t see the image are left out.

Fix: Add a caption, descriptive text, or an expandable explanation.

7. Duplicate H1s: Is there only one main heading (H1) on the page?

Use the browser’s dev tools or a heading map plugin. Every page should have one clear H1 — the title or purpose of the page. Multiple H1s confuse assistive tech.

Fix: Reorganize content so that only the page title is H1. Use H2s and H3s for subsections.

8. Headings for Sections: Are sections broken up with logical, clear headings?

Skim the page like a screen reader would: can you navigate by heading alone? If not, add clear headings (H2, H3, etc.) for each new section or idea.

Fix: Use semantic heading tags — not just bold text — to organize content structure.

9. Form Input Labels (ARIA or Visible): Do all form fields have a label?

Hover over or inspect form fields. If you don’t see a label (either visible or coded with aria-label), users might not know what to enter.

Fix: Add a <label> for each input field, or use aria-label if a visual label doesn’t fit the design.

10. Link Text Clarity: Can you tell where a link goes just by reading the text?

Avoid vague phrases like “Click here” or “Learn more.” Screen reader users often browse links out of context, so every link should stand on its own.

Fix: Use descriptive link text, e.g., “View pricing plans” or “Download our accessibility guide.”

11. Button Text Accessibility: Is the purpose of every button clear?

If a button says “Submit” or “Go,” that’s fine — as long as it’s in a form. But if it just says “>” or uses an icon alone, it may not be accessible.

Fix: Make sure buttons have visible text or accessible labels via aria-label.

12. Document Language: Does the HTML specify the correct language?

Check the page source. You should see something like <html lang=”en”>. Without this, screen readers can’t use the right pronunciation rules.

Fix: Set the document language explicitly in the <html> tag.

Bonus Tip: Do This on Mobile Too

Once you’ve done your 10-minute desktop review, take 2 minutes to open the same page on your phone. Try tapping around with one hand. Can you reach the buttons? Are links spaced well enough to tap? This is often where usability fails hard — especially for people with motor impairments.

What Next?

This checklist is just the beginning. It’s the same process I’ve taught to designers, developers, and small business owners who want to make the web better for everyone — and it’s the foundation of my book, Practical UX.

If this was helpful and you want to go deeper, you’ll love the book.

👉 Get your copy of Practical UX here: https://practicaluxbook.com

TL;DR — Your 10-Minute Accessibility Checklist

  • Color Contrast
  • Skip Link
  • Alt Text for Linked, Decorative, and Meaningful Images
  • Complex Images Described
  • One H1 Only
  • Headings for Each Section
  • Input Labels Present
  • Clear Link Text
  • Button Purpose is Clear
  • Document Language Set

I’m Maigen Thomas and I’m on a mission to empower 1,000 early-career designers and other digital technologists with the skills and tools they need to increase their socio-economic status.

I’m the Founder of Level 11 Technology, an Apprenticeship Agency. I bring 10+ years of experience in enterprise software SaaS product design and a background in full-stack development to her UX and Gamification Design Consulting. I taught 3 cohorts of the UX/UI Design Bootcamp at UC Berkeley and wrote the $1m flagship UX/UI Design curriculum. Follow me on LinkedIn or join the MaigenUX Patreon for exclusive access to quests (with cash prizes!), professional mentorship and motivation, and Accessibility and Usability learning content.

--

--

Maigen Thomas
Maigen Thomas

Written by Maigen Thomas

Founder of Level 11 Technology, an Apprenticeship Agency • Speaker • Author • Idea Machine.

No responses yet