Skip to content

Accessibility statement

Anyone selling accessibility should have their own site held to it. So here is what was tested and what to do if something gets in your way.

Scope

This statement covers the website at ercancicek.com in both its German and English versions.

How this statement was prepared

I prepared this statement on August 18, 2026, and last reviewed it on November 3, 2026. It is based on a self-assessment against WCAG 2.2.

How accessible is this site?

The site is built to WCAG 2.2 level AA and largely meets its requirements. The known exceptions are listed in the next section.

As a micro-enterprise I am not required to publish this statement. It is voluntary.

Parts that are not fully accessible yet

  • On desktop, Pixel-Ercan's speech bubble follows the mouse pointer, so you can't reach it with the mouse (WCAG 1.4.13). Press Escape to hide it for the rest of your visit. It only shows short quips, so you don't miss anything.
  • Mel-Menu, my playful portfolio from 2016, is not accessible. It only works with a mouse or a finger. It leads to pages you can also reach through the navigation.

Deliberate decisions

The green buttons stand out from the white and grey background with less than 3:1 contrast. WCAG does not require it here. The W3C says: If a control has visible content (such as text …), a border … is not required (Understanding 1.4.11, Boundaries (opens in a new tab)).

Content from other providers

Links to other sites, such as LinkedIn, GitHub or CodePen, lead to services whose accessibility I can't influence.

Report a barrier

If something blocks you, write to me at contact@ercancicek.com. I will answer and tell you when it is fixed.

Status of this statement

November 3, 2026