Manifest position 153 · CrUX rank bucket 1000
https://fe.afip.gob.ar
Coverage complete
All 58 catalog checks were judged across the exposed directory, its only linked page, and an HTTP failure state.
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-emulated screenshot is pixel-identical to the light capture: white canvas and black text; the DOM contains no CSS or color-scheme declaration. F03 medium: The page ignores the user’s dark color-scheme preference |
respect-user-preferencesrespects-reduced-motion | pass | high | The reduced-motion probe confirmed the emulated preference and found zero active animations; the page has no scripts or styles. |
respect-user-preferencesrespects-contrast | pass | high | High-contrast emulation leaves the native heading/link legible, and Lighthouse reports no contrast failures. |
implement-natural-interactionsview-transitions | issues | high | The only route change, from the directory to a.html, is a plain cross-document link with no CSS or view-transition styling, so it swaps abruptly. F04 low: The only route change is an abrupt cross-document swap |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | Neither representative page has scroll-linked motion, parallax, scrollytelling, or reveal effects to implement. |
implement-natural-interactionsphysical-gestures | not-applicable | high | Neither page exposes gesture-driven controls, carousels, swipe actions, or custom pointer interactions. |
provide-guided-navigationscroll-state-aware-chrome | not-applicable | high | The pages have no navigation chrome and no meaningful scroll journey; the short static content does not warrant scroll-aware chrome. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, menu, popover, or other anchored overlay exists on either page. |
provide-guided-navigationdirects-attention | issues | high | The link is labelled only “a.html”; its destination is an unheaded token with no navigation cue, context, focus cue, or return path. F02 high: The only visible journey ends at an opaque, context-free token |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots and DOM show no popup, banner, interstitial, or overlay. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No overlay, disclosure, select, picker, or rich control is present, so no dismissible primitive is required. |
maximize-content-reduce-noisereduced-chrome | pass | high | The pages contain only their bare content and native browser styling, with no decorative or application chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360px viewport Chrome lays the page out at 980 CSS px and scales it to 0.367 because meta viewport is absent. This is a desktop canvas scaled down, not responsive reflow. F05 high: Mobile devices receive a scaled 980px layout instead of responsive reflow |
adapt-to-the-form-factorcomponent-level-responsiveness | not-applicable | high | There are no reusable components or component containers; only an h1, list, link, and plain token are rendered. |
adapt-to-the-form-factorinput-modality-aware | pass | high | The sole interactive element is a native anchor; Lighthouse target-size and link-name audits pass and browser-native keyboard focus remains available. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The first viewport says only “Index of /” and exposes a filename. It does not explain the AFIP-facing purpose, intended audience, or useful primary action. F01 high: The public entry page does not explain its purpose or useful next action |
support-core-task-successprimary-flow-completion | issues | high | Following the only action reaches a page containing only the opaque token “fe010”, with no heading, explanation, next step, or return control. F02 high: The only visible journey ends at an opaque, context-free token |
support-core-task-successclear-system-state-and-recovery | issues | high | A nonexistent route returns a generic Apache 404 with no home link, search, retry guidance, or recovery action. F13 medium: HTTP failures provide no recovery route |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse measured LCP 0.8s, CLS 0, and TBT 0ms; trace measured LCP 1262ms and no blocking tasks. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observer and Lighthouse both measured CLS 0 with no layout-shift entries. |
be-fast-and-stableefficient-main-thread | pass | high | Trace and layout observers found zero long tasks and 0ms total blocking time; the page ships no JavaScript. |
be-fast-and-stableefficient-resource-delivery | pass | high | HAR records only two requests and 915 transferred bytes, with no render-blocking candidates; the only failed request is a tiny favicon and does not delay content. |
be-fast-and-stabletrim-unused-and-duplicate-code | pass | high | DOM and HAR show no JavaScript, CSS, fonts, media, or third-party code, so there is no shipped unused or duplicate bundle. |
be-inclusivenames-roles-labels | pass | high | The only interactive element is a native anchor with a discernible name; there are no forms, images, canvas, or custom controls. Lighthouse link-name passes. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast passes and screenshots show native black text/blue link on white with clear contrast. |
be-inclusivestructure-and-focus | issues | high | The homepage has an h1 but no landmarks or language declaration, while a.html has no heading at all. The destination therefore lacks a meaningful document structure. F06 medium: Document structure is incomplete, especially on a.html |
be-inclusivelegible-text | pass | high | At desktop size the native heading and body text are unclipped and high contrast, with no custom fonts or mixed-font rendering problems. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Both pages omit meta viewport; a 360px device receives a 980px layout scaled to 36.7%, making native text much smaller than intended despite no horizontal overflow. F05 high: Mobile devices receive a scaled 980px layout instead of responsive reflow |
follow-best-practicesno-console-errors | issues | high | Lighthouse logs a 404 console/network error for /favicon.ico, which is also present in the HAR. F07 low: A missing favicon produces a console/network error on every load |
follow-best-practicessound-document-and-assets | issues | high | The server emits an HTML 3.2 Final public doctype that Chrome treats as BackCompat/quirks mode; a.html is six bytes of text with no authored document structure. F08 medium: The responses use quirks-mode or no authored HTML structure |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse finds no BFCache blocker, deprecated permission prompt, paste prevention, source-map issue, or third-party-cookie problem; the page ships no script or input handlers. |
be-discoverabletitle-and-description | issues | high | The homepage title is the generic “Index of /” and has no meta description; a.html has neither title nor description. F09 high: Pages lack descriptive search/share metadata |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The anchor is technically crawlable but its text is only “a.html”; neither page has a viewport meta element, and /robots.txt returns 404. F10 medium: Crawl and indexing signals are incomplete |
be-discoverablecanonical-and-indexing-signals | issues | high | Pages return 200, but expose no canonical or hreflang signals; both robots.txt and sitemap.xml return 404, leaving no explicit crawl policy or inventory. F10 medium: Crawl and indexing signals are incomplete |
be-discoverablestructured-and-shareable-metadata | not-applicable | high | Neither page represents an article, product, organisation profile, event, place, or other rich entity; the exposed directory/token has no legitimate rich-result entity to encode. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, X-Content-Type-Options, Referrer-Policy and frame protection are absent. Both first-party cookies are set without Secure or HttpOnly and with SameSite=None. F11 high: Security headers and first-party cookie attributes are unsafe |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker and HAR evidence shows zero third-party origins, zero known trackers, only two requests, and no exposed client secret. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Lighthouse confirms no geolocation or notification request on load. No login, account, or authentication flow exists, so WebAuthn is not relevant here. |
be-private-and-securedefensive-browser-policies | issues | high | No HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy, or CSP frame-ancestors is configured. F12 high: Browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | pass | high | Both pages are fully present in raw server responses and render without JavaScript; discoverability evidence confirms they are not JS shells. |
be-resilientresilient-runtime-behaviour | pass | high | No runtime scripts, async dependencies, overlays, menus, background work, or mutable DOM state exist that could become fragile. |
be-resilientoffline-and-installable | not-applicable | high | This is a tiny static server directory/diagnostic surface, not an app-like experience; a manifest, service worker, and installability are not proportionate requirements. |
be-resilientnetwork-and-http-failure-states | issues | high | The tested 404 is a generic server page with no route back to the homepage or useful recovery action. F13 medium: HTTP failures provide no recovery route |
be-internationalisedlang-dir-and-logical-properties | issues | high | Neither page declares html[lang] (Lighthouse confirms the failure), so assistive technology and translation tooling cannot reliably identify the content language. F14 medium: The document language is undeclared |
be-internationalisedlocale-aware-data | not-applicable | high | The representative pages display no dates, numbers, currency, duration, calendar, address, or other locale-sensitive value. |
be-internationalisedtime-zone-correctness | not-applicable | high | No date, event, schedule, timestamp, recurrence, or time-zone-dependent concept is exposed. |
be-trustworthyno-dark-patterns | pass | high | There is no consent, upsell, subscription, advertising, destructive action, hidden offer, or deceptive choice; only one plain link is present. |
be-trustworthyhumane-error-handling | not-applicable | high | No form or user input exists on the representative pages. Generic HTTP recovery is judged separately under core-task and resilience checks. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No input fields, sign-in, address, payment, or signup form exists. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No commercial, checkout, subscription, consent, authentication, or account-management flow exists. |
be-sustainableoptimised-assets | pass | high | The image audit found zero images and HAR shows no fonts, media, or decorative assets; only 915 bytes transferred. |
be-sustainableno-wasteful-work | pass | high | The page has no scripts or background requests; trace found no long tasks and HAR recorded only the document and failed favicon. |
be-sustainablethird-party-and-media-budget | pass | high | There are zero third-party origins and no scripts, fonts, image, video, audio, or animation payload. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This exposed surface is a bare directory/diagnostic token with no safe user capability or transactional form for an agent to invoke; adding WebMCP tooling would not be meaningful. |
be-agent-readyon-device-inference | not-applicable | high | The surface performs no language, summarisation, classification, or other inference task where a built-in on-device model would improve the experience. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | Neither page has a real repeatable interaction beyond ordinary cross-document navigation; fabricating a synthetic loop would not represent the site. |
be-memory-efficientbounded-footprint | pass | high | The heap summary reports 26,459 nodes and 763,644 self-size bytes, a small footprint proportionate to a two-element static page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The single-state heap summary contains no Detached* constructor among its reported populations, and the page ships no scripts, timers, observers, or event-listener registration code. |
Provenance
Canonical report: results/atomic/reports/0153-fe_afip_gob_ar.json
Report SHA-256: 31b9cca4b5f730807abd08fa653c22aeed417febfc1d5d142b8f0307b175a55b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/fe_afip_gob_ar/2026-07-18T19-23-39-635Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/fe_afip_gob_ar/2026-07-18T19-23-39-635Z
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.