Manifest position 971 · CrUX rank bucket 1000
https://www.ptt.cc
Coverage complete
Coverage-complete representative audit of seven paths/templates. Not covered: posting/login/account flows (not exposed by public WebBBS), age-gated boards, exhaustive board categories, and external legal/Facebook destinations.
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 | Direct evidence shows the divergence documented in F001. F001 medium: Theme is fixed rather than preference-aware |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion probe found zero active animations, so no non-essential motion continued under reduce. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast screenshot retained visible text, controls, and board rows; Lighthouse found no foreground/background minimum-contrast failure. |
implement-natural-interactionsview-transitions | issues | high | Direct evidence shows the divergence documented in F002. F002 low: Navigation and state changes swap abruptly |
implement-natural-interactionsscroll-driven-animations | not-applicable | medium | No scroll-linked animation is present, so there is no scroll event implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | medium | No gesture-driven interaction is offered on the audited read/search surfaces. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The board action bar remains available above the listing and clearly exposes paging/navigation state without obscuring content. |
provide-guided-navigationanchored-positioning | issues | high | Direct evidence shows the divergence documented in F003. F003 medium: Article menus are ad-hoc div overlays |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, selected board state, paging labels, and the article “return to board” affordance provide continuity. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | All load screenshots show content immediately with no pop-up, interstitial, or obscuring banner. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Direct evidence shows the divergence documented in F003. F003 medium: Article menus are ad-hoc div overlays |
maximize-content-reduce-noisereduced-chrome | pass | high | Board and article screenshots devote nearly all space to listings/content with compact chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Direct evidence shows the divergence documented in F004. F004 high: Legacy pages render as a scaled desktop canvas on phones |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Direct evidence shows the divergence documented in F005. F005 low: Reusable listing UI has no component-level adaptation |
adapt-to-the-form-factorinput-modality-aware | issues | high | Direct evidence shows the divergence documented in F006. F006 high: Search and article-list controls are not robustly input-modality aware |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, hot-board directory, board title, article title, and search field make the current purpose and next route clear. |
support-core-task-successprimary-flow-completion | pass | high | The exercised home → WebBBS → Stock → article and Stock → search results journeys completed with real links and content. |
support-core-task-successclear-system-state-and-recovery | issues | high | Direct evidence shows the divergence documented in F007. F007 medium: Error routes provide no recovery |
be-fast-and-stablegood-core-web-vitals | issues | high | Direct evidence shows the divergence documented in F008. F008 high: Render-blocking dependencies delay content |
be-fast-and-stablevisual-stability | pass | high | Observed mobile layouts reported CLS 0 and Lighthouse measured CLS 0.052, within the good range, despite unsized-image risk. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded zero long tasks and 0ms total blocking time; Lighthouse TBT was 10ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | Direct evidence shows the divergence documented in F008, F009. F008 high: Render-blocking dependencies delay content F009 medium: User images lack dimensions |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Direct evidence shows the divergence documented in F010. F010 medium: Analytics code dominates shipped JavaScript |
be-inclusivenames-roles-labels | issues | high | Direct evidence shows the divergence documented in F011. F011 high: Content images and search lack accessible names |
be-inclusivesufficient-contrast | issues | high | Direct evidence shows the divergence documented in F012. F012 high: Inline links rely on color alone |
be-inclusivestructure-and-focus | issues | high | Direct evidence shows the divergence documented in F013. F013 high: Pages lack semantic structure and consistent focus indication |
be-inclusivelegible-text | issues | high | Direct evidence shows the divergence documented in F004. F004 high: Legacy pages render as a scaled desktop canvas on phones |
be-inclusivezoom-reflow-targets-and-media | issues | high | Direct evidence shows the divergence documented in F004, F006. F004 high: Legacy pages render as a scaled desktop canvas on phones F006 high: Search and article-list controls are not robustly input-modality aware |
follow-best-practicesno-console-errors | issues | high | Direct evidence shows the divergence documented in F014. F014 low: A missing favicon logs a console error |
follow-best-practicessound-document-and-assets | issues | high | Direct evidence shows the divergence documented in F009. F009 medium: User images lack dimensions |
follow-best-practicesbrowser-platform-hygiene | issues | high | Direct evidence shows the divergence documented in F015. F015 medium: The runtime ships an obsolete jQuery build |
be-discoverabletitle-and-description | issues | high | Direct evidence shows the divergence documented in F016. F016 medium: Key public templates omit meta descriptions |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Direct evidence shows the divergence documented in F004, F017. F004 high: Legacy pages render as a scaled desktop canvas on phones F017 medium: Indexing signals are incomplete |
be-discoverablecanonical-and-indexing-signals | issues | high | Direct evidence shows the divergence documented in F017. F017 medium: Indexing signals are incomplete |
be-discoverablestructured-and-shareable-metadata | issues | high | Direct evidence shows the divergence documented in F018. F018 low: Article metadata lacks structured data |
be-private-and-securesecure-transport-and-headers | issues | high | Direct evidence shows the divergence documented in F019. F019 high: Browser security headers and cookie flags are absent |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Direct evidence shows the divergence documented in F020. F020 high: Tracking begins immediately with a broad third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | DOM, screenshots, and active probes across representative routes directly support this outcome. |
be-private-and-securedefensive-browser-policies | issues | high | Direct evidence shows the divergence documented in F019. F019 high: Browser security headers and cookie flags are absent |
be-resilientprogressive-enhancement | pass | high | DOM evidence is server-rendered and the crawler screenshot with JavaScript disabled retained the homepage content; no empty app shell exists. |
be-resilientresilient-runtime-behaviour | issues | high | Direct evidence shows the divergence documented in F003. F003 medium: Article menus are ad-hoc div overlays |
be-resilientoffline-and-installable | issues | high | Direct evidence shows the divergence documented in F021. F021 medium: The WebBBS has no install or offline fallback |
be-resilientnetwork-and-http-failure-states | issues | high | Direct evidence shows the divergence documented in F007. F007 medium: Error routes provide no recovery |
be-internationalisedlang-dir-and-logical-properties | issues | high | Direct evidence shows the divergence documented in F022. F022 high: Language and time output are not internationalisation-ready |
be-internationalisedlocale-aware-data | issues | high | Direct evidence shows the divergence documented in F022. F022 high: Language and time output are not internationalisation-ready |
be-internationalisedtime-zone-correctness | issues | high | Direct evidence shows the divergence documented in F022. F022 high: Language and time output are not internationalisation-ready |
be-trustworthyno-dark-patterns | pass | high | No consent wall, upsell, forced continuity, disguised advertisement, or destructive action appeared in any audited journey. |
be-trustworthyhumane-error-handling | not-applicable | medium | No data-entry form with validation exists in the representative public surfaces; board search has no required/invalid state. |
be-trustworthytrustworthy-input-assistance | not-applicable | medium | No address, payment, sign-in, or sign-up fields are present; the only input is a board keyword search. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | medium | No checkout, subscription, consent, authentication, or account-management flow is exposed in the audited public WebBBS. |
be-sustainableoptimised-assets | issues | high | Direct evidence shows the divergence documented in F023. F023 medium: Article images are not delivered responsively |
be-sustainableno-wasteful-work | issues | high | Direct evidence shows the divergence documented in F020. F020 high: Tracking begins immediately with a broad third-party footprint |
be-sustainablethird-party-and-media-budget | issues | high | Direct evidence shows the divergence documented in F020, F023. F020 high: Tracking begins immediately with a broad third-party footprint F023 medium: Article images are not delivered responsively |
be-agent-readystructured-agent-capabilities | not-applicable | medium | Emerging capability is not applicable to this conventional public read/search surface; no developer intent to expose WebMCP tools was available. |
be-agent-readyon-device-inference | not-applicable | medium | No on-device inference use case is required for the core read/search journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 menu toggle cycles, heap self size grew only 37,188 bytes (~0.8%); major constructor counts remained stable. |
be-memory-efficientbounded-footprint | pass | high | Board heap was ~4.73MB self size with ~115k snapshot nodes, proportionate for a server-rendered listing. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after summaries showed stable Array count (9042), closures +15, and no Detached* constructor among the largest retained constructors. |
Provenance
Canonical report: results/atomic/reports/0971-www_ptt_cc.json
Report SHA-256: 3d145bf66397d18ad44b31127e25b0bb20b0fcd571f349d1fc303fd165e2ca31
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ptt_cc/2026-07-24T05-18-02-041Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ptt_cc/2026-07-24T05-18-02-041Z
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.