Chatlytics Blogs
Version 1.0 · Last updated 22 October 2026 · Effective 22 October 2026
Operated by Chatlytics, the business of Omer Nesher, a licensed Israeli sole trader, business number 037289931, Israel ("Chatlytics", "we", "us", "our").
Contact: [email protected]
1. Our commitment
1.1 Chatlytics Blogs publishes websites that people read on phones, in groups, and often in a hurry. We want those sites to be usable by people with disabilities, including people who use screen readers, keyboard navigation, magnification or voice control.
1.2 Accessibility is part of how we build the Blogs, not a separate add-on. We treat it as an ongoing effort: we fix what we find, and we say plainly what is not yet fixed.
1.3 This statement describes the accessibility of the Blogs we generate and of our own website at chatlytics.blog. It does not describe the accessibility of third-party sites we link to.
2. The legal framework we work within
2.1 Chatlytics is an Israeli business serving primarily Israeli customers. Israeli law requires businesses to make their services accessible to people with disabilities, under the Equal Rights for Persons with Disabilities Law, 5758-1998 and the regulations made under it, including the regulations on accessibility of service.
2.2 The relevant technical standard in Israel is Israeli Standard SI 5568, which is based on the Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA.
2.3 We use WCAG 2.1 Level AA as our internal target, because it includes the WCAG 2.0 AA requirements and adds criteria that matter in practice, such as orientation, reflow and non-text contrast.
2.4 This statement is published in line with the Israeli requirement to publish an accessibility statement describing the accessibility of a service, the arrangements made for people with disabilities, and how to raise a problem.
3. Conformance status
3.1 We aim for WCAG 2.1 Level AA across the Blog templates, the reading experience and the account area.
3.2 We describe the current state as partially conformant: some parts of the Service meet the target, and some known gaps remain. The gaps we are aware of are listed in section 5. We do not claim full conformance, and this statement should not be read as a certification.
3.3 The Blogs contain content written and uploaded by Customers and their group members. We control the templates and the rendering, but we do not control what people write, photograph or embed. We provide the tools to do it accessibly; we cannot guarantee that every piece of user-generated content is accessible.
4. What we have done
4.1 Structure and semantics. Blog pages use headings in a logical order, landmark regions, lists where lists are meant, and buttons and links that are marked up as what they are.
4.2 Keyboard access. Menus, search, post navigation and account controls are operable with a keyboard. Focus is visible, and focus order follows the reading order.
4.3 Text and contrast. Body text meets the contrast target against its background in the default theme and in the themes we ship. Text can be resized up to 200% without loss of content or function.
4.4 Right-to-left support. Hebrew and other right-to-left languages are first-class: the layout, alignment, punctuation and mixed-direction text are built for RTL rather than mirrored afterwards.
4.5 Images and media. Images added through our own templates carry alternative text where the content model allows it. Video and audio we embed do not autoplay, and controls are exposed to assistive technology.
4.6 Forms and errors. Forms have visible labels, clear error messages, and do not rely on colour alone to communicate a problem.
4.7 Motion and timing. We avoid flashing content and avoid time limits on reading. Animations respect the operating system's reduced-motion setting where the browser exposes it.
4.8 Zoom and reflow. Pages remain usable at 320 CSS pixels wide without horizontal scrolling, apart from content that inherently needs two dimensions, such as wide tables.
5. Known limitations
5.1 Images in posts may lack alternative text. When a Customer or group member posts an image, the alternative text depends on what they provide. Where none is provided, we fall back to a generic description or to the image's caption.
5.2 Older posts. Posts published before an accessibility fix may still carry the older markup until they are re-rendered. We re-render on edit and on template updates, but a long archive may take time to catch up.
5.3 Embedded third-party content. Videos, polls, maps and social embeds come from other providers. Their accessibility is outside our control, and some may not be fully keyboard-operable or captioned.
5.4 Complex tables and data views. Wide tables in imported content may require horizontal scrolling on small screens.
5.5 Hebrew screen-reader behaviour. Some screen readers handle mixed Hebrew and English text, numbers and punctuation inconsistently. We test with common combinations, but behaviour varies by reader and version.
5.6 Password-protected Blogs. The password gate is keyboard-accessible and labelled, but it is intentionally minimal; it does not offer an alternative authentication method.
5.7 PDF and document attachments. Documents uploaded by Customers may not be tagged or readable by assistive technology. We do not currently convert or remediate them.
5.8 The account area. The core flows — sign-up, connecting a group, pausing publication, billing — are keyboard-accessible. Some secondary settings screens have not yet been through a full audit.
6. What we are working on
6.1 A full accessibility audit of the Blog templates and the account area against WCAG 2.1 Level AA, followed by a remediation plan with dates.
6.2 Better fallbacks for images posted without alternative text, including prompting the Customer for a description.
6.3 An accessibility check in the publishing flow, so that a Customer can see and fix problems before a post goes live.
6.4 Periodic testing with screen readers and keyboard-only navigation in Hebrew and English.
7. Alternative ways to get the content
7.1 If a Blog is difficult for you to use, write to [email protected] and tell us what you need. We can provide a post or a set of posts in another format, such as plain text or a document, and we will do so at no charge.
7.2 If you are a Customer and need a specific accommodation for your own Blog, contact us and we will look at what is possible within the templates.
7.3 We aim to respond to accessibility requests within 5 business days.
8. Feedback and contact
8.1 We want to hear about accessibility problems, including problems with this statement. Write to [email protected] with the Blog address, the page, and a short description of what happened and what you expected.
8.2 If you use assistive technology, tell us which one and which version. It helps us reproduce the problem.
9. Handling complaints
9.1 We record every accessibility complaint, investigate it, and reply with what we found and what we will do. Where a fix is not immediate, we give a date.
9.2 If you are not satisfied with our response, you may contact the Commissioner for Equal Rights for Persons with Disabilities in the Israeli Ministry of Justice, or the relevant authority in your country.
9.3 We do not charge for handling an accessibility complaint, and we do not require you to use a particular form.
10. Review
10.1 We review this statement at least once a year, and after any significant change to the Blog templates or the account area.
10.2 The date of the last review appears at the top of this document. If the review finds that a claim in this statement is no longer accurate, we will correct the statement rather than leave an outdated claim in place.
11. Contact details
Chatlytics — Omer Nesher, licensed Israeli sole trader, business number 037289931, Israel.
Accessibility and support: [email protected]