Skip to content
https://Funnytimes.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
9
REVIEW
5
PASS
10
INFO
0
Checks
24
10 PASS 5 REVIEW 9 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER (missing!) SEARCH MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

D
Heading Hierarchy
Action
44 headings, 1 skip(s)
FIX
44 headings, 1 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
5 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Animals
  • H3 Politics
  • H3 Religion
  • H3 Modern Life
  • H3 Love
  • H3 Life & Death
  • H3 Health
  • H3 Hobbies
  • H3 Easy Laughs
  • H3 Work & Money
  • H3 Holidays & Celebrations
  • H3 June 2026 Issue
  • H3 Animals
  • H3 Politics
  • H3 Religion
  • H3 Modern Life
  • H3 Love
  • H3 Life & Death
  • H3 Health
  • H3 Hobbies
  • H3 Easy Laughs
  • H3 Work & Money
  • H3 Holidays & Celebrations
  • H3 June 2026 Issue
  • H1 (empty)
  • H1 (empty)
  • H1 (empty)
  • H1 (empty)
  • H1 When was the last time your newspaper made you laugh? duplicate H1
  • H2 Many magazines are informative, insightful, even important, but only one is absolutely essential to understanding the human condition in this postmodern era.  That magazine is, of course, Funny Times
  • H2 A Peek Inside the Issue
  • H3 It’s A Gas
  • H3 Piraro Knows How To Optimize
  • H3 Cartoonists Corner: Ruben Bolling and Tom Tomorrow
  • H3 Hot Ideas for the 2020s
  • H1 (empty)
  • H3 THE FUNNY TIMES skipped
  • H3 FUNNY STUFF BY CATEGORY
  • H3 HOT OFF THE PRESSES …
  • H3 May 2026 Caption Contest Winner
  • H3 Cartoonists Corner: Ruben Bolling and Tom Tomorrow
  • H3 Crossword and Puzzle Solutions for The June 2026 Issue
  • H3 Singer Has Created A Monster
  • H4 Privacy Overview

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
51 of 60 images have issues
FIX
51 of 60 images have issues
Critical::
42 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
40 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
9 image(s) with generic alt text
Info::
4 image(s) with alt text over 125 characters
Info::
5 image(s) with good alt text
60 images 5 good alt text 9 generic 42 missing
IssueCount
missing42 image(s)
generic9 image(s)
too long4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✗ PNG Icons Missing
✗ 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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation
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
5 of 20 controls have issues
REVIEW
5 of 20 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="gform_submit_button_5">; <input type="submit" id="gform_submit_button_5">; <input type="button" name="login_button" id="login_button-mob">; <input type="button" name="forgot_button" id="forgot_button-mob">; <input type="text" name="s" id="td-header-search-mob">
Info::
15 control(s) properly labeled
20 controls
15 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#input_5_6textInstagramfor/id
#input_5_5emailSign up for our weekly Take-a-Break newsletter and we’ll send you a FREE digital mini magazine!for/id
ak_hp_textareatextareaΔnone
#input_5_6textInstagramfor/id
#input_5_5emailSign up for our weekly Take-a-Break newsletter and we’ll send you a FREE digital mini magazine!for/id
ak_hp_textareatextareaΔnone
#login_email-mobtextyour usernamefor/id
#login_pass-mobpasswordyour passwordfor/id
#forgot_email-mobtextyour emailfor/id
#wt-cli-checkbox-necessarycheckboxNecessaryfor/id
#wt-cli-checkbox-functionalcheckboxFunctionalfor/id
#wt-cli-checkbox-performancecheckboxPerformancefor/id
#wt-cli-checkbox-analyticscheckboxAnalyticsfor/id
#wt-cli-checkbox-advertisementcheckboxAdvertisementfor/id
#wt-cli-checkbox-otherscheckboxOthersfor/id
#login_button-mobbutton(none)none
#gform_submit_button_5submit(none)none
#forgot_button-mobbutton(none)none
#td-header-search-mobtext(none)none
#gform_submit_button_5submit(none)none

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

<input type="submit" id="gform_submit_button_5">; <input type="submit" id="gform_submit_button_5">; <input type="button" name="login_button" id="login_button-mob">; <input type="button" name="forgot_button" id="forgot_button-mob">; <input type="text" name="s" id="td-header-search-mob">

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

C
Tabindex Anti-Patterns
Action
4 positive, 0 -1-on-focusable
REVIEW
4 positive, 0 -1-on-focusable
Warning::
Positive tabindex on <input id="input_5_5">: tabindex=49
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
Warning::
Positive tabindex on <input id="gform_submit_button_5">: tabindex=50
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
Warning::
Positive tabindex on <input id="input_5_5">: tabindex=49
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
Warning::
Positive tabindex on <input id="gform_submit_button_5">: tabindex=50
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
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 Page Not Found - The Funny Times ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA
h1 When was the last time your newspaper ma…
1.79:1
#000000
on
#043772
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Many magazines are informative, insightf…
1.79:1
#000000
on
#043772
needs 3.0:1 (large text)
24px · bottom of viewport
h2 A Peek Inside the Issue
1.79:1
#000000
on
#043772
needs 3.0:1 (large text)
24px · bottom of viewport
h3 It’s A Gas
1.79:1
#000000
on
#043772
needs 3.0:1 (large text)
19px · bottom of viewport
h3 THE FUNNY TIMES
1.79:1
#000000
on
#043772
needs 3.0:1 (large text)
19px · bottom of viewport
h3 FUNNY STUFF BY CATEGORY
1.79:1
#000000
on
#043772
needs 3.0:1 (large text)
19px · bottom of viewport
h3 HOT OFF THE PRESSES …
1.79:1
#000000
on
#043772
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 When was the last ti…1.79:13.0:1
#000000
#043772
Fail
h2 Many magazines are i…1.79:13.0:1
#000000
#043772
Fail
h2 A Peek Inside the Is…1.79:13.0:1
#000000
#043772
Fail
h3 It’s A Gas1.79:13.0:1
#000000
#043772
Fail
h3 THE FUNNY TIMES1.79:13.0:1
#000000
#043772
Fail
h3 FUNNY STUFF BY CATEG…1.79:13.0:1
#000000
#043772
Fail
h3 HOT OFF THE PRESSES …1.79:13.0:1
#000000
#043772
Fail
title Home - The Funny Tim…21.00:14.5:1
#000000
#FFFFFF
Pass
title Home - The Funny Tim…14.88:14.5:1
#000000
#A6E2FA
Pass
span Subscribe11.87:14.5:1
#000000
#6ACFF6
Pass
span Shop11.87:14.5:1
#000000
#6ACFF6
Pass
span About11.87:14.5:1
#000000
#6ACFF6
Pass
span Read Online11.87:14.5:1
#000000
#6ACFF6
Pass
span Submissions11.87:14.5:1
#000000
#6ACFF6
Pass
span Facebook11.87:14.5:1
#000000
#6ACFF6
Pass
span Instagram11.87:14.5:1
#000000
#6ACFF6
Pass
span Youtube11.87:14.5:1
#000000
#6ACFF6
Pass
a Animals11.87:14.5:1
#000000
#6ACFF6
Pass
span Dogs11.87:14.5:1
#000000
#6ACFF6
Pass
span Cats11.87:14.5:1
#000000
#6ACFF6
Pass

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 82/100 — 6 failing, 24 passed
REVIEW
82

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
CARTOON OF THE WEEK div.vc_row > div.vc_column > div.wpb_wrapper > div.td_block_wrap
Read more div.td-module-container > div.td-module-meta-info > div.td-read-more > a
CARTOONISTS CORNER div.vc_row > div.vc_column > div.wpb_wrapper > div.td_block_wrap
Read more div.td-module-container > div.td-module-meta-info > div.td-read-more > a
MURMURS AND MUSINGS div.vc_row > div.vc_column > div.wpb_wrapper > div.td_block_wrap
Read more div.td-module-container > div.td-module-meta-info > div.td-read-more > a
May 2026 Caption Contest Winner div.td-module-container > div.td-module-meta-info > h3.entry-title > a
Cartoonists Corner: Ruben Bolling and Tom Tomorrow div.td-module-container > div.td-module-meta-info > h3.entry-title > a
Crossword and Puzzle Solutions for The June 2026 Issue div.td-module-container > div.td-module-meta-info > h3.entry-title > a
Singer Has Created A Monster div.td-module-container > div.td-module-meta-info > h3.entry-title > a
Cookie settings span > div.cli-bar-container > div.cli-bar-btn_container > a.medium
ACCEPT span > div.cli-bar-container > div.cli-bar-btn_container > a#cookie_action_close_header

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#gform_fields_5 > div#field_5_5 > div.ginput_container > input#input_5_5 div#gform_fields_5 > div#field_5_5 > div.ginput_container > input#input_5_5
div#gform_wrapper_5 > form#gform_5 > div.gform-footer > input#gform_submit_button_5 div#gform_wrapper_5 > form#gform_5 > div.gform-footer > input#gform_submit_button_5
div#gform_fields_5 > div#field_5_5 > div.ginput_container > input#input_5_5 div#gform_fields_5 > div#field_5_5 > div.ginput_container > input#input_5_5
div#gform_wrapper_5 > form#gform_5 > div.gform-footer > input#gform_submit_button_5 div#gform_wrapper_5 > form#gform_5 > div.gform-footer > input#gform_submit_button_5

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
THE FUNNY TIMES div.td-block-row > div.td-block-span12 > div.tds-title > h3.tdm-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.gform-body > div#gform_fields_5 > div#field_5_4 > img div.gform-body > div#gform_fields_5 > div#field_5_4 > img
div.gform-body > div#gform_fields_5 > div#field_5_4 > img div.gform-body > div#gform_fields_5 > div#field_5_4 > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.td_block_wrap > div#tdi_80 > div.tdw-wmc-wrap > a.tdw-wmc-link div.td_block_wrap > div#tdi_80 > div.tdw-wmc-wrap > a.tdw-wmc-link
div.td_block_wrap > div#tdi_39 > div.tdw-wmc-wrap > a.tdw-wmc-link div.td_block_wrap > div#tdi_39 > div.tdw-wmc-wrap > a.tdw-wmc-link
div.wpb_wrapper > div.tdm_block > div.tds-button > a.tds-button5 div.wpb_wrapper > div.tdm_block > div.tds-button > a.tds-button5

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.td-md-is-android html.td-md-is-android

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
●Input buttons have discernible text.
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○Buttons have an accessible name
○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
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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
○`<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.
○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
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 199 chars
Got: 1 >120-char heading(s)
Info::
3 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: 3 all-caps heading(s)
A
Form Input Types
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
Input "login_email" should use type="email" (currently type="text")
Field name "login_email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "forgot_email" should use type="email" (currently type="text")
Field name "forgot_email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A
Form Input Quality
1 input-semantic issue(s) across 20 form control(s)
PASS
1 input-semantic issue(s) across 20 form control(s)
Info::
4 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="input_5">, <input type="email" name="input_5">, <input type="button" name="login_button"> (+1 more).
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 "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 179 visible text node(s) render at >= 12 CSS pixels
PASS
All 179 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
1 mobile-depth signal(s) detected
PASS
1 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback