Accessibility Review Record
This is a dated source and test-definition review based on the Ministry checklist derived from WCAG 2.2 Level A and the site's WCAG 2.2 AA target. It is not a completed WCAG-EM evaluation, conformance report, certificate, or proof that every defined test passed in production.
Scope represented in the source review
- Turkish and English home, writing archive, and about pages.
- Category pages, representative Turkish and English articles, and the article table of contents.
- Privacy, disclaimer, statements hub, and accessibility pages.
- Shared header, footer, language switcher, theme control, pagination, filtering, and copy controls.
Methods used
- Source inspection of Vue templates, intended generated HTML semantics, CSS rules, and localized content.
- Review of earlier exploratory keyboard, 400% zoom, and narrow reflow notes; these are not treated as current expert-user results.
- Inspection of defined regression tests for ALT coverage, heading structure, language marking, link text, focus management, and ARIA states.
- Inspection of the defined production-build, route-generation, localization, and internal-link checks; a definition is not a retained passing result.
Recorded findings and fixes
- The repository contains localized ALT fields and a permanent rule requiring actual-image inspection when article images are added or changed.
- The repository contains a regression check intended to detect generic or unclear link text.
- English passages inside Turkish content were marked with lang="en".
- The repository contains a content check intended to detect instructions that rely only on color, position, shape, or direction.
- Sticky positioning was removed in narrow reflow so the header and article title do not obscure content at 400% zoom.
- The mobile table-of-contents control was moved earlier in keyboard order; open, close, Escape, focus return, and focus wrapping were fixed.
- Filter results are announced through a live region; the current page and article section are exposed programmatically.
- Durable checks were added for heading hierarchy, the skip link, visible focus, reduced motion, and minimum target size.
Ministry Level A checklist mapping
The official checklist covers 31 WCAG 2.2 Level A success criteria. “Mapped to source/test evidence” means the record points to a relevant control or test definition; it does not mean the criterion passed a complete current evaluation. “No applicable example identified” is limited to this source review. Neither label is an independent conformance decision.
1.1.1 — Non-text Content
Mapped to source/test evidenceALT coverage for meaningful images and exclusion of decorative elements from the accessibility tree were reviewed.
1.2.1 — Audio-only and Video-only (Prerecorded)
No applicable exampleThe reviewed pages contain no audio-only or video-only content.
1.2.2 — Captions (Prerecorded)
No applicable exampleThe reviewed scope contains no prerecorded synchronized media.
1.2.3 — Audio Description or Media Alternative
No applicable exampleThe reviewed scope contains no prerecorded synchronized media requiring a description.
1.3.1 — Info and Relationships
Mapped to source/test evidenceHeadings, lists, landmarks, statuses, and programmatic relationships for selected items were reviewed.
1.3.2 — Meaningful Sequence
Mapped to source/test evidenceDOM reading order and content order in narrow reflow were reviewed.
1.3.3 — Sensory Characteristics
Mapped to source/test evidenceInstructions were checked to ensure they do not rely only on color, shape, sound, direction, or location.
1.4.1 — Use of Color
Mapped to source/test evidenceSelections and states are also conveyed through text or programmatic state rather than color alone.
1.4.2 — Audio Control
No applicable exampleNo audio starts automatically when a page opens.
2.1.1 — Keyboard
Mapped to source/test evidenceHeader, filters, pagination, theme, language switcher, and mobile table of contents were reviewed for keyboard use.
2.1.2 — No Keyboard Trap
Mapped to source/test evidenceThe mobile table of contents contains focus, closes with Escape, and returns focus to its trigger.
2.1.4 — Character Key Shortcuts
No applicable exampleNo single-character keyboard shortcuts are defined.
2.2.1 — Timing Adjustable
No applicable exampleUser actions have no time limit.
2.2.2 — Pause, Stop, Hide
No applicable exampleThere is no automatically starting moving, scrolling, or blinking content.
2.3.1 — Three Flashes or Below Threshold
No applicable exampleThere is no flashing content.
2.4.1 — Bypass Blocks
Mapped to source/test evidenceA focus-visible skip link moves directly to the main content.
2.4.2 — Page Titled
Mapped to source/test evidenceReviewed routes have localized page titles describing their purpose.
2.4.3 — Focus Order
Mapped to source/test evidenceFocus order was reviewed, including keeping the mobile table-of-contents trigger from appearing after the article.
2.4.4 — Link Purpose (In Context)
Mapped to source/test evidenceLink text was scanned; generic wording such as “click here” was not found.
2.5.1 — Pointer Gestures
No applicable exampleNo feature requires a multipoint or path-based pointer gesture.
2.5.2 — Pointer Cancellation
Mapped to source/test evidenceInteractions primarily use native link and button activation behavior.
2.5.3 — Label in Name
Mapped to source/test evidenceVisible control labels were reviewed for inclusion in accessible names.
2.5.4 — Motion Actuation
No applicable exampleNo feature is operated by device motion.
3.1.1 — Language of Page
Mapped to source/test evidenceEvery route sets the html lang value to Turkish or English.
3.2.1 — On Focus
Mapped to source/test evidenceReceiving focus alone does not trigger an unexpected change of context.
3.2.2 — On Input
Mapped to source/test evidenceFilter and view controls change state consistently with their labels and expected behavior.
3.2.6 — Consistent Help
Mapped to source/test evidenceRepeated social contact links are generated from shared components in a consistent order.
3.3.1 — Error Identification
No applicable exampleThe reviewed public pages contain no data-entry form that produces validation errors.
3.3.2 — Labels or Instructions
No applicable exampleThere is no form requesting user input.
3.3.7 — Redundant Entry
No applicable exampleThere is no process requiring the same information to be entered again.
4.1.2 — Name, Role, Value
Mapped to source/test evidenceNative HTML controls, accessible names, and states such as aria-current and aria-expanded were reviewed.
Additional WCAG 2.2 AA checks
Beyond the Level A checklist, the following topics are represented in source controls or test definitions for the site's voluntary AA target; this list is not a current pass result.
- Text and interface contrast in light and dark themes.
- 400% text enlargement, 320 CSS pixel reflow, and text spacing.
- Visible focus and preventing sticky or fixed content from obscuring focus.
- Minimum target size and alternatives for interactions that would require dragging.
- Descriptive headings and labels, and more than one navigation route.
- Language marking for passages in another language.
- Consistent navigation and consistent identification of the same functions.
- Whether any applicable form, authentication, or error-prevention feature exists.
Limitations
This record is not an independent audit, formal conformance report, or certification. A complete WCAG-EM evaluation and a usability study with experienced disabled users have not been carried out. The screen-reader exercise was exploratory and cannot replace testing by an experienced user. The Playwright/axe browser suite has not been rerun after the latest information-architecture changes.