Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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

Detection limited to meta tags and inline styles.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

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

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Form Accessibility

Action

3 of 7 controls have issues

REVIEW

3 of 7 controls have issues

3 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="radio" name="widget-preview[view]" id="widget-preview[view][desktop]">; <input type="radio" name="widget-preview[view]" id="widget-preview[view][tablet]">; <input type="radio" name="widget-preview[view]" id="widget-preview[view][mobile]">

4 control(s) properly labeled

7 controls

4 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
#widgetCreatorSettings[help]	checkbox	Show help	for/id
#widgetCreatorSettings[accordion]	checkbox	Solo mode	for/id
#widgetCreatorSettings[dark]	checkbox	Dark mode	for/id
#widgetCreatorSettings[responsivePreview]	checkbox	Responsive preview	for/id
#widget-preview[view][tablet]	radio	(none)	none
#widget-preview[view][mobile]	radio	(none)	none
#widget-preview[view][desktop]	radio	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

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

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Heading Hierarchy

32 headings

PASS

32 headings

Multiple H1 headings (6 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Looking for the Instagram widget like this one?
H2 You are in the right place!
H1 Features duplicate H1
H2 Responsive
H2 Tiny
H2 Fast
H2 Official Instagram API
H2 Links directly to Instagram
H2 Ads free
H2 Multiple Instagram accounts
H2 Hashtag filtering
H2 3 different type of widgets
H2 A lot of customizable options
H2 Custom CSS
H2 99% of supported websites
H2 Copy and paste installation
H2 Tutorials
H2 Support
H1 Some of our users duplicate H1
H2 Sofia Larios
H2 Herstory
H2 BabymeeModaBebe ®
H2 OCHALLENGER
H2 Centauro Esporte
H2 Wepink
H1 Widgets in numbers duplicate H1
H1 How to add LightWidget to your website? duplicate H1
H2 WordPress
H2 Shopify
H2 Drupal
H2 More integrations
H1 About LightWidget duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 27 images OK

PASS

All 27 images OK

15 decorative image(s) correctly marked

12 image(s) with good alt text

27 images 12 good alt text 15 decorative

All images have appropriate alt text.

A+

Link & Button Quality

32 links, 3 buttons — all OK

PASS

32 links, 3 buttons — all OK

32 link(s) with descriptive text

32 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

35 links and buttons have descriptive text

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 Looking for the	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h1 like this one?	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h1 Features	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h1 Some of our users	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h1 Widgets in numbers	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h1 How to add LightWidg…	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h1 About LightWidget	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 You are in the right…	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Responsive	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Tiny	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Fast	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Official Instagram A…	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Links directly to In…	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Ads free	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Multiple Instagram a…	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Hashtag filtering	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 3 different type of …	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 A lot of customizabl…	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 Custom CSS	18.77:1	3.0:1	#000000	#F2F2F3	Pass
h2 99% of supported web…	18.77:1	3.0:1	#000000	#F2F2F3	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 21 passed

PASS

100

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.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

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

●Links have a discernible name

●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.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[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 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

○`<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

○Links are distinguishable without relying on color.

○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.

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