Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 6 REVIEW 6 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email">

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-25gabj

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://candora-omega.vercel.app/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://candora-omega.vercel.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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

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

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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="text">; <input type="email">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	(Qidirish...)	placeholder only
input	email	(Elektron pochta manzilingiz)	placeholder only

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

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

Tap Target Adequacy

3 tap target(s) too small or too close together

REVIEW

3 tap target(s) too small or too close together

3 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

94% of visible text renders at >= 12 CSS px (10 below threshold)

REVIEW

94% of visible text renders at >= 12 CSS px (10 below threshold)

10 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: <p> 11.0px ("Toshkentdagi 1 200+ mamnun buyurtmachila..."); <p> 11.0px ("Madagaskar vanili & Belgiya shokoladi"); <p> 11.0px ("Qo'lda pardozlangan har bir detal"); <p> 11.0px ("Sovutilgan holda yangi yetkazish"); <span> 10.0px ("01 / Kolleksiya").

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 Shirinlik emas.

1.12:1

#000000

#18110B

needs 3.0:1 (large text)

32px · above the fold

h2 Noir Velvet 70% Qora Shokoladli Tort

1.12:1

#000000

#161209

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Har Bir Shirinlik Ortidagi Uch Qadriyat

1.12:1

#000000

#161209

needs 3.0:1 (large text)

24px · bottom of viewport

h2 To'rt Xil Kayfiyat Olamini Tanlang

1.12:1

#000000

#161209

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Qo'lda Tayyorlangan

1.12:1

#000000

#161209

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Made by Hand.

1.12:1

#000000

#161209

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Mijozlarimizning Qalbidan Chiqqan Fikrla…

1.12:1

#000000

#161209

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Eksklyuziv Imtiyozlar Klubiga Qo'shiling

1.12:1

#000000

#161209

needs 3.0:1 (large text)

24px · bottom of viewport

h3 01. Sof Ta'm (Taste)

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 02. Artisan Mahorat (Craft)

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 03. Unutilmas Lahza (Moment)

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 NOIR

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 BLANC

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ROSE

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 GOLD

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Noir Velvet 70% Qora Shokoladli Tort

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Qirollik Rezavorli Bayram Torti

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tilla Rangli Qulupnayli Shiffon Torti

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Imperator Qizil Baxmal (Red Velvet) Tort…

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tuzlangan Karamelli Drip Torti

1.12:1

#000000

#161209

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Shirinlik emas.	1.12:1	3.0:1	#000000	#18110B	Fail
h2 Noir Velvet 70% Qora…	1.12:1	3.0:1	#000000	#161209	Fail
h2 Har Bir Shirinlik Or…	1.12:1	3.0:1	#000000	#161209	Fail
h2 To'rt Xil Kayfiyat O…	1.12:1	3.0:1	#000000	#161209	Fail
h2 Qo'lda Tayyorlangan	1.12:1	3.0:1	#000000	#161209	Fail
h2 Made by Hand.	1.12:1	3.0:1	#000000	#161209	Fail
h2 Mijozlarimizning Qal…	1.12:1	3.0:1	#000000	#161209	Fail
h2 Eksklyuziv Imtiyozla…	1.12:1	3.0:1	#000000	#161209	Fail
h3 01. Sof Ta'm (Taste)	1.12:1	3.0:1	#000000	#161209	Fail
h3 02. Artisan Mahorat …	1.12:1	3.0:1	#000000	#161209	Fail
h3 03. Unutilmas Lahza …	1.12:1	3.0:1	#000000	#161209	Fail
h3 NOIR	1.12:1	3.0:1	#000000	#161209	Fail
h3 BLANC	1.12:1	3.0:1	#000000	#161209	Fail
h3 ROSE	1.12:1	3.0:1	#000000	#161209	Fail
h3 GOLD	1.12:1	3.0:1	#000000	#161209	Fail
h3 Noir Velvet 70% Qora…	1.12:1	3.0:1	#000000	#161209	Fail
h3 Qirollik Rezavorli B…	1.12:1	3.0:1	#000000	#161209	Fail
h3 Tilla Rangli Qulupna…	1.12:1	3.0:1	#000000	#161209	Fail
h3 Imperator Qizil Baxm…	1.12:1	3.0:1	#000000	#161209	Fail
h3 Tuzlangan Karamelli …	1.12:1	3.0:1	#000000	#161209	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

32 headings, 1 skip(s)

PASS

32 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Shirinlik emas.Bir lahza.
H2 Noir Velvet 70% Qora Shokoladli Tort
H2 Har Bir Shirinlik Ortidagi Uch Qadriyat
H3 01. Sof Ta'm (Taste)
H3 02. Artisan Mahorat (Craft)
H3 03. Unutilmas Lahza (Moment)
H2 To'rt Xil Kayfiyat Olamini Tanlang
H3 NOIR
H3 BLANC
H3 ROSE
H3 GOLD
H2 Qo'lda Tayyorlangan Nafis Shirinliklar (100+ xil)
H3 Noir Velvet 70% Qora Shokoladli Tort
H3 Qirollik Rezavorli Bayram Torti
H3 Tilla Rangli Qulupnayli Shiffon Torti
H3 Imperator Qizil Baxmal (Red Velvet) Torti
H3 Tuzlangan Karamelli Drip Torti
H3 Pistali Mussli Ko'zgu Tort
H3 Katta Tantana & To'y Qavatli Torti
H3 Klassik Nyu-York Chernikali Chizkeyk
H3 Opera Parisienne Fransuz Torti
H3 Asalli Medovik Oltin Tort
H3 Qora O'rmon (Black Forest Kirsch) Torti
H3 Tropik Mango & Marakuya Mussli Tort
H2 Made by Hand.Not by Machine.
H4 Saralangan Xomashyo skipped
H4 Sekin Temperlash
H4 Qo'lda Pardozlash
H3 Sizning Orzuingiz. Bizning Ustaxonamiz.
H3 Hashamat Quti Ochilishidan Boshlanadi
H2 Mijozlarimizning Qalbidan Chiqqan Fikrlar
H2 Eksklyuziv Imtiyozlar Klubiga Qo'shiling

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

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

4 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 4 all-caps heading(s)

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

18 image(s) with good alt text

18 images 18 good alt text

All images have appropriate alt text.

Link & Button Quality

19 links, 49 buttons — all OK

PASS

19 links, 49 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://instagram.com/candora.uz; https://t.me/candora_uz

17 link(s) with descriptive text

19 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://instagram.com/candora.uz	Candora Instagram sahifasi	new tab	Add '(opens in new tab)' to text
https://t.me/candora_uz	Candora Telegram kanali	new tab	Add '(opens in new tab)' to text

66 links and buttons have descriptive text

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

https://instagram.com/candora.uz; https://t.me/candora_uz

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

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "uz"

PASS

Lang attribute set to "uz"

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

Got: uz

A+

Tabindex Anti-Patterns

13 explicit tabindex attribute(s) checked, no anti-patterns

PASS

13 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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.

Lighthouse Accessibility Audits

Score 90/100 — 4 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.

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
Reyting: 4.7 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.8 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.9 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 5 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.7 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.8 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.9 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 5 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.7 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.8 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.9 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 5 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 5 yulduz `div.grid > div.p-6 > div.space-y-3 > div.flex`
Reyting: 5 yulduz `div.grid > div.p-6 > div.space-y-3 > div.flex`
Reyting: 5 yulduz `div.grid > div.p-6 > div.space-y-3 > div.flex`
Reyting: 5 yulduz `div.grid > div.p-6 > div.space-y-3 > div.flex`

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.

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
Saralangan Xomashyo `div.space-y-4 > div.flex > div > h4.text-sm`

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Desert 1 `div.aspect-square > div.absolute > div.flex > button.h-1.5`
Desert 2 `div.aspect-square > div.absolute > div.flex > button.h-1.5`
Desert 3 `div.aspect-square > div.absolute > div.flex > button.h-1.5`

These items highlight common accessibility best practices.

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
UZ `nav.max-w-7xl > div.flex > div.relative > button.flex`

○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

●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

●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

●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

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

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

○Links are distinguishable without relying on color.

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

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