Skip to content
https://Dylankotzer.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
6
PASS
13
INFO
0
Checks
24
13 PASS 6 REVIEW 5 FIX
D
Landmark Structure
Action
No landmarks
FIX
No 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
Info::
No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-bfqck4
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #000000
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 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.

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.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Mobile-Readable Font Sizes
91% of visible text renders at >= 12 CSS px (2 below threshold)
REVIEW
91% of visible text renders at >= 12 CSS px (2 below threshold)
Info::
2 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: <p> 9.6px ("main"); <p> 9.6px ("Prettier").
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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
title Dylan
2.30:1
#000000
on
#494847
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span EXPLORER
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
div Home
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
div overview.md
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
div skills.jsx
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
div experience.js
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
div education.ts
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
div projects.py
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
div calendly.html
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
button overview.md
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
button skills.jsx
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
button experience.js
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
button education.ts
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
button projects.py
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · mid-page
button calendly.html
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · mid-page
p Hi! I'm DylanGPT, an AI assistant that c…
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · mid-page
p Tell me about your AI experience
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · mid-page
p Can I hire you?
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · mid-page
p Tell me more about your recent projects.
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · mid-page
p What's your favorite tech stack?
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · mid-page

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)
ElementRatioRequiredFGBGResult
title Dylan2.30:14.5:1
#000000
#494847
Fail
span EXPLORER1.26:14.5:1
#000000
#1E1E1E
Fail
div Home1.26:14.5:1
#000000
#1E1E1E
Fail
div overview.md1.26:14.5:1
#000000
#1E1E1E
Fail
div skills.jsx1.26:14.5:1
#000000
#1E1E1E
Fail
div experience.js1.26:14.5:1
#000000
#1E1E1E
Fail
div education.ts1.26:14.5:1
#000000
#1E1E1E
Fail
div projects.py1.26:14.5:1
#000000
#1E1E1E
Fail
div calendly.html1.26:14.5:1
#000000
#1E1E1E
Fail
button overview.md1.26:14.5:1
#000000
#1E1E1E
Fail
button skills.jsx1.26:14.5:1
#000000
#1E1E1E
Fail
button experience.js1.26:14.5:1
#000000
#1E1E1E
Fail
button education.ts1.26:14.5:1
#000000
#1E1E1E
Fail
button projects.py1.26:14.5:1
#000000
#1E1E1E
Fail
button calendly.html1.26:14.5:1
#000000
#1E1E1E
Fail
p Hi! I'm DylanGPT, an…1.26:14.5:1
#000000
#1E1E1E
Fail
p Tell me about your A…1.26:14.5:1
#000000
#1E1E1E
Fail
p Can I hire you?1.26:14.5:1
#000000
#1E1E1E
Fail
p Tell me more about y…1.26:14.5:1
#000000
#1E1E1E
Fail
p What's your favorite…1.26:14.5:1
#000000
#1E1E1E
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 84/100 — 4 failing, 19 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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Turn on the light div.MuiGrid-root > div.MuiPaper-root > div.MuiBox-root > div.MuiBox-root

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.MuiPaper-root > div.MuiBox-root > div.info-trigger > button.MuiButtonBase-root div.MuiPaper-root > div.MuiBox-root > div.info-trigger > button.MuiButtonBase-root
div.MuiContainer-root > div.MuiPaper-root > div.MuiBox-root > button.MuiButtonBase-root div.MuiContainer-root > div.MuiPaper-root > div.MuiBox-root > button.MuiButtonBase-root

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.

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
overview.md div.MuiGrid-root > div.MuiContainer-root > div.MuiBox-root > button.MuiButton-root
skills.jsx div.MuiGrid-root > div.MuiContainer-root > div.MuiBox-root > button.MuiButton-root
experience.js div.MuiGrid-root > div.MuiContainer-root > div.MuiBox-root > button.MuiButton-root
education.ts div.MuiGrid-root > div.MuiContainer-root > div.MuiBox-root > button.MuiButton-root
projects.py div.MuiGrid-root > div.MuiContainer-root > div.MuiBox-root > button.MuiButton-root
calendly.html div.MuiGrid-root > div.MuiContainer-root > div.MuiBox-root > button.MuiButton-root
DylanGPT Ready div.MuiGrid-root > div.MuiContainer-root > div.MuiPaper-root > div.MuiBox-root
main div.MuiGrid-root > div.css-1tl3wyk > a.MuiTypography-root > p.MuiTypography-root
Prettier div.MuiBox-root > div.css-1vznupw > div.MuiBox-root > p.MuiTypography-root

These are opportunities to improve the legibility of your content.

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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●The page contains a heading, skip link, or landmark region
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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
○Heading elements appear in a sequentially-descending order
○`<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.
○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
○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 Text Quality
No headings to evaluate -- check is N/A
PASS
No headings to evaluate -- check is N/A
Info::
No headings to evaluate -- check is N/A
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea id=":r7:">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#:r7:textarea(Ask me anything about Dylan's experience and skills...)placeholder only

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

<textarea id=":r7:">

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

A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <textarea>
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
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Create React App Sample
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Create React App Sample ✓192×192 icon ✓512×512 icon ✓Start URL . ✓Display Mode standalone ✓
Name Create React App Sample Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 3 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback