Accessibility Statement

We design Merlin to work with a keyboard, with screen readers, with browser zoom and on a phone. If something gets in your way, tell us: we'll help you complete the task another way and fix the problem.

We aim to meet Israeli Standard IS 5568, which is based on the Web Content Accessibility Guidelines (WCAG) 2.0 at level AA, as the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013 require. We work toward WCAG 2.1 level AA.

Merlin works best in the current versions of Chrome, Safari, Edge and Firefox, with VoiceOver on Mac and iPhone, and NVDA on Windows.

• Keyboard: most of Merlin can be used with a keyboard alone (see the limitations below), with a visible focus outline and a “Skip to content” link. Windows keep the keyboard inside them while they are open, close with Escape, and return you to where you were.
• Screen readers: pages have one main heading and a clear heading order, main areas are marked as navigation and content, form fields have labels, and errors are tied to the field they belong to and read out.
• Reading: the language of each page is set, and pages are designed to work when zoomed to 200% and on a phone screen without sideways scrolling.
• Movement: if your device is set to reduce motion, Merlin turns its animations off.
• No overlay: we don't use an accessibility “overlay” widget. We fix the pages themselves, which is what makes them work with your own assistive technology.

These parts of Merlin are not fully accessible yet. We are working on them.

• Signing a contract: the signature has to be drawn with a mouse, a finger or a stylus. There is no keyboard-only way to sign yet.
• Contracts and briefs: pages of a contract or a brief are shown as images, so a screen reader can't read their text on screen.
• Comments on briefs and videos: placing a comment on a part of a brief needs a mouse or touch.
• Videos: videos that creators upload don't have captions.
• Colour contrast: some error and status messages use red or green text that is lighter than the standard requires.
• Some controls: some formatting buttons in the brief editor can't be reached with the Tab key, the date picker's month buttons can lose keyboard focus, and the featured videos in the library move on by themselves (they stop while you point at them or focus them, and stay still if your device is set to reduce motion).

If any of the above stops you, contact the accessibility coordinator below. We can send you the text of your contract or brief in an accessible format, arrange another way to sign, take your feedback in chat or by email, or do the step with you.

To report a problem, ask for help or suggest an improvement, contact:

• Name: [Accessibility coordinator name — to confirm]
• Phone: [Accessibility coordinator phone — to confirm]
• Email: [Accessibility coordinator email — to confirm]
• Post: Magic Merlin Ltd., [Registered office address — to confirm]

Please tell us which page you were on, what you were trying to do, and what browser and assistive technology you use. We'll reply as soon as we can, and fix reported problems as quickly as possible.

[Whether the company relies on an exemption under regulation 35F, and which one — to confirm]

This statement was prepared on October 19, 2026, after an internal review of Merlin's main pages against WCAG 2.1 level AA. We review it whenever Merlin changes in a way that affects accessibility.