Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Accessibility Test Automation: a11y Checks in CI with axe-core, Lighthouse, Playwright and ESLint, and the Limits of Automation
You protect accessibility in CI not with one tool but with layers: angular-eslint, axe in component tests, page and state scans in a real browser, Lighthouse as a regression alarm, and the manual testing that is still needed. In Bookstore we find a real violation that only appears in one state, set up a GitHub Actions gate that baselines existing debt and fails the build on new violations, and produce a Level A report for the Ministry's checklist.
What Is Accessibility and Why Is It Mandatory? WCAG 2.2, POUR, A/AA/AAA and Obligations in Türkiye and the EU
Accessibility means a product can be used by everyone, including people with disabilities, and today it is a legal obligation through Circular 2025/10 in Türkiye and the European Accessibility Act in the EU; in practice both point to WCAG 2.2 AA. The post explains WCAG's structure of POUR, guidelines, success criteria and levels, what changed in 2.2 and what the Circular and the EAA mean for developers; we set up the series' Bookstore lab and run the first axe scan.