Skip to content
https://karinderya.org

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
87
GRADE
B
FIX
3
REVIEW
4
PASS
17
INFO
0
Checks
24
17 PASS 4 REVIEW 3 FIX
D
Mobile-Readable Font Sizes
Action
55% of visible text renders at >= 12 CSS px (84 below threshold)
FIX
55% of visible text renders at >= 12 CSS px (84 below threshold)
Warning::
84 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: <small> 9.3px ("FIELD GUIDE"); <div> 11.2px ("KARINDERYA FIELD GUIDE / CHECKED 2026-08..."); <small> 10.0px ("CODES, WORKERS, UPDATES & GUIDES"); <p> 11.5px ("Independent fan guide · Current public i..."); <span> 9.9px ("SHIFT CONTROL // KDY-01").
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404: This page could not be found. Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color #061217 CSS indicators Detected

Detection limited to meta tags and inline styles.

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 KARINDERYA
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 What is current right now
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pick the problem you can see
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Upgrade the queue, not the room
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Close one table from start to finish
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Use the smallest useful answer
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Know which link is official
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Before the next shift
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Run the shift
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Field manual
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Site desk
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Check current codes
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Track the latest update
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Measure the shift
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Clear the first loop
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Seat
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Assign
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cook
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Serve
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Collect
1.16:1
#000000
on
#06181E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 KARINDERYA1.16:13.0:1
#000000
#06181E
Fail
h2 What is current righ…1.16:13.0:1
#000000
#06181E
Fail
h2 Pick the problem you…1.16:13.0:1
#000000
#06181E
Fail
h2 Upgrade the queue, n…1.16:13.0:1
#000000
#06181E
Fail
h2 Close one table from…1.16:13.0:1
#000000
#06181E
Fail
h2 Use the smallest use…1.16:13.0:1
#000000
#06181E
Fail
h2 Know which link is o…1.16:13.0:1
#000000
#06181E
Fail
h2 Before the next shif…1.16:13.0:1
#000000
#06181E
Fail
h2 Run the shift1.16:13.0:1
#000000
#06181E
Fail
h2 Field manual1.16:13.0:1
#000000
#06181E
Fail
h2 Site desk1.16:13.0:1
#000000
#06181E
Fail
h3 Check current codes1.16:13.0:1
#000000
#06181E
Fail
h3 Track the latest upd…1.16:13.0:1
#000000
#06181E
Fail
h3 Measure the shift1.16:13.0:1
#000000
#06181E
Fail
h3 Clear the first loop1.16:13.0:1
#000000
#06181E
Fail
h3 Seat1.16:13.0:1
#000000
#06181E
Fail
h3 Assign1.16:13.0:1
#000000
#06181E
Fail
h3 Cook1.16:13.0:1
#000000
#06181E
Fail
h3 Serve1.16:13.0:1
#000000
#06181E
Fail
h3 Collect1.16:13.0:1
#000000
#06181E
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.

A
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #main-content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN ASIDE "Karinderya shift control preview" CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+
Heading Hierarchy
23 headings
PASS
23 headings
Info::
Single H1 present
  • H1 KARINDERYAROBLOX WIKI:CODES, WORKERS, UPDATES & GUIDES
  • H2 What is current right now
  • H2 Pick the problem you can see
  • H3 Check current codes
  • H3 Track the latest update
  • H3 Measure the shift
  • H3 Clear the first loop
  • H2 Upgrade the queue, not the room
  • H2 Close one table from start to finish
  • H3 Seat
  • H3 Assign
  • H3 Cook
  • H3 Serve
  • H3 Collect
  • H2 Use the smallest useful answer
  • H3 2 official + 1 reported
  • H3 Fix the task in front of you
  • H3 Know what each system does
  • H2 Know which link is official
  • H2 Before the next shift
  • H2 Run the shift
  • H2 Field manual
  • H2 Site desk
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 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: 1 all-caps heading(s)
A+
Alt Text Quality
All 4 images OK
PASS
All 4 images OK
Info::
3 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
4 images 1 good alt text 3 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
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
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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: Karinderya Field Guide
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Karinderya Field Guide 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name Karinderya Field Guide Display Mode standalone Theme Color #061217 Background Color #061217 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.
A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 24 passed
PASS
96

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
2 official + 1 reported section.field-metrics > div.site-container > article.metric-cell > small
Tools, guides, wiki section.field-metrics > div.site-container > article.metric-cell > small
Seats + stoves section.field-metrics > div.site-container > article.metric-cell > small
2026 current status section.field-metrics > div.site-container > article.metric-cell > small
01 div.site-container > div.signal-board > div.signal-card > b
02 div.site-container > div.signal-board > div.signal-card > b
karinderya.org · Independent fan resource body.inter_5901b7c6-module__ec5Qua__variable > footer.site-footer > div.site-container > span
Privacy footer.site-footer > div.site-container > span > a
Terms footer.site-footer > div.site-container > span > a
Disclosure footer.site-footer > div.site-container > span > a

These are opportunities to improve the legibility of your content.

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
KARINDERYA FIELD GUIDE body.inter_5901b7c6-module__ec5Qua__variable > header.site-header > div.site-nav-shell > a.site-brand
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
`[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 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
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
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 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
Form elements have associated labels
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.
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.

Send Feedback