Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://gyazo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

48

GRADE

F

FIX

6

REVIEW

5

PASS

2

INFO

0

Checks

13

2 PASS 5 REVIEW 6 FIX

D

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F

Heading Hierarchy

Action

39 headings, 6 skip(s)

FIX

39 headings, 6 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 The fastest wayto use your moments
H2 Loved worldwide
H2 Save Instantly, Stay in Flow
H5 Capture both videos and still images skipped
H5 Quick capture with shortcuts
H5 Upload as you capture
H5 Frame Capture
H2 Collect what you see, instantly
H5 Collections skipped
H5 Group Collections
H5 Save with Right-Click
H5 Drag & Drop File Upload
H2 Find what you need, instantly
H5 Search captures with OCR skipped
H5 Find by Metadata
H5 Organize and search with tags
H5 Add notes to captures
H2 Share what you see, instantly
H5 Auto preview in chat and SNS skipped
H5 Image editing tools
H5 Video editing tools
H5 Share from webcam
H5 Access from the menu window
H2 Save AnywhereFind Anywhere
H2 Keep your datasafe and secure
H2 Used by 20 million people around the world
H5 Neil White skipped
H5 Keigo Ando
H5 Kakeru Someya
H2 Ugrade to Gyazo Pro
H5 Record up to 10 minutes of video skipped
H5 Create unlimited collections
H5 Access all your captures
H5 AI-powered text extraction
H2 Let’s start for free
H2 Product
H2 Downloads
H2 Resources
H2 Related Services

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

F

Alt Text Quality

Action

46 of 46 images have issues

FIX

46 of 46 images have issues

46 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 image-in-link without alt text

An image inside a link with no alt creates an empty link.

46 images 46 missing

Issue	Count
missing	46 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

C

Link & Button Quality

Action

3 issue(s) across 49 links and 2 buttons

REVIEW

3 issue(s) across 49 links and 2 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://gyazo.com/; https://corp.helpfeel.com

14 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://updates.gyazo.com; https://help.gyazo.com/; https://help.gyazo.com/contact-us; https://x.com/gyazo; https://www.facebook.com/gyazo/; https://updates.gyazo.com; https://twitter.com/gyazo; https://www.facebook.com/gyazo; https://www.helpfeel.com/; https://cosen.se/product (+4 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.navbar-toggle (#69 on page)

33 link(s) with descriptive text

49 links

2 empty

0 generic text

14 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://gyazo.com/	(empty)	empty	Add link text or aria-label
https://updates.gyazo.com	Product Updates	new tab	Add '(opens in new tab)' to text
https://help.gyazo.com/	Help Center	new tab	Add '(opens in new tab)' to text
https://help.gyazo.com/contact-us	Support Contact	new tab	Add '(opens in new tab)' to text
https://x.com/gyazo	X (Twitter)	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/gyazo/	Facebook	new tab	Add '(opens in new tab)' to text
#memo	NoteCapture what you see insta…	img no alt	Add alt attribute to the image
#collect	CollectSave what inspires you …	img no alt	Add alt attribute to the image
#find	FindFind what you need instant…	img no alt	Add alt attribute to the image
#share	ShareShare what you see instan…	img no alt	Add alt attribute to the image
https://corp.helpfeel.com	(empty)	empty	Add link text or aria-label
https://updates.gyazo.com	Product Updates	new tab	Add '(opens in new tab)' to text
https://twitter.com/gyazo	X (Twitter)	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/gyazo	Facebook	new tab	Add '(opens in new tab)' to text
https://www.helpfeel.com/	Helpfeel: Self-Service AI Syst…	new tab	Add '(opens in new tab)' to text
https://cosen.se/product	Cosense: AI Knowledge Base	new tab	Add '(opens in new tab)' to text
https://corp.helpfeel.com	Helpfeel Inc.	new tab	Add '(opens in new tab)' to text
https://gyazo.com/doc/terms	Terms	new tab	Add '(opens in new tab)' to text
https://corp.helpfeel.com/en/privacy	Privacy	new tab	Add '(opens in new tab)' to text
https://gyazo.com/doc/jp_commercial_act	SCT Act in Japan	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

34 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://gyazo.com/; https://corp.helpfeel.com

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://updates.gyazo.com; https://help.gyazo.com/; https://help.gyazo.com/contact-us; https://x.com/gyazo; https://www.facebook.com/gyazo/; https://updates.gyazo.com; https://twitter.com/gyazo; https://www.facebook.com/gyazo; https://www.helpfeel.com/; https://cosen.se/product (+4 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.navbar-toggle (#69 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Gyazo - Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

C

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✗ Multiple Sizes Missing

C

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: Gyazo

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name Gyazo ✓192×192 icon ✗512×512 icon ✗Start URL /captures ✓Display Mode standalone ✓

Name Gyazo Display Mode standalone Icons 1 icon(s)

C

Lighthouse Accessibility Audits

Action

Score 74/100 — 6 failing, 14 passed

REVIEW

74

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.navbar > div.container > div.navbar-header > button.navbar-toggle `nav.navbar > div.container > div.navbar-header > button.navbar-toggle`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hero-grid-wrapper > div.hero-grid > a.hero-item > img.hero-item-bg `div.hero-grid-wrapper > div.hero-grid > a.hero-item > img.hero-item-bg`
div.hero-grid-wrapper > div.hero-grid > a.hero-item > img.hero-item-bg `div.hero-grid-wrapper > div.hero-grid > a.hero-item > img.hero-item-bg`
div.hero-grid-wrapper > div.hero-grid > a.hero-item > img.hero-item-bg `div.hero-grid-wrapper > div.hero-grid > a.hero-item > img.hero-item-bg`
div.hero-grid-wrapper > div.hero-grid > a.hero-item > img.hero-item-bg `div.hero-grid-wrapper > div.hero-grid > a.hero-item > img.hero-item-bg`
body.product > div.content > section.users > img.users-map `body.product > div.content > section.users > img.users-map`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img `div.col-lg-10 > div.benefit-features-grid > div.benefit-feature > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img `div.benefit-usecases-grid > div.benefit-usecase > div.benefit-usecase-icon > img`
section.platforms > div.platforms-bg > div.platforms-bg-rect > img `section.platforms > div.platforms-bg > div.platforms-bg-rect > img`
div.security-grid > div.security-item > div.security-item-icon > img `div.security-grid > div.security-item > div.security-item-icon > img`
div.security-grid > div.security-item > div.security-item-icon > img `div.security-grid > div.security-item > div.security-item-icon > img`
div.security-grid > div.security-item > div.security-item-icon > img `div.security-grid > div.security-item > div.security-item-icon > img`
div.security-grid > div.security-item > div.security-item-icon > img `div.security-grid > div.security-item > div.security-item-icon > img`
div.container > div.testimonials-grid > div.testimonials-card > img.testimonials-profile-image `div.container > div.testimonials-grid > div.testimonials-card > img.testimonials-profile-image`
div.container > div.testimonials-grid > div.testimonials-card > img.testimonials-profile-image `div.container > div.testimonials-grid > div.testimonials-card > img.testimonials-profile-image`
div.container > div.testimonials-grid > div.testimonials-card > img.testimonials-profile-image `div.container > div.testimonials-grid > div.testimonials-card > img.testimonials-profile-image`
body.product > div.content > section.cta-bottom > img.cta-bottom-bg `body.product > div.content > section.cta-bottom > img.cta-bottom-bg`
div.row > div.col-lg-4 > a > img `div.row > div.col-lg-4 > a > img`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.navbar-header > div.navbar-brand > a `div.container > div.navbar-header > div.navbar-brand > a`
div.container > div.row > div.col-lg-4 > a `div.container > div.row > div.col-lg-4 > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get Gyazo for free `section.hero > div.container > div.text-center > a#hero-download`
Uploads `div.container > div.users-items > div.users-item > div.users-item-desc`
View pricing and plans `div.content > section.upgrade > div.container > a.btn`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Capture both videos and still images `div.benefit-features-grid > div.benefit-feature > div.benefit-feature-text > h5.benefit-feature-title`
Collections `div.benefit-features-grid > div.benefit-feature > div.benefit-feature-text > h5.benefit-feature-title`
Search captures with OCR `div.benefit-features-grid > div.benefit-feature > div.benefit-feature-text > h5.benefit-feature-title`
Auto preview in chat and SNS `div.benefit-features-grid > div.benefit-feature > div.benefit-feature-text > h5.benefit-feature-title`
Neil White `div.testimonials-grid > div.testimonials-card > div.testimonials-profile > h5.testimonials-profile-name`
Record up to 10 minutes of video `div.col-lg-10 > div.upgrade-grid > div.upgrade-item > h5.upgrade-item-title`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The fastest way	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 to use your moments	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Loved worldwide	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Save Instantly, Stay…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Collect what you see…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Find what you need, …	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Share what you see, …	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Save	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Find	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Keep your data	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 safe and secure	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Used by 20 million p…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Ugrade to Gyazo Pro	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Let’s start for fr…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Product	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Downloads	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Resources	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Related Services	20.12:1	3.0:1	#000000	#FAFAFA	Pass
title Gyazo · Screen Reco…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Download	21.00:1	4.5:1	#000000	#FFFFFF	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback