Accessibility Statement

Our commitment

We want RanklyGo to be usable by everyone, including people who browse with a keyboard alone, with a screen reader, with the page magnified, or with colours and motion adjusted to suit them. We treat that as part of building the product rather than as an afterthought.

The standard we work to

We aim to meet WCAG 2.1 level AA, the standard referenced by Israeli Standard 5568 (IS 5568) and by accessibility law in the European Union and elsewhere.

We describe our current status as partially conformant: most of the standard is met, and we know of some areas that are not yet verified. We say partially rather than fully because our conformance has not been independently audited, and we would rather tell you where we are than claim more than we can show.

What is in place

• Every page can be operated with a keyboard, and the control you are on is shown with a visible focus outline.
• A “Skip to content” link is the first thing you reach with the keyboard, so you can pass the header and navigation.
• Pages use proper headings, landmarks and labelled form fields, so a screen reader can navigate by structure rather than by reading everything.
• Dialogs, menus and other interactive controls are built on accessible component primitives that manage focus and announce themselves.
• Text meets the required contrast against its background in both the light and dark themes, and the interface follows your system's light or dark preference.
• The interface is available in English and Hebrew, and the page's language and reading direction change with it, including right-to-left layout for Hebrew.
• Layouts reflow to narrow screens and to enlarged text without content being lost or requiring horizontal scrolling.
• Decorative icons are hidden from screen readers so they are not read out as meaningless items.

Known limitations

We would rather name these than let you discover them:

• Charts and graphs. Performance charts convey information visually. The same figures are available as text and numbers next to every chart, but the charts themselves are not fully described to a screen reader.
• Images you and your clients upload. We cannot supply alternative text for media you add to a post. Where a platform offers an alt-text field, we encourage you to use it.
• Content on connected platforms. Posts published to Facebook, Instagram, LinkedIn, TikTok or YouTube are displayed by those platforms, whose accessibility is theirs rather than ours.
• Not independently audited. Our assessment is our own review against the standard, not a third-party audit.

Telling us about a problem

If any part of RanklyGo is difficult or impossible for you to use, please tell us — it is the fastest way for it to get fixed, and we would rather hear it than not.

Email omri@smartallocations.com with the page or feature involved, what you were trying to do, and how you were browsing — for example the browser and screen reader you use. We aim to reply within 5 working days and, where something needs fixing, to tell you when we expect to have done it.

If you need something from RanklyGo that you cannot reach, say so in the same email and we will find another way to get it to you while the underlying problem is being fixed.

Accessibility coordinator

Omri Schul is responsible for accessibility at RanklyGo and can be reached at omri@smartallocations.com.

RanklyGo is a sub-company of Smart Allocations Limited.