LESSON 0440 minutes · Last tested 10 September 2026

Test mobile layout, links, forms and accessibility

Run a practical launch check on the parts that commonly break outside the builder preview.

THE GOAL

What you will finish

Complete a repeatable launch check and record any issue that still needs work.

Free toolsChrome or FirefoxA real phone if availableLighthouseKeyboard only
WORK THROUGH IT

Step by step

  1. 01

    Start at 320 pixels

    Check every page at a narrow mobile width. Look for clipped text, horizontal scrolling, tiny controls and fixed elements covering content.

  2. 02

    Use only the keyboard

    Move through links, menus and forms with Tab, Shift+Tab, Enter and Space. Confirm the focus position is always visible.

  3. 03

    Test real form outcomes

    Submit valid, invalid and empty forms. Confirm errors are understandable and successful requests reach their destination.

  4. 04

    Check names and contrast

    Images need useful alternative text when they carry meaning. Form fields need labels. Text and controls must remain readable.

  5. 05

    Run a final link check

    Open internal links, external links, canonical URLs, the privacy notice and the contact path from the live domain.

COPYABLE PROMPT

Use this as a starting point

Create a launch test for this website. Cover 320-pixel mobile layout, keyboard navigation, visible focus, headings, labels, alternative text, colour contrast, reduced motion, broken links, form success and failure, privacy links, metadata and live-domain redirects. Return a table with test, expected result, actual result and status.

Replace the bracketed notes with your own facts. Read the answer before using it.

COMMON ERRORS

Watch for these

  • Testing only inside the AI builder
  • Checking one desktop browser
  • Calling a form complete without confirming delivery
  • Hiding focus outlines for visual reasons
FINAL CHECK

Before you continue

  • No horizontal scrolling at 320 pixels
  • All actions work with a keyboard
  • Forms show useful outcomes
  • Pages have one clear main heading
  • Reduced-motion preferences are respected
PRIMARY GUIDANCE

Read the source material