Skip to content
https://stry-kon.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
6
REVIEW
8
PASS
10
INFO
0
Checks
24
10 PASS 8 REVIEW 6 FIX
D
Mobile Keyboard & Autofill
Action
4/4 eligible field(s) missing autocomplete or inputmode
FIX
4/4 eligible field(s) missing autocomplete or inputmode
Warning::
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">, <input type="email" name="email">
Warning::
2 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, tel.
Got: <input type="email" name="email">, <input type="tel" name="phone">
F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ 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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 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
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 header NAV 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

C
Heading Hierarchy
Action
47 headings, 3 skip(s)
REVIEW
47 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Scale Your Brand With Precision Marketing
  • H2 Industries We Scale
  • H3 Roofing Companies
  • H3 Restaurants
  • H3 E-Commerce Stores
  • H3 Local Businesses
  • H3 Healthcare
  • H3 Real Estate
  • H3 Marketing
  • H3 Professional Services
  • H2 Full-Service Digital Suite
  • H3 Social Media Management
  • H3 Social Media Marketing
  • H3 Lead Generation
  • H3 Website Development
  • H3 Google Ads
  • H3 SEO Services
  • H3 AEO
  • H3 Shopify Development
  • H2 Built For Revenue, Not Just Views
  • H4 Senior Expertise Only skipped
  • H4 Future-Proof Tech Integration
  • H4 100% Real-Time Transparency
  • H2 Our 5-Stage Growth Protocol
  • H3 Discovery & Diagnostic Audit
  • H3 Custom Growth Strategy
  • H3 Flawless Campaign Execution
  • H3 Aggressive Ad Optimization
  • H3 Omnichannel Expansion
  • H2 Numbers That Don't Lie
  • H2 High-Converting Interfaces
  • H3 LuxeFashion Shopify Scaling
  • H3 HealthTech Growth Campaign
  • H2 Paid Ads Case Studies
  • H3 Scaling E-Commerce Sales with Meta Advertising
  • H3 Omnichannel Performance Optimization
  • H2 Teaser Pricing Structures
  • H2 What Our Partners Say
  • H4 Zayn Malik skipped
  • H4 Robert Miller
  • H2 Frequently Asked Questions
  • H2 Ready to Outpace the Competition?
  • H2 Connect With Our Strategists
  • H4 Quick Links skipped
  • H4 Services
  • H4 Contact Info
  • H4 Let's Grow Your Business

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

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

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
Form Accessibility
Action
5 of 5 controls have issues
REVIEW
5 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="service">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="name">; <input type="email" name="email">; <input type="tel" name="phone">; <textarea name="message">
5 controls
0 labeled
4 placeholder only
1 unlabeled
ControlTypeLabelMethod
nametext(John Doe)placeholder only
emailemail(john@company.com)placeholder only
phonetel(+1 (555) 000-0000)placeholder only
messagetextarea(Tell us about your project scope & revenue goals...)placeholder only
serviceselect(none)none

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

<select name="service">

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

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

<input type="text" name="name">; <input type="email" name="email">; <input type="tel" name="phone">; <textarea name="message">

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

B
Mobile-Readable Font Sizes
99% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
99% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 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: <div> 10.0px ("Most Popular").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title This Page Does Not Exist ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
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 Scale Your Brand With
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Industries We Scale
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Full-Service
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built For Revenue, Not Just Views
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our 5-Stage Growth Protocol
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Numbers That Don't Lie
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 High-Converting Interfaces
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Paid Ads Case Studies
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Teaser Pricing Structures
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Our Partners Say
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked Questions
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to Outpace the Competition?
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connect With Our Strategists
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Roofing Companies
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Restaurants
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
19px · bottom of viewport
h3 E-Commerce Stores
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Local Businesses
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Healthcare
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Real Estate
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Marketing
1.14:1
#000000
on
#141415
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Scale Your Brand Wit…1.14:13.0:1
#000000
#141415
Fail
h2 Industries We Scale1.14:13.0:1
#000000
#141415
Fail
h2 Full-Service1.14:13.0:1
#000000
#141415
Fail
h2 Built For Revenue, N…1.14:13.0:1
#000000
#141415
Fail
h2 Our 5-Stage Growth P…1.14:13.0:1
#000000
#141415
Fail
h2 Numbers That Don't L…1.14:13.0:1
#000000
#141415
Fail
h2 High-Converting Inte…1.14:13.0:1
#000000
#141415
Fail
h2 Paid Ads Case Studie…1.14:13.0:1
#000000
#141415
Fail
h2 Teaser Pricing Struc…1.14:13.0:1
#000000
#141415
Fail
h2 What Our Partners Sa…1.14:13.0:1
#000000
#141415
Fail
h2 Frequently Asked Que…1.14:13.0:1
#000000
#141415
Fail
h2 Ready to Outpace the…1.14:13.0:1
#000000
#141415
Fail
h2 Connect With Our Str…1.14:13.0:1
#000000
#141415
Fail
h3 Roofing Companies1.14:13.0:1
#000000
#141415
Fail
h3 Restaurants1.14:13.0:1
#000000
#141415
Fail
h3 E-Commerce Stores1.14:13.0:1
#000000
#141415
Fail
h3 Local Businesses1.14:13.0:1
#000000
#141415
Fail
h3 Healthcare1.14:13.0:1
#000000
#141415
Fail
h3 Real Estate1.14:13.0:1
#000000
#141415
Fail
h3 Marketing1.14:13.0:1
#000000
#141415
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 18 passed
REVIEW
86

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
TRUSTED ADVERTISING & TECHNOLOGY PARTNERS body.bg-background > section.py-10 > div.max-w-[1440px] > p.text-xs
INITIATE GROWTH section#contact > div.max-w-[1440px] > div.space-y-6 > span.text-primary
© 2026 StryKon. All Rights Reserved. Digital Craftsmanship. body.bg-background > footer.bg-[#0e0e0f] > div.max-w-[1440px] > p
Privacy Policy footer.bg-[#0e0e0f] > div.max-w-[1440px] > div.flex > a.hover:text-white
Terms of Service footer.bg-[#0e0e0f] > div.max-w-[1440px] > div.flex > a.hover:text-white

These are opportunities to improve the legibility of your content.

Navigation

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
Senior Expertise Only div.space-y-4 > div.flex > div > h4.text-white
Zayn Malik div.max-w-3xl > div.testimonial-card > div > h4.text-white
QUICK LINKS footer.bg-[#0e0e0f] > div.max-w-[1440px] > div.space-y-4 > h4.font-bold

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Social Media Management Social Media Marketing Lead Generation Website Developm… form#leadForm > div.grid > div > select.w-full

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

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>`
●`[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
●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 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.
●Elements with visible text labels have matching accessible names.
○`[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-hidden="true"]` elements do not contain focusable descendents
○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
○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.
○Identical links have the same purpose.
○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
All 47 heading(s) have substantive, well-formed text
PASS
All 47 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
8 image(s) with good alt text
8 images 8 good alt text
All images have appropriate alt text.
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
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
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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+
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