Capshy

עברית

Accessibility Statement: Capshy

Last updated: 4 November 2026

Draft. Written under Israel's Equal Rights for Persons with Disabilities Law, 5758-1998, and the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013, mainly regulation 35E. [For legal review before publishing.]

1. Our commitment

We want everyone to be able to caption their videos, including people who use a screen reader, larger text or high contrast. Captions themselves matter a great deal to people who are deaf or hard of hearing, which is one reason we built the App.

The service is operated by Shalom Vider, a sole proprietor (osek patur) in Israel. [For legal review: whether the small-business exemption in regulation 35F(g) applies. Even if it does, we have made the adjustments described here.]

2. What this statement covers

  • The Capshy Android app, version 1.16 and later, as installed from Google Play.
  • Our web pages: the Privacy Policy, the Terms of Use, account deletion and this statement.

3. Level of accessibility

The App was adapted to Israeli Standard 5568, which is based on WCAG 2.0 level AA. We also applied parts of WCAG 2.1 (for example target size and an alternative to dragging).

How it was checked: by our own review. We went through every screen, sheet and dialog in the App, in light and dark mode, and at 200% text size. An automated check we built for this confirms that every button and control has a spoken name, a role (button, switch, check box, choice) and a state (on or off, selected or not), and a touch area of at least 48 by 48. We calculated the contrast ratio of the text colours against their backgrounds. The review was not carried out by a certified accessibility auditor.

4. What we did

Screen reader (TalkBack):

  • Every button, icon and image that does something has a clear name, in Hebrew and in English.
  • Switches and check boxes are read as one row: the name, the kind of control and its state. You can tap the whole row, not just the small control.
  • Choices from a set (language, template, font, animation, network, position) are read as "selected" or "not selected".
  • Tabs are read as tabs, and screen titles are marked as headings so you can jump between them.
  • Every colour in the colour picker is read by name ("yellow", "blue"), not just as a coloured square.
  • Progress messages (extracting audio, transcribing, creating the video) are announced as they change.
  • Controls locked to the PRO plan are read as locked, and tapping them explains why.

Alternatives to dragging and pinching:

  • Trimming the video: a slider with two handles, which also works with a screen reader.
  • Caption height: a slider, as well as dragging on the preview.
  • Logo, title and progress bar position: a choice of fixed positions, as well as dragging.
  • Timer position, framing the video (moving and zooming) and moving a line you added: TalkBack actions ("Move timer up", "Zoom in", "Move line down" and so on) in the screen reader's actions menu.
  • Caption, timer and logo size: sliders.

Vision:

  • Text grows with the phone's font size setting. We checked every screen at 200%.
  • Contrast of at least 4.5:1 between text and background, in light and dark mode. In this update we darkened the secondary text, which was too faint.
  • Dark and light mode, following the phone or chosen by you.
  • Information is never given by colour alone: a line with a number also carries a "Number" tag, and a PRO feature a "PRO" tag.

Touch and operation:

  • A touch area of at least 48 by 48 for every button and control.
  • Nothing has a time limit. Transcription and video creation carry on in the background, and you can cancel them.
  • Every action that deletes something or costs money asks first, and deleting a line can be undone.

Language:

  • The interface is in Hebrew and English, and the screen direction (right-to-left or left-to-right) follows the language.
  • Plain wording: short sentences, one term for each thing, and buttons named after their action.

5. What is not yet fully accessible, and the alternative

  • The video and caption preview is visual by nature. The screen reader reads the text of each line, with its time, on the editing screen, where you can also correct it.
  • Choosing a design (font, colours, animations) is a visual choice. Every option is read by name, and there are ready-made templates, so you can create a video without choosing anything.
  • Animated demonstrations (in templates and animations) are not described beyond the animation's name.
  • Google services (sign-in, purchases, an ad you chose to watch) appear in Google's own windows, and their accessibility is Google's responsibility.
  • The teleprompter uses the camera. All its controls are read aloud, but framing yourself in front of the camera is visual.
  • The exported video has captions burned into the picture. If you need a separate caption file, you can export an SRT file (PRO plan).

If you meet a problem not listed here, please tell us (section 7).

6. Using the App with assistive tools

  • TalkBack: phone Settings → Accessibility → TalkBack. The App needs no extra setup.
  • Text size: Settings → Display → Font size and style.
  • Dark mode: Settings → Display, or in the App's settings under "Appearance".
  • TalkBack actions (moving and zooming without dragging): with focus on the preview or on a line's handle, open TalkBack's actions menu (usually swipe down then right, or a single-finger triple tap).

7. Contacting us about accessibility

We do not have a separate accessibility coordinator. Requests are handled by the operator of the service:

  • Name: Shalom Vider
  • Email: support@capshy.com
  • Address: 122 Rabbi Akiva St., Apt. 13, Bnei Brak 5146205, Israel
  • In the App: Settings → Contact us.

To help us help you, tell us what you were trying to do, on which screen, and which tool you used (for example TalkBack or larger text). We will reply within 14 days. If the problem needs a code fix, we will tell you when to expect it and, until then, offer another way to complete the action.

8. Updates to this statement

We update this statement whenever we change something that affects accessibility, and at least once a year. The date at the top is the date of the latest update.