https://myseshnyc.com/?utm_source=google&utm_medium=organic&utm_campaign=gmb

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

Landmark Structure

Action

19 landmarks

FIX

19 landmarks

No <main> landmark found

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

6 <nav> landmark(s) found

6 of 6 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No contentinfo (footer) landmark

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

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

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

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.

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

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

Tap Target Adequacy

2 tap target(s) too small or too close together

REVIEW

2 tap target(s) too small or too close together

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.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | SeshNYC ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 The Bronx Dispensary Locals Trust

1.09:1

#000000

#080F12

needs 3.0:1 (large text)

32px · mid-page · over background image/gradient

h2 Shop Our Cannabis Menu

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Homegrown

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Who Care

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 New York's Top Cannabis Brands

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Experience Cannabis

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Way

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What Our Customers Say

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 for Every Cannabis Need

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Visit Our Bronx Location

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Save More on Cannabis in the Bronx

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tips for Visiting a Bronx Dispensary

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FAQ: Bronx Dispensary Near Me

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Start Your Cannabis Journey with SeshNYC

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Flower

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 PreRolls

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Vapes

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Edibles

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tinctures

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The Bronx Dispensary…	1.09:1	3.0:1	#000000	#080F12	Fail
h2 Shop Our Cannabis Me…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Homegrown	1.00:1	3.0:1	#000000	#000000	Fail
h2 Who Care	1.00:1	3.0:1	#000000	#000000	Fail
h2 New York's Top Canna…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Experience Cannabis	1.00:1	3.0:1	#000000	#000000	Fail
h2 Way	1.00:1	3.0:1	#000000	#000000	Fail
h2 What Our Customers S…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Your	1.00:1	3.0:1	#000000	#000000	Fail
h2 for Every Cannabis N…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Visit Our Bronx Loca…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Save More on Cannabi…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Tips for Visiting a …	1.00:1	3.0:1	#000000	#000000	Fail
h2 FAQ: Bronx Dispensar…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Start Your Cannabis …	1.00:1	3.0:1	#000000	#000000	Fail
h3 Flower	1.00:1	3.0:1	#000000	#000000	Fail
h3 PreRolls	1.00:1	3.0:1	#000000	#000000	Fail
h3 Vapes	1.00:1	3.0:1	#000000	#000000	Fail
h3 Edibles	1.00:1	3.0:1	#000000	#000000	Fail
h3 Tinctures	1.00:1	3.0:1	#000000	#000000	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.

A+

Heading Hierarchy

38 headings

PASS

38 headings

Single H1 present

H1 The Bronx Dispensary Locals Trust
H2 Shop Our Cannabis Menu
H3 Flower
H3 PreRolls
H3 Vapes
H3 Edibles
H3 Tinctures
H3 Extracts
H3 Topicals
H2 Homegrown Bronx Locals Who Care
H2 New York's Top Cannabis Brands
H2 Experience Cannabis The Bronx Way
H2 What Our Customers Say
H2 Your Bronx Dispensary for Every Cannabis Need
H3 New to Cannabis?
H3 Looking for Specific Effects?
H3 Exploring New Products?
H2 Visit Our Bronx Location
H2 Save More on Cannabis in the Bronx
H2 Tips for Visiting a Bronx Dispensary
H3 Know the Legal Age
H3 Always Bring Your ID
H3 No Medical Card Needed
H3 Factor in Cannabis Taxes
H3 Know the Bronx Dispensary Limit
H3 Smoke Weed in the Right Spots
H2 FAQ: Bronx Dispensary Near Me
H3 I live in Woodlawn Heights and want a cannabis dispensary close by. Do you have one?
H3 I'm in Wakefield and looking for a solid Bronx dispensary. How far are you?
H3 I live in Williamsbridge and want a local cannabis dispensary. Do you serve this neighborhood?
H3 I'm over in Edenwald and looking for a dispensary nearby. Where's the closest one?
H3 I live in Olinville and want to check out a cannabis dispensary with a good vibe. Is SeshNYC close?
H3 I'm in Norwood (Bainbridge) and looking for the best dispensary in the Bronx. Where should I go?
H3 I live in Pelham Gardens and need a cannabis dispensary nearby. Can I get to you quickly?
H3 I'm in Baychester and searching for a Bronx weed shop with good variety. Any recommendations?
H3 I'm in Kingsbridge and want a Bronx dispensary with premium flower. How close are you?
H3 I'm in the East Bronx and need a weed dispensary near me with quality products. Where should I go?
H2 Start Your Cannabis Journey with SeshNYC

A+

Heading Text Quality

All 38 heading(s) have substantive, well-formed text

PASS

All 38 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 40 images OK

PASS

All 40 images OK

40 image(s) with good alt text

40 images 40 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

89 links, 16 buttons — all OK

PASS

89 links, 16 buttons — all OK

13 link(s) open in new tab without warning

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

Got: https://maps.app.goo.gl/WQL8qCDDd5RuvZTa7; https://maps.app.goo.gl/1wroneNFr6a688cx8; https://maps.app.goo.gl/bNCYd2yrJzEdKsJE8; https://maps.app.goo.gl/LnGZiNctcbQAGQgz5; https://maps.app.goo.gl/bjo5zsnbu6rgkg2L7; https://maps.app.goo.gl/jTBVUjuzxHRWHKSi8; https://maps.app.goo.gl/RF3wqYjQx9AVVfXT9; https://maps.app.goo.gl/wTXDBPUfMzdfgRbN9; https://maps.app.goo.gl/QRZ8qpvqC1kYVpKG6; https://maps.app.goo.gl/4Er7XdtAKrT418E8A (+3 more)

76 link(s) with descriptive text

89 links

0 empty

0 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://maps.app.goo.gl/WQL8qCDDd5RuvZTa…	from Woodlawn Heights to SeshN…	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/1wroneNFr6a688cx…	Williamsbridge to SeshNYC	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/bNCYd2yrJzEdKsJE…	driving directions from Edenwa…	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/LnGZiNctcbQAGQgz…	directions from Olinville to o…	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/bjo5zsnbu6rgkg2L…	driving directions from Norwoo…	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/jTBVUjuzxHRWHKSi…	directions from Pelham Gardens	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/RF3wqYjQx9AVVfXT…	directions from Baychester	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/wTXDBPUfMzdfgRbN…	driving from Kingsbridge to ou…	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/QRZ8qpvqC1kYVpKG…	driving from East Bronx	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/4Er7XdtAKrT418E8…	4219 Webster Avenue, Bronx NY …	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Myseshnyc-12269…	facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/myseshnyc/	instagram	new tab	Add '(opens in new tab)' to text
https://cannabis.ny.gov/dispensary-locat…	New York Office of Cannabis Ma…	new tab	Add '(opens in new tab)' to text

92 links and buttons have descriptive text

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

https://maps.app.goo.gl/WQL8qCDDd5RuvZTa7; https://maps.app.goo.gl/1wroneNFr6a688cx8; https://maps.app.goo.gl/bNCYd2yrJzEdKsJE8; https://maps.app.goo.gl/LnGZiNctcbQAGQgz5; https://maps.app.goo.gl/bjo5zsnbu6rgkg2L7; https://maps.app.goo.gl/jTBVUjuzxHRWHKSi8; https://maps.app.goo.gl/RF3wqYjQx9AVVfXT9; https://maps.app.goo.gl/wTXDBPUfMzdfgRbN9; https://maps.app.goo.gl/QRZ8qpvqC1kYVpKG6; https://maps.app.goo.gl/4Er7XdtAKrT418E8A (+3 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

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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

2 explicit tabindex attribute(s) checked, no anti-patterns

PASS

2 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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+

Mobile-Readable Font Sizes

All 147 visible text node(s) render at >= 12 CSS pixels

PASS

All 147 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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.

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 23 passed

PASS

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
BRONX LOCALS `div.bde-div-16-458 > div.bde-div-16-459 > h2.bde-heading-16-460 > span`
BRONX DISPENSARY `div.bde-div-16-230 > div.bde-div-16-231 > h2.bde-heading-16-232 > span`
STORE HOURS `div.bde-columns-16-256 > div.bde-column-16-257 > div.bde-div-16-258 > div.bde-text-16-259`
DELIVERY HOURS `div.bde-columns-16-256 > div.bde-column-16-261 > div.bde-div-16-262 > div.bde-text-16-263`
Try our cannabis quiz! `div > div.sc-kpDqfm > div > span`

These are opportunities to improve the legibility of your content.

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
VIP Rewards `div.bde-div-47-123 > div.bde-rich-text-47-107 > p > a`
Privacy Policy `div.bde-div-47-123 > div.bde-rich-text-47-107 > p > a`

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

●Links are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

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

○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

○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

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

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