Accessibility Statement

I want this site to be usable by as many people as possible, including people who use screen readers, keyboard navigation, or other assistive technology.

The standard I build to

This site is built to target the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. In practice, that means I pay attention to things like:

• Color contrast that meets AA thresholds for text and interface elements
• Full keyboard access, with a visible focus indicator and a skip-to-content link
• Proper heading structure and landmark regions so assistive technology can navigate the page
• Labels on every form field, and clear, descriptive links
• Meaningful alternative text for images, and decorative images marked as such
• Respecting the "reduce motion" setting in your operating system

What changed in the last review

I audited the whole site against these points in August 2026 and fixed what did not hold up:

• The focus outline was brand green everywhere, which is easy to see on the light pages but nearly invisible on the dark bands and the footer. On dark sections it is now white.
• The chat button floats over the page, and where it crossed the dark footer its edge disappeared into the background. It now carries a light ring.
• Three "Open the live demo" links sat on the same page with identical names, so a screen reader read the same thing three times. Each one now names its project.
• The project form marked errors only through the browser's own popups. It now shows a message under the field it belongs to, moves focus there, and announces the sending and success states.
• The "Skip to content" link moved the page but not always the focus, and landed under the sticky header. Both are fixed.

Honest limits

"Targeting WCAG 2.1 AA" is a commitment to a standard, not a legal certification. Accessibility is ongoing work, and no site is ever perfectly accessible for everyone. If you come across something that is hard to use, I'd genuinely like to know. It helps me fix it and build better.

I do not use an accessibility overlay or widget on this site. Those tools often create more problems than they solve; instead, accessibility is built into the underlying code.

Two things I know about and have not done yet: the project form has one heading for the whole page, so there is no separate heading to jump to before the form itself; and the three concept demo sites under /demo/ were built earlier and have not been through the same review as the rest of the site.

Telling me about a problem

If any part of this site is difficult to access or use, please email me at berat@beratsimsek.com with a short description of the problem and the page it's on. I read every message and will do my best to put it right.

Contact

Berat Şimşek, independent freelancer, Türkiye (GMT+3). Email: berat@beratsimsek.com.