Skip to content
https://evolution.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
5
REVIEW
8
PASS
0
INFO
0
Checks
13
8 REVIEW 5 FIX
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
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::
2 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 2 <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.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

C
Alt Text Quality
Action
4 of 161 images have issues
REVIEW
4 of 161 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
31 decorative image(s) correctly marked
Info::
126 image(s) with good alt text
161 images 126 good alt text 31 decorative 4 missing
IssueCount
missing4 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

B
Form Accessibility
2 of 10 controls have issues
REVIEW
2 of 10 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">; <input type="search" name="s">
Info::
8 control(s) properly labeled
10 controls
8 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxFunctionalfor/id
#cmplz-preferences-optincheckboxPreferencesfor/id
#cmplz-statistics-optincheckboxStatisticsfor/id
#cmplz-marketing-optincheckboxMarketingfor/id
#cmplz-functional-optoutcheckboxFunctionalfor/id
#cmplz-preferences-optoutcheckboxPreferencesfor/id
#cmplz-statistics-optoutcheckboxStatisticsfor/id
#cmplz-marketing-optoutcheckboxMarketingfor/id
ssearch(Search our website)placeholder only
ssearch(Search our website)placeholder only

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

<input type="search" name="s">; <input type="search" name="s">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Evolution ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
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
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA
a Who We Are
1.95:1
#000000
on
#810306
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Our Mission
2.07:1
#000000
on
#890206
needs 4.5:1 (normal text)
16px · top of page (header area)
a Our Brands
1.41:1
#000000
on
#570104
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Compliance & Markets
1.27:1
#000000
on
#450403
needs 4.5:1 (normal text)
16px · above the fold
a Evolution Timeline
2.13:1
#000000
on
#8B050D
needs 4.5:1 (normal text)
16px · above the fold
a Customers
1.75:1
#000000
on
#720704
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Our Games
2.09:1
#000000
on
#870D02
needs 4.5:1 (normal text)
16px · above the fold
a Live Casino
2.83:1
#000000
on
#A71D0F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Slots
2.88:1
#000000
on
#A82012
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Game Shows
2.43:1
#000000
on
#97150C
needs 4.5:1 (normal text)
16px · above the fold
a First Person
1.39:1
#000000
on
#451810
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

6 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
title Evolution - Leading …21.00:14.5:1
#000000
#FFFFFF
Pass
a Who We Are21.00:14.5:1
#000000
#FFFFFF
Pass
a Who We Are1.95:14.5:1
#000000
#810306
Fail
a Our Mission2.07:14.5:1
#000000
#890206
Fail
a Our Brands1.41:14.5:1
#000000
#570104
Fail
a Compliance & Markets1.27:14.5:1
#000000
#450403
Fail
a Evolution Timeline2.13:14.5:1
#000000
#8B050D
Fail
a Customers1.75:14.5:1
#000000
#720704
Fail
a Our Games2.09:14.5:1
#000000
#870D02
Fail
a Live Casino2.83:14.5:1
#000000
#A71D0F
Fail
a Slots2.88:14.5:1
#000000
#A82012
Fail
a Game Shows2.43:14.5:1
#000000
#97150C
Fail
a First Person1.39:14.5:1
#000000
#451810
Fail
a Live Blackjack20.12:14.5:1
#000000
#FAFAFA
Pass
a Live Roulette21.00:14.5:1
#000000
#FFFFFF
Pass
a Live Baccarat21.00:14.5:1
#000000
#FFFFFF
Pass
a Super Sic Bo & Drago…21.00:14.5:1
#000000
#FFFFFF
Pass
a Live Poker21.00:14.5:1
#000000
#FFFFFF
Pass
a Land Based21.00:14.5:1
#000000
#FFFFFF
Pass
a News21.00:14.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.

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 7 failing, 20 passed
REVIEW
70

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
WHO WE ARE div.d-flex > ul#menu-primary-menu-1 > div.dropdown > div.dropdown-toggle
OUR GAMES div.d-flex > ul#menu-primary-menu-1 > div.dropdown > div.dropdown-toggle
NEWS div.d-flex > ul#menu-primary-menu-1 > div.dropdown > div.dropdown-toggle
INVESTORS div.d-flex > ul#menu-primary-menu-1 > div.dropdown > div.dropdown-toggle

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
section#hero-slider > div.owl-carousel > div.owl-nav > button.owl-prev section#hero-slider > div.owl-carousel > div.owl-nav > button.owl-prev
section#hero-slider > div.owl-carousel > div.owl-nav > button.owl-next section#hero-slider > div.owl-carousel > div.owl-nav > button.owl-next

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.owl-carousel > div.owl-nav > button.owl-prev > img div.owl-carousel > div.owl-nav > button.owl-prev > img
div.owl-carousel > div.owl-nav > button.owl-next > img div.owl-carousel > div.owl-nav > button.owl-next > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#standard-wrapper > section#our-share > div.container > iframe#euroland_frame_id div#standard-wrapper > section#our-share > div.container > iframe#euroland_frame_id

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.container > div.d-flex > div.image-circle > a div.container > div.d-flex > div.image-circle > a
div.container > div.d-flex > div.image-circle > a div.container > div.d-flex > div.image-circle > a
div.container > div.d-flex > div.image-circle > a div.container > div.d-flex > div.image-circle > a
div.container > div.d-flex > div.image-circle > a div.container > div.d-flex > div.image-circle > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
div.owl-stage > div.owl-item > div.item > a div.owl-stage > div.owl-item > div.item > a
section.site-footer-socials > div.container > div.d-flex > a.social-icon section.site-footer-socials > div.container > div.d-flex > a.social-icon
section.site-footer-socials > div.container > div.d-flex > a.social-icon section.site-footer-socials > div.container > div.d-flex > a.social-icon
section.site-footer-socials > div.container > div.d-flex > a.social-icon section.site-footer-socials > div.container > div.d-flex > a.social-icon
section.site-footer-socials > div.container > div.d-flex > a.social-icon section.site-footer-socials > div.container > div.d-flex > a.social-icon
section.site-footer-socials > div.container > div.d-flex > a.social-icon section.site-footer-socials > div.container > div.d-flex > a.social-icon
div.row > div.col-lg-12 > div.d-flex > a div.row > div.col-lg-12 > div.d-flex > a
div.row > div.col-lg-12 > div.d-flex > a div.row > div.col-lg-12 > div.d-flex > a

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
CUSTOM ROULETTE div.owl-item > div.item > div.slide-content > a.cta
EVOLUTION LAUNCHES MONOPOLY LIVE IN THE U.S. div.col-md-4 > a.news-card > div.news-card-content > p.h4
EVOLUTION CELEBRATES 20 YEARS OF INNOVATION, GROWTH AND INDUSTRY LEADERSHIP div.col-md-4 > a.news-card > div.news-card-content > p.h4
EVOLUTION LAUNCHES CRAZY TIME BRASIL, BRINGING ITS MOST ICONIC LIVE GAME SHOW T… div.col-md-4 > a.news-card > div.news-card-content > p.h4
SEE MORE div.banner-container > div.banner-content > div.button-wrap > a.cta

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
WHO WE ARE OUR GAMES NEWS INVESTORS CAREERS CLIENT AREA CONTACT US header#site-header > nav.navbar > div.d-flex > ul#menu-primary-menu-1

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○Heading elements appear in a sequentially-descending order
○`<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
○Links are distinguishable without relying on color.
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Send Feedback