Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

2 landmarks

FIX

2 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

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

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

Heading Hierarchy

5 headings, 1 skip(s)

REVIEW

5 headings, 1 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H2 → H4 (missing H3)

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

H1 Version 4.73
H1 IrfanView graphic viewer duplicate H1
H2 Get IrfanView (version 4.73)
H4 Useful Partner Sites skipped
H3 A Load of Features

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

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

Link & Button Quality

Action

2 issue(s) across 39 links and 0 buttons

REVIEW

2 issue(s) across 39 links and 0 buttons

2 link(s) with no accessible text

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

Got: main_what_is_engl.htm; main_what_is_ger.htm

10 link(s) open in new tab without warning

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

Got: forum.htm; https://dappcdn.com/download/graphic-apps/irfanview; https://dappcdn.com/download/graphic-apps/irfanview; https://dappcdn.com/download/graphic-apps/irfanview; https://dappcdn.com/download/graphic-apps/irfanview; https://www.stempelservice.de/; https://icons8.com/lunacy; https://www.ramotion.com/startup-branding/; https://domainunion.de/; https://playmain.com/

27 link(s) with descriptive text

39 links

2 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
main_what_is_engl.htm	(empty)	empty	Add link text or aria-label
main_what_is_ger.htm	(empty)	empty	Add link text or aria-label
forum.htm	Forum	new tab	Add '(opens in new tab)' to text
https://dappcdn.com/download/graphic-app…	DOWNLOAD …	new tab	Add '(opens in new tab)' to text
https://dappcdn.com/download/graphic-app…	PLUGINS	new tab	Add '(opens in new tab)' to text
https://dappcdn.com/download/graphic-app…	DOWNLOAD …	new tab	Add '(opens in new tab)' to text
https://dappcdn.com/download/graphic-app…	PLUGINS	new tab	Add '(opens in new tab)' to text
https://www.stempelservice.de/	www.stempelservice.de	new tab	Add '(opens in new tab)' to text
https://icons8.com/lunacy	icons8.com/lunacy	new tab	Add '(opens in new tab)' to text
https://www.ramotion.com/startup-brandin…	Ramotion	new tab	Add '(opens in new tab)' to text
https://domainunion.de/	domainunion	new tab	Add '(opens in new tab)' to text
https://playmain.com/	Playmain	new tab	Add '(opens in new tab)' to text

27 links and buttons have descriptive text

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

main_what_is_engl.htm; main_what_is_ger.htm

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.

forum.htm; https://dappcdn.com/download/graphic-apps/irfanview; https://dappcdn.com/download/graphic-apps/irfanview; https://dappcdn.com/download/graphic-apps/irfanview; https://dappcdn.com/download/graphic-apps/irfanview; https://www.stempelservice.de/; https://icons8.com/lunacy; https://www.ramotion.com/startup-branding/; https://domainunion.de/; https://playmain.com/

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

title IrfanView - Official Homepage - One of t…

1.61:1

#000000

#313131

needs 4.5:1 (normal text)

16px · top of page (header area)

label Menu

1.61:1

#000000

#313131

needs 4.5:1 (normal text)

16px · top of page (header area)

span Version 4.73

1.59:1

#000000

#303030

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.52:1

#000000

#2D2D2D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Send Us an Email

1.23:1

#000000

#1E1929

needs 4.5:1 (normal text)

16px · above the fold

a Other Mirrors

1.19:1

#000000

#1B1722

needs 4.5:1 (normal text)

16px · above the fold

option Select Mirror

1.23:1

#000000

#1D1B23

needs 4.5:1 (normal text)

16px · above the fold

option Germany 1

1.29:1

#000000

#211F28

needs 4.5:1 (normal text)

16px · above the fold

option Germany 2

1.28:1

#000000

#201E26

needs 4.5:1 (normal text)

16px · above the fold

option Germany 3

1.25:1

#000000

#201C24

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 IrfanView graphic vi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get IrfanView (	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A Load of Features	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title IrfanView - Official…	1.61:1	4.5:1	#000000	#313131	Fail
label Menu	1.61:1	4.5:1	#000000	#313131	Fail
span Version 4.73	1.59:1	4.5:1	#000000	#303030	Fail
a Home	1.52:1	4.5:1	#000000	#2D2D2D	Fail
a Send Us an Email	1.23:1	4.5:1	#000000	#1E1929	Fail
a Other Mirrors	1.19:1	4.5:1	#000000	#1B1722	Fail
option Select Mirror	1.23:1	4.5:1	#000000	#1D1B23	Fail
option Germany 1	1.29:1	4.5:1	#000000	#211F28	Fail
option Germany 2	1.28:1	4.5:1	#000000	#201E26	Fail
option Germany 3	1.25:1	4.5:1	#000000	#201C24	Fail
option Italy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Poland	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Portuguese	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Russia	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Download	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a IrfanView 32-bit	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 82/100 — 4 failing, 11 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
GET IRFANVIEW (VERSION 4.73) `div.l-box > div.download-img-desc > div#download-desc > h2`
VERSION 4.73 `div.download-img-desc > div#download-desc > h2 > strong`
32-BIT `div.l-box > div#download-options > div.download-option > p.download-style-box`
PLUGINS `div#download-options > div.download-option > div.btn-group > a.plugin-btn`
64-BIT `div.l-box > div#download-options > div.download-option > p.download-style-box`
PLUGINS `div#download-options > div.download-option > div.btn-group > a.plugin-btn`
OTHER DOWNLOAD SITES `div.container > div.download > div.l-box > a.register-support`
DONATE / SUPPORT / REGISTER IRFANVIEW `div.container > div.download > div.l-box > a.register-support`
USEFUL PARTNER SITES `div.container > div.partner-sites > div.l-box > h4`

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
domainunion `div.footer-content > div.container > div.footer-text > a`
Playmain `div.footer-content > div.container > div.playmain > a`

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
USEFUL PARTNER SITES `div.container > div.partner-sites > div.l-box > h4`

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

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

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

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 image(s) with good alt text

5 images 5 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <select>

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#nav-trigger	checkbox	Menu	for/id
select	select	(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

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