Accessibility statement

Last updated and last reviewed: 2026-10-19

RAKIA (by KesemItay) is committed to serving everyone equally, including people with disabilities. Our target is WCAG 2.1 level AA, which covers the three frameworks we work under: Israel (IS 5568), the European Union (EN 301 549) and the United States (ADA practice). The known gaps are listed openly below.

Exemption notice

RAKIA is run by a registered sole proprietor (Osek Patur) in Israel. Under regulation 35F(g) of the Israeli Service Accessibility Regulations (2013), an osek patur is exempt from the website-accessibility duties, and under the EU European Accessibility Act a microenterprise that provides services is exempt from its duties. Even so, we work to make the site meet WCAG 2.1 level AA, and the known gaps are listed below. If you have difficulty using the site, contact us by email or with the form at the bottom of this page, and we will give you the information or the service in another accessible way, free of charge. This is not legal advice.

The law and the standard

• Israel: the Equal Rights for Persons with Disabilities Law (1998) and the Service Accessibility Regulations (2013), section 35, based on Israeli Standard IS 5568 (September 2023 edition, part 1 for websites and part 2 for digital documents), which builds on WCAG 2.0 level AA.
• European Union: the European Accessibility Act (Directive 2019/882) and the standard EN 301 549, which builds on WCAG 2.1 level AA.
• United States: the Americans with Disabilities Act, Title III, where WCAG 2.1 level AA is the accepted measure.
• Our target: WCAG 2.1 level AA, and on a few points more than that (a 44 pixel touch target on most buttons, and an alternative to dragging as in WCAG 2.2).

How the service meets the requirements

RAKIA is a web app where clubs and individuals make sports posters: you upload a photo, pick an example, write or tell Roki (an AI assistant in a chat) what to change, then approve or download the poster. This is how the service is built so that everyone can use it:

• Perceivable: every meaningful image has alternative text and decorative images are marked as such; text contrast is at least 4.5:1, and text box edges, the focus ring and icons at least 3:1; pages fit a 320 pixel wide screen without sideways scrolling, work in portrait and landscape, and keep their content when line, letter and word spacing are increased; the film on the beta page is silent, and the four steps it shows are written out under it.
• Operable: full keyboard navigation with a clearly visible focus; a "skip to content" link on every page; pop-up windows (feedback, Roki's chat) keep the focus inside and close with Esc; the editor that moves the words on a poster works without dragging or pinching: the arrow keys, Move buttons (up, down, left, right) and Size buttons (+ and -); help that opens on mouse hover stays open while you move onto it and closes with Esc; the system setting "reduce motion" is respected: animations stop and the film does not start by itself, and it has a Pause / Play button.
• Understandable: plain language; a label on every field; error messages in words; in Roki's chat a screen reader says who wrote ("Roki:" or "You:"), and Hebrew bubbles read right to left.
• Robust: components are standard HTML with an accessible name on every icon button; status messages (saved, sent, an error, new chat messages) are announced to screen readers without moving the focus, and the painting card's stopwatch is not read out every second.
• An accessibility menu on every page (the corner button): bigger text, high contrast, stop animations, readable font, underlined links and a light mode.
• The new screens (the top bar and the phone's tab bar, Create and the chat with Roki, the poster card and its versions strip, Roki's list of changes, the painting card, the consent and age screen, and the feedback window) were built and checked to the same rules.

What was checked

• An automatic WCAG scan (axe) of the public pages on 13.10.2026 found no issues. The pages scanned: rakia.io, /personal_beta, /personal_beta/waitlist, /accessibility and /sign-in.
• On 19.10.2026: a code review of the new screens against WCAG 2.1 AA, and checks in a browser on a computer and a phone (375 and 320 pixels): a name on every button and link, touch target sizes, narrow screens without sideways scrolling, increased text spacing, and the contrast of the system's colours. The issues found were fixed the same day.
• A full manual test with screen readers (VoiceOver on iPhone and Mac, TalkBack on Android, NVDA on a computer) and an audit by an outside accessibility expert have not been done yet. They are planned.

What is not yet fully accessible

• The posters are AI-made images, and the text inside them cannot be copied or read out. Their image descriptions currently name the athlete; the words you wrote for a poster can be read as text on the plan card and in the chat.
• The editor that moves the words shows their place on the picture by sight. With a keyboard or a screen reader you can move and resize them, and the place is said in numbers, but the design is hard to judge without seeing it. Instead, you can tell Roki in words what to move.
• Roki's replies are written by AI and can be wrong. If a reply is not clear to you, write to us.
• A few small floating buttons on phones (the accessibility menu, the menu and the account) are 36 to 40 pixels, under our own 44 pixel goal but above what WCAG requires.
• Some forms in the club system are missing visible field labels; we are adding them.
• Content that clubs and users upload (photos, logos and results) is third-party content, and the site meets the standard for it only in part.
• The Telegram bot runs inside Telegram, so its accessibility depends on the Telegram app. If an action in the bot is not accessible to you, write to us and we will help you do it on the site or another way.
• Our emails (for example the welcome email) were built to accessible patterns but have not been tested in every email app.
• The club system (after sign-in) and the personal area have not yet had the full manual screen-reader test described above. If anything there is hard to use, write to us and we will make it accessible.

Browsers and service

• Browsers: Supported browsers: current versions of Chrome, Safari, Firefox and Edge, on computers and phones.
• Physical service: We have no office or physical service point; service is given on the site and by email.

Temporary faults

No temporary faults are known at the moment. If a feature is down for more than a week, we list it here.

Accessibility contact

Itay Mizrachi, email: kesemitaymedia@gmail.com, address: 11 Shivat Zion St., Rishon LeZion, Israel. You can also use the form below. As a business with fewer than 25 employees we are not required to appoint an accessibility coordinator; Itay Mizrachi is the contact person. Until an issue is fixed we will offer another way to get the service, for example by doing the task for you by email. We aim to answer every message within 7 business days and to fix any issue as soon as possible.

Found an accessibility problem? Report it here and we will take care of it:

If your report is not resolved to your satisfaction, you may contact the Commission for Equal Rights of Persons with Disabilities at the Israeli Ministry of Justice. Users in the European Union may also contact the accessibility market surveillance authority of their country.