Last reviewed: 22 October 2026.

Mor David wants mordavid.com to be usable by everyone, including people with disabilities. This statement describes the accessibility level of the site, the adjustments that were made, known limitations, and how to ask for help.

Standard and conformance level

The site aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, which covers the requirements of Israeli Standard IS 5568 (based on WCAG 2.0 level AA) as required by the Equal Rights for Persons with Disabilities (Accessibility Adjustments for Service) Regulations, 5773-2013.

Current status: partially conformant. Automated and manual keyboard testing found no remaining failures of WCAG 2.1 AA; the status will be updated to fully conformant after screen-reader testing. Known limitations are listed below.

Accessibility adjustments on the site

Semantic structure: proper headings, landmarks (header, navigation, main content, footer) and lists, so screen readers can navigate the page.
Full keyboard access, with a visible focus indicator and a logical focus order.
Text alternatives for informative images; decorative images are hidden from assistive technology.
Sufficient colour contrast in both the dark and the light theme, and information is never conveyed by colour alone.
Text can be resized up to 200% and the page zoomed up to 400% without loss of content; the layout adapts to small screens.
Animations respect the operating system's "reduce motion" setting: decorative transitions are turned off, and the logo carousel moves at half speed. A short scan-line effect on the home-page portrait runs twice on load (about 3 seconds in total) and then stops. The carousel can be paused at any time with its pause button or by hovering over it, and the accessibility menu's "Stop animations" option stops it completely.
The contact form has visible labels, marks required fields, shows an error message next to each field that needs correction, and announces the result to screen readers.
Links that open in a new tab are announced as such to screen readers.

Accessibility menu

An accessibility menu is available from the "Accessibility" button at the bottom corner of every page. It lets you:

increase the text size;
switch to a high-contrast display;
stop animations and transitions;
highlight links;
increase line, word and letter spacing for easier reading.

Your choices are saved in your browser (local storage) and applied on every page until you reset them. The menu complements, and does not replace, the accessibility built into the site itself.

Known limitations

Despite the effort to make every page accessible, some content may not yet be fully accessible:

Screenshots in articles: some article images are screenshots of code, terminals or messages. Each has a text description, but not every detail visible in the image is reproduced in text.
Code samples are presented as preformatted text and may require horizontal scrolling on small screens.
Older articles republished from other platforms (such as Medium) may not follow the heading structure of newer content.
Third-party sites linked from this site (such as GitHub, LinkedIn, X or Medium) are not under the site's control, and their accessibility is the responsibility of their operators.

If you find a barrier that is not listed here, please report it (see below).

Compatibility and testing

The site is designed to work with recent versions of major browsers (Chrome, Firefox, Safari and Edge) and with common screen readers (such as NVDA, JAWS and VoiceOver).

Testing method: automated checks with axe-core on every page in both themes at desktop and mobile widths, manual keyboard-only testing, colour-contrast measurement, reflow testing at 320 px and 400% zoom, and text-spacing override testing (October 2026). Screen-reader testing with NVDA and VoiceOver is planned, and this statement will be updated with its results.

Accessibility coordinator and feedback

If you encounter an accessibility problem, need information in an accessible format, or have a suggestion, please contact the accessibility coordinator:

Name: Mor David
LinkedIn: mor-david-cyber
Or use the contact form.

When reporting a problem, it helps to include the page address, a short description of the issue, and the browser and assistive technology you were using. Requests are answered as soon as possible, and in any case within 7 business days.

Updates to this statement

This statement was last reviewed on the date shown at the top and will be updated as the site changes and accessibility is improved.