https://shubham-tripathi-portfolio.ai.studio

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 4 REVIEW 7 FIX

Mobile Keyboard & Autofill

Action

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

FIX

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

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" id="input-name">, <input type="email" name="email" id="input-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" name="email" id="input-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-bfer7j

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #101827

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

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

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 1 <nav> element(s)

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.

Heading Text Quality

3 heading-text-quality issue(s) detected

REVIEW

3 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "X"

Got: 1 ≤2-char heading(s)

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: - H1: 132 chars

Got: 1 >120-char heading(s)

18 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: 18 all-caps heading(s)

Form Accessibility

3 of 3 controls have issues

REVIEW

3 of 3 controls have issues

3 control(s) rely on placeholder only

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

Got: <input type="text" name="name" id="input-name">; <input type="email" name="email" id="input-email">; <textarea name="message" id="textarea-message">

3 controls

0 labeled

3 placeholder only

0 unlabeled

Control	Type	Label	Method
#input-name	text	(e.g. John Doe)	placeholder only
#input-email	email	(name@company.com)	placeholder only
#textarea-message	textarea	(Outline your goals, requirements, timeline, or links to references...)	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

Mobile-Readable Font Sizes

Action

71% of visible text renders at >= 12 CSS px (157 below threshold)

REVIEW

71% of visible text renders at >= 12 CSS px (157 below threshold)

157 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: <span> 10.0px ("TRIPATHI STUDIO"); <span> 11.0px ("CURRENT SPECIALIZATION FOCUS:"); <span> 10.0px ("Standard"); <span> 10.0px ("Partnership"); <span> 10.0px ("Tenure").

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 BUILD DIGITAL EXPERIENCES

1.20:1

#000000

#13192A

needs 3.0:1 (large text)

32px · bottom of viewport

h1 THAT TURN IDEAS

1.20:1

#000000

#11192A

needs 3.0:1 (large text)

32px · bottom of viewport

h2 TECHNOLOGY MEETS CREATIVE CRAFT.

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 SERVICES & ARCHITECTURE

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 SELECTED WORKS & ARCHITECTURE

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 CORE STACK & CAPABILITIES

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 METHODOLOGY & SPRINT ARCHITECTURE

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Professional Background & Resume

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 DELIVERING EXCELLENCE

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FREQUENTLY ASKED QUESTIONS

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 HAVE A PROJECT IN MIND? LET’S BUILD IT…

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 LET'S BUILD

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h2 READY TO BUILD

1.19:1

#000000

#111929

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Turning ambitious ideas into digital exp…

1.19:1

#000000

#111929

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Website Design & Development

1.19:1

#000000

#111929

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI UGC Video Ads & Product Ads

1.19:1

#000000

#111929

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI Assistant Developer & Smart Apps

1.19:1

#000000

#111929

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI Agents & Automation

1.19:1

#000000

#111929

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Thumbnails, Posters & Banner Design

1.19:1

#000000

#111929

needs 3.0:1 (large text)

19px · bottom of viewport

h3 UI/UX Design

1.19:1

#000000

#111929

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 BUILD DIGITAL EXPERI…	1.20:1	3.0:1	#000000	#13192A	Fail
h1 THAT TURN IDEAS	1.20:1	3.0:1	#000000	#11192A	Fail
h2 TECHNOLOGY MEETS CRE…	1.19:1	3.0:1	#000000	#111929	Fail
h2 SERVICES & ARCHITECT…	1.19:1	3.0:1	#000000	#111929	Fail
h2 SELECTED WORKS & ARC…	1.19:1	3.0:1	#000000	#111929	Fail
h2 CORE STACK & CAPABIL…	1.19:1	3.0:1	#000000	#111929	Fail
h2 METHODOLOGY & SPRINT…	1.19:1	3.0:1	#000000	#111929	Fail
h2 Professional Backgro…	1.19:1	3.0:1	#000000	#111929	Fail
h2 DELIVERING EXCELLENC…	1.19:1	3.0:1	#000000	#111929	Fail
h2 FREQUENTLY ASKED QUE…	1.19:1	3.0:1	#000000	#111929	Fail
h2 HAVE A PROJECT IN MI…	1.19:1	3.0:1	#000000	#111929	Fail
h2 LET'S BUILD	1.19:1	3.0:1	#000000	#111929	Fail
h2 READY TO BUILD	1.19:1	3.0:1	#000000	#111929	Fail
h3 Turning ambitious id…	1.19:1	3.0:1	#000000	#111929	Fail
h3 Website Design & Dev…	1.19:1	3.0:1	#000000	#111929	Fail
h3 AI UGC Video Ads & P…	1.19:1	3.0:1	#000000	#111929	Fail
h3 AI Assistant Develop…	1.19:1	3.0:1	#000000	#111929	Fail
h3 AI Agents & Automati…	1.19:1	3.0:1	#000000	#111929	Fail
h3 Thumbnails, Posters …	1.19:1	3.0:1	#000000	#111929	Fail
h3 UI/UX Design	1.19:1	3.0:1	#000000	#111929	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

47 headings

PASS

47 headings

Single H1 present

H1 Subham Tripathi | Website Designer & AI Creative Specialist — Tripathi Studio: BUILD DIGITAL EXPERIENCESTHAT TURN IDEASINTO REALITY.
H2 TECHNOLOGY MEETS CREATIVE CRAFT.
H3 Turning ambitious ideas into digital experiences people remember.
H4 Subham Tripathi
H2 SERVICES & ARCHITECTURE
H3 Website Design & Development
H3 AI UGC Video Ads & Product Ads
H3 AI Assistant Developer & Smart Apps
H3 AI Agents & Automation
H3 Thumbnails, Posters & Banner Design
H3 UI/UX Design
H3 Branding & Logo Design
H3 Digital Product Design
H4 Need a Custom Solution or Multi-Disciplinary Retainer?
H2 SELECTED WORKS & ARCHITECTURE
H3 NeuroFlow AI Assistant
H3 NeuroFlow AI Assistant
H3 Lumina Luxury Residences
H3 VaultPay Next-Gen FinTech
H3 Aether Roasters Brand Identity
H3 Hyperion Kinetic Ad Campaign
H3 Enchanted Realm Coloring Book
H3 Synapse Predictive Analytics
H3 Pulse AI Studio Generator
H3 Kronos Pro Mobile Health & Biometrics
H2 CORE STACK & CAPABILITIES
H2 METHODOLOGY & SPRINT ARCHITECTURE
H3 DISCOVER
H3 PLAN
H3 CREATE
H3 DELIVER
H2 Professional Background & Resume
H2 DELIVERING EXCELLENCEON EVERY COMMITMENT.
H3 Sub-Second Speeds & Clean Code
H3 Cinematic Aesthetic & Visual Identity
H3 Direct Partnership & Clear Milestones
H2 FREQUENTLY ASKED QUESTIONS
H2 HAVE A PROJECT IN MIND? LET’S BUILD IT.
H2 LET'S BUILDSOMETHING EXCEPTIONAL.
H3 EMAIL
H3 X
H3 LINKEDIN
H3 FIVERR
H2 READY TO BUILDSOMETHING EXCEPTIONAL?
H3 SUBHAM TRIPATHI
H4 Navigation
H4 Assurance

A+

Alt Text Quality

All 19 images OK

PASS

All 19 images OK

19 image(s) with good alt text

19 images 19 good alt text

All images have appropriate alt text.

Link & Button Quality

63 links, 61 buttons — all OK

PASS

63 links, 61 buttons — all OK

21 link(s) open in new tab without warning

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

Got: https://x.com/SubhamTripxuc; https://www.linkedin.com/in/bunny-tripathi-17b718370?utm_source=share_via&utm…; https://example.com/demo/neuroflow; https://example.com/demo/lumina; https://example.com/demo/vaultpay; https://example.com/demo/aether; https://example.com/demo/hyperion; https://example.com/demo/enchanted; https://example.com/demo/synapse; https://example.com/demo/pulse-ai (+11 more)

42 link(s) with descriptive text

63 links

0 empty

0 generic text

21 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://x.com/SubhamTripxuc	Open X Profile	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/bunny-tripat…	Open LinkedIn Profile of Subha…	new tab	Add '(opens in new tab)' to text
https://example.com/demo/neuroflow	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://example.com/demo/lumina	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://example.com/demo/vaultpay	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://example.com/demo/aether	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://example.com/demo/hyperion	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://example.com/demo/enchanted	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://example.com/demo/synapse	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://example.com/demo/pulse-ai	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://example.com/demo/kronos	Open Live Experience	new tab	Add '(opens in new tab)' to text
https://x.com/SubhamTripxuc	@SubhamTripxuc	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/bunny-tripat…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://x.com/SubhamTripxuc	OPEN X PROFILE	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/bunny-tripat…	OPEN LINKEDIN PROFILE	new tab	Add '(opens in new tab)' to text
https://x.com/SubhamTripxuc	X	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/bunny-tripat…	LINKEDIN	new tab	Add '(opens in new tab)' to text
https://x.com/SubhamTripxuc	X (Twitter) Profile	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/bunny-tripat…	LinkedIn Profile	new tab	Add '(opens in new tab)' to text
https://x.com/SubhamTripxuc	Open X Profile	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/bunny-tripat…	Open LinkedIn Profile of Subha…	new tab	Add '(opens in new tab)' to text

103 links and buttons have descriptive text

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

https://x.com/SubhamTripxuc; https://www.linkedin.com/in/bunny-tripathi-17b718370?utm_source=share_via&utm…; https://example.com/demo/neuroflow; https://example.com/demo/lumina; https://example.com/demo/vaultpay; https://example.com/demo/aether; https://example.com/demo/hyperion; https://example.com/demo/enchanted; https://example.com/demo/synapse; https://example.com/demo/pulse-ai (+11 more)

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

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 22 passed

PASS

100

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.

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
ST SUBHAM TRIPATHI TRIPATHI STUDIO `header.fixed > div.max-w-7xl > div.flex > a.flex`
VIEW MY WORK `div.grid > div.lg:col-span-7 > div.flex > a#hero-view-work-btn`
LET'S TALK `div.grid > div.lg:col-span-7 > div.flex > a#hero-lets-talk-btn`
ASK SUBHAM DIRECTLY `section#faq > div.max-w-4xl > div.mt-14 > a.btn-luxury-primary`
shivamtripathi59814@gmail.com `div.max-w-5xl > div.mt-12 > div.flex > a.inline-flex`
shivamtripathi59814@gmail.com `div.grid > div.md:col-span-6 > div.pt-2 > a.text-sm`

○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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

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

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