Manifest position 770 · CrUX rank bucket 1000
https://esaj.tjsp.jus.br
Coverage complete
Atomic coverage complete across the public portal, service listings, legacy first-instance judgment search 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 | The dark-emulated screenshot is visually identical to the light capture, and the CSS probe found no prefers-color-scheme rule. F1 medium: The portal does not follow the user’s dark colour preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The modern portal CSS contains prefers-reduced-motion handling; the legacy form exposes no animations to suppress. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse reports color-contrast, heading-order and visible-label/accessibility-name failures on the modern portal; the legacy search scores 0.70 for accessibility. F2 high: Text contrast and accessible naming fall below an inclusive baseline. |
implement-natural-interactionsview-transitions | issues | high | CSS/DOM probing found no view-transition usage while representative service selections replace the main content. F3 medium: Service navigation swaps content abruptly without preserving spatial context. |
implement-natural-interactionsscroll-driven-animations | pass | high | The CSS probe found animation-timeline support and no main-thread long tasks during load; no imperative scroll-motion failure was observed. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven, swipe, pull-to-refresh or scroll-snap interaction exists on the representative public-service paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Desktop screenshots show a static header/sidebar; the probe found no container-query support and representative navigation changes have no attention cue. F4 low: Navigation chrome does not respond to page position or guide attention through long pages. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, transient popover or viewport-edge anchored menu was present on the representative paths. |
provide-guided-navigationdirects-attention | issues | high | CSS/DOM probing found no view-transition usage while representative service selections replace the main content. Desktop screenshots show a static header/sidebar; the probe found no container-query support and representative navigation changes have no attention cue. F3 medium: Service navigation swaps content abruptly without preserving spatial context. F4 low: Navigation chrome does not respond to page position or guide attention through long pages. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots across four representative pages show no interstitial or content-obscuring overlay. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No overlay, dialog, popover or disclosure widget was present to which this primitive choice would apply. |
maximize-content-reduce-noisereduced-chrome | pass | high | The modern templates devote the main viewport to service content and keep header/sidebar controls compact. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360px viewport, layout metrics report a 980px layout viewport, scale 0.367 and no viewport meta; the screenshot renders form text and controls extremely small. F5 high: The legacy first-instance judgment search is a desktop canvas scaled down on phones. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | At a requested 360px viewport, layout metrics report a 980px layout viewport, scale 0.367 and no viewport meta; the screenshot renders form text and controls extremely small. F5 high: The legacy first-instance judgment search is a desktop canvas scaled down on phones. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The home probe found numerous 14–20px-high links/buttons; Lighthouse also fails target-size on the legacy search. F6 high: Many primary controls have undersized touch targets. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Each representative page has a clear Portuguese heading, purpose statement and directly named service/search action. |
support-core-task-successprimary-flow-completion | pass | high | The public judgment-search form accepted a free-text query and returned a populated results view without authentication. |
support-core-task-successclear-system-state-and-recovery | issues | high | A representative unknown route returned a bare browser HTTP 404 with only Reload, no portal navigation, explanation or recovery path. F7 high: HTTP failure states abandon users to the browser’s generic error page. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 6.5s on the portal and 8.6s on the legacy search; the raw trace measured LCP 4.23s. F8 high: Primary pages load too slowly for the Core Web Vitals baseline. |
be-fast-and-stablevisual-stability | pass | high | Layout and Lighthouse evidence report CLS 0 on the modern portal and approximately 0.0003 on the legacy search. |
be-fast-and-stableefficient-main-thread | pass | high | The trace reports zero long tasks and 0ms TBT; Lighthouse TBT was 87ms on home and 0ms on the legacy route. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records 871KB transferred, including 711KB across six scripts; four app chunks account for about 707KB and LCP is delayed despite zero trace long tasks. F9 medium: A simple service directory ships a disproportionate JavaScript payload and delayed dependency chain. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR records 871KB transferred, including 711KB across six scripts; four app chunks account for about 707KB and LCP is delayed despite zero trace long tasks. F9 medium: A simple service directory ships a disproportionate JavaScript payload and delayed dependency chain. |
be-inclusivenames-roles-labels | issues | high | The form probe found 15 visible controls without programmatic labels; Lighthouse fails form labels, image alt, link names, ARIA validity and main landmark. F10 high: The legacy search has unlabeled controls, missing alternatives and weak landmarks. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports color-contrast, heading-order and visible-label/accessibility-name failures on the modern portal; the legacy search scores 0.70 for accessibility. F2 high: Text contrast and accessible naming fall below an inclusive baseline. |
be-inclusivestructure-and-focus | issues | high | The form probe found 15 visible controls without programmatic labels; Lighthouse fails form labels, image alt, link names, ARIA validity and main landmark. F10 high: The legacy search has unlabeled controls, missing alternatives and weak landmarks. |
be-inclusivelegible-text | issues | high | The 980px desktop layout is reduced to 36.7% scale in a 360px viewport, making labels, inputs and instructions tiny. F11 high: The mobile rendering of the legacy search is not comfortably legible. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a requested 360px viewport, layout metrics report a 980px layout viewport, scale 0.367 and no viewport meta; the screenshot renders form text and controls extremely small. The home probe found numerous 14–20px-high links/buttons; Lighthouse also fails target-size on the legacy search. The 980px desktop layout is reduced to 36.7% scale in a 360px viewport, making labels, inputs and instructions tiny. F5 high: The legacy first-instance judgment search is a desktop canvas scaled down on phones. F6 high: Many primary controls have undersized touch targets. F11 high: The mobile rendering of the legacy search is not comfortably legible. |
follow-best-practicesno-console-errors | issues | high | Lighthouse’s errors-in-console audit fails on both the modern portal and legacy search; the HAR also records a 403 translation-resource request. F12 medium: Representative pages emit browser errors. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse reports no doctype, a deprecated API and low-resolution imagery on /cjpg; its best-practices score is 0.46. F13 medium: The legacy template uses quirks-era document and asset practices. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse’s errors-in-console audit fails on both the modern portal and legacy search; the HAR also records a 403 translation-resource request. Lighthouse reports no doctype, a deprecated API and low-resolution imagery on /cjpg; its best-practices score is 0.46. F12 medium: Representative pages emit browser errors. F13 medium: The legacy template uses quirks-era document and asset practices. |
be-discoverabletitle-and-description | issues | high | /robots.txt and /sitemap.xml return 404; /cjpg lacks a meta description; probes found no canonical, Open Graph or JSON-LD metadata. F14 medium: Public service pages lack consistent crawl and sharing signals. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | At a requested 360px viewport, layout metrics report a 980px layout viewport, scale 0.367 and no viewport meta; the screenshot renders form text and controls extremely small. /robots.txt and /sitemap.xml return 404; /cjpg lacks a meta description; probes found no canonical, Open Graph or JSON-LD metadata. F5 high: The legacy first-instance judgment search is a desktop canvas scaled down on phones. F14 medium: Public service pages lack consistent crawl and sharing signals. |
be-discoverablecanonical-and-indexing-signals | issues | high | /robots.txt and /sitemap.xml return 404; /cjpg lacks a meta description; probes found no canonical, Open Graph or JSON-LD metadata. F14 medium: Public service pages lack consistent crawl and sharing signals. |
be-discoverablestructured-and-shareable-metadata | issues | high | /robots.txt and /sitemap.xml return 404; /cjpg lacks a meta description; probes found no canonical, Open Graph or JSON-LD metadata. F14 medium: Public service pages lack consistent crawl and sharing signals. |
be-private-and-securesecure-transport-and-headers | issues | high | Both final pages omit CSP, HSTS, nosniff, framing, referrer and permissions policies. /cjpg sets JSESSIONID cookies without Secure, HttpOnly or SameSite protection. F15 high: Sensitive public-service routes lack browser defenses and set insecure session cookies. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | /cjpg sets __utma for 400 days plus several __utm cookies, all without Secure and with SameSite=None. F16 medium: The legacy search sets long-lived legacy analytics cookies before user action. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The primary banner says users sign in with username/password plus an emailed verification code; the platform probe found no PublicKeyCredential/navigator.credentials use in the loaded surface. F17 medium: Authentication messaging still centres passwords and emailed OTP rather than phishing-resistant credentials. |
be-private-and-securedefensive-browser-policies | issues | high | Both final pages omit CSP, HSTS, nosniff, framing, referrer and permissions policies. /cjpg sets JSESSIONID cookies without Secure, HttpOnly or SameSite protection. /cjpg sets __utma for 400 days plus several __utm cookies, all without Secure and with SameSite=None. F15 high: Sensitive public-service routes lack browser defenses and set insecure session cookies. F16 medium: The legacy search sets long-lived legacy analytics cookies before user action. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 1% raw/rendered word coverage: raw HTML has 26 text characters versus 2,676 rendered and the crawler capture remains at a loading indicator. F18 high: Core portal content is absent without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Representative menus, cards and search controls rendered without clipped overlays or broken asynchronous shell state after load. |
be-resilientoffline-and-installable | not-applicable | high | Live court searches depend on current server data; offline/installability is not a proportionate requirement for this intrinsically online service. |
be-resilientnetwork-and-http-failure-states | issues | high | A representative unknown route returned a bare browser HTTP 404 with only Reload, no portal navigation, explanation or recovery path. F7 high: HTTP failure states abandon users to the browser’s generic error page. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The /cjpg DOM probe found an empty html lang while Lighthouse fails html-has-lang; the modern portal correctly uses pt-BR. F19 medium: The legacy Portuguese page does not declare its language. |
be-internationalisedlocale-aware-data | pass | high | Visible court dates use the expected Brazilian day/month/year convention and the modern template declares pt-BR. |
be-internationalisedtime-zone-correctness | not-applicable | high | Representative pages expose dates but no times, cross-zone events, recurrence or DST-sensitive scheduling. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, disguised advertising, forced continuity, confirmshaming or preselected commercial choice appeared on representative paths. |
be-trustworthyhumane-error-handling | issues | high | The probe found no autocomplete tokens, many unlabeled fields and no exposed invalid/error state; a synthetic free-text query returned a huge generic result set rather than explaining the mismatch. F20 high: The legacy search offers weak input assistance and unclear validation semantics. |
be-trustworthytrustworthy-input-assistance | issues | high | The probe found no autocomplete tokens, many unlabeled fields and no exposed invalid/error state; a synthetic free-text query returned a huge generic result set rather than explaining the mismatch. F20 high: The legacy search offers weak input assistance and unclear validation semantics. |
be-trustworthysafe-commercial-and-account-flows | pass | high | No commercial flow exists; account messaging clearly discloses password plus emailed verification and no deceptive continuity was observed. |
be-sustainableoptimised-assets | issues | high | Lighthouse reports no doctype, a deprecated API and low-resolution imagery on /cjpg; its best-practices score is 0.46. F13 medium: The legacy template uses quirks-era document and asset practices. |
be-sustainableno-wasteful-work | pass | high | Trace/layout evidence found no long tasks or ongoing media work; the page made 24 load requests with only two small third-party resource requests. |
be-sustainablethird-party-and-media-budget | pass | high | No video/audio/autoplay media was present; third-party transfer was 2.9KB of 871KB and no known tracker origin was detected on home. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capabilities are emerging and no declared intent requests WebMCP or agent actions for this portal. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is part of the representative user journeys, so on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten menu-toggle cycles, heap self size fell from 12,805,911 to 12,786,279 bytes and node count fell from 169,174 to 168,863. |
be-memory-efficientbounded-footprint | pass | high | The loaded portal heap is about 12.8MB self size with 169k nodes, proportionate to this service directory. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The repeated-interaction heap did not grow overall and neither summary reported a Detached* constructor among retained-size leaders. |
Provenance
Canonical report: results/atomic/reports/0770-esaj_tjsp_jus_br.json
Report SHA-256: eec5476d8899581ec283082c691c70eac521e8c885b4fc491a849ae257661d32
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/esaj_tjsp_jus_br/2026-07-22T22-50-08-244Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/esaj_tjsp_jus_br/2026-07-22T22-50-08-244Z
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.