You have heard the word “accessibility” enough times to know it matters. Maybe a customer complained they could not use your checkout. Maybe your lawyer mentioned something about compliance. Maybe you just want to do the right thing. The problem is, every guide you find seems to assume you are a developer with a toolbox full of browser extensions and terminal commands.

This guide is different. You do not need to install anything. You do not need to read a line of code. All you need is a browser and five minutes. By the end, you will know whether your website has serious accessibility problems — and what to do about them.

Why a Quick Audit Matters

A full accessibility audit can take days and cost thousands of dollars. That is valuable work, but it is not where you should start. Most websites have a handful of glaring issues that affect the largest number of people. A five-minute check catches these big-ticket problems before you invest in a comprehensive review.

Think of it like a smoke detector. It does not replace a full fire inspection, but it tells you if the house is on fire right now. That information alone is worth the effort.

Before You Start

Open your website in Google Chrome, Microsoft Edge, or Firefox. Any modern browser will work. Navigate to your homepage or your most important page — the one customers visit the most. That is where we begin.

Ready? Start the timer.

Step 1: The Tab Test (60 Seconds)

Put your mouse aside. Click somewhere on the page, then press the Tab key on your keyboard. Keep pressing it.

What to Watch For

• Can you see where you are? Each time you press Tab, a visible outline or highlight should appear around the focused element. If you press Tab and nothing seems to happen visually, that is a problem. People who navigate with keyboards (and there are more of them than you think) have no idea where they are on the page.

• Does it follow a logical order? The focus should move from top to bottom, left to right — roughly following the visual layout. If it jumps randomly from the footer to the header to a sidebar, users will get lost.

• Can you reach everything? Try to Tab to your navigation menu, your search bar, your call-to-action buttons, and your forms. If you cannot reach something with Tab alone, keyboard users cannot reach it either.

• Can you escape? If you open a dropdown menu or a popup, can you close it by pressing Escape and continue tabbing? If you get stuck and cannot move forward or backward, that is called a keyboard trap — one of the most serious accessibility failures.

Write down anything that felt broken or confusing. Move on.

Step 2: The Zoom Test (60 Seconds)

Hold down Ctrl (or Cmd on Mac) and press the + key several times until your browser zoom reaches 200%. On most browsers, the zoom level appears in the address bar or in the View menu.

What to Watch For

• Does text get cut off? If words disappear behind images or run off the edge of the screen, users with low vision who zoom in will miss your content.

• Do buttons and links overlap? Interactive elements that pile on top of each other become impossible to click accurately.

• Can you still navigate? The main menu should still be usable. If it breaks apart or hides behind other elements at 200% zoom, that is a real barrier.

• Does horizontal scrolling appear? A small amount may be unavoidable, but if you have to scroll sideways constantly to read a paragraph, the layout is not responding to zoom properly.

Reset your zoom (Ctrl+0 or Cmd+0) and move on.

Step 3: The Image Check (60 Seconds)

Right-click on any important image on the page and select Inspect (or Inspect Element). I know I said no developer tools — but this is the one small exception, and it takes only seconds.

A panel will open with the image’s code highlighted. Look for the text that says alt="something". That “something” is the alt text — the description a screen reader will announce to people who cannot see the image.

What to Watch For

• Is the alt text missing? If you see alt="" (empty) or no alt at all, blind users get nothing. If the image conveys important information — a product photo, a chart, an infographic — it needs a real description.

• Is the alt text meaningful? Alt text like “image1.jpg” or “photo” is almost as bad as no alt text. A product image should describe the product: “Blue running shoe, side view, Nike Air Max” is far better than “shoe.”

• Are decorative images marked as decorative? Not every image needs alt text. Purely decorative images (background patterns, visual dividers) should have empty alt text (alt=""), which tells screen readers to skip them. But if you are unsure, it is safer to describe the image.

Check three to five images on the page. If most of them are missing meaningful alt text, the rest of the site probably has the same problem.

A Simpler Way to Check (No Inspect Needed)

If even the Inspect method feels like too much, try this instead: hover over an image and see if a tooltip appears. Some browsers show the alt text as a tooltip, though this is not perfectly reliable. A more dependable shortcut is to disable images entirely. In Chrome, go to Settings, Privacy and Security, Site Settings, Images, and choose “Don’t allow sites to show images.” Reload your page. Wherever you see a broken image icon with no text, that image is missing its description.

Turn images back on when you are done.

Step 4: The Heading Structure Check (60 Seconds)

Screen reader users often navigate a page by jumping between headings, the same way sighted users scan a page by reading the bold, large text. If your headings are out of order or missing, it is like reading a book where the chapter titles have been removed.

Here is the quick way to check. In Chrome or Edge, press Ctrl+Shift+J (or Cmd+Option+J on Mac) to open the console. Type the following and press Enter:

document.querySelectorAll('h1,h2,h3,h4,h5,h6').forEach(h => console.log(h.tagName, h.textContent.trim()))

You will see a list of all headings on the page with their levels (H1, H2, H3, and so on).

What to Watch For

• Is there exactly one H1? Your page should have one main heading. Having zero or having five H1 tags confuses both screen readers and search engines.

• Do headings go in order? You should not jump from H1 to H4. The sequence should step down logically: H1, then H2, then H3 if needed. Skipping levels is like having a book outline that goes Chapter 1, Sub-sub-section 1.1.1 — the reader is lost.

• Are the headings meaningful? A heading that says “Section 2” or “Content” is not helpful. Headings should tell the reader what the following section is about.

If using the console feels too technical, there is another way. Simply look at your page and notice the large, bold text. Those should be your headings. If you see large text that is just regular text styled to look like a heading (but is not actually coded as a heading), screen reader users will never find it.

Step 5: The Screen Reader Quick Test (60 Seconds)

This is optional but eye-opening. Every major operating system includes a free screen reader.

• Mac: Press Cmd+F5 to turn on VoiceOver. Press it again to turn it off.
• Windows: Press Windows+Ctrl+Enter to start Narrator. Same keys to stop it.
• iPhone: Ask Siri to “turn on VoiceOver.”
• Android: Go to Settings, Accessibility, TalkBack.

Close your eyes (or look away from the screen) and try to complete one simple task on your website — like finding your phone number or navigating to your contact page.

What to Watch For

• Can you understand what is being read? If the screen reader announces “button, button, link, link, image, image” without any descriptive labels, your site is a wall of meaningless noise.

• Does it read things in the right order? If the screen reader jumps around the page in a confusing sequence, the underlying page structure needs work.

• Can you complete the task? If you cannot find basic information with your eyes closed, imagine how frustrating that experience is for someone who relies on this tool every day.

Turn off the screen reader when you are done.

What to Do With Your Results

You probably found at least one or two issues. That is completely normal — most websites do. Here is how to prioritize:

Fix First (High Impact)

1. Keyboard traps — If users get stuck, they literally cannot use your site. This is the top priority.
2. Missing focus indicators — Without visible focus, keyboard users are navigating blind.
3. Missing alt text on important images — Especially product photos, informational graphics, and team portraits.

Fix Soon (Medium Impact)

4. Heading structure problems — Out-of-order or missing headings make navigation inefficient for screen reader users.
5. Zoom issues — Content that breaks at 200% zoom locks out users with low vision.

Fix When You Can (Lower Urgency)

6. Tab order quirks — Slightly off tab order is confusing but usually not a complete blocker.
7. Decorative images without empty alt text — Minor annoyance for screen reader users but not a crisis.

How to Fix These Issues If You Are Not a Developer

You do not need to write code to fix many of these problems.

• Alt text can be added through the media manager in WordPress, Shopify, Squarespace, and most other content management systems. Just click on the image and look for the “Alt text” field.

• Headings can be fixed in your content editor. Make sure you are selecting actual heading levels (Heading 1, Heading 2) rather than just making text bold or increasing the font size.

• Focus indicators and keyboard traps usually require a developer or a theme change. Write down the specific issue and share it with your web developer or agency. Being able to say “When I Tab to the main menu dropdown, I get stuck and cannot move past it” is much more actionable than “The site is not accessible.”

Make This a Habit

Run this five-minute check every time you publish a new page, launch a redesign, or update your theme. Accessibility is not a one-time project. It is an ongoing practice, just like updating your content or checking your analytics.

The more you do it, the faster it gets. After a few rounds, you will spot problems instinctively. And every issue you catch is one less barrier between your business and a customer who needs what you are selling.

What Comes Next

A five-minute audit is a strong starting point, but it only scratches the surface. Color contrast, form labels, video captions, and dozens of other factors matter too. The key is to start where you are and improve over time.

We’re building a simple accessibility checker for non-developers — no DevTools, no jargon. Join our waitlist to get early access.