Implemented features and testing limits

This website includes a skip-to-content link, semantic headings, labelled form fields, visible keyboard focus, Hebrew RTL and English/Russian LTR layouts, and reduced-motion support. WCAG 2.2 Level AA is an improvement target. This statement does not claim a comprehensive audit across all browsers and assistive technologies, or certify conformance. We continue to investigate and correct reported barriers.

Feedback and assistance

We continuously work to keep our website accessible and easy to use. If you encounter any difficulty reading content, navigating pages or submitting an enquiry using assistive technology, please contact us by email or WhatsApp as listed on the Contact page. Mention the page URL and nature of the issue so we can assist you directly and resolve the technical barrier.

Contact

CyberFixCrew
[email protected]
Message us on WhatsApp

Report the barrier you encountered

If a page or form is difficult to use, send its address and a short description through the contact details. Device, browser and assistive-technology details can help when you are comfortable sharing them. We can discuss an alternative way to handle the enquiry while investigating the issue. This statement is not an accessibility certification.

Read the scope of local accessibility checks

On 29 October 2026, local English-page checks covered 43 routes in Chromium-based Edge at widths 1440, 390 and 320 pixels, with additional checks without JavaScript. They examined headings, links, horizontal overflow and selected interaction paths.

  1. Use the skip link to reach main content.
  2. Contact us if navigation or enquiry submission presents a barrier.
  3. Include the page, browser and assistive technology when relevant.

What the local checks do and do not establish

These checks do not certify WCAG conformance or represent a complete screen-reader assessment. WCAG 2.2 AA remains an improvement target. Existing email and WhatsApp routes provide an alternative while a reported barrier is investigated.

What the local checks do and do not establish
CheckedObserved scopeNot established
LayoutThree viewport widthsEvery device/browser
KeyboardSkip-link focus and selected form behaviorComplete keyboard audit
RenderingHeadings without JavaScriptScreen-reader conformance

Example: report the step where a barrier occurs

If an input is difficult to use, send the page and the step where progress stopped through the direct contact alternatives. This is an illustrative scenario, not a customer case or a promised result.

Further reading: W3C: Web Content Accessibility Guidelines overview