Manifest position 783 · CrUX rank bucket 1000
https://fa.wikipedia.org
Coverage complete
Coverage-complete agentic audit of six representative paths; no source was supplied and no fixes were applied.
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 | issues | high | Dark-media screenshot is pixel-equivalent in appearance to the light capture; body remains rgb(248,249,250) and computed color-scheme is normal. F1 medium: System dark preference is ignored. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, the probe found zero active animations on the home page. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast: more screenshot preserves text, links, icons, and borders, and Lighthouse color-contrast passed. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection across home, article, and search found zero view-transition rules; cross-document article navigation is an abrupt swap. F2 low: Article navigation swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The representative pages contain no parallax, scrollytelling, entry/exit reveal, or other scroll-linked animation to implement. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, carousel, or gesture-driven surface exists in the representative reading, search, editing, or sign-in paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 24,793px article has static chrome and CSS inspection found no scroll-state query or scroll progress treatment. F3 low: Long articles provide no scroll-state guidance. |
provide-guided-navigationanchored-positioning | issues | medium | Multiple menu/navigation surfaces are present, while CSS inspection found no anchor positioning or position-try rules. F4 low: Menus do not use modern anchored positioning. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show selected article tabs with persistent underlines, a table of contents, clear section headings, and blue in-page links. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial home, article, and search screenshots contain no load-time interstitial or content-obscuring banner. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The post-action editor welcome modal is a DIV role=dialog without aria-modal; its actions are anchors with role=button, and no dialog/popover element exists. F5 medium: The editor welcome modal is custom rather than a modal dialog primitive. |
maximize-content-reduce-noisereduced-chrome | pass | high | Desktop screenshots devote the dominant region to article or search content; navigation chrome is compact and peripheral. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At requested viewport 360x800 the page declares meta viewport width=1120, producing a 1120 CSS-pixel desktop canvas scaled to 0.321x and tiny text. F6 high: Mobile pages shrink a fixed 1120px desktop canvas instead of reflowing. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found zero @container rules and the same fixed 1120px composition on home and article mobile captures. F7 medium: Reused components have no container-level adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus probe shows a visible 2px outline, but Lighthouse target-size fails and 387 of 405 visible home controls measure under 24px on one axis. F8 high: Most interactive targets are too small for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home and article first viewports clearly identify Wikipedia, the article title, reading surface, search, and edit action. |
support-core-task-successprimary-flow-completion | pass | high | A query reached a populated search-results page; the edit action loaded the editor and welcome dialog within 10 seconds; sign-in exposed its complete form. |
support-core-task-successclear-system-state-and-recovery | pass | high | The editor displays a progress state before becoming usable, and the tested HTTP 404 explains the missing title and offers search, backlinks, purge, and deletion-log recovery links. |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse measured LCP 1.8s, CLS 0, and TBT 10ms; all are in the good lab range. |
be-fast-and-stablevisual-stability | pass | high | Both mobile layout observations report CLS 0 with no recorded shifts; Lighthouse also reports CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | Lighthouse TBT is 10ms; trace recorded one 171.82ms long task and 121.82ms TBT, with no sustained blocking pattern. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records a redirect, two parser-blocking stylesheets, and multiple missing cache headers; Lighthouse estimates 980ms redirect savings and flags render blocking and cache lifetimes. F9 medium: Delivery has avoidable redirect, cache, and render-blocking cost. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 92KiB unused JavaScript and 45KiB unused CSS; the largest script transfers 200,189 bytes. F10 medium: The entry page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails aria-required-attr, image-alt, label, and link-name; the home image audit reports 16 missing alt values and the DOM probe finds an unlabelled search field. F11 high: Accessible names, roles, labels, and alternatives are incomplete. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast passes and preference screenshots retain visible foreground/background separation. |
be-inclusivestructure-and-focus | issues | high | Focus is visibly outlined and landmarks exist, but search results jump from h1 directly to repeated h6 headings and Lighthouse fails definition-list structure and required ARIA attributes. F12 medium: Some document structures do not express a logical reading hierarchy. |
be-inclusivelegible-text | issues | high | Desktop Persian text is readable, but the 360px capture scales the fixed 1120px layout to 0.321x, making article text extremely small. F6 high: Mobile pages shrink a fixed 1120px desktop canvas instead of reflowing. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Meta viewport is fixed at width=1120 and the page shrinks instead of reflowing; Lighthouse target-size fails. No tested path contains audio/video requiring captions. F6 high: Mobile pages shrink a fixed 1120px desktop canvas instead of reflowing. F8 high: Most interactive targets are too small for touch. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passes on the entry page. |
follow-best-practicessound-document-and-assets | issues | high | DOCTYPE html, UTF-8, and image aspect ratios are sound, but Lighthouse reports an unsized image and the image audit identifies one missing dimension. F13 low: At least one image lacks intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports missing source maps for large first-party JavaScript and logged DevTools inspector issues; prompt-on-load and paste-prevention audits pass. F14 low: Debugging/platform hygiene is incomplete. |
be-discoverabletitle-and-description | issues | high | Home, article, search, and edit probes have descriptive titles but no meta description; Lighthouse fails meta-description. F15 medium: Public pages omit meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | All 512 home anchors have hrefs and robots permits article crawling, but the viewport is fixed to width=1120 and is not mobile-friendly. F6 high: Mobile pages shrink a fixed 1120px desktop canvas instead of reflowing. |
be-discoverablecanonical-and-indexing-signals | issues | high | Public home and article responses are 200 with canonical URLs and no noindex, while no hreflang links are exposed for localized variants and /sitemap.xml returns 404. F16 low: Localized article indexing signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | pass | high | Home and article each expose JSON-LD plus Open Graph title/type/image metadata matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff, and CSP are present, but CSP permits unsafe-inline and unsafe-eval; one fawikimwuser-sessionId cookie is not Secure and all seven cookies use SameSite=None. F17 high: CSP and cookie posture leave avoidable exposure. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker scan finds no known trackers or external analytics; third-party requests are limited to Wikimedia upload/auth origins and secrets scan finds none. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission request-on-load signal was found; sign-in uses autocomplete=username webauthn and current-password, with WebAuthn/passkey code present. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS and nosniff are strong, but headers lack Referrer-Policy, Permissions-Policy, X-Frame-Options, and the CSP shown has no frame-ancestors directive. F18 medium: Several browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability captures report 100% raw-HTML content coverage for home and article, with title and h1 present without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Navigation/menu chrome and the editor dialog remain within the viewport in exercised states; repeated menu toggling returns to aria-expanded=false with unchanged DOM count. |
be-resilientoffline-and-installable | not-applicable | high | Persian Wikipedia is a public content MPA rather than an installable app; offline installability is contextual and was not presented as a product goal. |
be-resilientnetwork-and-http-failure-states | pass | high | A real 404 returns HTTP 404 with a clear explanation and actionable search, backlink, purge, and deletion-log recovery options. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All representative pages declare lang=fa and dir=rtl; screenshots demonstrate correct RTL ordering and probes find logical CSS properties in use. |
be-internationalisedlocale-aware-data | pass | medium | Persian interface labels and article numbers/dates are localized, and language-aware server-rendered markup is consistent across representative paths. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative encyclopedia, search, edit, and sign-in pages do not coordinate scheduled events or accept time-zone-sensitive input. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, confirmshaming, forced continuity, disguised advertising, or nagging upsell appears in the tested public paths. |
be-trustworthyhumane-error-handling | pass | high | No-result search and missing-page states explain outcomes without blame and offer clear recovery; editor loading gives visible progress. |
be-trustworthytrustworthy-input-assistance | pass | high | Sign-in fields are labelled and use autocomplete=username webauthn and current-password; search fields use the search input type. |
be-trustworthysafe-commercial-and-account-flows | pass | high | No commercial flow exists; the relevant sign-in flow clearly labels credentials, offers password recovery/account creation, and supports WebAuthn discovery. |
be-sustainableoptimised-assets | issues | high | Image audit reports 30 legacy-format images, 26 below-fold images without loading=lazy, one oversized image, and one missing srcset. F19 medium: Image delivery leaves avoidable bytes and requests. |
be-sustainableno-wasteful-work | pass | high | The 551,504-byte page has no known tracker workload, no autoplay media, and only one load long task; background work appears proportionate to the encyclopedia surface. |
be-sustainablethird-party-and-media-budget | pass | high | Third-party transfer is 168,028 bytes and confined to Wikimedia image/auth origins; no audio, video, or autoplay media is present. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing product intent or transactional agent surface was found; this emerging capability is contextual. |
be-agent-readyon-device-inference | not-applicable | high | No declared on-device AI experience or inference task was found; this emerging capability is contextual. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 20 menu toggles, DOM nodes remain exactly 7,332 and the menu returns closed; heap node count changes only 344,279→344,788 and closures 6,286→6,283. |
be-memory-efficientbounded-footprint | pass | high | The long 62,962-character article uses a 23.5MB snapshot self-size and 7,332 live DOM elements, proportionate to a large server-rendered article. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap constructor summaries expose no Detached* population; closure count decreases by three and live DOM count is unchanged after 20 toggles. |
Provenance
Canonical report: results/atomic/reports/0783-fa_wikipedia_org.json
Report SHA-256: c91ba7414c001383e0e8d668ce8278119b2a23d3d7abdd74ff30af2daa923370
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/fa_wikipedia_org/2026-07-23T00-23-35-316Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/fa_wikipedia_org/2026-07-23T00-23-35-316Z
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.