Skip to main content
Accessibility

Accessibility Statement

This is a personal website where I share ideas, experience, and technical notes. I want that work to be readable by as many people as possible without unnecessary barriers. I see accessibility not merely as a legal obligation, but as a natural part of the open web.

I am not disabled, and I do not have a disabled family member or close contact who can test this site regularly. I therefore cannot assume that I fully understand the barriers other people encounter. I am still trying to make the site as accessible as I can by following standards, approaching the work with empathy, and making accessibility part of ongoing maintenance. Feedback about anything I have missed is especially valuable.

Target and scope

Turkey’s 2025/10 accessibility circular covers the public bodies and the listed private-sector and e-commerce services in its scope. Based on this site's current personal, non-transactional publishing model, it does not appear to fall within those listed categories; this is a conditional assessment, not legal advice, and must be revisited if the service model changes. I voluntarily use WCAG 2.2 Level AA as the engineering and publishing target.

Conformance status

This statement records a self-evaluation; it is not a certificate or an independent conformance report. The site uses WCAG 2.2 Level AA as its development baseline. I do not currently claim “full conformance” or certification because a complete WCAG-EM evaluation and usability testing with experienced disabled users have not yet been carried out.

What I reviewed and changed

The current public record is a source and test-definition review, not a completed WCAG-EM evaluation. It identifies controls present in the repository and the checks defined for changes; a defined check is not described as a passed production test without a retained result.

  • Semantic heading and landmark structure, a skip link to the main content, page language, and language attributes for passages in another language.
  • Keyboard operation, visible and logical focus order, focus management in the table-of-contents popover, and protection against fixed layers covering the focused element.
  • Text resizing to 200% and reflow at 400% zoom, including non-sticky narrow layouts and removal of clipping from necessary text.
  • Localized alternative text for cover and inline images, with decorative visuals removed from the accessibility tree.
  • Link purposes that remain understandable without vague labels such as “click here”.
  • Selection and status that do not rely only on color, shape, or position; dynamic result announcements, reduced-motion support, and light/dark theme checks.

Assessment approach

The 28 August 2026 record is a source and test-definition review carried out by the site owner and developer. Automation is intended as a repeatable safety net, not as a substitute for human evaluation, and the page distinguishes test coverage from completed test evidence.

  • Defined source and content regression checks for structure, alternative-text coverage, link names, and language parts.
  • A defined axe-core browser audit suite for representative templates, both languages, light and dark themes, and a narrow reflow viewport.
  • Earlier exploratory keyboard, focus, screen-reader, and 400% zoom checks, which are not treated as expert usability evidence.
  • Defined production-build, localization-key, and internal-link checks for ongoing changes.

Technical specifications

The accessibility of this site relies on semantic HTML, CSS, JavaScript, and WAI-ARIA where native HTML does not express the necessary state. The main article content is rendered as HTML on the server; some menus, filters, theme controls, and copy actions require JavaScript.

Known limitations

No complete current evaluation verifies every WCAG 2.2 A and AA success criterion for the production site. Automated tools and experiments by a developer who is not an experienced screen-reader user cannot replace the lived experience of disabled people. A complete WCAG-EM evaluation and usability testing with experienced disabled users remain outstanding; not every browser, operating-system, and assistive-technology combination has been tested. Third-party sites reached through external links are outside this statement’s scope.

Ongoing maintenance

Accessibility is not a one-off project. WCAG 2.2 AA rules are part of this repository’s development instructions and regression controls. New pages, components, and content will preserve the same baseline; this statement will be updated when known limitations or the evaluation scope changes and reviewed at least annually.

Feedback

If you cannot reach a page, operate a control, or understand content because of an accessibility barrier, you can contact me on X or LinkedIn.

If possible, include the page address, the barrier you encountered, and the browser or assistive technology you were using. You do not need to disclose your disability or other personal information. Only the detail needed to understand and repair the issue is useful; I will try to respond as soon as I can.

References

The structure of this statement and its technical target are based on the following sources.