Accessibility

D

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.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

1 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

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.

C

Landmark Structure

Action

5 landmarks

REVIEW

5 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

Skip navigation link present

Skip link target(s) don't exist on page: #content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

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

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

C

Heading Hierarchy

Action

39 headings, 1 skip(s)

REVIEW

39 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

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

H2 You can’t change the whole world, but you can change one child’s world.
H2 Social Impact Since 1962
H2 Our Vision & Mission
H2 Our Vision
H2 Our Mission
H2 POSSIBLE RESPONSE
H2 About Us
H2 Our Journey of Giving Every Child a Home and Hope
H2 What we do - Our Program
H2 Our Homes For Homeless Children
H2 Child Development Center For Growth & Learning
H2 Our Contact Center Support Line for Homless Children
H2 News & Updates
H2 Earth Day with Snehasadan
H3 April 22, 2025
H2 Building Skills, Building Futures
H3 July 8, 2025
H2 63rd Anniversary of Snehasadan
H3 June 29th, 2025
H2 Fr. Welington Patil
H2 A Vision of Our Father
H2 Stories of Change
H2 Our Events
H2 Donor Speaks
H2 Our Partner
H2 Our Blogs
H2 MY EXPEREINCE OF SNEHASADNA AS A HOUSE PARENT
H2 MY LIFE IS ON THE FORU WHEEL
H2 Mr. Francis Aranha and Mrs. Jacinta Aranha are the House Parent of Snehasadan House No.4.
H2 Moments of Hope
H2 Light Their Future
H4 GIVE US CALL skipped
H2 Contact
H3 Behind Holy Family Church, Andheri (East), Mumbai-400093
H3 snesadan@yahoo.com
H3 +91 83558 97568
H2 About Us
H2 Download
H2 Make a Difference Today

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

C

Link & Button Quality

Action

4 issue(s) across 101 links and 6 buttons

REVIEW

4 issue(s) across 101 links and 6 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://snehasadan.org/

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://snehasadan.org/my-expereince-of-snehasadna-as-a-house-parent/ ("Read more"); https://snehasadan.org/my-life-is-on-the-foru-wheel/ ("Read more"); https://snehasadan.org/mr-francis-aranha-and-mrs-jacinta-aranha-are-the-house… ("Read more")

15 link(s) open in new tab without warning

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

Got: https://wa.me/918355897568; https://pages.razorpay.com/snehasadan; https://pages.razorpay.com/snehasadan; /our-homes/; https://snehasadan.org/journey/; https://snehasadan.org/our-homes/; https://snehasadan.org/child-development/; https://snehasadan.org/contact-center/; https://snehasadan.org/board/; https://pages.razorpay.com/snehasadan (+5 more)

82 link(s) with descriptive text

101 links

1 empty

3 generic text

15 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/918355897568	Chat with Us	new tab	Add '(opens in new tab)' to text
https://snehasadan.org/	(empty)	empty	Add link text or aria-label
https://pages.razorpay.com/snehasadan	Donate Now	new tab	Add '(opens in new tab)' to text
https://pages.razorpay.com/snehasadan	Donate Now	new tab	Add '(opens in new tab)' to text
/our-homes/	Know More	new tab	Add '(opens in new tab)' to text
https://snehasadan.org/journey/	Know More	new tab	Add '(opens in new tab)' to text
https://snehasadan.org/our-homes/	Know More	new tab	Add '(opens in new tab)' to text
https://snehasadan.org/child-development…	Know More	new tab	Add '(opens in new tab)' to text
https://snehasadan.org/contact-center/	Know More	new tab	Add '(opens in new tab)' to text
https://snehasadan.org/board/	Know More	new tab	Add '(opens in new tab)' to text
#	Raja …	img no alt	Add alt attribute to the image
#	Vishal Singh …	img no alt	Add alt attribute to the image
#	Ankita Pawar …	img no alt	Add alt attribute to the image
#	Sanjay Patil …	img no alt	Add alt attribute to the image
#	Akshay Tambe …	img no alt	Add alt attribute to the image
#	Akshay Tambe …	img no alt	Add alt attribute to the image
#	Vishal Singh …	img no alt	Add alt attribute to the image
#	Ankita Pawar …	img no alt	Add alt attribute to the image
#	Sanjay Patil …	img no alt	Add alt attribute to the image
#	Akshay Tambe …	img no alt	Add alt attribute to the image
https://snehasadan.org/my-expereince-of-…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: My Expereince Of Snehasadna As A House Parent
https://snehasadan.org/my-life-is-on-the…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: My Life Is On The Foru Wheel
https://snehasadan.org/mr-francis-aranha…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Mr Francis Aranha And Mrs Jacinta Aranha Are The House Parent Of Snehasadan House No 4
https://pages.razorpay.com/snehasadan	Donate now	new tab	Add '(opens in new tab)' to text
https://wpastra.com	Astra WordPress Theme	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/snehasadanandhe…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/snehasadanandh…	Instagram	new tab	Add '(opens in new tab)' to text
http://www.youtube.com/@snehasadan18ngo2…	Youtube	new tab	Add '(opens in new tab)' to text
https://webconstructive.com/?utm_source=…	WebConstructive	new tab	Add '(opens in new tab)' to text

88 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://snehasadan.org/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://snehasadan.org/my-expereince-of-snehasadna-as-a-house-parent/ ("Read more"); https://snehasadan.org/my-life-is-on-the-foru-wheel/ ("Read more"); https://snehasadan.org/mr-francis-aranha-and-mrs-jacinta-aranha-are-the-house… ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://wa.me/918355897568; https://pages.razorpay.com/snehasadan; https://pages.razorpay.com/snehasadan; /our-homes/; https://snehasadan.org/journey/; https://snehasadan.org/our-homes/; https://snehasadan.org/child-development/; https://snehasadan.org/contact-center/; https://snehasadan.org/board/; https://pages.razorpay.com/snehasadan (+5 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

B

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (3 below threshold)

3 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> 0.0px ("Read more..."); <span> 0.0px ("Know more..."); <span> 0.0px ("Know more...").

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found – Snehasadan | Orphanage ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

B

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

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

Got: 4 all-caps heading(s)

A+

Alt Text Quality

1 of 71 images have issues

PASS

1 of 71 images have issues

1 image(s) with generic alt text

29 decorative image(s) correctly marked

41 image(s) with good alt text

71 images 41 good alt text 29 decorative 1 generic

Issue	Count
generic	1 image(s)

A

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
text-717	text	Name	none
tel-107	tel	Phone	none
text-817	text		none
text-859	text	Quantity	none
input	submit	(none)	none

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

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

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

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

Got: en-US

A

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <button id="e-n-tab-title-838695062">

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

tabindex="-1" on naturally-focusable <a>

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

tabindex="-1" on naturally-focusable <a>

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

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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

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.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 You can’t change t…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Social Impact Since …	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Our Vision & Mission	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Our Vision	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Our Mission	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 POSSIBLE RESPONSE	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 About Us	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Our Journey of Givin…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 What we do - Our Pro…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Our Homes	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Child Development Ce…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Our Contact Center	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 News & Updates	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Earth Day with Sneha…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Building Skills, Bui…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 63rd Anniversary of …	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Fr. Welington Patil	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 A Vision of Our Fath…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Stories of Change	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Our Events	20.12:1	3.0:1	#000000	#FAFAFA	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.

A

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 24 passed

PASS

91

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
Donate Now `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
30,000+ children helped since 1962 `div.elementor-element > div.elementor-element > div.elementor-widget-container > p`
ABOUT US `div.elementor-element > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title`
Every rupee you give helps provide children with education, safety, shelter, an… `div.ekit-wid-con > div.ekit-heading > div.ekit-heading__description > p`

These are opportunities to improve the legibility of your content.

Names and labels

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.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`

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 `html`

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

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

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

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Deprecated ARIA roles were not used

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

○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

○Form elements have associated labels

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

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