Skip to content

Accessibility Statement

Sync.me exists to help you know who's calling and connect with the people in your life — and that only means something if everyone can actually use the site to do it. We're working to make Sync.me accessible to people with disabilities, including people who navigate by keyboard, who use a screen reader, or who rely on other assistive technology. This statement explains where that work stands today, honestly: what's already in place, what still needs work, and how to reach us if something isn't working for you.

Conformance Status

Our accessibility target is WCAG 2.1 Level AA, the technical benchmark shared by Israeli Standard 5568, the EU's European Accessibility Act (EAA), and Germany's Barrierefreiheitsstärkungsgesetz (BFSG) — the regulations that apply to Sync.me as a service used by people in Israel, the EU, and Germany.

Right now, Sync.me is partially conformant with WCAG 2.1 AA. That means many parts of the site meet this standard, but not all of it does yet, and we haven't completed the testing needed to claim full conformance. The section below, "Known Limitations," lists the specific gaps we're aware of.

This statement covers the Sync.me web site: our marketing pages (home, feature pages, pricing, blog, about, and our quiz), the phone-lookup and search product pages, account and subscription management, and our legal pages (Privacy Policy, Terms of Use, Cookies Policy). It does not cover our native mobile apps, or third-party content we don't control, such as the Google reCAPTCHA widget or App Store and Google Play listings.

Accessibility Features Already in Place

We've made concrete, shipped changes across the site, including:

  • Visible keyboard focus. Buttons, links, form fields, menus, and other interactive elements now show a clear focus outline when you navigate with a keyboard, replacing focus indicators that were previously suppressed almost everywhere on the site.
  • Accessible forms. Form fields have real, programmatically associated labels (not just visual text), and validation errors are announced to assistive technology rather than silently replacing the label. Our custom dropdown menus can be operated fully with arrow keys, Enter, Space, and Escape.
  • Accessible dialogs. Sign-in, download, and other pop-up dialogs across the site now trap keyboard focus inside them while open and close with the Escape key — neither was true before.
  • Keyboard-operable navigation. The main menu, mobile menu, and language selector can all be operated by keyboard, with proper expand/collapse announcements for screen readers. A "skip to main content" link is available as the very first stop when tabbing into any page.
  • Meaningful image descriptions. Purely decorative images and icons are hidden from screen readers so they don't create noise, and icons that convey information can carry proper text alternatives.
  • Improved color contrast. Text colors that didn't meet the required contrast ratio — including link text, secondary text, and error text — have been darkened to pass WCAG's 4.5:1 threshold for text.
  • Corrected heading structure. Heading levels across our feature pages, search and phone-lookup pages, and quiz have been fixed so the page structure reads logically to screen readers, instead of skipping or duplicating levels.
  • A pause control for moving content. The one continuously looping animation on the site (next to AI-generated results on our search page) now has a keyboard-accessible pause/play control.
  • Right-to-left (RTL) support. Hebrew and Arabic versions of the site now render properly right-to-left, with numbers, phone numbers, and prices correctly displayed left-to-right within RTL text, as they should be.
  • A redesigned phone number and search experience. The phone number field and search bar have keyboard-operable country selectors and focus indicators that follow the whole field, not just the underlying input.
  • Automated guardrails. We've turned on accessibility linting (eslint-plugin-jsx-a11y) in our codebase to catch common issues — like missing labels or missing alt text — before they ship.

Known Limitations

We'd rather tell you exactly where things stand than round up. As of this statement, we know about the following gaps:

  • Manual accessibility testing has gone further, but isn’t complete sitewide. We’ve completed a live keyboard-only pass (no mouse) across the site’s header navigation, mega-menus and mobile menu, pop-up dialogs, cookie preferences, and our Contact Us form, plus an accessibility-tree audit — a scriptable stand-in for a screen reader — on the home page and Contact Us form. We haven’t yet extended this to every page on the site, and we haven’t yet done a real, live screen reader (VoiceOver) session with an actual assistive-technology user.
  • 200% browser zoom has been spot-checked, not tested site-wide. We’ve confirmed that our home page and one representative feature page reflow correctly at 200% zoom, with no clipped or overlapping content, in both left-to-right and right-to-left layouts. We haven’t yet extended this check to every page on the site.
  • Some interface text was translated by an engineer, not a professional translator. The "skip to main content" link, the pause/play animation button labels, and a few RTL-related labels were translated directly into our ten non-English languages without a native-speaker review. They work correctly with assistive technology, but we haven’t verified how natural they sound. Separately, the close button on our pop-up dialogs hasn’t been translated yet at all — it’s still announced in English regardless of which language you’re using.
  • We don't yet run automated accessibility scans. We rely on static code linting to catch markup issues like missing labels, but this can't detect real-world problems like actual rendered contrast, focus order, or what a screen reader announces. Automated scanning (such as axe-core) is planned but not yet implemented.
  • A few accessibility lint rules are set to warn, not block. Four rules governing custom interactive elements are currently warnings while we finish converting the underlying components to natively accessible elements. That number has come down from 26 to 10 open warnings as more of these elements were converted.
  • Our country-code dropdowns use simplified keyboard support. The country selector in our phone number field and search bar is a real, keyboard-focusable button with correct expand/collapse announcements, but it doesn't yet use the full listbox pattern that gives a native select-equivalent screen reader experience. That richer pattern is planned as future work.
  • Right-to-left support isn't complete everywhere. We prioritized the site's core layout — header, footer, navigation, menus, forms — and all numbers and phone numbers. Some less-visited pages may still have residual left/right layout issues we haven't found yet; we're fixing these incrementally as they surface.
  • Four legal pages are intentionally English-only. Our Cookies Policy, Privacy Policy, CCPA notice, and Terms of Use are shown in English and left-to-right regardless of your language setting. This is a deliberate content decision, not an oversight, but we want you to know about it if you use the site in Hebrew or Arabic.
  • AI-generated search content has limited heading support. On our search page, AI-generated answers currently support one level of subheading correctly. If the AI ever produces deeper heading levels, the heading structure in that area isn't guaranteed to be correct.
  • One small cosmetic issue. The "Manage Cookies" button on our Cookies Policy page lost its distinct hover color as a side effect of a contrast fix (the underline that appears on hover is still there). This doesn't affect accessibility, but we're noting it for completeness.
  • This statement covers our web site only. We can't make claims here about the accessibility of our native mobile apps, or of third-party content we don't control, such as payment processor screens, the reCAPTCHA widget, or app store listings.

How to Give Feedback or Report an Issue

If you run into an accessibility barrier anywhere on Sync.me, or something in this statement doesn't match what you're experiencing, please tell us — we want to know. Contact us at support@sync.me and let us know which page you were on and what happened; we'll do our best to get back to you and address it.

Statement Date

This statement was published in July 2026 and reflects the accessibility work completed as of that date. Accessibility work at Sync.me is ongoing rather than a one-time project, so we'll review and update this page as we close further gaps — at minimum once a year, and whenever we complete another round of accessibility improvements.