ShipGuardeRELEASE CLEARANCE BUREAU
How it worksUse casesDocsPricing
FREE CHECK · ACCESSIBILITY

Accessibility check, verified.

Paste a public page. It runs the axe-core WCAG 2 AA rules on the page as a browser renders it, then confirms each finding against the live DOM before showing it to you.

All six checks
RUN IT ON YOUR SITEFREE · NO ACCOUNT

Six read-only checks on one page: accessibility, performance, SEO, console and network errors, broken links, cookie handling. About a minute. Nothing is submitted, signed into, or changed.

WHAT IT LOOKS AT

The questions it asks of the page.

01Colour contrast of visible text against its real background, measured after the page has settled
02Buttons, links and form controls with no accessible name
03Images without alternative text, including logos and icons that carry meaning
04Heading order, landmarks, and ARIA attributes that contradict the element they sit on
05Focusable elements hidden from assistive technology, and hidden elements that still take focus
06The viewport tag: whether pinch-zoom has been switched off
WHAT IT FINDS MOST OFTEN

From real public pages. No company named.

FOUND
CAROUSEL ARROWS AND ICON-ONLY BUTTONS WITH NO NAME

A screen reader announces each one as "button" and nothing else, so the control cannot be used. Add an aria-label that says what the button does, or visually hidden text inside it.

FOUND
PINCH-ZOOM DISABLED ON THE PRICING PAGE

A viewport tag with user-scalable=no or maximum-scale=1 stops low-vision visitors enlarging the table. Remove user-scalable and maximum-scale from the viewport meta tag. One line.

FOUND
MUTED TEXT UNDER 4.5:1 CONTRAST

A single CSS class with opacity .55 dropped 46 elements on one page under the AA minimum at once. Darken the colour token instead of lowering opacity. Fix the token and every use follows.

WHAT IT CANNOT SEE

The honest limit.

This is a page check. It sees one page in one state. It does not test whether a keyboard user can complete a sign-up or a checkout; that is a journey, and the pilot runs journeys.

Run the journey too: the pilotCheck a page now
INQUIRIES

Questions about the accessibility check.

Which standard does it check against?
WCAG 2 level AA, using the axe-core rule set, run on the rendered page in a real browser rather than on the HTML source.
Why do you verify findings? Do scanners get it wrong?
Yes, often. A page that fades sections in as you scroll reports every heading below the fold as low contrast if it is measured mid-animation. The check settles the page first and confirms each finding against the live DOM, and it drops the ones it cannot confirm.
Does it test pages behind a login?
Not here. The free check only reads public pages and never signs in, submits a form, or changes anything. Authenticated pages are tested in the pilot, with credentials you provide.
THE OTHER FIVE

Every run does all six.

01Broken links
02SEO basics
03Performance
04Console & network errors
05Cookies & consent

Code review checks the diff. ShipGuarde also checks the running product, so a release does not ship on the hope that nothing broke.

Join the free 30-day pilotStart a 7-day trial

NO CREDIT CARD · CONNECT GITHUB IN UNDER FIVE MINUTES · CANCEL ANY TIME

ShipGuarde

RELEASE CLEARANCE BUREAU
ISSUING AUTHORITY FOR SOFTWARE RELEASES
[email protected]

PRODUCT

  • Features
  • PR Reviews
  • Visual QA
  • Compare
  • Integrations
  • Pricing

RESOURCES

  • Free website check
  • Docs
  • How it works
  • Use cases
  • Sample report
  • Founding pilot
  • Blog
  • Changelog
  • FAQ
  • Support

COMPANY

  • About
  • Security
  • Status
  • Contact us
  • Privacy
  • Terms
  • Refunds
  • Sub-processors
FILED · SG-482 · ACME-COMMERCEEST. 2026