Skip to content
https://embedgooglemap.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 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
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!) MAIN (missing!) CONTENTINFO footer

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
6 of 11 controls have issues
REVIEW
6 of 11 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" id="mapZoom">; <input type="text" id="mapWidth">; <input type="number" id="widthValue">; <input type="text" id="mapHeight">; <input type="number" id="heightValue">; <textarea id="codeOutput">
Info::
5 control(s) properly labeled
11 controls
5 labeled
0 placeholder only
6 unlabeled
ControlTypeLabelMethod
#addresstextType Your Addressfor/id
#sAddresstextStart Addressfor/id
#dAddresstextDestination Addressfor/id
#map_typeselectMap Typefor/id
#isResponsivecheckboxMake Map Responsivefor/id
#mapWidthtext(none)none
#widthValuenumber(none)none
#mapHeighttext(none)none
#heightValuenumber(none)none
#mapZoomtext(none)none
#codeOutputtextarea(none)none

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

<input type="text" id="mapZoom">; <input type="text" id="mapWidth">; <input type="number" id="widthValue">; <input type="text" id="mapHeight">; <input type="number" id="heightValue">; <textarea id="codeOutput">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 23 passed
REVIEW
84

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.

ARIA

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.card-body > div.form-group > div#zoomSlider > div.slider-handle div.card-body > div.form-group > div#zoomSlider > div.slider-handle
div.col-lg-6 > div.form-group > div#widthSlider > div.slider-handle div.col-lg-6 > div.form-group > div#widthSlider > div.slider-handle
div.col-lg-6 > div.form-group > div#heightSlider > div.slider-handle div.col-lg-6 > div.form-group > div#heightSlider > div.slider-handle

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Community div.col-lg-12 > div#generate_map > div.mb-3 > a.btn
Generate Code div.w-100 > div.card > div.card-body > button.btn
try best ai humanizer div.card > div.col-lg-12 > p > a
www.embedgooglemap.net div.row > div.col-lg-12 > div.copyright > a

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-lg-6 > div.form-group > div.input-group > input#widthValue div.col-lg-6 > div.form-group > div.input-group > input#widthValue
div.col-lg-6 > div.form-group > div.input-group > input#heightValue div.col-lg-6 > div.form-group > div.input-group > input#heightValue

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-lg-8 > div.w-100 > div#map-container > iframe#map-canvas div.col-lg-8 > div.w-100 > div#map-container > iframe#map-canvas

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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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 Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H5 Map Code
  • H1 Embed Google Maps on Your Website for Free
  • H2 What Google Maps Is
  • H2 Why Embedding a Map Helps Your Website
  • H2 How to Embed Google Maps Without an API
  • H2 Where the Embed Code Works
  • H2 Frequently Asked Questions
  • H3 Is this really free?
  • H3 Do I need technical skills?
  • H3 Does the map work on mobile devices?
  • H3 Can I change the map later?
  • H3 Why not use the Google Maps API?
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
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)
ElementRatioRequiredFGBGResult
h1 Embed Google Maps on…19.27:13.0:1
#000000
#F5F5F6
Pass
h2 What Google Maps Is19.27:13.0:1
#000000
#F5F5F6
Pass
h2 Why Embedding a Map …19.27:13.0:1
#000000
#F5F5F6
Pass
h2 How to Embed Google …19.27:13.0:1
#000000
#F5F5F6
Pass
h2 Where the Embed Code…19.27:13.0:1
#000000
#F5F5F6
Pass
h2 Frequently Asked Que…19.27:13.0:1
#000000
#F5F5F6
Pass
h3 Is this really free?19.27:13.0:1
#000000
#F5F5F6
Pass
h3 Do I need technical …19.27:13.0:1
#000000
#F5F5F6
Pass
h3 Does the map work on…19.27:13.0:1
#000000
#F5F5F6
Pass
h3 Can I change the map…19.27:13.0:1
#000000
#F5F5F6
Pass
h3 Why not use the Goog…19.27:13.0:1
#000000
#F5F5F6
Pass
title Embed Google Map, 10…19.95:14.5:1
#000000
#F9F9F9
Pass
a Community19.95:14.5:1
#000000
#F9F9F9
Pass
div Embed Google Map19.95:14.5:1
#000000
#F9F9F9
Pass
label Type Your Address19.77:14.5:1
#000000
#F8F8F8
Pass
label Start Address19.27:14.5:1
#000000
#F5F5F6
Pass
label Destination Address19.11:14.5:1
#000000
#F4F4F5
Pass
label Map Type19.11:14.5:1
#000000
#F4F4F5
Pass
option Roadmap19.11:14.5:1
#000000
#F4F4F5
Pass
option Satellite19.11:14.5:1
#000000
#F4F4F5
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback