Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 5 REVIEW 5 FIX

Alt Text Quality

Action

18 of 38 images have issues

FIX

18 of 38 images have issues

18 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

An image inside a link with no alt creates an empty link.

8 decorative image(s) correctly marked

12 image(s) with good alt text

38 images 12 good alt text 8 decorative 18 missing

Issue	Count
missing	18 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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

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.

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: #027be3

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 ✗

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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

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

Heading Hierarchy

2 headings

REVIEW

2 headings

No H1 heading found

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

H2 Jendela Pencegahan
H2 Pelayanan Publik

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

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (2 below threshold)

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: <button> 0.0px ("Previous"); <button> 0.0px ("Next").

Favicon & Branding

13 icon(s) detected

REVIEW

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

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Action

Score 76/100 — 5 failing, 17 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.

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.full-width > div.row > div.row > button.q-btn `div.full-width > div.row > div.row > button.q-btn`
search `div.full-width > div.row > div.row > button.q-btn`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.flex > div.self-center > img.self-center `div.flex > div.flex > div.self-center > img.self-center`
div.row > div.q-avatar > div.q-avatar__content > img `div.row > div.q-avatar > div.q-avatar__content > img`
div.cursor-pointer > div.q-avatar > div.q-avatar__content > img `div.cursor-pointer > div.q-avatar > div.q-avatar__content > img`
div.cursor-pointer > div.q-avatar > div.q-avatar__content > img `div.cursor-pointer > div.q-avatar > div.q-avatar__content > img`
div.cursor-pointer > div.q-avatar > div.q-avatar__content > img `div.cursor-pointer > div.q-avatar > div.q-avatar__content > img`
div.cursor-pointer > div.q-avatar > div.q-avatar__content > img `div.cursor-pointer > div.q-avatar > div.q-avatar__content > img`
div.cursor-pointer > div.q-avatar > div.q-avatar__content > img `div.cursor-pointer > div.q-avatar > div.q-avatar__content > img`
div.cursor-pointer > div.q-avatar > div.q-avatar__content > img `div.cursor-pointer > div.q-avatar > div.q-avatar__content > img`

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
Tentang JAGA.ID `div.col > div.relative-position > div.q-card__section > div.text-h6`
Sebuah portal informasi publik mengenai pencegahan korupsi yang diinisiasi oleh… `div.col > div.relative-position > div.q-card__section > div.q-my-md`
portal informasi publik `div.relative-position > div.q-card__section > div.q-my-md > strong`
Partisipasi, Akuntabilitas, Respon, `div.relative-position > div.q-card__section > div.q-my-md > strong`
Transparasi `div.relative-position > div.q-card__section > div.q-my-md > strong`
Jaringan Pencegahan Korupsi Indonesia (JAGA.ID). `div.relative-position > div.q-card__section > div.q-my-md > strong`
Mengapa SPI Diperlukan `div.q-expansion-item__container > div.q-item > div.q-item__section > div.q-item__label`
Rentan `div.col > div.row > div.col > div.text-grey-spi`
Waspada `div.col > div.row > div.col > div.text-grey-spi`
terJAGA `div.col > div.row > div.col > div.text-grey-spi`
Umum `div.q-card__section > div.q-card__section > div.q-mx-md > div.berita-category`
Lainnya `button.q-btn > span.q-btn__wrapper > span.q-btn__content > span.block`
Lainnya `div.row > button.q-btn > span.q-btn__wrapper > span.q-btn__content`
SAYa yang bertanda tangan di bawah ini Nama Paulus Gunardi Agung ingin menyampa… `div > div.home-mobile-card > div.text-three-line > p`
Keluhan `div.q-pt-sm > div > div.home-mobile-card > div.berita-category`
Beranda `div.col > div#goToHome > div.row > label.text-red`
Berita `div.col > div#goToBerita > div.row > label.text-grey`
KELUHAN `div.col > div#goToCreateKeluhan > div.row > label.text-red`
Panduan `div.col > div#goToTentang > div.row > label.text-grey`
Forum `div.col > div#goToListDiskusi > div.row > label.text-grey`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

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

●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

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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

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

○Form elements have associated labels

○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

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

○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 2 heading(s) have substantive, well-formed text

PASS

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

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

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
#f_c0519272-35d7-4133-9f87-207905fb5160	input	ID	none

Link & Button Quality

1 issue(s) across 20 links and 23 buttons

PASS

1 issue(s) across 20 links and 23 buttons

1 link(s) with no accessible text

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

Got: https://www.kpk.go.id/id/

19 link(s) with descriptive text

20 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.kpk.go.id/id/	(empty)	empty	Add link text or aria-label

42 links and buttons have descriptive text

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

https://www.kpk.go.id/id/

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

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-us"

PASS

Lang attribute set to "en-us"

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

Got: en-us

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <button id="slick-slide-control11">

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 id="slick-slide-control12">

Iframe Accessibility

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

PASS

1/1 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+

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Jaga

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Jaga ✓192×192 icon ✓512×512 icon ✓Start URL . ✓Display Mode standalone ✓

Name Jaga Display Mode standalone Theme Color #027be3 Background Color #ffffff Icons 5 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

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

2 mobile-depth signal(s) detected

PASS

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

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
h2 Jendela Pencegahan	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Pelayanan Publik	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title JAGA - Platform Penc…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Jendela Pencegahan	21.00:1	4.5:1	#000000	#FFFFFF	Pass
i expand_more	20.82:1	4.5:1	#000000	#FEFEFE	Pass
div Pelayanan Publik	21.00:1	4.5:1	#000000	#FFFFFF	Pass
i expand_more	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Diskusi	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Keluhan	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Berita Jaga	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Hasil Kajian KPK	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Pedoman Pencegahan K…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Tentang	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Jendela Pencegahan	21.00:1	4.5:1	#000000	#FFFFFF	Pass
i expand_more	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Pelayanan Publik	21.00:1	4.5:1	#000000	#FFFFFF	Pass
i expand_more	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Forum	21.00:1	4.5:1	#000000	#FFFFFF	Pass
i expand_more	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Lainnya	21.00:1	4.5:1	#000000	#FFFFFF	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.

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