Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 4 REVIEW 3 FIX

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: https://foodqualityvault.com/images/food-quality-vault-social-share.png

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 ✗

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)

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: <span> 10.0px ("Engineering Portal").

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

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 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 Present

✓ Multiple Sizes Present

PWA Depth

2 PWA signal(s) surfaced

REVIEW

2 PWA signal(s) surfaced

Manifest declares display="browser" -- no PWA UX

When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).

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+

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

31 headings, 1 skip(s)

PASS

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

H3 Safety & Hazards (1–6)
H3 Operations & Advanced (7–12)
H1 Global Food Quality & Safety Vault
H2 Digital HACCP & Biosecurity Engineering
H3 Digital HACCP, IoT & AI Quality Assurance
H3 Food Defense, Fraud & Cyber-Biosecurity
H2 Master Vault Curriculum Overview (Pillars 1–12)
H2 From Hazard Recognition to Verified Process Control
H2 Key Takeaways
H2 Table of Contents
H3 Start with the Science
H3 Map the Process
H3 Control the Significant Risks
H3 Verify, Validate, Improve
H2 What Strong Quality Systems Look Like in Practice
H3 A practical review sequence for food safety teams
H2 Built for Learners, Practitioners, and Technical Review
H2 Turning Food Safety Records into Useful Evidence
H3 Trend, Don't Just File
H3 Investigate the System
H3 Close the Learning Loop
H2 Food Quality Begins Before Production
H2 Authoritative sources for independent verification
H2 Questions and Answers
H3 What does Digital HACCP & Biosecurity Engineering mean in this guide?
H3 How should you use this information in practice?
H2 Conclusion and Recommended Next Step
H4 Learning Pillars skipped
H4 Legal & Compliance
H4 Direct Communication
H3 Search Food Quality Vault

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

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

PASS

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

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

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 decorative image(s) correctly marked

5 images 5 decorative

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search" id="vault-search-input">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#vault-search-input	search	(Search modules, pillars, pathogens, regulations, methods...)	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

Link & Button Quality

55 links, 3 buttons — all OK

PASS

55 links, 3 buttons — all OK

7 link(s) open in new tab without warning

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

Got: https://www.fda.gov/food/nutrition-food-labeling-and-critical-foods/food-alle…; https://eur-lex.europa.eu/eli/reg/2011/1169/oj; https://www.facebook.com/profile.php?id=61595625471561; https://www.youtube.com/@FOODQUALITYVAULT; https://x.com/foodqvault; https://www.linkedin.com/in/food-quality-vault-a91154404; https://www.instagram.com/foodqualityvault/

48 link(s) with descriptive text

55 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.fda.gov/food/nutrition-food-…	US FDA — Food Allergies and …	new tab	Add '(opens in new tab)' to text
https://eur-lex.europa.eu/eli/reg/2011/1…	EU Regulation (EU) No 1169/201…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	Food Quality Vault on Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@FOODQUALITYVAUL…	Food Quality Vault on YouTube	new tab	Add '(opens in new tab)' to text
https://x.com/foodqvault	Food Quality Vault on X	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/food-quality…	Food Quality Vault on LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/foodqualityvau…	Food Quality Vault on Instagra…	new tab	Add '(opens in new tab)' to text

51 links and buttons have descriptive text

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

https://www.fda.gov/food/nutrition-food-labeling-and-critical-foods/food-alle…; https://eur-lex.europa.eu/eli/reg/2011/1169/oj; https://www.facebook.com/profile.php?id=61595625471561; https://www.youtube.com/@FOODQUALITYVAULT; https://x.com/foodqvault; https://www.linkedin.com/in/food-quality-vault-a91154404; https://www.instagram.com/foodqualityvault/

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+

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

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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

Web Manifest

Valid manifest

PASS

Valid manifest

Name present: Food Quality Vault

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name Food Quality Vault ✓192×192 icon ✓512×512 icon ✓Start URL ./ ✓Display Mode browser ✗

Name Food Quality Vault Display Mode browser Theme Color #eab308 Background Color #ffffff Icons 2 icon(s)

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Global Food Quality …	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Digital HACCP & Bios…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Master Vault Curricu…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 From Hazard Recognit…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Key Takeaways	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Table of Contents	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 What Strong Quality …	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Built for Learners, …	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Turning Food Safety …	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Food Quality Begins …	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Authoritative source…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Questions and Answer…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h2 Conclusion and Recom…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h3 Safety & Hazards (1�…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h3 Operations & Advance…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h3 Digital HACCP, IoT &…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h3 Food Defense, Fraud …	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h3 Start with the Scien…	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h3 Map the Process	19.11:1	3.0:1	#000000	#F4F4F5	Pass
h3 Control the Signific…	19.11:1	3.0:1	#000000	#F4F4F5	Pass

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 93/100 — 3 failing, 19 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
VAULT `a.flex > div > span.text-lg > span.text-yellow-600`

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
LEARNING PILLARS `div.max-w-7xl > div.grid > div > h4.text-white`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FOOD QUALITY VAULT ENGINEERING PORTAL `body.bg-[#f4f4f5] > header#navbar > div.max-w-7xl > a.flex`

○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

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

●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 are distinguishable without relying on color.

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

●Skip links are focusable.

●Document has a main landmark.

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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