Manifest position 369 · CrUX rank bucket 1000
https://archiveofourown.org
Coverage complete
Coverage complete across 58 catalog checks and six representative public paths. Authenticated, posting, download, collection-management and account-settings flows were not covered because no credentials or mutation consent were supplied.
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-mode screenshot is pixel-identical to the light desktop view; the preference probe reports colorScheme normal and body background rgb(255, 255, 255) while prefers-color-scheme: dark matches. F01 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion probe found no active animations and only two 25 ms color transitions. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot preserves visible text, controls, borders and focus affordances. |
implement-natural-interactionsview-transitions | issues | high | DOM and stylesheet probes found no @view-transition rule or view-transition CSS on the representative MPA templates. F02 low: Cross-document navigation changes abruptly with no View Transition support. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, reveal or carousel interaction exists on the representative templates, so there is no implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The sampled MPA surfaces expose no swipe, pull, drag or gesture-driven control requiring a platform gesture implementation. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 4,613 px mobile search-results page and 3,306 px work detail keep static global chrome and expose no scroll-state queries or progress affordance. F03 low: Long pages provide no scroll-state-aware orientation. |
provide-guided-navigationanchored-positioning | issues | high | DOM inspection shows .dropdown-menu and custom #modal-wrap/#modal elements, with no anchor-name, position-anchor or position-try usage. F04 low: Menus and overlays use legacy manually positioned dropdown/modal markup. |
provide-guided-navigationdirects-attention | pass | high | Representative page loads land on descriptive headings and the mobile article highlights the current item in its local navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots across home, search, work and article templates show content immediately with no obscuring interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The rendered DOM contains custom #modal-bg, #modal-wrap and #modal while the probe reports zero dialog, popover and details elements. F05 medium: Custom div-based overlays replace semantic dialog and popover primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Homepage and reading templates devote the main viewport to archive content with compact global navigation. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout primitives report 0 px overflow at 360 px on home, search results and work detail. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Stylesheet inspection found no @container rules even though cards, forms and navigation modules are reused across wide and narrow contexts. F06 low: Responsive behavior relies on viewport styles rather than component-level adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The 360 px target probe lists primary navigation at 26 px high, Search at 22 px, news links at 13 to 16 px and footer links at 12 to 28 px. F07 high: Many mobile controls and links have touch targets substantially below 44 by 44 CSS pixels. |
support-core-task-successclear-purpose-and-primary-action | pass | high | First viewport states clear the archive purpose and expose fandom browse, search and account actions. |
support-core-task-successprimary-flow-completion | pass | high | The Work Search journey completed to 76,325 results for test and exposed Edit Your Search without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | The 404 route returns HTTP 404, names the failure clearly, and preserves global navigation and search. |
be-fast-and-stablegood-core-web-vitals | pass | high | Trace measured FCP/LCP 922.74 ms, TBT 0 and layout CLS 0.0014; Lighthouse performance scored 1.0. |
be-fast-and-stablevisual-stability | pass | high | Desktop CLS was 0.0014 and mobile CLS was 0 with no observed shifts. |
be-fast-and-stableefficient-main-thread | pass | high | Trace found zero long tasks and 0 ms TBT; mobile search results recorded one borderline 50 ms task. |
be-fast-and-stableefficient-resource-delivery | pass | high | HAR totals 28 requests and 207 KB with no missing cache headers or HTTP errors; trace LCP remained under 1 second. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 53 KiB unused JavaScript in jQuery UI 1.10.0 (89.9 percent unused) and 17 KiB unused CSS (85.3 percent); HAR attributes 94,109 transferred bytes to the Google CDN. F08 medium: The homepage ships substantial unused legacy JavaScript and CSS. |
be-inclusivenames-roles-labels | pass | high | Lighthouse label and link-name audits pass; DOM probes find labels for visible form fields and alt text on the logo. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured 3.61:1 for 12.25 px white text on #1185fe; 4.5:1 is required. F09 medium: The Bluesky follow button fails WCAG AA text contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse flags the account module h4 after the page h2 as invalid heading order. F10 medium: The homepage heading hierarchy skips a level. |
be-inclusivelegible-text | pass | high | Desktop and mobile screenshots show readable body copy, restrained line lengths and no clipping on sampled templates. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Layout evidence shows no horizontal overflow at 360 px, while the target probe finds dozens of active controls below 44 px high. F11 medium: Mobile reflow succeeds, but target sizing does not remain comfortably operable. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passes with an empty error table. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive reports missing width and height; Lighthouse expects about 80 by 56 pixels but receives 61 by 42, and the image contributes a small observed layout shift. F12 low: The shared logo lacks intrinsic dimensions and is too low-resolution for its rendered size at common device pixel ratios. |
follow-best-practicesbrowser-platform-hygiene | issues | high | The DOM loads jQuery 1.9.0 and jQuery UI 1.10.0; Lighthouse reports three deprecations from Cloudflare challenge code. F13 medium: The page depends on stale libraries and a third-party script emitting deprecated API warnings. |
be-discoverabletitle-and-description | issues | high | The sampled work has a descriptive title but repeats the generic site description rather than summarizing the visible work. F14 medium: Detail and article templates do not provide page-specific meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Links use real href values, viewport meta is present, public content is server rendered, and robots rules intentionally exclude search/query surfaces. |
be-discoverablecanonical-and-indexing-signals | issues | high | Home and sampled work probes found no rel=canonical; /sitemap.xml returned HTTP 404 while robots.txt defines crawler-specific policy. F15 medium: Public pages lack canonical links and the expected sitemap endpoint returns 404. |
be-discoverablestructured-and-shareable-metadata | issues | high | The sampled work probe found no JSON-LD and no Open Graph tags despite representing a rich creative work entity. F16 medium: Public works and news lack structured data and social-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show no HSTS, CSP is limited to frame-ancestors, and _otwarchive_session is HttpOnly and SameSite=Lax but lacks Secure. F17 high: Transport defenses and session-cookie settings are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker probe found no known trackers and only one third-party origin; secrets scan found no exposed credentials. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login DOM contains username and password controls but no WebAuthn or passkey affordance; no permission prompt fired on load. F18 medium: Sign-in exposes password authentication without a phishing-resistant passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | Clickjacking, nosniff and Referrer-Policy are present, but HSTS and Permissions-Policy are absent and CSP only defines frame-ancestors. F19 medium: Browser-enforced policy coverage is partial. |
be-resilientprogressive-enhancement | pass | high | Discoverability reports 100% homepage and 82% work-content coverage without JavaScript, with no empty app shell. |
be-resilientresilient-runtime-behaviour | pass | high | Menus have real fallback hrefs and sampled pages remained usable without JavaScript; no clipped overlay was observed in tested states. |
be-resilientoffline-and-installable | not-applicable | high | AO3 is a server-rendered content archive rather than an installable app in the tested public scope; offline reading is separately available through downloads. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately missing path returns a clear 404 message while preserving site navigation and search. |
be-internationalisedlang-dir-and-logical-properties | issues | high | CSS captured by the DOM primitive contains 95 physical left/right declarations versus 12 logical inline declarations; html has lang=en but no explicit dir. F20 medium: The stylesheet remains heavily dependent on physical left and right properties. |
be-internationalisedlocale-aware-data | issues | high | Representative pages expose text such as 20 Jul 2026 and 2026-07-20 without time datetime semantics or evidence of locale-aware formatting. F21 low: Dates are rendered in fixed English or ISO-style text rather than user-locale-aware markup. |
be-internationalisedtime-zone-correctness | pass | high | News timestamps explicitly label UTC and sampled work publication dates are unambiguous ISO dates. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, disguised advertisement, forced continuity or confirmshaming appeared in the sampled public browse, search and reading journeys. |
be-trustworthyhumane-error-handling | pass | high | Search accepts optional criteria without premature required errors; the invalid-looking date criterion remains editable and returns a transparent query summary. |
be-trustworthytrustworthy-input-assistance | issues | high | The username field uses autocomplete=on, while password, guest name and guest email fields omit purpose-specific tokens. F22 medium: Authentication and guest-input fields use incomplete autocomplete semantics. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The public login surface has no passkey registration, authentication or management affordance, leaving a phishing-prone credential as the only visible method. F23 medium: The account flow relies on password-only authentication. |
be-sustainableoptimised-assets | issues | high | The images primitive finds one PNG logo with no responsive source; HAR also transfers a 13,314-byte PNG texture on every homepage load. F24 low: Shared decorative and brand images use legacy PNG assets without responsive alternatives. |
be-sustainableno-wasteful-work | pass | high | Trace shows no background long tasks, HAR is 207 KB total, and no autoplay media exists on sampled templates. |
be-sustainablethird-party-and-media-budget | issues | high | HAR records 94,109 of 206,994 bytes from ajax.googleapis.com, dominated by jQuery and jQuery UI, with no known tracker detected. F25 medium: A third-party legacy script pair consumes nearly half the homepage transfer budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | AO3 explicitly disallows GPTBot, ChatGPT-User and CCBot in robots.txt, which evidences that agent-facing capability exposure is outside current intent. |
be-agent-readyon-device-inference | not-applicable | high | The public archive does not present an on-device inference use case, and its robots policy indicates no current agent-facing intent. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | Ten login-menu toggles in one page session reduced reported used heap by 109,447 bytes after settling and left DOM count unchanged at 323. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap summary reports 5.5 MB self size and 102,712 snapshot nodes, proportionate to the page and stable interaction probe. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Repeated toggling produced zero DOM-node growth; before/post heap summaries contain no reported Detached constructor population. |
Provenance
Canonical report: results/atomic/reports/0369-archiveofourown_org.json
Report SHA-256: fd1539f3ce7ecf0bb19645708fc0d0877906e7dbfdcfac9ef0653bed3a4ac502
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/archiveofourown_org/2026-07-20T07-24-31-512Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/archiveofourown_org/2026-07-20T07-24-31-512Z
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.