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 3 REVIEW 5 FIX

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

No <nav> landmark found

No banner (header) 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-vfavm2

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://instagram.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://instagram.com/manifest.json

Manifest contains invalid JSON.

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 ✗

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Link & Button Quality

1 issue(s) across 16 links and 1 buttons

REVIEW

1 issue(s) across 16 links and 1 buttons

9 link(s) open in new tab without warning

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

Got: https://about.meta.com/; https://about.instagram.com/; https://about.instagram.com/blog/; https://about.instagram.com/about-us/careers; https://help.instagram.com/; https://developers.facebook.com/docs/instagram; https://www.meta.ai/?utm_source=foa_web_footer; https://www.threads.com/; https://www.facebook.com/help/instagram/261704639352628

1 button(s) with no accessible text

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

Got: input[type="submit"] (#286 on page)

7 link(s) with descriptive text

16 links

0 empty

0 generic text

9 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://about.meta.com/	Meta	new tab	Add '(opens in new tab)' to text
https://about.instagram.com/	About	new tab	Add '(opens in new tab)' to text
https://about.instagram.com/blog/	Blog	new tab	Add '(opens in new tab)' to text
https://about.instagram.com/about-us/car…	Jobs	new tab	Add '(opens in new tab)' to text
https://help.instagram.com/	Help	new tab	Add '(opens in new tab)' to text
https://developers.facebook.com/docs/ins…	API	new tab	Add '(opens in new tab)' to text
https://www.meta.ai/?utm_source=foa_web_…	Meta AI	new tab	Add '(opens in new tab)' to text
https://www.threads.com/	Threads	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/help/instagram/…	Contact Uploading & Non-Users	new tab	Add '(opens in new tab)' to text
<input>	(empty)	empty	Add button text or aria-label

7 links and buttons have descriptive text

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

https://about.meta.com/; https://about.instagram.com/; https://about.instagram.com/blog/; https://about.instagram.com/about-us/careers; https://help.instagram.com/; https://developers.facebook.com/docs/instagram; https://www.meta.ai/?utm_source=foa_web_footer; https://www.threads.com/; https://www.facebook.com/help/instagram/261704639352628

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.

input[type="submit"] (#286 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

Favicon & Branding

8 icon(s) detected

REVIEW

8 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 Missing

✓ Multiple Sizes Present

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#_r_4_	text	Mobile number, username or email	for/id
#_r_7_	password	Password	for/id
select	select	Switch Display Language	aria-label
input	submit	(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

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

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

Dark Mode✓ Dark Mode Supported

color-scheme meta light ✓Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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
title Instagram	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Log into Instagram	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Mobile number, usern…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Password	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Log in	18.91:1	4.5:1	#000000	#F2F3F5	Pass
span Forgot password?	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Log in with Facebook	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Create new account	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Meta	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span About	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Blog	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Jobs	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Help	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span API	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Privacy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Terms	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Locations	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Instagram Lite	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Meta AI	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Threads	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.

Lighthouse Accessibility Audits

Score 94/100 — 1 failing, 21 passed

PASS

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta#viewport `head > meta#viewport`

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Select elements have associated label elements.

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links have a discernible name

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○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

○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

○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

○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

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

○`<object>` elements have alternate text

○Skip links are focusable.

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