SCNET · Enterprise IT · Ankara, Türkiye

Sanal Çekirdek

We publish our accessibility target — and what we have not met.

An accessibility statement is the document that sets out which accessibility target a website follows, what has been done to meet it and what has not been done yet. This page covers sanalcekirdek.com and rests on self-assessment.

A statement is not a conformance certificate. Rather than calling an unaudited site 'accessible', we write the target, the practice and the limit separately.

Target and conformance status

The site is built toward WCAG 2.2 level AA. Conformance has not been audited by an independent organization to date; the assessment here rests on the development team's own measurement. No claim of full conformance is made on this page.

  • Target version WCAG 2.2, target level AA
  • Assessment method: self-assessment
  • No third-party audit report exists
  • The statement is updated as the site structure changes

Accessibility decisions in place

Accessibility is not a layer added after publication; it is the markup itself. Pages are built from HTML that carries meaning, can be traversed end to end with a keyboard, and keep focus visible at every step.

  • Every content page opens with a 'skip to content' link; the error page has no navigation block to skip, so it needs none
  • The menu follows a disclosure navigation pattern open to keyboards
  • The focus ring is never removed from any component
  • Color contrast is calculated against the AA threshold

User preferences come before site defaults

The system setting that reduces motion is honored, and every page with a masthead carries a button that stops motion. Stopped motion covers not only animation but in-page smooth scrolling as well; the preference is stored in the browser and still applies on the next page.

  • The motion preference is stored in the browser
  • The system 'reduced motion' setting is applied separately
  • Light and dark themes meet the same contrast threshold
  • Page language is declared; the two languages are published separately

Known limits and feedback

Every untested area is a limit. Systematic testing with screen readers has not been carried out yet. The statement covers this website only; systems built for customers are subject to their own assessment.

  • Screen reader testing is among the planned work
  • No VPAT or equivalent conformance report has been prepared
  • Every reported issue is logged and answered
  • Corrections appear in the update to this page

How we work

  1. Decide accessibility at the design stage
  2. Build markup from meaning rather than appearance
  3. Review keyboard and focus order page by page
  4. Verify contrast and motion preferences by measurement
  5. Close each reported issue with a record and a fix

How success is measured

  • Every page can be traversed end to end with a keyboard
  • Focus order matches visual order
  • Contrast measurements stay above the AA threshold
  • Reported issues are tracked to a recorded close

Frequently asked questions

Does the site conform to WCAG 2.2 AA?

That is the target; full conformance is not claimed because no independent audit has been carried out. The success criteria met in self-assessment and the known limits are written separately on this page.

How do I report an accessibility issue?

Write to the address on the contact page and name the page you were on and the assistive technology you used. The report is logged; no general resolution-time promise is made, but you are told what changed.

Does the statement cover customer projects?

No. This statement covers sanalcekirdek.com only. Accessibility requirements for systems built for a customer are defined in that engagement's own contract.

If something on the site made access harder, tell us; knowing the page and the tool you used makes the fix faster.

Report an accessibility issue