Accessibility Statement

Daniel Mashkov is committed to providing an inclusive web experience for all users, including people with disabilities, in accordance with Israel's Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013 (regulation 35), which require Israeli Standard IS 5568 — based on the W3C Web Content Accessibility Guidelines (WCAG) 2.0 — at level AA. The site targets WCAG 2.2 level AA, a later version of the same guidelines.

• Semantic HTML and ARIA tree: <header>, <nav>, <main>, <footer>, and <section> landmarks on every page. ARIA roles (role, aria-label, aria-live, aria-modal) set on all interactive components.
• Full keyboard navigation: All interactive elements reachable via Tab, Enter, Space, and Escape. Focus traps activate in modals and the mobile navigation drawer.
• Color contrast ≥ 4.5:1: Body text measures 7.73:1 on the light theme's white background (11.2:1 in the dark theme, 13.3:1 in the comic theme); headings measure 14.89:1. Exceptions found in the September 2026 audit — some white text on the brand gradient and a few comic-theme links — are listed under Known Gaps.
• Alt text on all images: Decorative images carry alt=""; content images carry specific descriptions.
• Focus management in modals: The exit-intent offer and the booking modal return focus to the triggering element on close.
• Respects prefers-reduced-motion: CSS and requestAnimationFrame-driven animations, including the CountUp number counters, are suppressed under prefers-reduced-motion: reduce. The site uses native browser scroll throughout — no smooth-scroll library — and scroll-linked effects are disabled when reduced motion is on.
• Skip-to-content link: First focusable element on every page jumps to #main-content.
• Full RTL support for Hebrew: CSS logical properties (text-start, ps-/pe-) throughout; the Hebrew pages are checked in Chrome and in WebKit, the engine behind Safari.
• Autocomplete on form fields: Name, email, phone and company fields carry the matching autocomplete values.
• Respects your color-scheme preference: The site follows your operating-system light/dark preference — a dark OS appearance loads the dark theme automatically (prefers-color-scheme) and live-updates when you change it. You can also choose light, dark, or the comic theme yourself from the control panel; each theme is tuned for readable text contrast.

SC 2.5.5 (AAA) — Target Size (Enhanced) — 44×44 CSS px on primary controls

Primary controls and navigation — buttons, navbar links, the language toggle, the project filter chips and the cookie-banner buttons — are at least 44×44 CSS pixels. All other targets are at least 24×24 CSS pixels or spaced accordingly, which meets SC 2.5.8 Target Size (Minimum, AA); inline text links are exempt under both criteria.

Partial for 2.5.5, which asks for 44×44 on every target.

SC 3.3.7 (A) — Redundant Entry

Multi-step forms (project intake, scope estimator) never ask for the same information twice, and the values you typed are kept when validation fails, so nothing has to be re-entered. There is no session timeout and no CAPTCHA.

SC 3.3.8 (AA) — Accessible Authentication (Minimum)

The site has no login, account or password. No form requires a cognitive test (puzzle, image recognition or transcription); spam is filtered on the server without asking you to prove anything. Fields carry autocomplete values so browsers and password managers can fill them.

SC 1.4.6 (AAA) — Contrast (Enhanced) — 7:1 Ratio

Body text (#52525b on #ffffff) measures 7.73:1; headings (#27272a on #ffffff) measure 14.89:1. Body text is 11.2:1 in the dark theme and 13.3:1 in the comic theme.

Known gap: secondary (muted) text measures 5.28:1 in the light theme and 6.24:1 in the dark theme — AA, but below 7:1. Gradient-clipped headline text can also fall below 7:1.

SC 2.4.13 (AAA) — Focus Appearance — 3:1 indicator

Buttons and form fields show a 2px solid ring in --color-primary-deep with a 2px outline-offset, so the ring sits on the page background: 5.77:1 against white, well above the 3:1 minimum. The base brand cyan is only 2.06:1 on white, which is why the deepened token is used. Plain text links use the browser's default focus indicator.

Partial: the custom ring covers buttons and form fields; other links rely on the browser default.

SC 2.4.11 (AA) — Focus Not Obscured (Minimum)

The fixed navbar is offset with scroll-padding-top on the document root, so a focused element scrolls clear of it.

Known issue: on small screens the floating buttons and the cookie banner can overlap page content. This is being reduced.

SC 2.3.3 (AAA) — Animation from Interactions — Vestibular Disorder Protection

The site uses native browser scroll — no smooth-scroll library is loaded. With prefers-reduced-motion: reduce, CSS and requestAnimationFrame-driven animations, including the CountUp counters and scroll-linked effects, are suppressed.

• SC 1.4.3: The September 2026 audit measured some white text on the brand gradient at about 2:1, and a few comic-theme links at 3.9:1 — below the 4.5:1 AA minimum. Being fixed.
• SC 1.4.6: Secondary (muted) text — 5.28:1 light, 6.24:1 dark — and gradient-clipped headline text fall below 7:1.
• SC 1.2.6: Sign Language: Not provided — no sign language interpretation available for video or audio content.
• SC 2.4.9: Some "Read more" patterns rely on surrounding context for link purpose. Planned fix.
• Screen readers: Manual testing with NVDA and VoiceOver has not been done yet. It is planned; until then, screen-reader support rests on semantic HTML, ARIA and automated checks.

• Email: info@danielmashkov.com
• Phone / WhatsApp: +972 58 345 8145
• Accessibility contact: Daniel Mashkov, who runs this site
• Describe the issue, your browser, version, and assistive technology in use
• You can report a missing accessibility adjustment or ask for any content or service in another way; until a fix is live, I will provide it by another route, such as email or a call
• Acknowledgment within 48 hours; resolution or workaround within 14 business days
• Third-party parts: the booking calendar (Cal.com) and the WhatsApp chat are external services whose accessibility is up to their providers, so conformance there may be partial. You can always book or ask by email instead

• axe-core automated checks (Playwright, both languages)
• Keyboard-only navigation
• Reflow at 320 CSS pixels
• Contrast measured on rendered pixels in Chrome
• Browsers checked: Chrome on desktop and WebKit (Safari's engine) on mobile. Other current browsers should work but are not tested separately. Forms and booking need JavaScript enabled
• Manual screen-reader testing (NVDA, VoiceOver) — planned, not yet done