Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 8 REVIEW 5 FIX

Landmark Structure

Action

7 landmarks

FIX

7 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 banner (header) 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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.melbournepolytechnic.edu.au/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.melbournepolytechnic.edu.au/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #ffffff

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

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

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Heading Hierarchy

14 headings

REVIEW

14 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Melbourne Polytechnic Graduation 2026
H2 Free TAFE
H2 We're Training Provider of the Year
H2 Melbourne Polytechnic Graduation 2026
H2 Courses at Melbourne Polytechnic
H3 Find your course
H3 Start in July
H3 Free TAFE
H3 Information Sessions
H2 Supporting your study and career journey
H3 Skills and Jobs Centre
H3 Scholarships
H3 Student support services
H3 Student Jobs Board

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Link & Button Quality

Action

3 issue(s) across 298 links and 63 buttons

REVIEW

3 issue(s) across 298 links and 63 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a (#1437 on page)

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /about-us/news-and-events/news/2024-large-training-provider-award/ ("Read more")

11 link(s) open in new tab without warning

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

Got: https://www.facebook.com/MelbournePolytechnic; https://www.linkedin.com/school/melbourne-polytechnic/; https://www.youtube.com/channel/UClePEnOnePHra3IZRqpJMRQ; https://instagram.com/melbpoly; https://policies.melbournepolytechnic.edu.au; https://www.facebook.com/MelbournePolytechnic; https://www.linkedin.com/school/melbourne-polytechnic/; https://www.youtube.com/channel/UClePEnOnePHra3IZRqpJMRQ; https://instagram.com/melbpoly; https://www.calicoagency.com.au/ (+1 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.header__menu-butt (#1064 on page)

285 link(s) with descriptive text

298 links

1 empty

1 generic text

11 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/MelbournePolyte…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/melbourn…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UClePEnO…	YouTube	new tab	Add '(opens in new tab)' to text
https://instagram.com/melbpoly	Instagram	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
/about-us/news-and-events/news/2024-larg…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: 2024 Large Training Provider Award
https://policies.melbournepolytechnic.ed…	Policies and Procedures	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/MelbournePolyte…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/melbourn…	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UClePEnO…	YouTube	new tab	Add '(opens in new tab)' to text
https://instagram.com/melbpoly	Instagram	new tab	Add '(opens in new tab)' to text
https://www.calicoagency.com.au/	Digital Agency - Calico	new tab	Add '(opens in new tab)' to text
https://www.calicoagency.com.au/	Digital Agency - Calico	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

347 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a (#1437 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/about-us/news-and-events/news/2024-large-training-provider-award/ ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.facebook.com/MelbournePolytechnic; https://www.linkedin.com/school/melbourne-polytechnic/; https://www.youtube.com/channel/UClePEnOnePHra3IZRqpJMRQ; https://instagram.com/melbpoly; https://policies.melbournepolytechnic.edu.au; https://www.facebook.com/MelbournePolytechnic; https://www.linkedin.com/school/melbourne-polytechnic/; https://www.youtube.com/channel/UClePEnOnePHra3IZRqpJMRQ; https://instagram.com/melbpoly; https://www.calicoagency.com.au/ (+1 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

Icon-only buttons need an aria-label so screen readers can announce them.

button.header__menu-butt (#1064 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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.

Mobile-Readable Font Sizes

Action

84% of visible text renders at >= 12 CSS px (23 below threshold)

REVIEW

84% of visible text renders at >= 12 CSS px (23 below threshold)

23 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: <button> 11.0px ("Close"); <button> 11.0px ("Back"); <button> 11.0px ("Back"); <button> 11.0px ("Back"); <button> 11.0px ("Back").

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

Favicon & Branding

14 icon(s) detected

REVIEW

14 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA

button Locations

3.15:1

#000000

#5B587F

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

button Students

1.17:1

#000000

#110A4A

needs 4.5:1 (normal text)

16px · above the fold

button Industry and Partnerships

1.32:1

#000000

#19175C

needs 4.5:1 (normal text)

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

span About Us

1.17:1

#000000

#110A4A

needs 4.5:1 (normal text)

16px · above the fold

a Contact Us

1.17:1

#000000

#110A4A

needs 4.5:1 (normal text)

16px · above the fold

span Current Students

1.21:1

#000000

#140F4F

needs 4.5:1 (normal text)

16px · above the fold

span Staff

1.29:1

#000000

#18155A

needs 4.5:1 (normal text)

16px · above the fold

button Back

1.17:1

#000000

#110B4A

needs 4.5:1 (normal text)

16px · above the fold

div Study with Us

1.17:1

#000000

#110B4A

needs 4.5:1 (normal text)

16px · above the fold

2 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
h3 Find your course	18.99:1	3.0:1	#000000	#E5F7F8	Pass
h3 Start in July	18.99:1	3.0:1	#000000	#E5F7F8	Pass
h3 Free TAFE	18.99:1	3.0:1	#000000	#E5F7F8	Pass
h3 Information Sessions	18.99:1	3.0:1	#000000	#E5F7F8	Pass
h3 Skills and Jobs Cent…	18.99:1	3.0:1	#000000	#E5F7F8	Pass
h3 Scholarships	18.99:1	3.0:1	#000000	#E5F7F8	Pass
h3 Student support serv…	18.99:1	3.0:1	#000000	#E5F7F8	Pass
h3 Student Jobs Board	18.99:1	3.0:1	#000000	#E5F7F8	Pass
title Melbourne Polytechni…	16.17:1	4.5:1	#000000	#E1E2E1	Pass
button Close	18.93:1	4.5:1	#000000	#F3F3F3	Pass
button Study with Us	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Locations	3.15:1	4.5:1	#000000	#5B587F	Fail
button Students	1.17:1	4.5:1	#000000	#110A4A	Fail
button Industry and Partner…	1.32:1	4.5:1	#000000	#19175C	Fail
span About Us	1.17:1	4.5:1	#000000	#110A4A	Fail
a Contact Us	1.17:1	4.5:1	#000000	#110A4A	Fail
span Current Students	1.21:1	4.5:1	#000000	#140F4F	Fail
span Staff	1.29:1	4.5:1	#000000	#18155A	Fail
button Back	1.17:1	4.5:1	#000000	#110B4A	Fail
div Study with Us	1.17:1	4.5:1	#000000	#110B4A	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.

Lighthouse Accessibility Audits

Score 83/100 — 5 failing, 23 passed

REVIEW

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Melbourne Polytechnic Graduation 2026 Watch the 2026 Melbourne Polytechnic Grad… `div#tns1-ow > div#tns1-iw > div#tns1 > div#tns1-item0`
We're Training Provider of the Year Melbourne Polytechnic was named Large Train… `div#tns1-ow > div#tns1-iw > div#tns1 > div#tns1-item2`
Melbourne Polytechnic Graduation 2026 Watch the 2026 Melbourne Polytechnic Grad… `div#tns1-ow > div#tns1-iw > div#tns1 > div.home-carousel__slide`

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.header__main > div.header__main-inner > div.header__menu-toggle > button.header__menu-butt `div.header__main > div.header__main-inner > div.header__menu-toggle > button.header__menu-butt`

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
SEE THE COURSES `div#tns1-item1 > div.home-carousel__info > div.home-carousel__info-inner > a.home-carousel__butt`
Find your course `div.cards-block__cards > a.cards-block__card > div.cards-block__card-info > h3`
Start in July `div.cards-block__cards > a.cards-block__card > div.cards-block__card-info > h3`
Free TAFE `div.cards-block__cards > a.cards-block__card > div.cards-block__card-info > h3`
Information Sessions `div.cards-block__cards > a.cards-block__card > div.cards-block__card-info > h3`
Skills and Jobs Centre `div.cards-block__cards > a.cards-block__card > div.cards-block__card-info > h3`
Scholarships `div.cards-block__cards > a.cards-block__card > div.cards-block__card-info > h3`
Student support services `div.cards-block__cards > a.cards-block__card > div.cards-block__card-info > h3`
Student Jobs Board `div.cards-block__cards > a.cards-block__card > div.cards-block__card-info > h3`
Call Us 1300 635 276 `div.footer__pre > div.footer__pre-inner > a.footer__pre-link > span`
Ask us a question `div.footer__pre > div.footer__pre-inner > a.footer__pre-link > span`
Attend an Info Session `div.footer__pre > div.footer__pre-inner > a.footer__pre-link > 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
Search `form.mp-search-bar__form > div.mp-search-bar__controls > label.mp-search-bar__search > a.mp-search-bar__search-icon`
Home `div.footer__copy-inner > div.footer__copy-text > span.footer__copy-links > 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

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Links are distinguishable without relying on color.

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

○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

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

PASS

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

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

A+

Alt Text Quality

All 21 images OK

PASS

All 21 images OK

2 decorative image(s) correctly marked

19 image(s) with good alt text

21 images 19 good alt text 2 decorative

All images have appropriate alt text.

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 controls have issues

1 control(s) rely on placeholder only

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

Got: <input name="query">

2 control(s) properly labeled

3 controls

2 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
query	input	Search	aria-label
#query	text		none
query	input	(Search for a course)	placeholder only

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

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

Form Input Types

3 input(s) using type=text where a specific type would help

PASS

3 input(s) using type=text where a specific type would help

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<html lang="en"> is set and valid

Got: en

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

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

tabindex="-1" on naturally-focusable <button>

Iframe Accessibility

1/3 iframe(s) missing title; 0 placeholder(s)

PASS

1/3 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

3 mobile-depth signal(s) detected

PASS

3 mobile-depth signal(s) detected

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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