Manifest position 723 · CrUX rank bucket 1000
https://www.uol.com.br
Coverage complete
Coverage-complete audit across homepage, section, article, and invalid-route recovery. Noticias subdomain returned Access Denied, so equivalent www.uol.com.br sports templates were used. Search, authenticated account, subscription checkout/cancellation, and payment were not covered because they require broader cross-property or credentialed flows.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-condition screenshot is visually the same white interface as the default and the feature probe found zero prefers-color-scheme rules. F01 medium: System dark mode is ignored |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce active, 13 animations remained running with durations of 1 to 3 seconds. F02 medium: Motion continues under reduced-motion preference |
respect-user-preferencesrespects-contrast | issues | high | The CSS feature probe found no prefers-contrast or forced-colors rules; the high-contrast screenshot retained the same low-emphasis chrome. F03 low: No explicit high-contrast adaptation |
implement-natural-interactionsview-transitions | issues | high | Rendered HTML and accessible CSS contained no view-transition or startViewTransition usage across the homepage navigation surface. F04 low: Route changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation was observed, so there is no scroll-handler implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | medium | Feature probe found platform overscroll behavior and no inline pointer/touch-move handlers; reading uses native scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage is 17,705 CSS pixels tall, while the feature probe found no scroll-state queries or scroll-timeline indicator. F05 low: Long news feed has no scroll-state guidance |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored popover, or edge-positioned menu was exercised in the representative core reading paths. |
provide-guided-navigationdirects-attention | pass | medium | Desktop and mobile screenshots show strong lead-headline hierarchy, section labels, and clear article context. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Fresh sports loads are covered by a modal on desktop and mobile; body scrolling is locked and the dialog describes sharing with 211 partners. F06 high: Consent modal blocks the section before content can be used |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The consent probe found role=dialog on a DIV without aria-modal; no dialog or popover primitive exists on the homepage. F07 medium: Consent overlay is a custom div rather than a modal primitive |
maximize-content-reduce-noisereduced-chrome | issues | high | The desktop first viewport gives roughly 300px to a blank advertising slot plus multiple header rows before the lead headline, and the mobile page remains dense. F08 medium: Advertising and service chrome crowds the primary news content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The homepage forces a 1210px layout viewport at 360px, while the article reports 85px horizontal overflow and visibly overlaps the title, navigation, currency, and subscription controls. F09 critical: Mobile layouts are broken or scaled down |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The feature probe found no container queries, and the article header components overlap at 360px instead of re-composing. F10 high: Shared components do not adapt to their available space |
adapt-to-the-form-factorinput-modality-aware | issues | high | Homepage focus sampling found top navigation links only about 14px high and multiple links/inputs with outline none; some controls are 24x24. F11 high: Several controls are too small or lose visible focus |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Homepage and article screenshots present a clear news portal purpose and prominent lead/article reading actions. |
support-core-task-successprimary-flow-completion | issues | high | At 360px the article headline and header controls overlap, the page is wider than the viewport, and the cookie banner obscures the opening paragraphs. F12 critical: The mobile article reading journey is obstructed |
support-core-task-successclear-system-state-and-recovery | issues | high | A deliberately invalid path redirected to https://www.uol.com.br/#404 but displayed normal homepage content, with no not-found heading, explanation, search, or recovery state. F13 high: Invalid URLs silently become the homepage |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 6.7s, Speed Index 10.1s, TTI 17.2s, and performance score 0.56. F14 high: Homepage load performance misses the user-centric bar |
be-fast-and-stablevisual-stability | pass | medium | Layout observer measured CLS 0.000069 on home and 0 on the article during the observation windows. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 280ms TBT; the trace found four long tasks, up to 113ms, and 99.89ms trace TBT. F15 medium: Main-thread work causes blocking tasks |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR captured 192 requests and 2.61MB transferred, including 56 scripts/1.90MB; fonts took about 2.1s. Parser-discovered candidates were confirmed async where sampled, but the network dependency volume remains high. F16 high: Resource delivery is dominated by scripts and third parties |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 897KiB unused JavaScript, led by player, advertising, analytics, consent, and bidding bundles. F17 high: Nearly 900KiB of JavaScript is unused on load |
be-inclusivenames-roles-labels | issues | high | axe found critical missing image alt, two unnamed links, 24 prohibited ARIA uses, and focusable controls inside aria-hidden carousels; the DOM probe found unlabeled email/password inputs. F18 high: Accessible names and roles are incomplete |
be-inclusivesufficient-contrast | issues | high | axe reported 54 color-contrast failures, including weather text and promoted headline text. F19 high: Many text elements fail WCAG contrast |
be-inclusivestructure-and-focus | issues | high | axe found no main landmark, incorrect heading order, empty headings, non-unique/nested landmarks, and aria-hidden focusable carousel content. F20 high: Document structure and focus semantics are unreliable |
be-inclusivelegible-text | issues | high | At 360px the article title is covered by header/navigation controls and body content is clipped/obscured. F21 critical: Article text is not legible at a common mobile width |
be-inclusivezoom-reflow-targets-and-media | issues | high | The article overflows by 85px at 360px and homepage target sampling found links around 14px high and 24x24 controls. F22 high: Reflow and target sizing fail on mobile |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured CORS errors and failed Adnxs network requests in the console. F23 medium: Third-party integrations log runtime failures |
follow-best-practicessound-document-and-assets | issues | high | The images audit found 90 of 100 images missing dimensions, 21 below-fold images not lazy-loaded, and two missing alts; axe also flagged a delayed meta refresh. F24 medium: Asset markup creates avoidable risk |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found an unload handler that blocks BFCache and missing/broken maps for large first-party/player JavaScript. F25 medium: The page blocks BFCache and has source-map defects |
be-discoverabletitle-and-description | pass | medium | DOM and Lighthouse confirm descriptive titles and meta descriptions on home and article. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found an anchor without href, and the homepage viewport is hard-coded to width=1210 rather than device width. F26 medium: A login action is not crawlable and homepage mobile metadata is non-responsive |
be-discoverablecanonical-and-indexing-signals | pass | medium | Home and article return 200, expose canonical URLs, index/follow metadata, and robots.txt lists section news sitemaps. |
be-discoverablestructured-and-shareable-metadata | pass | medium | DOM probes found JSON-LD WebSite/Organization on home, two JSON-LD blocks on article, and Open Graph metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Although HTTPS, HSTS, and frame-ancestors are present, X-Content-Type-Options is missing and all 19 observed cookies were flagged insecure by the primitive; several analytics/consent cookies lack Secure. F27 high: Cookie and response protections are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe saw 62 third-party origins and 12 known trackers; the HAR attributed 185/192 requests and 2.44MB to non-main origins, while consent copy names 211 partners. F28 critical: The page activates an exceptionally broad tracking surface |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The homepage sign-in markup exposes email/password fields with no autocomplete tokens and no WebAuthn/passkey signal was observed. F29 medium: The exposed sign-in form lacks modern input/auth affordances |
be-private-and-securedefensive-browser-policies | issues | high | Headers lack Permissions-Policy and nosniff; Referrer-Policy remains no-referrer-when-downgrade, and CSP only specifies frame-ancestors. F30 medium: Defensive browser policies are only partial |
be-resilientprogressive-enhancement | pass | medium | Discoverability captures show 97% home and 89% article word coverage in raw server HTML with title, h1, and description present. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative screenshots, DOM/evaluate probes, and active path inspection found the check outcome satisfied without a conflicting signal. |
be-resilientoffline-and-installable | not-applicable | high | UOL is a continuously updated news service; full offline/installable behavior is not necessary for the audited reading journey, although progressive rendering remains applicable. |
be-resilientnetwork-and-http-failure-states | issues | high | An invalid URL is rewritten to #404 and then renders ordinary homepage content rather than a clear error and recovery state. F31 high: HTTP failure recovery is misleading |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The document declares lang=pt-br and the feature probe found logical CSS properties. |
be-internationalisedlocale-aware-data | pass | medium | Rendered currency uses Brazilian decimal comma and article dates use the expected Brazilian day/month/year format. |
be-internationalisedtime-zone-correctness | pass | medium | Article publication context states São Paulo and presents an unambiguous dated local publication time. |
be-trustworthyno-dark-patterns | issues | high | The first consent layer offers Consent and Manage options, but no equally prominent Reject choice; it describes 211 partners. The homepage fallback says continued browsing is agreement and offers only OK. F32 critical: Consent choice is asymmetric and tracking begins before a clear rejection |
be-trustworthyhumane-error-handling | not-applicable | high | No user-submitted primary form was part of the public reading journey; authentication submission was not attempted with credentials. |
be-trustworthytrustworthy-input-assistance | issues | high | The DOM probe found email and password inputs with empty autocomplete values and no programmatic labels. F33 medium: Sign-in fields omit autocomplete assistance |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Checkout, subscription completion, cancellation, and authenticated account management were explicitly outside this public, credential-free audit. |
be-sustainableoptimised-assets | issues | high | Of 100 images, 90 lacked dimensions, 40 lacked srcset, 21 below-fold images were not lazy, and four were oversized. F34 medium: Image delivery misses responsive efficiency basics |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimated 897KiB unused JS and the HAR recorded 64 fetch/XHR requests on initial load. F35 high: The page performs substantial work unrelated to immediate content |
be-sustainablethird-party-and-media-budget | issues | high | Third parties accounted for 185 requests and 2.44MB of 2.61MB transferred; 62 third-party origins were observed. F36 high: Third-party code dominates the page budget |
be-agent-readystructured-agent-capabilities | issues | high | Content is server-rendered (89 to 97 percent crawler coverage), but robots.txt explicitly disallows major agent/search user agents and no structured WebMCP capability is exposed. F37 medium: Public article content is deliberately unavailable to most AI agents |
be-agent-readyon-device-inference | not-applicable | high | Built-in on-device inference is an emerging optional enhancement and is not required to deliver the audited news reading journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 full-feed scroll down/up cycles, heap self size rose only 3.6% (61.1MB to 63.3MB) and node count 3.0%, bounded for newly loaded feed content. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap contained 1,318,836 nodes and 61.1MB self size before user interaction, with 236,636 closures. F38 medium: Homepage memory footprint is disproportionate for a news index |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries show modest bounded growth and no Detached constructor among top retained constructors; Promise count decreased. |
Provenance
Canonical report: results/atomic/reports/0723-www_uol_com_br.json
Report SHA-256: 98cb8546e5667a8acd3cfe04f5c3fc1b2e65170a55feb48934601a19b0590ff8
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_uol_com_br/2026-07-22T15-50-28-735Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_uol_com_br/2026-07-22T15-50-28-735Z
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.