Skip to content
https://Evidi.dk

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
D
Tap Target Adequacy
Action
15 tap target(s) too small or too close together
FIX
15 tap target(s) too small or too close together
Warning::
15 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.
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-9otvnt
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.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://Evidi.dk/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://Evidi.dk/manifest.json

Manifest contains invalid JSON.

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.
C
Form Accessibility
Action
4 of 16 controls have issues
REVIEW
4 of 16 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">
Info::
12 control(s) properly labeled
16 controls
12 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#search_mobiletextSøgfor/id
#search489571textSøgfor/id
#search489570textSøgfor/id
#search489572textSøgfor/id
#search_languagetextSøgfor/id
#search_searchtextSøgfor/id
#footer-search-querytextSøgfor/id
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

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

B
Form Input Types
4 input(s) using type=text where a specific type would help
REVIEW
4 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">.
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">.
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">.
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">.
C
Tabindex Anti-Patterns
Action
0 positive, 9 -1-on-focusable
REVIEW
0 positive, 9 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogPoweredbyCybot">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavDetails">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAdSettings">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAbout">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="tab2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="tab3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="tab4">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="tab5">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="tab6">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h1 Forside
2.01:1
#000000
on
#194648
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Kraften i samarbejde
2.01:1
#000000
on
#194648
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sociale medier
2.01:1
#000000
on
#194648
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Søg
2.01:1
#000000
on
#194648
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Vores kunder
2.01:1
#000000
on
#194648
needs 3.0:1 (large text)
19px · bottom of viewport
a Consent
3.88:1
#000000
on
#7A6750
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Details
1.31:1
#000000
on
#331C0C
needs 4.5:1 (normal text)
16px · top of page (header area)
a [#IABV2SETTINGS#]
1.40:1
#000000
on
#352311
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
1.43:1
#000000
on
#332616
needs 4.5:1 (normal text)
16px · above the fold
div This website uses cookies
1.61:1
#000000
on
#402D1A
needs 4.5:1 (normal text)
16px · above the fold
span We use cookies to personalise content an…
1.45:1
#000000
on
#342716
needs 4.5:1 (normal text)
16px · above the fold
span If you would like to read more about our…
1.67:1
#000000
on
#383323
needs 4.5:1 (normal text)
16px · above the fold
span HERE
1.78:1
#000000
on
#3B3827
needs 4.5:1 (normal text)
16px · above the fold
span If you wish to read more about how we pr…
1.73:1
#000000
on
#393627
needs 4.5:1 (normal text)
16px · above the fold
span HERE
1.55:1
#000000
on
#322E1F
needs 4.5:1 (normal text)
16px · above the fold
span Evidi AS, organization number 927 119 78…
1.58:1
#000000
on
#352F1E
needs 4.5:1 (normal text)
16px · above the fold
a [#DSR_FORM_URL_TEXT#]
1.82:1
#000000
on
#413824
needs 4.5:1 (normal text)
16px · above the fold
div [#GPC_BANNER_ICON#]
1.93:1
#000000
on
#493B21
needs 4.5:1 (normal text)
16px · mid-page
div [#GPC_TOAST_TEXT#]
1.99:1
#000000
on
#4B3D25
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 Forside2.01:13.0:1
#000000
#194648
Fail
h2 Kraften i samarbejde2.01:13.0:1
#000000
#194648
Fail
h2 Sociale medier2.01:13.0:1
#000000
#194648
Fail
h2 Søg2.01:13.0:1
#000000
#194648
Fail
h3 Vores kunder2.01:13.0:1
#000000
#194648
Fail
title Evidi | Styrken ligg…9.75:14.5:1
#000000
#B0B1AF
Pass
a Consent3.88:14.5:1
#000000
#7A6750
Fail
a Details1.31:14.5:1
#000000
#331C0C
Fail
a [#IABV2SETTINGS#]1.40:14.5:1
#000000
#352311
Fail
a About1.43:14.5:1
#000000
#332616
Fail
div This website uses co…1.61:14.5:1
#000000
#402D1A
Fail
span We use cookies to pe…1.45:14.5:1
#000000
#342716
Fail
span If you would like to…1.67:14.5:1
#000000
#383323
Fail
span HERE1.78:14.5:1
#000000
#3B3827
Fail
span If you wish to read …1.73:14.5:1
#000000
#393627
Fail
span HERE1.55:14.5:1
#000000
#322E1F
Fail
span Evidi AS, organizati…1.58:14.5:1
#000000
#352F1E
Fail
a [#DSR_FORM_URL_TEXT#…1.82:14.5:1
#000000
#413824
Fail
div [#GPC_BANNER_ICON#]1.93:14.5:1
#000000
#493B21
Fail
div [#GPC_TOAST_TEXT#]1.99:14.5:1
#000000
#4B3D25
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.

A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Hovedmenu" 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
9 headings
PASS
9 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Forside
  • H1 Sammen bygger vi fremtidens IT-løsninger duplicate H1
  • H2 Kraften i samarbejde
  • H3 Vores kunder
  • H2 Vores kompetencer
  • H2 Hvem vi er
  • H2 Kontakt os
  • H2 Sociale medier
  • H2 Søg

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Heading Text Quality
All 9 heading(s) have substantive, well-formed text
PASS
All 9 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
1 of 16 images have issues
PASS
1 of 16 images have issues
Warning::
1 image(s) with generic alt text
Info::
5 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
16 images 10 good alt text 5 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Input Quality
16 form control(s) checked, no input-semantic issues
PASS
16 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 "da"
PASS
Lang attribute set to "da"
Info::
<html lang="da"> is set and valid
Got: da
A+
Iframe Accessibility
All 2 iframe(s) have descriptive titles
PASS
All 2 iframe(s) have descriptive titles
Info::
All 2 iframe(s) have title attributes
A+
Mobile-Readable Font Sizes
All 44 visible text node(s) render at >= 12 CSS pixels
PASS
All 44 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
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
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.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
A
Lighthouse Accessibility Audits
Score 94/100 — 3 failing, 28 passed
PASS
94

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.

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
DK div.pad-wrapper > ul.w-full > li > a.text-footer-feature

These are opportunities to improve the legibility of your content.

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
Brancher vi hjælper footer#bottom > div.pad-wrapper > div.flex > a.detail
Leveranceområder footer#bottom > div.pad-wrapper > div.flex > a.detail
Produkter footer#bottom > div.pad-wrapper > div.flex > a.detail
Aktuelt footer#bottom > div.pad-wrapper > div.flex > a.detail
Events footer#bottom > div.pad-wrapper > div.flex > a.detail
Arbejde hos os footer#bottom > div.pad-wrapper > div.flex > a.detail
Mød menneskene footer#bottom > div.pad-wrapper > div.flex > a.detail
Ledelse & Bæredygtighed footer#bottom > div.pad-wrapper > div.flex > a.detail
LinkedIn footer#bottom > div.pad-wrapper > div.flex > a.detail
Facebook footer#bottom > div.pad-wrapper > div.flex > a.detail
Instagram footer#bottom > div.pad-wrapper > div.flex > a.detail
Privatlivspolitik div.pad-wrapper > ul.w-full > li.mb-3 > a.block
Cookiepolitik div.pad-wrapper > ul.w-full > li.mb-3 > a.block
Whistleblower div.pad-wrapper > ul.w-full > li.mb-3 > a.block
Teknologiordbog div.pad-wrapper > ul.w-full > li.mb-3 > a.block

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
DK header#top > div.page-header > div.wrapper > a.page-header__sitemenu-button
DK div.pad-wrapper > ul.w-full > li > a.text-footer-feature
SE div.pad-wrapper > ul.w-full > li > a
○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
●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
●`[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
●`[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
●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
●`[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
●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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○`<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.
○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