Manifest position 121 · CrUX rank bucket 1000
https://namu.wiki
Coverage complete
Coverage-complete audit of five representative public templates/journeys. Authenticated edit, account, discussion submission and board.namu.wiki flows were not covered because they require separate permissions and/or represent another host.
Attempts
1 / 3
Judged checks
58 / 58
Blocked
0
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | pass | high | Screenshot comparison and computed-style DOM probe under light and dark media. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion evaluate probe found zero active animations and a prefers-reduced-motion rule. |
respect-user-preferencesrespects-contrast | pass | high | High-contrast screenshot showed controls and text remained visible; separate baseline colour failures are recorded under sufficient-contrast. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no view-transition CSS on the home template, despite full-document wiki navigation being the dominant interaction. F03 low: Page and route changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | Platform probe found no scroll-linked animations and observed scrolling had no animation or long-running scroll effect. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile screenshots and repeated native scrolling showed platform scrolling without custom gesture surfaces or pointer-driven motion. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The article is about 25,101 CSS px tall; platform inspection found no scroll timeline or scroll-state styles, while screenshots show only fixed up/down controls. F04 low: Long articles provide jump controls but no scroll-state-aware progress or responsive chrome. |
provide-guided-navigationanchored-positioning | pass | high | No tooltip/popover/menu requiring anchored placement was open on representative paths; native/details disclosure was present and no drifting overlay was observed. |
provide-guided-navigationdirects-attention | pass | high | Article title, section hierarchy, recent-change filters, search result headings and missing-page recovery action directly identify the current state. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a full modal covering the article before interaction; mobile leaves almost no content visible. F01 high: A consent wall obscures the core page on every fresh visit. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM recon found four DIV role=dialog surfaces and no native <dialog>; several hidden preference/vendor surfaces also add duplicate headings. F02 medium: Consent overlays use custom role=dialog containers rather than native dialog semantics. |
maximize-content-reduce-noisereduced-chrome | pass | high | Crawler and post-content screenshots show a compact two-row header and content-dominant wiki layout once the separately-reported consent wall is excluded. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout metrics at 360 px report 0 horizontal overflow on home and a 25k-px article. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Both mobile layouts avoid horizontal overflow, but the platform probe found no @container rules on the template. F05 low: The layout adapts to mobile, but reusable components rely on viewport-level behavior rather than container queries. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused search input computed to outline:none and box-shadow:none; the UI probe found multiple links only 12–17 px high, and axe reported positive tabindex on search. F06 high: Keyboard focus and touch-target support are inconsistent. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, article, recent and search states have descriptive h1/title text and visible next actions. |
support-core-task-successprimary-flow-completion | pass | high | Direct search journey returned 10,000 results with a visible route to the exact 대한민국 article. |
support-core-task-successclear-system-state-and-recovery | pass | high | Missing-document state explicitly says the document cannot be found and offers 새 문서 만들기; search reports result count and timing. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 5.73 s, FCP 4.98 s and performance 65; the independent trace measured LCP 2.29 s, showing substantial condition-dependent delay. F07 high: Cold-load performance is outside the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | Mobile CLS was 0.050 on home and 0.053 on article, within the good threshold despite image sizing risks. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded two long tasks, longest 135 ms and TBT 113.7 ms; the long article mobile layout observed a 165 ms task. F08 medium: Startup includes avoidable long main-thread tasks. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded two redirects and 1.57 MB transferred; DOM confirmation shows adsbygoogle.js in HEAD with async=false/defer=false. Lighthouse estimates 1.51 s render-blocking savings. F09 high: Redirects, blocking styles and an un-deferred ad script delay content delivery. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 663 KiB unused JavaScript and 108 KiB unused CSS; HAR shows scripts account for 1.21 MB of transfer. F10 medium: The page ships large amounts of unused code. |
be-inclusivenames-roles-labels | issues | high | axe reported critical image-alt failures and serious link-name failures; the images probe counted 14 images without alt text. F11 high: Important links and images lack accessible names or alternatives. |
be-inclusivesufficient-contrast | issues | high | axe found green text at 4.46:1 against #1c1d1f and orange links with only 1.66:1 contrast against surrounding text and no non-colour affordance. F12 high: Text links fail minimum contrast and often rely on colour alone. |
be-inclusivestructure-and-focus | issues | high | axe found content outside landmarks, tabindex=1, and unnamed links; the DOM has no main, nav or header elements and the focus probe showed no visible input outline. F13 high: Landmarks and focus order are not robust. |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show readable Korean text, stable wrapping and no horizontal clipping at 360 px. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The rendered meta viewport is user-scalable=no; axe classifies this as critical even though 360 px layouts do not horizontally overflow. F14 critical: The viewport explicitly disables user zoom. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no recorded items. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 25 of 26 images missing a width or height attribute and 14 oversized; mobile layout recorded CLS around 0.05. F15 medium: Most images omit intrinsic dimensions and several are oversized. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported three deprecations from the Cloudflare challenge script and failed valid-source-maps for large first-party JavaScript. F16 medium: Loaded scripts trigger deprecated browser API warnings and large first-party bundles lack source maps. |
be-discoverabletitle-and-description | issues | high | DOM and discoverability evidence found no meta[name=description], and Lighthouse failed the meta-description audit; og:description exists only as social metadata. F17 medium: Pages have descriptive titles but no standard meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse passes crawlable links and robots, while the viewport disables scaling with user-scalable=no. F29 high: The page is crawlable and responsive but not mobile-friendly for users who need zoom. |
be-discoverablecanonical-and-indexing-signals | issues | high | HTTP 200, canonical URL and permissive per-route robots rules were observed; missing sitemap is separately recorded. F18 low: The site exposes no sitemap at the conventional URL. |
be-discoverablestructured-and-shareable-metadata | issues | high | The platform probe found complete og:* tags and zero JSON-LD blocks on an article-like page. F19 low: Article pages provide Open Graph metadata but no structured entity data. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show HSTS and nosniff, but no CSP. Cookie audit found FCCDCF without Secure or HttpOnly, SameSite=None, expiring in about 390 days. F20 high: Transport is HTTPS, but CSP is absent and one long-lived consent cookie is not Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR attributes 26 requests and 805,184 bytes to third parties; trackers found DoubleClick and Google syndication, while the consent copy names 210 partners. F21 high: The default page has a large advertising and tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No notification/geolocation prompt appeared on load and no permission call was observed in representative anonymous paths; authentication was not required for core reading/search. |
be-private-and-securedefensive-browser-policies | issues | high | Headers include HSTS and X-Frame-Options SAMEORIGIN, but omit CSP, Referrer-Policy and Permissions-Policy. F22 medium: Several defensive browser policies are missing. |
be-resilientprogressive-enhancement | pass | high | Article raw HTML returned 200 with title/h1 and 69% rendered-word coverage; crawler screenshot contains the article without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Search, listing, article and missing-document templates rendered usable states with no console errors or clipped horizontal layout. |
be-resilientoffline-and-installable | issues | high | DOM recon found no manifest, while the UI probe reports service-worker support but controlled=false and metadata declares mobile-web-app-capable=yes. F23 low: The app-like wiki advertises mobile capability but has no manifest or active service worker controller. |
be-resilientnetwork-and-http-failure-states | pass | high | The intentionally missing document produced a clear message and recovery action rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The root correctly declares lang=ko, but the English consent dialog and Spanish/Portuguese footer are inside the same language context without nested lang attributes. F24 medium: Substantial non-Korean interface text is not language-scoped. |
be-internationalisedlocale-aware-data | pass | high | RecentChanges renders Korean relative times and the footer exposes the detected Europe/London zone rather than hard-coding a Korean clock. |
be-internationalisedtime-zone-correctness | pass | high | Rendered footer explicitly reports Europe/London for the test environment, showing zone-aware presentation. |
be-trustworthyno-dark-patterns | issues | high | Screenshots show equally prominent Consent and Manage options buttons but no direct Reject all action, while copy requests personalised ads and sharing with 210 partners. F25 high: The first consent surface emphasises acceptance and hides refusal behind settings. |
be-trustworthyhumane-error-handling | pass | high | Search accepts a query and returns a clear count/results state; missing documents provide a recovery action without blaming the user. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | Representative public forms are search/filter controls, not address, payment, sign-in or sign-up fields where autofill tokens apply. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription or authenticated account-management flow was entered in the anonymous representative scope. |
be-sustainableoptimised-assets | issues | high | Images probe found 14 oversized assets, 25 missing at least one intrinsic dimension, 12 below-fold images not lazy-loaded and two legacy PNGs. F26 medium: Image delivery wastes bytes and omits sizing metadata. |
be-sustainableno-wasteful-work | issues | high | Scripts account for 1.21 MB; third parties account for 805 KB, and startup includes long tasks while the primary content is simple text. F27 medium: Advertising and consent work dominates a text-first page load. |
be-sustainablethird-party-and-media-budget | issues | high | More than half of 1.57 MB transferred is third-party, with ad and consent scripts among the largest resources. F28 medium: Third-party transfer is disproportionate to the core wiki experience. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No developer intent or agent-facing transactional capability was identified; the emerging WebMCP opportunity is outside this public wiki audit. |
be-agent-readyon-device-inference | not-applicable | high | No local inference use case is necessary for the core task of reading and searching wiki content. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Same-session probe repeated full-page scroll 10 times: DOM stayed 6023, animations stayed 0 and JS heap changed by only 131,008 bytes. |
be-memory-efficientbounded-footprint | pass | medium | Heap snapshot totals were about 28.9 MB with 6,023 rendered elements, proportionate to a long wiki page plus consent UI. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Ten repeated scroll cycles added zero DOM nodes or animations; independent snapshots differed by only 0.093% self size, with no unbounded-growth signal. |
Provenance
Canonical report: results/atomic/reports/0121-namu_wiki.json
Report SHA-256: 262e2a4e264489ff26efe25826cf5d746902883100eb900de91ed212037927e5
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/namu_wiki/2026-07-18T14-04-37-348Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/namu_wiki/2026-07-18T14-04-37-348Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.