Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 6 REVIEW 3 FIX

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

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) 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 1 <nav> element(s)

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.

Alt Text Quality

4 of 29 images have issues

REVIEW

4 of 29 images have issues

4 image(s) with filename as alt text

1 image(s) with alt text over 125 characters

24 image(s) with good alt text

29 images 24 good alt text 4 generic

Issue	Count
filename	4 image(s)
too long	1 image(s)

Form Accessibility

Action

6 of 6 controls have issues

REVIEW

6 of 6 controls have issues

6 control(s) without accessible label

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

Got: <input>; <input>; <input>; <input>; <input>; <input>

6 controls

0 labeled

0 placeholder only

6 unlabeled

Control	Type	Label	Method
input	input	(none)	none
input	input	(none)	none
input	input	(none)	none
input	input	(none)	none
input	input	(none)	none
input	input	(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

Link & Button Quality

3 issue(s) across 199 links and 13 buttons

REVIEW

3 issue(s) across 199 links and 13 buttons

3 link(s) with generic text

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

Got: https://genially.com/customer-stories/intel/ ("Read more"); /trust-center/ ("Learn more"); /create/ ("More")

13 link(s) open in new tab without warning

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

Got: https://academy.genially.com/en/; https://blog.genially.com/en/; https://help.genially.com/lang/en_us/?from=web/; https://status.genial.ly/; https://community.genially.com/; https://www.instagram.com/genially_official/; https://www.facebook.com/Geniallyofficial/; https://x.com/genially/; https://www.youtube.com/@genially_official/; https://www.linkedin.com/company/geniallyofficial/ (+3 more)

183 link(s) with descriptive text

199 links

0 empty

3 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://genially.com/customer-stories/in…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Intel
/trust-center/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Trust Center
/create/	More	generic text	Replace with descriptive text
Before: More Suggested: Create
https://academy.genially.com/en/	Genially Academy	new tab	Add '(opens in new tab)' to text
https://blog.genially.com/en/	Blog	new tab	Add '(opens in new tab)' to text
https://help.genially.com/lang/en_us/?fr…	Help Center	new tab	Add '(opens in new tab)' to text
https://status.genial.ly/	System status	new tab	Add '(opens in new tab)' to text
https://community.genially.com/	Community	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/genially_offic…	$Instagram Link	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Geniallyofficia…	$Facebook Link	new tab	Add '(opens in new tab)' to text
https://x.com/genially/	$X Link	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@genially_offici…	$Youtube Link	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/geniall…	$Linkedin Link	new tab	Add '(opens in new tab)' to text
https://www.pinterest.es/geniallyweb/	$Pinterest Link	new tab	Add '(opens in new tab)' to text
https://www.producthunt.com/products/gen…	$ProductHuntWhite Link	new tab	Add '(opens in new tab)' to text
https://his6wix78o9.typeform.com/to/afCs…	Complaints channel	new tab	Add '(opens in new tab)' to text

196 links and buttons have descriptive text

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

https://genially.com/customer-stories/intel/ ("Read more"); /trust-center/ ("Learn more"); /create/ ("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.

https://academy.genially.com/en/; https://blog.genially.com/en/; https://help.genially.com/lang/en_us/?from=web/; https://status.genial.ly/; https://community.genially.com/; https://www.instagram.com/genially_official/; https://www.facebook.com/Geniallyofficial/; https://x.com/genially/; https://www.youtube.com/@genially_official/; https://www.linkedin.com/company/geniallyofficial/ (+3 more)

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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | Genially ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

18 icon(s) detected

REVIEW

18 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Build interactive and gamified experienc…

1.12:1

#000000

#121212

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Key Features

1.12:1

#000000

#121212

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get started with a template

1.12:1

#000000

#121212

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sign up free

1.12:1

#000000

#121212

needs 3.0:1 (large text)

24px · bottom of viewport

title Genially | The easiest way to create int…

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · top of page (header area)

span Genialy home page

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · top of page (header area)

p Features

1.79:1

#000000

#393645

needs 4.5:1 (normal text)

16px · top of page (header area)

p Interactions & Animations

1.79:1

#000000

#393645

needs 4.5:1 (normal text)

16px · top of page (header area)

p Turn static content into engaging experi…

1.79:1

#000000

#393645

needs 4.5:1 (normal text)

16px · above the fold

p Genially AI

1.79:1

#000000

#393645

needs 4.5:1 (normal text)

16px · above the fold

p Speed up content creation with the help …

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

p Accessibility

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

p Create interactive content that’s acce…

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

p Widgets

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

p Pre-built widgets are your shortcut to d…

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

p Brand Kit

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

p Roll out consistent and on-brand content…

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

p Collaboration & Team Management

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · mid-page

p Live co-editing and advanced controls fo…

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · mid-page

p Quiz Builder

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Build interactive an…	1.12:1	3.0:1	#000000	#121212	Fail
h2 Key Features	1.12:1	3.0:1	#000000	#121212	Fail
h2 Get started with a t…	1.12:1	3.0:1	#000000	#121212	Fail
h2 Sign up free	1.12:1	3.0:1	#000000	#121212	Fail
title Genially \| The easie…	1.12:1	4.5:1	#000000	#121212	Fail
span Genialy home page	1.12:1	4.5:1	#000000	#121212	Fail
p Features	1.79:1	4.5:1	#000000	#393645	Fail
p Interactions & Anima…	1.79:1	4.5:1	#000000	#393645	Fail
p Turn static content …	1.79:1	4.5:1	#000000	#393645	Fail
p Genially AI	1.79:1	4.5:1	#000000	#393645	Fail
p Speed up content cre…	1.12:1	4.5:1	#000000	#121212	Fail
p Accessibility	1.12:1	4.5:1	#000000	#121212	Fail
p Create interactive c…	1.12:1	4.5:1	#000000	#121212	Fail
p Widgets	1.12:1	4.5:1	#000000	#121212	Fail
p Pre-built widgets ar…	1.12:1	4.5:1	#000000	#121212	Fail
p Brand Kit	1.12:1	4.5:1	#000000	#121212	Fail
p Roll out consistent …	1.12:1	4.5:1	#000000	#121212	Fail
p Collaboration & Team…	1.12:1	4.5:1	#000000	#121212	Fail
p Live co-editing and …	1.12:1	4.5:1	#000000	#121212	Fail
p Quiz Builder	1.12:1	4.5:1	#000000	#121212	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) 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

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

10 headings

PASS

10 headings

Single H1 present

H1 Build interactive and gamified experiences
H2 Build stunning and original courses, fast
H2 Boost engagement in the classroom
H2 Key Features
H3 One click and it’s interactive
H3 Unlock the power of play
H3 Audiovisual storytelling, made easy with AI
H2 Built on trust
H2 Get started with a template
H2 Sign up free

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Genially

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Genially ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Genially Display Mode standalone Icons 8 icon(s)

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 26 passed

PASS

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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2 `div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2`
div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2 `div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2`
div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2 `div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2`
div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2 `div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2`
div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2 `div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2`
div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2 `div.Flex-sc-29vjs2-0 > div.SessionInputstyled__Wrapper-sc-1oi93fy-3 > div.SessionInputstyled__InputsContainer-sc-1oi93fy-0 > input.SessionInputstyled__StyledInput-sc-1oi93fy-2`

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
article.ComponentContainer-ul9wa2-0 > div.MediaContainer__MediaColumn-sc-1j48vct-1 > div.Iframestyle__IframeWrapper-kqqy6g-1 > iframe.Iframestyle__ResponsiveIframe-kqqy6g-0 `article.ComponentContainer-ul9wa2-0 > div.MediaContainer__MediaColumn-sc-1j48vct-1 > div.Iframestyle__IframeWrapper-kqqy6g-1 > iframe.Iframestyle__ResponsiveIframe-kqqy6g-0`
article.ComponentContainer-ul9wa2-0 > div.MediaContainer__MediaColumn-sc-1j48vct-1 > div.Iframestyle__IframeWrapper-kqqy6g-1 > iframe.Iframestyle__ResponsiveIframe-kqqy6g-0 `article.ComponentContainer-ul9wa2-0 > div.MediaContainer__MediaColumn-sc-1j48vct-1 > div.Iframestyle__IframeWrapper-kqqy6g-1 > iframe.Iframestyle__ResponsiveIframe-kqqy6g-0`

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.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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 use only permitted ARIA attributes

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

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

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

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