Skip to content
https://evergabe.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
4
PASS
15
INFO
0
Checks
24
15 PASS 4 REVIEW 5 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="language">; <input type="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">
3 controls
0 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
qtext(Search)placeholder only
languageselect(none)none
inputsubmit(none)none

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

<select name="language">; <input type="submit">

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.

<input type="text" name="q">

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
title evergabe.com
1.95:1
#000000
on
#34403E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Start
1.88:1
#000000
on
#313E3C
needs 4.5:1 (normal text)
16px · top of page (header area)
a CPV
1.83:1
#000000
on
#2E3C3B
needs 4.5:1 (normal text)
16px · top of page (header area)
a Search
1.83:1
#000000
on
#2F3C3B
needs 4.5:1 (normal text)
16px · top of page (header area)
a Contact
1.86:1
#000000
on
#303D3C
needs 4.5:1 (normal text)
16px · above the fold
span Region wählen
1.88:1
#000000
on
#313E3C
needs 4.5:1 (normal text)
16px · above the fold
a Belgique/België
1.98:1
#000000
on
#35413F
needs 4.5:1 (normal text)
16px · above the fold
a Česko
2.01:1
#000000
on
#364240
needs 4.5:1 (normal text)
16px · above the fold
a Danmark
2.07:1
#000000
on
#384440
needs 4.5:1 (normal text)
16px · above the fold
a Deutschland
2.10:1
#000000
on
#394541
needs 4.5:1 (normal text)
16px · above the fold
a Eesti
1.88:1
#000000
on
#2E3E3F
needs 4.5:1 (normal text)
16px · above the fold
a Éire/Ireland
1.87:1
#000000
on
#2D3E40
needs 4.5:1 (normal text)
16px · above the fold
a España
1.85:1
#000000
on
#2C3D3F
needs 4.5:1 (normal text)
16px · above the fold
a France
2.89:1
#000000
on
#515859
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Hrvatska
3.88:1
#000000
on
#6A6A6A
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Here is your order17.30:13.0:1
#000000
#E9E9E9
Pass
h2 Tenders and orders i…17.30:13.0:1
#000000
#E9E9E9
Pass
h2 Why are there EU-wid…17.30:13.0:1
#000000
#E9E9E9
Pass
h2 Public procurement l…17.30:13.0:1
#000000
#E9E9E9
Pass
title evergabe.com1.95:14.5:1
#000000
#34403E
Fail
a Start1.88:14.5:1
#000000
#313E3C
Fail
a CPV1.83:14.5:1
#000000
#2E3C3B
Fail
a Search1.83:14.5:1
#000000
#2F3C3B
Fail
a Contact1.86:14.5:1
#000000
#303D3C
Fail
span Region wählen1.88:14.5:1
#000000
#313E3C
Fail
a Belgique/België1.98:14.5:1
#000000
#35413F
Fail
a Česko2.01:14.5:1
#000000
#364240
Fail
a Danmark2.07:14.5:1
#000000
#384440
Fail
a Deutschland2.10:14.5:1
#000000
#394541
Fail
a Eesti1.88:14.5:1
#000000
#2E3E3F
Fail
a Éire/Ireland1.87:14.5:1
#000000
#2D3E40
Fail
a España1.85:14.5:1
#000000
#2C3D3F
Fail
a France2.89:14.5:1
#000000
#515859
Fail
a Hrvatska3.88:14.5:1
#000000
#6A6A6A
Fail
a Ísland9.90:14.5:1
#000000
#B2B2B2
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 26 passed
REVIEW
85

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu header > nav#main > div.mobile-menu > a#nav-open-btn

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.search-field > div.search-field-container > div.field-group > button div.search-field > div.search-field-container > div.field-group > button

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
български (bg) Hrvatski (hr) česky (cs) dansk (da) Nederlands (nl) English (en)… div.container > div.content > form > select

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.

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
Tenders and orders in england div.container-full > div.block-center > div.content > h2
Why are there EU-wide tenders? div.container-full > div.block-center > div.content > h2
Public procurement law in the EU div.container-full > div.block-center > div.content > h2
Accept All div.sc-koXPp > div.sc-iHGNWf > div.sc-bmzYkS > button.sc-gsFSXq
Deny div.sc-koXPp > div.sc-iHGNWf > div.sc-bmzYkS > button.sc-gsFSXq

These are opportunities to improve the legibility of your content.

○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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○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.
○`<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.
○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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 header NAV MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
4 headings
PASS
4 headings
Info::
Single H1 present
  • H1 Here is your order
  • H2 Tenders and orders in england
  • H2 Why are there EU-wide tenders?
  • H2 Public procurement law in the EU
A+
Heading Text Quality
All 4 heading(s) have substantive, well-formed text
PASS
All 4 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 73 visible text node(s) render at >= 12 CSS pixels
PASS
All 73 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback