Manifest position 285 · CrUX rank bucket 1000
https://m.youm7.com
Coverage complete
All 58 catalog checks were judged across four representative public-news paths.
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 | Emulated dark mode matched, but computed body colors remained rgb(195,30,30)/rgb(51,51,51) and color-scheme remained normal. F01 medium: Respects color scheme is not adequately supported. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned no active animations, so no non-essential motion persisted. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found insufficient foreground/background contrast, and prefers-contrast: more produced no theme response. F02 medium: Respects contrast is not adequately supported. |
implement-natural-interactionsview-transitions | issues | high | DOM and animation probes across navigation-heavy news templates found no View Transition usage or equivalent continuity. F03 medium: View transitions is not adequately supported. |
implement-natural-interactionsscroll-driven-animations | pass | high | The rendered homepage reported no active scroll-linked or time-based animations; content does not depend on scroll animation. |
implement-natural-interactionsphysical-gestures | issues | high | The dense carousel/navigation UI exposes many tiny controls (87 visible targets below 24px) rather than touch-sized, direct manipulation controls. F04 medium: Physical gestures is not adequately supported. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long pages (homepage CSS height 10,936px; article 7,091px) provide no visible progress or adaptive reading chrome. F05 medium: Scroll state aware chrome is not adequately supported. |
provide-guided-navigationanchored-positioning | pass | high | Consent and navigation overlays remained visibly attached and centered without clipping in the inspected mobile viewport. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show consistent red headline hierarchy, prominent lead stories, and section labels directing attention to current news. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A consent interstitial dims and blocks the full homepage, section, and article before the reader can use the content. F06 high: No intrusive interruptions is not adequately supported. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | The DOM exposed four dialog/role=dialog surfaces and the consent interface includes Manage options, Confirm choices, and Close controls. |
maximize-content-reduce-noisereduced-chrome | issues | high | The mobile screenshot is a scaled 1190px desktop portal with dense navigation, ads, tickers, sidebars, and dozens of competing story modules. F07 medium: Reduced chrome is not adequately supported. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360px viewport the page declares meta viewport width=1190 and Chrome lays out a 1250 CSS-pixel canvas scaled to 0.288. F08 critical: Responsive no horizontal scroll is not adequately supported. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Homepage, section, article, and search all retain roughly 1190-1250px desktop component geometry at 360px instead of reflowing. F09 medium: Component level responsiveness is not adequately supported. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Probe found 87 visible controls below 24px and the focused search input computed outline-style none. F10 medium: Input modality aware is not adequately supported. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Arabic title, logo, lead stories, section navigation, and headline hierarchy make the news-reading purpose immediately clear. |
support-core-task-successprimary-flow-completion | issues | high | The exercised search URL remained on a loading spinner with no results or actionable recovery after the wait window. F11 high: Primary flow completion is not adequately supported. |
support-core-task-successclear-system-state-and-recovery | issues | high | Search shows an indefinite spinner without empty/error explanation, retry action, or completion state. F12 high: Clear system state and recovery is not adequately supported. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.4s, FCP 2.5s, TBT 200ms, Speed Index 6.8s, and performance score 0.79. F13 high: Good core web vitals is not adequately supported. |
be-fast-and-stablevisual-stability | issues | high | Article layout observer measured CLS 0.158, including shifts of 0.0617 and 0.0928. F14 high: Visual stability is not adequately supported. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 2.3s main-thread work, TBT 200ms, and time-to-interactive 15.3s. F15 medium: Efficient main thread is not adequately supported. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 249 requests and 2.80MB transferred; seven parser-inserted stylesheets and one synchronous head script were confirmed as render-blocking candidates. F16 high: Efficient resource delivery is not adequately supported. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 503KiB unused JavaScript plus 14KiB unused CSS. F17 medium: Trim unused and duplicate code is not adequately supported. |
be-inclusivenames-roles-labels | issues | high | Probe found 7 unlabeled form controls, 19 empty links, and one unnamed button despite image alt coverage. F18 high: Names roles labels is not adequately supported. |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast audit failed on rendered content. F19 medium: Sufficient contrast is not adequately supported. |
be-inclusivestructure-and-focus | issues | high | Homepage heading sample begins with many navigation H2 elements before content, 19 links have no accessible name, and focused search has no visible outline. F20 medium: Structure and focus is not adequately supported. |
be-inclusivelegible-text | issues | high | Body text is 14px on a fixed 1190px layout scaled to 28.8% at 360px, making text and controls visually tiny. F21 high: Legible text is not adequately supported. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The fixed meta viewport width=1190 prevents mobile reflow and 87 visible controls are under 24px. F22 high: Zoom reflow targets and media is not adequately supported. |
follow-best-practicesno-console-errors | issues | high | Lighthouse errors-in-console audit scored 0 and DevTools Issues were logged. F23 medium: No console errors is not adequately supported. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype and UTF-8 are present, 13 images lack dimensions and Lighthouse found incorrect image aspect ratios. F24 medium: Sound document and assets is not adequately supported. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported a deprecated API warning and failed its Inspector Issues audit. F25 medium: Browser platform hygiene is not adequately supported. |
be-discoverabletitle-and-description | pass | high | Homepage and article both provide specific titles and meta descriptions; the article title and description match its content. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Robots permits major crawlers and links are real anchors, but meta viewport width=1190 makes all representative templates non-mobile-friendly. F26 medium: Crawlable and mobile friendly is not adequately supported. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage and article expose self-referential canonical URLs, index/follow robots, HTTP 200, and robots.txt points to a news sitemap. |
be-discoverablestructured-and-shareable-metadata | pass | high | Article exposes NewsArticle and BreadcrumbList JSON-LD plus complete Open Graph title, description, URL, and image metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, nosniff, frame protection, Referrer-Policy, and Permissions-Policy are all absent. F27 high: Secure transport and headers is not adequately supported. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 25 third-party origins and six known tracker domains; HAR attributed 209 requests and 2.51MB to third parties. F28 high: Data minimisation and third parties is not adequately supported. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No sign-in, account, passkey, or runtime permission request exists in the audited public-news paths. |
be-private-and-securedefensive-browser-policies | issues | high | All inspected defensive response policies were absent and three analytics/consent cookies lacked Secure while using SameSite=None for about 390-400 days. F29 high: Defensive browser policies is not adequately supported. |
be-resilientprogressive-enhancement | issues | high | Article discoverability found only 8% content-token overlap without JavaScript and classified the rendered article as a JS shell. F30 high: Progressive enhancement is not adequately supported. |
be-resilientresilient-runtime-behaviour | issues | high | Search stayed indefinitely in a spinner state and Lighthouse recorded console/Inspector errors, showing weak degraded runtime behavior. F31 medium: Resilient runtime behaviour is not adequately supported. |
be-resilientoffline-and-installable | not-applicable | high | A manifest is linked, but this public news audit found no declared offline/installable product intent; offline capability is not required for the core reading task. |
be-resilientnetwork-and-http-failure-states | issues | high | The search journey exposes no timeout, retry, stale-results, or explanatory failure state when results do not resolve. F32 medium: Network and http failure states is not adequately supported. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=ar and dir=rtl, and all representative screenshots render right-to-left Arabic content. |
be-internationalisedlocale-aware-data | issues | high | Visible Arabic publication dates are plain text with no time/datetime semantics, limiting locale-aware parsing and reformatting. F33 medium: Locale aware data is not adequately supported. |
be-internationalisedtime-zone-correctness | issues | high | Article dates have no machine-readable datetime or timezone even though Open Graph uses UTC, leaving visible event time ambiguous for automation. F34 medium: Time zone correctness is not adequately supported. |
be-trustworthyno-dark-patterns | pass | high | Consent offers Manage options alongside Consent and exposes Confirm choices/Close; no forced purchase, account, or cancellation pattern was found. |
be-trustworthyhumane-error-handling | issues | high | Search can remain on a spinner without an error explanation, recovery action, or accessible status announcement. F35 medium: Humane error handling is not adequately supported. |
be-trustworthytrustworthy-input-assistance | issues | high | The search input has no label and no autocomplete value, so assistive technology and input assistance receive no purpose cue. F36 medium: Trustworthy input assistance is not adequately supported. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription purchase, payment, cancellation, or account flow exists in the audited public-news scope. |
be-sustainableoptimised-assets | issues | high | All 100 sampled images use legacy PNG/GIF/JPEG; 75 lack srcset, 89 below-fold images are not lazy-loaded, and 13 lack dimensions. F37 high: Optimised assets is not adequately supported. |
be-sustainableno-wasteful-work | issues | high | The homepage loads 249 requests, including 209 third-party requests, before the reader interacts; Lighthouse also found 503KiB unused JavaScript. F38 medium: No wasteful work is not adequately supported. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 2.51MB and 209 requests, with ad-tech, analytics, and bidding origins dominating the load. F39 high: Third party and media budget is not adequately supported. |
be-agent-readystructured-agent-capabilities | issues | high | The public publisher allows major AI crawlers but exposes no WebMCP/tool declarations, while article no-JS content coverage is only 8%. F40 high: Structured agent capabilities is not adequately supported. |
be-agent-readyon-device-inference | not-applicable | high | The site is a conventional news publisher and exposes no summarisation or language-model feature for which on-device inference would be relevant. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | No representative repeatable app interaction exists on these document-style news pages; repeated scrolling is not a valid leak target. |
be-memory-efficientbounded-footprint | issues | high | Baseline heap contained 571,554 nodes and 31.30MB self size on a document page, alongside 249 requests and extensive third-party code. F41 medium: Bounded footprint is not adequately supported. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | After ten scroll cycles, heap node count fell from 571,554 to 569,377 while self size changed only +21,482 bytes; no unbounded retained growth signal appeared. |
Provenance
Canonical report: results/atomic/reports/0285-m_youm7_com.json
Report SHA-256: 4f98bb4240201564b2c839c9a0f505fd90b93a9525c8b40a54ebe4dfeabf1016
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_youm7_com/2026-07-19T17-21-01-913Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_youm7_com/2026-07-19T17-21-01-913Z
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.