Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 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 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

Form Accessibility

Action

11 of 19 controls have issues

FIX

11 of 19 controls have issues

9 control(s) without accessible label

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

Got: <input type="file" id="anywhere-upload-input">; <input type="file" id="anywhere-upload-input-camera">; <textarea name="viewer-links" id="uploaded-embed-code-0">; <textarea name="html-embed-medium" id="uploaded-embed-code-1">; <textarea name="html-embed-thumbnail" id="uploaded-embed-code-2">; <textarea name="bbcode-embed-medium" id="uploaded-embed-code-3">; <textarea name="bbcode-embed-thumbnail" id="uploaded-embed-code-4">; <input type="number" name="form-height" id="form-height">; <input type="text" name="form-album-password">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <textarea name="urls">; <input type="text" name="form-album-name">

8 control(s) properly labeled

19 controls

8 labeled

2 placeholder only

9 unlabeled

Control	Type	Label	Method
#upload-expiration	text	Automatically delete image	for/id
#uploaded-embed-toggle	select	Embed codes	for/id
#form-title	text	Title optional	for/id
#form-width	number	Resize image	for/id
#form-description	textarea	Description optional	for/id
#form-album-description	textarea	Album description optional	for/id
#form-privacy	select	Album privacy	for/id
#modal-share-url	text	Link	for/id
form-album-name	text	(Album name)	placeholder only
urls	textarea	(Add the image URLs here)	placeholder only
#anywhere-upload-input-camera	file	(none)	none
#form-height	number	(none)	none
#uploaded-embed-code-0	textarea	(none)	none
#uploaded-embed-code-1	textarea	(none)	none
#uploaded-embed-code-2	textarea	(none)	none
#uploaded-embed-code-3	textarea	(none)	none
#uploaded-embed-code-4	textarea	(none)	none
form-album-password	text	(none)	none
#anywhere-upload-input	file	(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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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.

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 ✗

Link & Button Quality

2 issue(s) across 123 links and 8 buttons

REVIEW

2 issue(s) across 123 links and 8 buttons

1 link(s) with no accessible text

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

Got: #file

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: ("learn more")

5 link(s) open in new tab without warning

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

Got: https://api.imgbb.com/; https://api.imgbb.com/; https://api.imgbb.com/; https://imgbb.com/tos; https://imgbb.com/privacy

116 link(s) with descriptive text

123 links

1 empty

1 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	learn more	generic text	Replace with descriptive text
Before: learn more Suggested: Home page
#file	(empty)	empty	Add link text or aria-label
https://api.imgbb.com/	API Access	new tab	Add '(opens in new tab)' to text
https://api.imgbb.com/	API Access	new tab	Add '(opens in new tab)' to text
https://api.imgbb.com/	API Access	new tab	Add '(opens in new tab)' to text
https://imgbb.com/tos	Terms of Service	new tab	Add '(opens in new tab)' to text
https://imgbb.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text

124 links and buttons have descriptive text

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

#file

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

Generic link text like 'click here' doesn't describe the destination.

("learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://api.imgbb.com/; https://api.imgbb.com/; https://api.imgbb.com/; https://imgbb.com/tos; https://imgbb.com/privacy

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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title That page doesn't exist (404) — ImgBB ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Action

Score 76/100 — 4 failing, 10 passed

REVIEW

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.

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
START UPLOADING `div#home-cover > div#home-cover-content > div.home-buttons > a.btn`
UPGRADE `div#home-cover-content > div#pricing-tier > div.pricing-tier-box > a.btn`
API Access `div.pricing-tier-box > ul.sentence-wrap > li > a`
69% OFF `div#pricing-tier > div.pricing-tier-box > div.pricing-ribbon > div`
UPGRADE `div#home-cover-content > div#pricing-tier > div.pricing-tier-box > a.btn`
API Access `div.pricing-tier-box > ul.sentence-wrap > li > a`
38% OFF `div#pricing-tier > div.pricing-tier-box > div.pricing-ribbon > div`
API Access `div.pricing-tier-box > ul.sentence-wrap > li > a`
Plugin API Contact Use of ImgBB constitutes acceptance of our Terms of Servi… `body#index > div.footer`
Plugin `div.footer > ul > li.with-icon > a`
API `div.footer > ul > li.with-icon > a`
Contact `div.footer > ul > li.with-icon > a`
Terms of Service `body#index > div.footer > a`
Privacy Policy `body#index > div.footer > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms of Service `body#index > div.footer > a`
Privacy Policy `body#index > div.footer > a`

These are opportunities to improve the legibility of your content.

Names and labels

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.content-width > ul.top-bar-right > li#top-bar-signin > a.top-btn-text `div.content-width > ul.top-bar-right > li#top-bar-signin > a.top-btn-text`

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.

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.device-mobile `html.device-mobile`

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-hidden="true"]` is not present on the document `<body>`

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

●Document has a `<title>` element

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

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

●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

○`[accesskey]` values are unique

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

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

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

○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

○Elements use only permitted ARIA attributes

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

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

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

○Buttons have an accessible name

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

Heading Hierarchy

5 headings

PASS

5 headings

Multiple H1 headings (2 found)

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

H1 Upload and share your images.
H1 ImgBB Pro account duplicate H1
H2 3 Year Pro
H2 Annual Plan
H2 Monthly Plan

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 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt 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 Upload and share you…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 ImgBB Pro account	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 3 Year Pro	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Annual Plan	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Monthly Plan	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title ImgBB — Upload Ima…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span About	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Plugin	20.82:1	4.5:1	#000000	#FEFEFE	Pass
a API	20.82:1	4.5:1	#000000	#FEFEFE	Pass
a Terms of Service	20.82:1	4.5:1	#000000	#FEFEFE	Pass
a Privacy	20.82:1	4.5:1	#000000	#FEFEFE	Pass
a Contact	20.82:1	4.5:1	#000000	#FEFEFE	Pass
a Afrikaans	20.12:1	4.5:1	#000000	#FAFAFA	Pass
a Azərbaycan	19.09:1	4.5:1	#000000	#F4F4F4	Pass
a Bosanski	19.09:1	4.5:1	#000000	#F4F4F4	Pass
a Català	19.09:1	4.5:1	#000000	#F4F4F4	Pass
a Cymraeg	19.09:1	4.5:1	#000000	#F4F4F4	Pass
a Dansk	19.09:1	4.5:1	#000000	#F4F4F4	Pass
a Deutsch	19.09:1	4.5:1	#000000	#F4F4F4	Pass
a Eesti	19.09:1	4.5:1	#000000	#F4F4F4	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.