Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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 ✗

Mobile Keyboard & Autofill

Action

1/2 eligible field(s) missing autocomplete or inputmode

REVIEW

1/2 eligible field(s) missing autocomplete or inputmode

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

Got: <input type="email" name="email" id="email-yui_3_17_2_1_1558652237178_10054-field">

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 mick blue ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only

h1 ABOUT MICK BLUE

1.09:1

#000000

#0C0E14

needs 3.0:1 (large text)

32px · mid-page

h2 I have been an actor in the entertainmen…

1.49:1

#000000

#202C3D

needs 3.0:1 (large text)

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

h2 Don't miss out...

1.08:1

#000000

#090E13

needs 3.0:1 (large text)

24px · bottom of viewport

title mick blue

1.03:1

#000000

#020505

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to Content

1.04:1

#000000

#050806

needs 4.5:1 (normal text)

16px · top of page (header area)

a Resume

1.04:1

#000000

#030706

needs 4.5:1 (normal text)

16px · top of page (header area)

a Contact

1.03:1

#000000

#030606

needs 4.5:1 (normal text)

16px · top of page (header area)

span Open Menu

1.03:1

#000000

#030605

needs 4.5:1 (normal text)

16px · above the fold

span Close Menu

1.04:1

#000000

#040706

needs 4.5:1 (normal text)

16px · above the fold

span Open Menu

1.04:1

#000000

#030706

needs 4.5:1 (normal text)

16px · above the fold

span Close Menu

1.04:1

#000000

#040706

needs 4.5:1 (normal text)

16px · above the fold

a Resume

1.03:1

#000000

#020505

needs 4.5:1 (normal text)

16px · above the fold

a Contact

1.04:1

#000000

#030706

needs 4.5:1 (normal text)

16px · above the fold

div Resume

1.90:1

#000000

#383E32

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div Contact

3.07:1

#000000

#4A5C72

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Resume

2.71:1

#000000

#42546B

needs 4.5:1 (normal text)

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

p Mick is a talented actor from Austria wi…

1.07:1

#000000

#090B0F

needs 4.5:1 (normal text)

16px · mid-page

div Newsletter Block

1.21:1

#000000

#131B24

needs 4.5:1 (normal text)

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

div This newsletter signup form needs a stor…

1.28:1

#000000

#19202B

needs 4.5:1 (normal text)

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

6 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 ABOUT MICK BLUE	1.09:1	3.0:1	#000000	#0C0E14	Fail
h2 The Austrian Actor!	3.97:1	3.0:1	#000000	#5A6D87	Pass
h2 I have been an actor…	1.49:1	3.0:1	#000000	#202C3D	Fail
h2 Don't miss out...	1.08:1	3.0:1	#000000	#090E13	Fail
title mick blue	1.03:1	4.5:1	#000000	#020505	Fail
a Skip to Content	1.04:1	4.5:1	#000000	#050806	Fail
a Resume	1.04:1	4.5:1	#000000	#030706	Fail
a Contact	1.03:1	4.5:1	#000000	#030606	Fail
span Open Menu	1.03:1	4.5:1	#000000	#030605	Fail
span Close Menu	1.04:1	4.5:1	#000000	#040706	Fail
span Open Menu	1.04:1	4.5:1	#000000	#030706	Fail
span Close Menu	1.04:1	4.5:1	#000000	#040706	Fail
a Resume	1.03:1	4.5:1	#000000	#020505	Fail
a Contact	1.04:1	4.5:1	#000000	#030706	Fail
div Resume	1.90:1	4.5:1	#000000	#383E32	Fail
div Contact	3.07:1	4.5:1	#000000	#4A5C72	Fail
a Resume	2.71:1	4.5:1	#000000	#42546B	Fail
p Mick is a talented a…	1.07:1	4.5:1	#000000	#090B0F	Fail
div Newsletter Block	1.21:1	4.5:1	#000000	#131B24	Fail
div This newsletter sign…	1.28:1	4.5:1	#000000	#19202B	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.

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

4 <nav> landmark(s) found

4 of 4 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

5 headings, 1 skip(s)

PASS

5 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H2 The Austrian Actor!
H2 I have been an actor in the entertainment industry for 23 years!
H1 ABOUT MICK BLUE
H2 Don't miss out...
H4 MICK BLUE skipped

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 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: 2 all-caps heading(s)

Alt Text Quality

2 of 6 images have issues

PASS

2 of 6 images have issues

2 image(s) with filename as alt text

2 decorative image(s) correctly marked

2 image(s) with good alt text

6 images 2 good alt text 2 decorative 2 generic

Issue	Count
filename	2 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#email-yui_3_17_2_1_1558652237178_10054-field	email	Email Address	for/id

Link & Button Quality

23 links, 3 buttons — all OK

PASS

23 links, 3 buttons — all OK

10 link(s) open in new tab without warning

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

Got: https://www.instagram.com/mickblueracing/; https://www.youtube.com/@mickblue7496; https://www.instagram.com/mickblueracing/; https://www.youtube.com/@mickblue7496; https://www.instagram.com/mickblueracing/; https://www.youtube.com/@mickblue7496; /resume; https://aishahopkins.com; https://www.instagram.com/mickblueracing/; https://www.youtube.com/@mickblue7496

13 link(s) with descriptive text

23 links

0 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/mickblueracing…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@mickblue7496	YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/mickblueracing…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@mickblue7496	YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/mickblueracing…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@mickblue7496	YouTube	new tab	Add '(opens in new tab)' to text
/resume	Resume	new tab	Add '(opens in new tab)' to text
https://aishahopkins.com	Aisha Hopkins Management	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/mickblueracing…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@mickblue7496	YouTube	new tab	Add '(opens in new tab)' to text

16 links and buttons have descriptive text

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

https://www.instagram.com/mickblueracing/; https://www.youtube.com/@mickblue7496; https://www.instagram.com/mickblueracing/; https://www.youtube.com/@mickblue7496; https://www.instagram.com/mickblueracing/; https://www.youtube.com/@mickblue7496; /resume; https://aishahopkins.com; https://www.instagram.com/mickblueracing/; https://www.youtube.com/@mickblue7496

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

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

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

All form input semantics look correct

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

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

All 16 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 94/100 — 2 failing, 20 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
Resume `div#block-7881141a3b9e710efa19 > div#yui_3_17_2_1_1793709078644_72 > div#yui_3_17_2_1_1793709078644_71 > a.sqs-block-button-element--large`

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
MICK BLUE `div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > h4`

These are opportunities to improve keyboard navigation in your application.

○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

●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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

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

○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

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

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

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