Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 REVIEW 9 FIX

Landmark Structure

Action

No landmarks

FIX

No 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

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Alt Text Quality

Action

11 of 31 images have issues

FIX

11 of 31 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

7 image(s) with generic alt text

9 decorative image(s) correctly marked

11 image(s) with good alt text

31 images 11 good alt text 9 decorative 7 generic 4 missing

Issue	Count
missing	4 image(s)
generic	7 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

Link & Button Quality

Action

5 issue(s) across 181 links and 2 buttons

FIX

5 issue(s) across 181 links and 2 buttons

4 link(s) with no accessible text

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

Got: a (#124 on page); javascript:speak_nopop(1549196,'rec'); javascript:speak_nopop(1558673,'rec'); https://enuk.dict.cc/

1 link(s) with generic text

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

Got: /latest-verifications.php ("More")

4 link(s) open in new tab without warning

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

Got: http://GreatFallsStatistics.com; https://gigperformer.com/; https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1528874672298&uri=CELEX%3…; https://www.dict.cc/?s=about%3A#impressum

172 link(s) with descriptive text

181 links

4 empty

1 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
//browse.dict.cc/	All Languages	img no alt	Add alt attribute to the image
	(empty)	empty	Add link text or aria-label
javascript:speak_nopop(1549196,'rec')	(empty)	empty	Add link text or aria-label
javascript:speak_nopop(1558673,'rec')	(empty)	empty	Add link text or aria-label
/latest-verifications.php	More	generic text	Replace with descriptive text
Before: More Suggested: Latest Verifications.Php
http://GreatFallsStatistics.com	GreatFallsStatistics...	new tab	Add '(opens in new tab)' to text
https://gigperformer.com/	gigperformer.com	new tab	Add '(opens in new tab)' to text
javascript:toggle_text('explanation')	What's this?	img no alt	Add alt attribute to the image
https://deuk.dict.cc/	Ukrainisch-Deutsch	img no alt	Add alt attribute to the image
https://enuk.dict.cc/	(empty)	empty	Add link text or aria-label
https://enuk.dict.cc/	Ukrainian-English	img no alt	Add alt attribute to the image
https://eur-lex.europa.eu/legal-content/…	EU law	new tab	Add '(opens in new tab)' to text
https://www.dict.cc/?s=about%3A#impressu…	privacy policy page	new tab	Add '(opens in new tab)' to text

174 links and buttons have descriptive text

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

a (#124 on page); javascript:speak_nopop(1549196,'rec'); javascript:speak_nopop(1558673,'rec'); https://enuk.dict.cc/

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.

/latest-verifications.php ("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.

http://GreatFallsStatistics.com; https://gigperformer.com/; https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1528874672298&uri=CELEX%3…; https://www.dict.cc/?s=about%3A#impressum

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

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

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.

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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://dict.cc/site.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://dict.cc/site.webmanifest

Manifest contains invalid JSON.

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 ✗

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Back-to-top link detected

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

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Heading Hierarchy

4 headings, 1 skip(s)

REVIEW

4 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: H1 → H3 (missing H2)

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

H1 English-German Dictionary
H2 dict.cc: English-German and Multilingual Dictionary
H1 We care about your privacy! duplicate H1
H3 Learn more why you are seeing this skipped

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

Form Accessibility

Action

4 of 4 controls have issues

REVIEW

4 of 4 controls have issues

4 control(s) without accessible label

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

Got: <input type="text" name="s" id="sinp">; <input type="submit">; <input type="button">; <select id="lpddbsf">

4 controls

0 labeled

0 placeholder only

4 unlabeled

Control	Type	Label	Method
#sinp	text	(none)	none
input	submit	(none)	none
input	button	(none)	none
#lpddbsf	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

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 1 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 English-German Dicti…	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h1 We care about your p…	7.96:1	3.0:1	#000000	#9AA0A7	Pass
h2 dict.cc: English-Ger…	7.96:1	3.0:1	#000000	#9AA0A7	Pass
h2 and	7.96:1	3.0:1	#000000	#9AA0A7	Pass
h2 Dictionary	7.96:1	3.0:1	#000000	#9AA0A7	Pass
h3 Learn more why you a…	7.96:1	3.0:1	#000000	#9AA0A7	Pass
title dict.cc \| German-Eng…	8.03:1	4.5:1	#000000	#A0A0A0	Pass
a All Languages	9.90:1	4.5:1	#000000	#B2B2B2	Pass
a dict.cc	9.90:1	4.5:1	#000000	#B2B2B2	Pass
div Online Dictionary En…	5.70:1	4.5:1	#666666	#FFFEFE	Pass
a äöüß...	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option DE <> EN	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option DE –> EN	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option EN –> DE	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option -----	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option DE <> EN	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option -----	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option DE <> BG	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option DE <> BS	20.86:1	4.5:1	#000000	#FFFEFE	Pass
option DE <> CS	20.86:1	4.5:1	#000000	#FFFEFE	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 83/100 — 3 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
dict.cc `div#h1-logo-and-search > div#h1-searchtools > div#h1-mobile-header-top > div#h1-mobile-logo`
DE/EN `div#h1-searchtools > div#h1-mobile-header-top > div#h1-mobile-choose-lang > div#h1-mobile-langmenubut`
Suche starten `div#maincontent > div#home_text > div > div`
BG `div#home_text > div > div > a.button1`
BS `div#home_text > div > div > a.button1`
CS `div#home_text > div > div > a.button1`
DA `div#home_text > div > div > a.button1`
EL `div#home_text > div > div > a.button1`
EN `div#home_text > div > div > a.button1`
EO `div#home_text > div > div > a.button1`
ES `div#home_text > div > div > a.button1`
FI `div#home_text > div > div > a.button1`
FR `div#home_text > div > div > a.button1`
HR `div#home_text > div > div > a.button1`
HU `div#home_text > div > div > a.button1`
IS `div#home_text > div > div > a.button1`
IT `div#home_text > div > div > a.button1`
LA `div#home_text > div > div > a.button1`
NL `div#home_text > div > div > a.button1`
NO `div#home_text > div > div > a.button1`
PL `div#home_text > div > div > a.button1`
PT `div#home_text > div > div > a.button1`
RO `div#home_text > div > div > a.button1`
RU `div#home_text > div > div > a.button1`
SK `div#home_text > div > div > a.button1`
SQ `div#home_text > div > div > a.button1`
SR `div#home_text > div > div > a.button1`
SV `div#home_text > div > div > a.button1`
TR `div#home_text > div > div > a.button1`
UK `div#home_text > div > div > a.button1`
Alle `div#home_text > div > div > a.button1`

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
Learn more why you are seeing this `div.sn-inner > div.sn-content > div.sn-tabs > h3`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

○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

●Links are distinguishable without relying on color.

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

●Document has a main landmark.

○`[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 a valid value for its `[lang]` attribute

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

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