Alt text & accessibility

Catch accessibility issues before launch day.

Frank checks every page for missing alt text and the accessibility basics that slip through on a deadline: heading order, form labels, unnamed buttons, tap targets and more.

Get startedSee pricing
  • Set up in 30 seconds
  • Unlimited scans
  • No code required

Updated

Why it matters

The basics are easy to miss.

  1. 01

    They're invisible

    A missing alt attribute or a skipped heading level looks exactly the same to a sighted reviewer.

  2. 02

    They're everywhere

    Every image, form field and button on every page is another chance for something to slip.

  3. 03

    People rely on them

    Screen reader and keyboard users depend on alt text, labels and a sensible heading order to use the site.

Alt text

Images without a description.

  1. 01How it's judged

    Missing and empty alt text

    A missing alt attribute is a major issue. An empty alt is a minor one, unless the image sits inside a link or button, where it leaves the link without a name. Decorative images are skipped.

    • Missing alt: major
    • Empty alt: minor
    • Hidden, tiny and presentation images skipped
    How scoring works

Accessibility

Plus the checks that slip on a deadline.

A separate accessibility check runs on every page alongside alt text.

  1. 01

    Page language

    Pages missing a language, which screen readers use to pronounce the content.

  2. 02

    Heading order

    Skipped heading levels, like an h2 straight to an h4, and pages with more than one h1.

  3. 03

    Form labels

    Form fields without a label, including fields that rely on placeholder text alone.

  4. 04

    Unnamed buttons and links

    Buttons and links with no readable name, such as icon-only buttons.

  5. 05

    Skip link

    Pages without a “skip to content” link for keyboard users.

  6. 06

    Autoplay and tap targets

    Audio or video that autoplays with sound, and tap targets smaller than 24×24px.

Frequently asked questions about accessibility checks

  • No. Frank flags alt text that's missing or empty. It doesn't judge poor alt text, such as “image” or a filename. If you find some while reviewing, pin a marker on the image for whoever writes the content.

  • No automated tool can confirm that on its own. Frank catches common issues quickly on every page, but it's still worth testing with a keyboard and a screen reader before launch.

  • Decorative images: hidden ones, tiny ones, and images marked as presentation or aria-hidden.

  • Missing page language, skipped heading levels, more than one h1, form fields without labels, buttons and links with no readable name, a missing skip link, media that autoplays with sound, tap targets under 24×24px, and tab order overridden with a positive tabindex.

Explore Frank

See what else Frank does for you.

  1. 01

    Broken link checking

    Frank tests every internal and external link on every page, follows redirects, and flags 404s, server errors and dead development links.

    Feature
  2. 02

    Figma design QA

    Map your Figma pages to your live site once, then review every page side by side with its approved design.

    Feature
  3. 03

    For Framer

    Automated QA for Framer sites: check every page and CMS page on your staging or preview URL before you publish to your domain.

    Solution
  4. 04

    For Webflow

    Automated QA for Webflow sites: check every page and CMS template on your webflow.io staging site before you connect the domain.

    Solution
  5. 05

    For WordPress

    Automated QA for WordPress sites: check every page on your staging site for lorem ipsum, broken links and accessibility before launch.

    Solution
  6. 06

    For agencies

    Consistent, automated QA across every project and every team member, with a scored record of every scan.

    Solution
  7. 07

    For freelancers

    A second pair of eyes for solo designers and developers: automated checks on every page, so you can hand over with confidence.

    Solution
  8. 08

    Frank vs BugHerd

    BugHerd collects visual feedback from clients and teams. Frank runs automated QA checks on every page. Here's how they compare.

    Comparison
  9. 09

    Frank vs Pixelay

    Pixelay overlays a Figma design on a live page inside Figma. Frank reviews every page against its design and runs automated QA checks too.

    Comparison
  10. 10

    Frank vs Sitepager

    Sitepager tracks what changes on a site between updates. Frank checks a build before launch and lines it up with the Figma design. Here's how they compare.

    Comparison
  11. 11

    Frank vs manual QA

    Manual QA is slow, inconsistent and easy to skip. Frank automates the repetitive half, so your team keeps the judgement calls.

    Comparison
  12. 12

    Lorem ipsum checker

    Frank checks every block of visible text on every page for Latin filler, in any word order, and flags it before your client sees it.

    Feature
  13. 13

    QA reports & scores

    Every page gets a score out of 100 and a red, amber or green status, with issues highlighted on a screenshot, every scan kept, and reports you can share with clients by link.

    Feature
  14. 14

    Team markers

    Pin issues straight onto a scanned page, comment, @mention a teammate and filter by priority, so nothing gets lost between review and fix.

    Feature

More on pre-launch QA

All articles

Ship sites everyone can use.

Run your first scan in minutes. Every plan includes unlimited projects and unlimited scans.

Get startedSee pricing
  • Set up in 30 seconds
  • Unlimited scans
  • No code required