Skip to content
https://123rf.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Warning::
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
BANNER (missing!) MAIN (missing!) CONTENTINFO footer

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
Alt Text Quality
Action
15 of 100 images have issues
FIX
15 of 100 images have issues
Critical::
15 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
11 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
4 decorative image(s) correctly marked
Info::
81 image(s) with good alt text
100 images 81 good alt text 4 decorative 15 missing
IssueCount
missing15 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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 ✗
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: 123RF Stock Photos
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name 123RF Stock Photos ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name 123RF Stock Photos Icons 1 icon(s)
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
title Stockfoto, Rechtenvrije Foto's en Stockb…
1.30:1
#000000
on
#212121
needs 4.5:1 (normal text)
16px · top of page (header area)
div Wij gebruiken cookies om je een betere e…
1.30:1
#000000
on
#212121
needs 4.5:1 (normal text)
16px · top of page (header area)
div Door onze website te gebruiken ga je ako…
1.30:1
#000000
on
#212121
needs 4.5:1 (normal text)
16px · top of page (header area)
a Cookiebeleid
1.30:1
#000000
on
#212121
needs 4.5:1 (normal text)
16px · top of page (header area)
button Accepteer
1.30:1
#000000
on
#212121
needs 4.5:1 (normal text)
16px · above the fold
span Prijzen
3.00:1
#000000
on
#595959
needs 4.5:1 (normal text)
16px · above the fold
span Alle Beelden
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
span Opties
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
div Zoeken op afbeelding
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
div Alle Beelden
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
div Stockfoto's
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
div Illustraties
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
div Video
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
div Audio
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
div Lettertypen
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
div FREE
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
div Zoeken op afbeelding
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Authentieke stockfot…19.47:13.0:1
#000000
#FFF6DC
Pass
h2 Vertrouwd door meer …19.47:13.0:1
#000000
#FFF6DC
Pass
h3 Creëer. Remix. Bezi…19.47:13.0:1
#000000
#FFF6DC
Pass
title Stockfoto, Rechtenvr…1.30:14.5:1
#000000
#212121
Fail
div Wij gebruiken cookie…1.30:14.5:1
#000000
#212121
Fail
div Door onze website te…1.30:14.5:1
#000000
#212121
Fail
a Cookiebeleid1.30:14.5:1
#000000
#212121
Fail
button Accepteer1.30:14.5:1
#000000
#212121
Fail
span Prijzen3.00:14.5:1
#000000
#595959
Fail
span Alle Beelden1.08:14.5:1
#000000
#0D0D0D
Fail
span Opties1.08:14.5:1
#000000
#0D0D0D
Fail
div Zoeken op afbeelding1.08:14.5:1
#000000
#0D0D0D
Fail
div Alle Beelden1.08:14.5:1
#000000
#0D0D0D
Fail
div Stockfoto's1.08:14.5:1
#000000
#0D0D0D
Fail
div Illustraties1.08:14.5:1
#000000
#0D0D0D
Fail
div Video1.08:14.5:1
#000000
#0D0D0D
Fail
div Audio1.08:14.5:1
#000000
#0D0D0D
Fail
div Lettertypen1.08:14.5:1
#000000
#0D0D0D
Fail
div FREE1.08:14.5:1
#000000
#0D0D0D
Fail
div Zoeken op afbeelding1.08:14.5:1
#000000
#0D0D0D
Fail

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+
Heading Hierarchy
6 headings
PASS
6 headings
Info::
Single H1 present
  • H1 Authentieke stockfoto's, vectoren en video's
  • H2 Vertrouwd door meer dan 3 miljoen creatieve professionals, 1,5 miljoen makers en marketeers wereldwijd.
  • H3 Creëer. Remix. Bezit.
  • H4 Onbeperkte stockfoto downloads
  • H4 Commercieel veilige stockfoto's
  • H4 Alles-in-één platform
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#mobile-search-bar-inputtextkeywordaria-label
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 28 passed
PASS
90

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Opties Zoeken op afbeelding Alle Beelden Stockfoto's Illustraties Video Audio L… form.SearchBarV2__form > div.SearchBarV2__searchFilterCategoryDropdown > div.SearchFilterCategoryDropdownV2__container > div.SearchFilterCategoryDropdownV2__list

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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 head > meta

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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[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
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●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 are distinguishable without relying on color.
●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
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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
○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
○Select elements have associated label elements.
○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
○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.
○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.

Send Feedback