Manifest position 27 · CrUX rank bucket 1000
https://www.cnnbrasil.com.br
Coverage complete
Coverage-complete model-driven audit across six representative paths. The repository web-uplift.json was not applied because it scopes the local playground, not this remote target.
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-preference screenshot is visually the same light page and modal as the default capture; CSS probing found no prefers-color-scheme rule. F01 medium: The site does not adapt to a dark system preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found six running animations, including two roughly 80-second animations, and no prefers-reduced-motion CSS rules. F02 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot preserved legible text, outlines and consent controls. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no view-transition-name or ::view-transition rules across the MPA navigation surfaces. F03 low: Route changes do not expose a coherent transition treatment. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface was present on the representative templates. |
implement-natural-interactionsphysical-gestures | pass | high | UI CSS probe found scroll-snap behavior for carousel interactions and no evidence of pointermove-driven gesture hijacking. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage is 32,812 px tall, but CSS inspection found no scroll-state query or progress treatment; the header remains generic site chrome. F04 low: Long news pages provide no position-aware reading chrome. |
provide-guided-navigationanchored-positioning | not-applicable | high | No edge-tethered tooltip or contextual popover was part of the representative core journeys. |
provide-guided-navigationdirects-attention | pass | high | Skip-to-content and skip-carousel anchors provide explicit attention/navigation targets in the recon DOM. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Homepage, article, section, live, mobile and 404 screenshots all show a large modal covering the primary content before interaction. F05 high: A consent wall obscures every representative page on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The UI probe found four div[role=dialog] nodes, zero dialog elements, zero popovers and no aria-modal on the visible consent dialog. F06 medium: The modal consent experience is built from custom div dialogs rather than a native modal primitive. |
maximize-content-reduce-noisereduced-chrome | issues | high | On mobile the consent panel consumes almost the full 360×800 viewport; on desktop the first view is dominated by consent and multiple chrome bands rather than a lead story. F07 medium: Consent and market/sports chrome crowd out the editorial content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Home and section mobile layout captures report 0 px horizontal overflow with a valid viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe found no @container rules despite reusable cards, rails and carousels appearing in different-width regions. F08 low: Responsive behavior is viewport-only rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found many focused links with outline-style none and no box shadow; visible controls measured 24×24, 32×32 and 36×36 px. F09 high: Keyboard focus is frequently invisible and several controls are too small. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage and article headings clearly identify the news purpose and lead/current stories. |
support-core-task-successprimary-flow-completion | pass | high | Real links reach section and article templates, and ?search=economia returns an “Exibindo resultados” state. |
support-core-task-successclear-system-state-and-recovery | pass | high | The tested missing URL presents a clear unavailable message and a working HOME recovery link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.5 s and TBT 550 ms; the independent trace observed LCP 7.55 s and 384 ms TBT. F10 high: Loading and responsiveness miss the good Core Web Vitals experience. |
be-fast-and-stablevisual-stability | pass | high | Observed mobile CLS was 0.018 on home and 0.014 on the section; Lighthouse CLS was 0.03. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reports 4.6 s main-thread work and 1.9 s script bootup; the trace contains a 360 ms long task. F11 high: Heavy scripting blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 213 requests and 6.56 MB, including 122 images/3.98 MB and 41 scripts/1.83 MB; two font stylesheets are high-priority parser-inserted blockers. F12 high: The homepage transfers an excessive request and byte payload. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 722 KiB unused JavaScript and 97 KiB unused CSS; ad, identity and social bundles are major contributors. F13 medium: Large amounts of unused code ship on the landing page. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found unnamed buttons/links, prohibited ARIA, 8 SVG images without text alternatives and 12 label/name mismatches. F14 high: Important controls and media affordances have broken accessible names or ARIA. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 26 contrast failures, including green financial values at 2.27:1 and pale sports labels as low as 1.58:1. F15 high: Multiple text treatments fail minimum contrast. |
be-inclusivestructure-and-focus | issues | high | Focused links commonly computed to outline none; Lighthouse also reports an ill-formed agent/accessibility tree and invalid tabpanel/ARIA usage. F16 high: Focus visibility and the accessibility tree are not reliable. |
be-inclusivelegible-text | pass | high | Article screenshot shows readable headline/body hierarchy and comfortable editorial line treatment once content is visible. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The target probe found 24–36 px controls, while the live page probe found several iframes with empty titles and no exposed caption tracks. F17 medium: Small targets and unlabeled live-media frames reduce inclusive access. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a React hydration error and a 404 request to the favorites API. F18 medium: The page logs runtime and network errors. |
follow-best-practicessound-document-and-assets | issues | high | The image probe found 3 images without dimensions, 60 below-fold images not lazy-loaded, 73 without srcset, 91 legacy-format assets and 55 empty/missing alt values requiring editorial review. F19 high: Image markup and delivery are inconsistent and wasteful. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed notification-on-start and reported that an in-flight iframe navigation prevented BFCache restoration. F20 medium: The page requests notification permission on load and misses BFCache. |
be-discoverabletitle-and-description | pass | high | Homepage and article probes show unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse passed crawlable anchors, robots and viewport checks; representative navigation uses real href links. |
be-discoverablecanonical-and-indexing-signals | issues | high | /sitemap.xml returns HTTP 404 with an application error body that contains both noindex and index robots tags plus a homepage canonical. F21 high: The advertised sitemap endpoint is broken and returns an index-confusing error document. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage and article expose Open Graph/Twitter metadata plus NewsMediaOrganization, WebSite, BreadcrumbList and NewsArticle JSON-LD. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and nosniff are present, but CSP and HSTS are absent; 11 cookies were reported without Secure and all 11 use SameSite=None. F22 high: Baseline response defenses and cookie protections are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 32 third-party origins and 5 known trackers; the HAR attributes 183 requests and 5.46 MB to non-main origins before a consent choice. F23 high: The default load has a very large third-party tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Lighthouse traced a notification-on-start request to notifpush.com/scripts/wpn2.js. F24 high: Notification permission is initiated without user context. |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no X-Frame-Options or CSP frame-ancestors, no Referrer-Policy and no Permissions-Policy. F25 high: Clickjacking, referrer and permissions defenses are not declared. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 91% raw-HTML coverage, title/H1/description present and no JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Representative listing, article and media templates rendered usable content and retained recovery navigation without blank-shell failure. |
be-resilientoffline-and-installable | not-applicable | high | CNN Brasil is a public news website rather than an installed app; offline installability is contextual and was not required for this audit. |
be-resilientnetwork-and-http-failure-states | pass | high | The non-existent route gives an intentional Portuguese error message and a HOME recovery action. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=pt-BR and reading direction is correct for the Portuguese content. |
be-internationalisedlocale-aware-data | pass | high | Rendered finance values and publication dates use Brazilian decimal, currency and day/month conventions. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited editorial pages display publication times for a single Brazilian locale and do not expose a cross-time-zone scheduling flow. |
be-trustworthyno-dark-patterns | issues | high | The visible dialog exposes only Consent and Manage options; the probe found no reject button, while the copy names 420 partners and content remains blocked. F26 high: The consent wall lacks a direct reject choice while offering immediate consent. |
be-trustworthyhumane-error-handling | issues | high | DOM inspection found the EMAIL and terms checkbox are not required and have no aria-describedby error association; the consent checkbox starts aria-invalid=false. F27 medium: The newsletter form does not expose robust required/error semantics. |
be-trustworthytrustworthy-input-assistance | pass | high | The newsletter email field uses type=email and autocomplete=email; search uses type=search. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, paid subscription or account-management journey was present in the representative editorial scope. |
be-sustainableoptimised-assets | issues | high | Image evidence found 91 legacy-format images, 73 without srcset and 60 below-fold images loaded eagerly; HAR image transfer reached 3.98 MB. F28 high: The page ships too many unoptimized image variants for an editorial landing page. |
be-sustainableno-wasteful-work | issues | high | The load performs 213 requests across 33 origins with 4.6 s main-thread work; much of the unused script is advertising, identity and analytics code. F29 high: Background advertising and analytics work is disproportionate. |
be-sustainablethird-party-and-media-budget | issues | high | HAR records 183 third-party requests and 5.46 MB, while Lighthouse reports a 4.25 MiB page under its run and 722 KiB potentially unused JavaScript. F30 high: Third-party scripts and media dominate the resource budget. |
be-agent-readystructured-agent-capabilities | pass | high | As a content site, it exposes server-rendered article text, semantic links and extensive JSON-LD; crawler coverage is 91%. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited editorial journeys requires an on-device generation or summarization feature. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll round trips, heap self size rose only 0.67% (60.0 to 60.4 MB) and node count 0.10%, with no unbounded trend in this bounded test. |
be-memory-efficientbounded-footprint | issues | high | Heap baseline contains 1,031,746 heap nodes and 60.0 MB self size; the live DOM probe counted 12,846 elements for one landing page. F31 medium: The settled homepage has a large memory and DOM footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries show stable closure counts and no Detached* constructor among top retained constructors. |
Provenance
Canonical report: results/atomic/reports/0027-www_cnnbrasil_com_br.json
Report SHA-256: 6ab039053b5b9ae267254e28093e95ce904a08d35d54d2e01426228e175c6f76
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_cnnbrasil_com_br/2026-07-17T22-31-52-474Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_cnnbrasil_com_br/2026-07-17T22-31-52-474Z
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.