https://lingora-dca55.web.app/?utm_source=chatgpt.com

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 3 REVIEW 6 FIX

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

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://lingora-dca55.web.app/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://lingora-dca55.web.app/manifest.json

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark 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

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (1 below threshold)

1 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <small> 11.5px ("Language learning, your way").

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 A new language, one step at a time.

1.10:1

#000000

#110C22

needs 3.0:1 (large text)

32px · above the fold

h2 Start with a language that matters to yo…

1.07:1

#000000

#0B0919

needs 3.0:1 (large text)

24px · mid-page

h2 A dedicated space for each skill

1.07:1

#000000

#0C091A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Your plan starts with you

1.06:1

#000000

#0B0819

needs 3.0:1 (large text)

19px · mid-page

h3 A clear learning path

1.07:1

#000000

#0C091A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Listen with focus

1.07:1

#000000

#0C091A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Speak with confidence

1.07:1

#000000

#0C091A

needs 3.0:1 (large text)

19px · bottom of viewport

title lingora

1.15:1

#000000

#18102E

needs 4.5:1 (normal text)

16px · top of page (header area)

strong LINGORA

1.15:1

#000000

#17112D

needs 3.0:1 (large text)

16px · top of page (header area)

small Language learning, your way

1.15:1

#000000

#16112C

needs 4.5:1 (normal text)

16px · top of page (header area)

button ☀️

1.14:1

#000000

#15102B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Interface language

1.14:1

#000000

#160F2B

needs 4.5:1 (normal text)

16px · above the fold

option العربية

1.14:1

#000000

#16102C

needs 4.5:1 (normal text)

16px · above the fold

option Français

1.13:1

#000000

#150F2A

needs 4.5:1 (normal text)

16px · above the fold

option Deutsch

1.14:1

#000000

#160F2A

needs 4.5:1 (normal text)

16px · above the fold

option Italiano

1.13:1

#000000

#160F29

needs 4.5:1 (normal text)

16px · above the fold

option English

1.13:1

#000000

#150E28

needs 4.5:1 (normal text)

16px · above the fold

button Sign in

1.11:1

#000000

#130D26

needs 4.5:1 (normal text)

16px · above the fold

span Learn • Practice • Grow

1.10:1

#000000

#120C24

needs 4.5:1 (normal text)

16px · above the fold

p A personal learning space to build a dai…

1.09:1

#000000

#0F0B1F

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 A new language, one …	1.10:1	3.0:1	#000000	#110C22	Fail
h2 Start with a languag…	1.07:1	3.0:1	#000000	#0B0919	Fail
h2 A dedicated space fo…	1.07:1	3.0:1	#000000	#0C091A	Fail
h3 Your plan starts wit…	1.06:1	3.0:1	#000000	#0B0819	Fail
h3 A clear learning pat…	1.07:1	3.0:1	#000000	#0C091A	Fail
h3 Listen with focus	1.07:1	3.0:1	#000000	#0C091A	Fail
h3 Speak with confidenc…	1.07:1	3.0:1	#000000	#0C091A	Fail
title lingora	1.15:1	4.5:1	#000000	#18102E	Fail
strong LINGORA	1.15:1	3.0:1	#000000	#17112D	Fail
small Language learning, y…	1.15:1	4.5:1	#000000	#16112C	Fail
button ☀️	1.14:1	4.5:1	#000000	#15102B	Fail
span Interface language	1.14:1	4.5:1	#000000	#160F2B	Fail
option العربية	1.14:1	4.5:1	#000000	#16102C	Fail
option Français	1.13:1	4.5:1	#000000	#150F2A	Fail
option Deutsch	1.14:1	4.5:1	#000000	#160F2A	Fail
option Italiano	1.13:1	4.5:1	#000000	#160F29	Fail
option English	1.13:1	4.5:1	#000000	#150E28	Fail
button Sign in	1.11:1	4.5:1	#000000	#130D26	Fail
span Learn • Practice �…	1.10:1	4.5:1	#000000	#120C24	Fail
p A personal learning …	1.09:1	4.5:1	#000000	#0F0B1F	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.

Heading Hierarchy

7 headings, 1 skip(s)

PASS

7 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 A new language, one step at a time.
H3 Your plan starts with you skipped
H2 Start with a language that matters to you
H2 A dedicated space for each skill
H3 A clear learning path
H3 Listen with focus
H3 Speak with confidence

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

A+

Heading Text Quality

All 7 heading(s) have substantive, well-formed text

PASS

All 7 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

1 decorative image(s) correctly marked

1 image(s) with good alt text

2 images 1 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	Interface language	none

A+

Link & Button Quality

8 links, 2 buttons — all OK

PASS

8 links, 2 buttons — all OK

8 link(s) with descriptive text

8 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

10 links and buttons have descriptive text

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 98/100 — 2 failing, 18 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.

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
Your plan starts with you `div.visual-panel > div.avatar-card > div > h3`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LINGORA Language learning, your way `div#root > div.app-shell > header.topbar > a.brand-wrap`

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

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

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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 have a discernible name

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○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

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

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