Skip to content
https://wikiauthoritygroup.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
7
REVIEW
7
PASS
10
INFO
0
Checks
24
10 PASS 7 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
6/8 eligible field(s) missing autocomplete or inputmode
FIX
6/8 eligible field(s) missing autocomplete or inputmode
Warning::
2 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: name, email.
Got: <input type="text" name="name">, <input type="email" name="email">
Warning::
4 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, tel.
Got: <input type="email" name="email">, <input type="tel" name="phone">, <input type="email" name="email">, <input type="tel" name="phone">
D
Mobile-Readable Font Sizes
Action
54% of visible text renders at >= 12 CSS px (197 below threshold)
FIX
54% of visible text renders at >= 12 CSS px (197 below threshold)
Warning::
197 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> 9.0px ("Verified Authority Standard"); <div> 11.0px ("Editorial advisory MMXXVI"); <div> 10.0px ("Publication rate accepted clients"); <div> 10.0px ("Engagements since MMXIX"); <div> 10.0px ("Typical engagement cycle").
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #0f1a1a
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 ModePartial Dark Mode
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) NAV MAIN ASIDE 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

C
Heading Hierarchy
Action
36 headings, 3 skip(s)
REVIEW
36 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 THE QUIET STANDARD FOR ENCYCLOPEDICPRESENCE.
  • H4 Dr. A. Reyes skipped
  • H4 Osterhagen AG
  • H4 M. Linden
  • H4 Pembroke Institute
  • H2 From the record to the page.
  • H4 Research skipped
  • H4 Draft
  • H4 Review
  • H4 Publish
  • H2 The encyclopedic standard we uphold.
  • H2 Four instruments, one standard.
  • H3 Editorial Drafting
  • H3 Translation & Localisation
  • H3 Factual Revision
  • H3 Monitoring Retainer
  • H3 Article Curation & Optimisation
  • H2 Is the subject a candidate?
  • H3 What best describes the subject?
  • H2 Wikipedia pages for every subject.
  • H2 Questions worth asking first.
  • H4 Can you guarantee a page will be published? skipped
  • H4 How long does the process typically take?
  • H4 Is what you do permitted under editorial policy?
  • H4 Do you handle monitoring after publication?
  • H4 Will our engagement remain confidential?
  • H2 A first conversation, under NDA.
  • H3 Begin a confidential consultation.
  • H4 USA
  • H4 EUROPE
  • H4 UAE
  • H5 Practice
  • H5 Firm
  • H5 Direct
  • H2 “ Begin your eligibility review.
  • H2 Your brief is with the editorial board.

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

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

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

C
Form Accessibility
Action
10 of 15 controls have issues
REVIEW
10 of 15 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="service">
Warning::
9 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="name">; <input type="email" name="email">; <input type="tel" name="phone">; <input type="text" name="company">; <textarea name="message">; <input type="text" name="name">; <input type="email" name="email">; <input type="tel" name="phone">; <textarea name="context">
Info::
5 control(s) properly labeled
15 controls
5 labeled
9 placeholder only
1 unlabeled
ControlTypeLabelMethod
subject_typeradionone
subject_typeradionone
subject_typeradionone
subject_typeradionone
subject_typeradionone
nametext(Full name)placeholder only
emailemail(Email address)placeholder only
phonetel(Phone number (with country code))placeholder only
nametext(Jane A. Ellison)placeholder only
emailemail(you@company.com)placeholder only
phonetel(+1 (___) ___ ____)placeholder only
companytext(Dr. Anton Reyes Director, Pembroke Institute)placeholder only
messagetextarea(Title, prior coverage, awards, forthcoming events anything relevant.)placeholder only
contexttextarea(Brief context subject, case for notability, desired outcome.)placeholder only
serviceselect(none)none

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

<select name="service">

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

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

<input type="text" name="name">; <input type="email" name="email">; <input type="tel" name="phone">; <input type="text" name="company">; <textarea name="message">; <input type="text" name="name">; <input type="email" name="email">; <input type="tel" name="phone">; <textarea name="context">

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
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 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.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 — Page Not Found | Wiki Authority Group ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
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
h2 From the record
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The encyclopedic
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Four instruments,
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Is the subject
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Wikipedia pages
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Questions worth
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 A first conversation,
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Begin your
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your brief is with the
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Editorial Drafting
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Translation & Localisation
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Factual Revision
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Monitoring Retainer
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Article Curation & Optimisation
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 What best describes the subject?
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Begin a confidential consultation.
1.05:1
#000000
on
#050909
needs 3.0:1 (large text)
19px · bottom of viewport
title Wiki Authority Group Editorial advisory…
1.06:1
#000000
on
#060A0A
needs 4.5:1 (normal text)
16px · top of page (header area)
b WikiAuthorityGroup
1.06:1
#000000
on
#060A0A
needs 3.0:1 (large text)
16px · top of page (header area)
small Verified Authority Standard
1.04:1
#000000
on
#050808
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.04:1
#000000
on
#050707
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 From the record1.05:13.0:1
#000000
#050909
Fail
h2 The encyclopedic1.05:13.0:1
#000000
#050909
Fail
h2 Four instruments,1.05:13.0:1
#000000
#050909
Fail
h2 Is the subject1.05:13.0:1
#000000
#050909
Fail
h2 Wikipedia pages1.05:13.0:1
#000000
#050909
Fail
h2 Questions worth1.05:13.0:1
#000000
#050909
Fail
h2 A first conversation…1.05:13.0:1
#000000
#050909
Fail
h2 Begin your1.05:13.0:1
#000000
#050909
Fail
h2 Your brief is with t…1.05:13.0:1
#000000
#050909
Fail
h3 Editorial Drafting1.05:13.0:1
#000000
#050909
Fail
h3 Translation & Locali…1.05:13.0:1
#000000
#050909
Fail
h3 Factual Revision1.05:13.0:1
#000000
#050909
Fail
h3 Monitoring Retainer1.05:13.0:1
#000000
#050909
Fail
h3 Article Curation & O…1.05:13.0:1
#000000
#050909
Fail
h3 What best describes …1.05:13.0:1
#000000
#050909
Fail
h3 Begin a confidential…1.05:13.0:1
#000000
#050909
Fail
title Wiki Authority Group…1.06:14.5:1
#000000
#060A0A
Fail
b WikiAuthorityGroup1.06:13.0:1
#000000
#060A0A
Fail
small Verified Authority S…1.04:14.5:1
#000000
#050808
Fail
a Home1.04:14.5:1
#000000
#050707
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 21 passed
REVIEW
86

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
(213) 328-0836 div#app > div.nav-drawer > div.nav-drawer-footer > a
Info@wikiauthoritygroup.com div#app > div.nav-drawer > div.nav-drawer-footer > a
INDEPENDENT EDITORIAL CONSULTANCY. NOT AFFILIATED WITH, ENDORSED BY, OR RELATED… div#app > footer.footer > div.shell > div.footer-disclaimer-line

These are opportunities to improve the legibility of your content.

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
Research div.shell > div.steps > div.step > h4
Can you guarantee a page will be published? div.faq-list > div.faq-item > button.faq-q > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select one Subject themself Counsel / Legal Publicist / Comms Chief of Staff Ot… form.contact-form > div.field-row > div.field > select

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.

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
(213) 328-0836 div.nav-inner > div.nav-right > div.nav-mobile-contact > a
Info@wikiauthoritygroup.com div.nav-inner > div.nav-right > div.nav-mobile-contact > a

These items highlight common accessibility best practices.

○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
●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
●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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○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.
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 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: 2 all-caps heading(s)
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
11 image(s) with good alt text
11 images 11 good alt text
All images have appropriate alt text.
A+
Form Input Types
15 form control(s) checked, no type mismatches
PASS
15 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
15 form control(s) checked, no input-semantic issues
PASS
15 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Tabindex Anti-Patterns
0 positive, 2 -1-on-focusable
PASS
0 positive, 2 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
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 <input>
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.)
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback