Manifest position 612 · CrUX rank bucket 1000
https://www.turkiye.gov.tr
Coverage complete
Coverage-complete public-surface audit. Authenticated/post-login services were excluded because no credentials or test account were supplied.
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 default capture, and the computed root color-scheme is “normal”. F01 medium: No user-preference-driven dark theme |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the header and search block still run 1 second fadeIn/fadeInDown animations and many 0.3–1 second transitions remain active. F02 medium: Reduced-motion preference does not suppress non-essential entrance motion |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast: more screenshot is unchanged from the default capture and no adaptive color-scheme is declared. F03 low: High-contrast preference produces no adaptation |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no view-transition CSS despite the browser API being available; observed route changes are full abrupt navigations. F04 low: Route and state changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | pass | high | Platform probe found no scroll-linked animation CSS and visual review found no parallax/scrollytelling effect that would require a scroll handler; no misuse was observed. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile screenshots show native vertical document scrolling and explicit carousel/navigation controls; no custom pointer-driven gesture that fights platform scrolling was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | DOM/computed evidence shows a fixed header, while the platform probe found no container/scroll-state rules or scroll timeline; the header does not adapt to page position. F05 low: Fixed navigation is not scroll-state aware |
provide-guided-navigationanchored-positioning | issues | high | The document-verification share menu is registered through edPopover JavaScript; the platform probe found no CSS anchor positioning rules or native popovers. F06 low: Transient menus rely on custom JavaScript positioning |
provide-guided-navigationdirects-attention | pass | high | Internal pages expose breadcrumb navigation, search results retain the query, and the verification flow exposes a four-step progress meter. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots across homepage, listing, content, form, and login show immediate content with no consent wall, popup, or interstitial obscuring it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | No blocking modal appears on load; disclosure and menu controls expose aria-expanded/aria-controls, and the tested flow remains dismissible/cancellable. |
maximize-content-reduce-noisereduced-chrome | pass | high | Mobile screenshots prioritize search, services, results, and form content; the header collapses to one compact bar. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360×800, layout metrics report scrollWidth=clientWidth=360 and zero horizontal overflow; all representative mobile screenshots reflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The representative pages reflow on mobile, but the platform probe found zero @container rules and computed container-type remains normal. F07 low: Responsive behavior is viewport-only rather than component-aware |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse reports 13 target-size failures; the direct probe found 44 visible interactive elements below 24 px in one dimension, including 11×11 carousel controls and 16 px-high footer links. F08 high: Numerous interactive targets are too small for reliable touch |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport prominently exposes service search and five plainly labelled service categories; verification and login screens state purpose and primary action. |
support-core-task-successprimary-flow-completion | pass | high | A search query returned 14 linked results, the public verification flow clearly states four stages, and login offers five authentication routes plus cancel/recovery; completion beyond authentication was intentionally not attempted without credentials. |
support-core-task-successclear-system-state-and-recovery | pass | high | Invalid verification submission shows a required-field error, the login page provides cancel and forgot-password actions, and the unknown route gives Back and Home recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.7 s, FCP 3.6 s, and performance 0.74; the separate trace measured LCP 2.46 s, showing variability around/above the good threshold. F09 high: Mobile loading performance misses the good LCP range |
be-fast-and-stablevisual-stability | pass | high | The 5 s mobile layout capture reports CLS 0 with no observed shifts; homepage images that lead the viewport reserve dimensions. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded one 84 ms long task and 34 ms total blocking time, while Lighthouse measured 0 ms TBT; scripting did not dominate the tested load. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR summary identifies two VeryHigh-priority stylesheets and four classic parser-inserted head scripts without async/defer/module; the DOM confirms these script attributes are absent. F10 medium: Parser-blocking resources lengthen the critical path |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 22 KiB unused JavaScript and 11 KiB unused CSS on the homepage. F11 medium: The page ships measurable unused CSS and JavaScript |
be-inclusivenames-roles-labels | issues | high | Lighthouse flags the my.gov.az link because its aria-labelledby name omits the visible URL/new-window text. F12 high: An interactive link’s accessible name does not match its visible label |
be-inclusivesufficient-contrast | issues | high | Lighthouse found seven contrast failures, including #4284be text on white/grey (3.32–3.98:1) and white text with a low-contrast teal text shadow. F13 high: Multiple text styles fail WCAG contrast |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports landmark-one-main failure, and the homepage DOM has zero <main> elements even though internal templates do use one. F14 high: The homepage lacks a main landmark |
be-inclusivelegible-text | pass | high | Representative 360 px screenshots show readable line wrapping, stable card/form alignment, and no clipping or horizontal truncation. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360 px layout itself has zero horizontal overflow, but Lighthouse reports 13 target-size failures across the reflowed homepage. F15 high: Touch target sizing undermines inclusive reflow |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed and no uncaught exception appeared during the representative page captures. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 26 of 35 images without width/height, 15 oversized images, 14 without responsive sources, and 24 legacy-format resources (including placeholders/icons). F16 medium: Image delivery lacks robust intrinsic and responsive sizing |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports one BFCache failure reason, reducing instant restoration on back navigation. F17 medium: The homepage is not eligible for back/forward cache |
be-discoverabletitle-and-description | pass | high | DOM evidence across homepage, search, information, verification, and login shows non-empty titles and a meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Robots allows all, the sitemap is populated, viewport metadata is present, and discoverability captures show 100% content coverage without JavaScript on home/list/search. |
be-discoverablecanonical-and-indexing-signals | issues | high | The probe found no canonical and zero hreflang links despite Turkish and English variants; robots and sitemap are otherwise present and permissive. F18 medium: Localized public pages omit canonical and hreflang signals |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage exposes four Open Graph tags but no JSON-LD for the government organization/site or search action. F19 low: Rich entity metadata stops at Open Graph |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and nosniff are present, but HSTS is absent, CSP permits unsafe-inline and unsafe-eval, Referrer-Policy is unsafe-url, and all five first-party cookies use SameSite=None. F20 critical: Security headers and cookie posture are weaker than expected for a national identity portal |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker capture found no known tracker domain and only the controlled e-Devlet CDN plus first-party analytics; secrets scan found no exposed credential. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; login offers password, electronic signature, mobile signature, internet banking, and national ID card rather than password alone. |
be-private-and-securedefensive-browser-policies | issues | high | The header audit found no Permissions-Policy and neither X-Frame-Options nor CSP frame-ancestors; CSP also lacks Trusted Types/origin-isolation protections. F21 high: Defensive browser policies are incomplete |
be-resilientprogressive-enhancement | issues | high | Discoverability shows 100% raw-content coverage, but the authored noscript message states e-Devlet requires JavaScript and core form behavior is script-dependent. F22 high: Core interaction requires JavaScript despite server-rendered content |
be-resilientresilient-runtime-behaviour | pass | high | Representative mobile pages and the share/menu/login controls render within viewport bounds; no cut-off overlay, blank shell, or unstable state was observed. |
be-resilientoffline-and-installable | issues | high | The platform probe found no web app manifest and the homepage exposes no service-worker registration path, despite being a high-use app-like portal. F23 medium: The app-like public service has no installable/offline web fallback |
be-resilientnetwork-and-http-failure-states | pass | high | The unknown route renders a clear 404 explanation with Back, Home, and footer navigation instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The English variant correctly sets lang=en, but its first 1,000 characters still include Turkish labels such as “Ana Sayfa”, “Ana Bölümler”, banner copy, and “Yeni Sekmede Açılır”. F24 medium: The English locale remains partly untranslated |
be-internationalisedlocale-aware-data | issues | high | The English route retains Turkish tax-period text and date wording instead of localized number/date content. F25 medium: Locale-sensitive content does not fully adapt to English |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public pages show dates but no time-of-day, time-zone coordination, recurring event scheduling, or DST-sensitive interaction to evaluate. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, disguised ad, forced continuity, preselected purchase, or confirmshaming was observed; login provides an equally visible cancel action. |
be-trustworthyhumane-error-handling | pass | high | Submitting the empty required verification field produces the specific Turkish message “Bu alanın doldurulması zorunludur” while preserving context. |
be-trustworthytrustworthy-input-assistance | issues | high | The public verification field and both login identity/password fields explicitly use autocomplete=off; the login form itself is also autocomplete=off. F26 high: Key identity and verification inputs disable autofill |
be-trustworthysafe-commercial-and-account-flows | pass | high | The authentication surface presents multiple methods, password recovery, explicit cancel, and contextual security guidance; no commercial commitment is present in tested public flows. |
be-sustainableoptimised-assets | issues | high | The image audit found 15 oversized images, 27 below-fold images without native lazy loading, and 14 images without srcset. F27 medium: Asset sizing creates avoidable transfer waste |
be-sustainableno-wasteful-work | pass | high | Trace showed low blocking time, HAR found only one tiny analytics beacon beyond CDN assets, and no autoplay audio/video or persistent background media was observed. |
be-sustainablethird-party-and-media-budget | issues | high | The 760 KB homepage load includes 10 font requests totaling 254 KB and 51 cross-origin CDN/analytics requests totaling about 750 KB, though no known commercial tracker was detected. F28 medium: Font and CDN transfer cost is high for a mostly informational first view |
be-agent-readystructured-agent-capabilities | issues | high | The probe found no WebMCP surface; agents must infer search and verification semantics from page markup even though raw content is crawlable. F29 low: High-value government tasks are not exposed as structured agent capabilities |
be-agent-readyon-device-inference | not-applicable | high | The tested search, directory, verification, and authentication tasks do not present an appropriate summarisation/generation workload where built-in on-device inference would clearly improve the experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 60 carousel state changes, heap self-size rose only ~106 KB (1.3%) and node count ~1.3% versus a fresh baseline, not evidence of unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was 7.97 MB self-size with 119,575 snapshot nodes for a 620-element public homepage, proportionate to the tested surface. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Baseline/post heap summaries show no Detached* constructor among top retained constructors and only small bounded closure/object changes after 60 state changes. |
Provenance
Canonical report: results/atomic/reports/0612-www_turkiye_gov_tr.json
Report SHA-256: 969b8456cf92d3b740cfa770666dce8ca2ecd08d18fcecdedb9a3561c12e58a4
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_turkiye_gov_tr/2026-07-21T22-41-00-588Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_turkiye_gov_tr/2026-07-21T22-41-00-588Z
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.