Accessibility statement for AutoScript Sync

This statement covers the AutoScript Sync website and the AutoScript Sync app for Windows.

Prepared 14 September 2026.

Our commitment

We want everyone who buys and uses AutoScript Sync to be able to do so. That includes people who use a keyboard instead of a mouse, a screen reader, Windows contrast themes, larger text or display scaling. Our aim is for the website and the app to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. WCAG is written for websites, so for the app we applied its requirements as closely as they fit desktop software.

We don't meet that standard yet. This page sets out plainly what works, what doesn't, and what we plan to change. If a problem here stops you using AutoScript Sync, please email us. The details are near the end of this page.

Conformance status

Website: partially conformant with WCAG 2.2 level AA. Most pages can be read and navigated. But almost every page we checked has at least one failure, and some failures are against the most basic (level A) requirements, including in checkout. Five of the failures are serious:

• the checkout window
• loading your own files in Report Studio
• Report Studio's charts
• the help chat
• a faint grey text colour used in several places

Windows app: not conformant with WCAG 2.2 level AA. Several failures are against the most basic (level A) requirements. At the moment, someone using only a keyboard cannot:

• generate a script for the video that is open. File > Batch Generate Folder... does work from the keyboard, but a batch can't then be cancelled from the keyboard.
• connect a device
• send a script to a device
• reliably stop a device

"Partially conformant" means that some parts do not meet the standard. "Not conformant" means that the app as a whole does not meet it, because core tasks can't be completed with a keyboard alone. The problems are listed below. The number in brackets after each one is the WCAG 2.2 success criterion it fails.

What this statement covers

Website (autoscriptsync.com)

• The home page
• The store, including checkout
• The download page
• Guides
• Report Studio
• The Discord link page
• The EULA (licence agreement)
• The "page not found" and "not available" error pages, and the page shown when a trial download is unavailable
• The help chat and the screenshot viewer, which appear on several pages

Not covered:

• Pages run by other companies that our site links to or sends you to: PayPal, Revolut, Discord and linktr.ee.
• The emails we send, such as the one with your licence key. These are plain text.
• The site's admin pages, which are not for customers.

Windows app

AutoScript Sync for Windows, versions 2.121.1 and 2.121.2. This covers:

• the main window and its menus
• the generation and batch progress windows
• AI Bulk Learn and its clip review window
• the motion-region window and the Live Track overlay
• the Vibration panel
• the help panel
• the licence window

Not covered: the installer, and the windows that Windows itself provides, such as file and folder pickers.

What works today

Website

• Language and titles: every page tells browsers and screen readers that it is in English, and every page has a meaningful title. The two error pages share one title (see below).
• Headings: they follow a logical order on the main pages, so you can move through a page by heading.
• Focus outline: the home, store, download and guides pages draw a clear teal outline around links and buttons that have keyboard focus. The help chat's message box is an exception (see below). Other pages show your browser's standard focus outline. We found nowhere that traps keyboard focus.
• FAQ and guides: the sections open and close with the keyboard.
• No video, audio or carousels: there is no video, no audio and no carousel.
• Motion: the only animation, on the home page, plays once and follows your system's "reduce motion" setting. On the home page, that setting also turns off smooth scrolling.
• Images:
  • The home page illustration has a text description.
  • Decorative icons are hidden from screen readers.
  • Screenshots have text alternatives, although the ones on the home page are too short (see below).
• Autofill: the name and email fields at checkout support your browser's autofill.
• Contrast: most text meets WCAG 2 contrast requirements, including body text, headings, links and buttons. The exception is a faint grey text colour, listed below. Under APCA, a newer and stricter way of measuring contrast, only the brightest text colour reaches the level we aim for. The secondary grey text, teal links and button text do not.
• Text spacing: extra letter, word, line and paragraph spacing did not cut off any text on the home, store or download pages.
• Narrow screens: the store, EULA and "page not found" pages fit a 320-pixel-wide screen without sideways scrolling.
• Error messages: errors from the order process are written in plain language.
• Page structure: the download page and Report Studio mark their main content as the main region. Report Studio's act table is a real table with headers.
• Help chat: the button that opens it has a name, and its suggested replies are real buttons.
• Sticky menu: in our tests, the menu fixed to the top of the page never completely hid the item that had keyboard focus.

Windows app

• Standard controls: nearly all controls are standard controls from the toolkit the app is built with (Qt), not custom-drawn ones. The toolkit normally tells Windows accessibility software what each control is and what state it is in, but we have not yet confirmed this with a screen reader. Many controls are named by their own visible text.
• Tab order: Tab moves through the main window in one logical order that follows the layout, and never gets stuck.
• Keyboard shortcuts that work:
  • Ctrl+O: Open Video
  • Ctrl+Z: undo. Ctrl+Shift+Z or Ctrl+Y: redo
  • Space: play or pause. Please read the safety section below.
  • Left and Right arrows: jump back or forward 5 seconds, and the device is re-synced. Please read the safety section below.
  • F11 or F: full screen. Esc: leave full screen
  • M: mute. T: turn Live Track on or off
  • Alt, then the arrow keys: open and move through the menus
• Generating from the keyboard: File > Batch Generate Folder... works from the keyboard. It creates scripts for every video in a folder that doesn't already have one.
• Live Track overlay: it passes your key presses on to the main window, so Space still pauses while the overlay has focus.
• Clip review window (AI Bulk Learn):
  • Keys 1 to 9 and 0 apply the ten most-used labels, and those buttons show their number key.
  • The other labels, and the Back and Skip buttons, can be reached with Tab and pressed with Space or Enter. Buttons don't show keyboard focus yet (see below).
  • In the AI Bulk Learn window itself, Enter opens the clip selected in the list.
• Vibration panel: once it is open, Tab reaches the intensity slider and the "Stop vibration" button, and Space or Enter presses that button.
• Focus on fields: dropdown lists, number boxes and text fields show keyboard focus. Their thin border turns teal.
• Contrast: the main text has strong contrast.
• Text size: text grows with Windows display scaling.
• Status: it is usually shown with text as well as colour. This covers sync status, licence status, batch progress rows and flagged labels.
• Tooltips: almost every control has one, in plain language.
• Errors: most errors appear in standard message boxes. Some appear only in the status bar (see below).
• Timing and flashing: nothing in the app's own screens disappears on a timer or flashes, and nothing has a time limit while you use the app. The videos you play may contain flashing. The one highlight is a single 2.2-second border around Stroke Settings.
• Device safety:
  • When a video playing in the app window ends or is stopped, scripted motion stops within about a second. This doesn't apply to Manual Mode, built-in patterns or the Vibration panel. We did not assess playback on a VR headset.
  • Setting the playback speed above 2x disengages the device at that moment. It does not stay disengaged: see "Stopping a device" below.
  • In the Vibration panel, the "Stop vibration" button, or closing the panel with the close button in its title bar, stops the vibration.

Known limitations: website

Buying a licence (store and checkout)

• The checkout window traps keyboard users behind it. When it opens, keyboard focus stays on the Checkout button behind it, and Tab moves through the page behind the window. Esc doesn't close it. When it closes, focus jumps to the top of the page. Screen readers are not told that a dialog has opened. (2.4.3, 4.1.2)
• Focus is lost at the "Nearly done" step. When checkout moves to this step, the button you were on disappears and keyboard focus is lost. This happens after a click, and also automatically when you come back to the browser window. (2.4.3)
• The name and email fields are not properly labelled. Their visible labels are not connected to them. A screen reader announces the email field only by its example text, "you@example.com". The name field has no name at all. (1.3.1, 4.1.2)
• The quantity controls are unclear. The quantity box has no label. The buttons beside it are announced only as "decrease" and "increase", without saying what they change. (1.3.1, 4.1.2, 2.4.6)
• Cart changes are silent. Adding something to the cart changes the cart count and total without telling screen reader users. Changing the quantity isn't announced either. (4.1.3)
• Errors are not announced. If your email address is rejected or the order can't be placed, the error appears on screen but isn't announced. The field isn't marked as having an error, and focus stays on the submit button. (4.1.3)
• The order confirmation is not announced. Once your order is recorded, the confirmation isn't announced, and the form you were in is hidden, so keyboard focus is lost. (4.1.3, 2.4.3)
• The Revolut option changes silently. If the amount doesn't match for Revolut, a warning appears without being announced. The Revolut option then stops being a link, and the only sign that it is disabled is that it fades. (4.1.3, 4.1.2)
• The checkout text fields are hard to see. Their edges are very faint, so it can be hard to see where to type. (1.4.11)
• Important notes are in faint text. Several notes are in faint grey text below the required contrast: when your licence key will arrive, the payment notes, the empty-cart message and the price note. (1.4.3)
• Decorative symbols are read aloud. Screen readers read out decorative arrow, tick and padlock symbols. (1.1.1)
• Payment links open new tabs. The Revolut and PayPal links open in a new tab without warning you first. This is not a level AA requirement, but we want you to know.

Report Studio

• You can't load your own files with a keyboard. "Choose files" can't be reached with Tab, and the drop area only works with a mouse. Only "Load example" works from the keyboard. (2.1.1)
• The charts have no text alternative. This covers the script plot and the stroke-rate and speed-distribution charts, so screen reader users get nothing from them. (1.1.1)
• The zoom and scrub slider has no label. (4.1.2, 1.3.1)
• The selected zoom is shown only visually. Screen readers aren't told which of the 1×, 4× and 16× buttons is selected. (4.1.2)
• Some small text is too faint. After an example is loaded, some small text, including the statistic labels and the subtitle, is below the required contrast. (1.4.3)
• The footer link is hard to spot. It is hard to tell apart from the text around it. (1.4.1)
• The page has no main heading. Its title is not marked up as a heading. (1.3.1)
• "Load example" loses keyboard focus. Pressing it removes the button you were on, so focus is lost, and the new content isn't announced. (2.4.3)
• The page scrolls sideways a little on very narrow screens. (1.4.10)

Help chat

• Answers are not announced. Screen readers don't read out the chat's answers. (4.1.3)
• Its open or closed state is not given. Screen readers aren't told whether the chat is open or closed, and the chat panel has no name. (4.1.2)
• The message box has no lasting label. Its only label is placeholder text, which disappears when you start typing. (3.3.2, 1.3.1)
• Esc doesn't close the chat. Closing it doesn't return focus to the button that opened it. (2.4.3)
• The message box edge is very faint. (1.4.11)
• The message box barely shows focus. It has no focus outline. The only sign is a thin border changing colour, which may not show at all in Windows contrast themes.

Screenshots

• Enlarging a screenshot needs a mouse. (2.1.1)
• Focus doesn't move into an enlarged screenshot. Tab still moves through the page behind it. Esc does close it. (2.4.3)
• Home page screenshots have short descriptions. Each one contains many small text labels, but has only a one-line description. (1.1.1)

Across the site

• Links in text are shown by colour only. They have no underline. On the EULA, the support email link looks like plain text. (1.4.1)
• Faint grey text is used in several places. It is below the required contrast in:
  • the footers
  • the "Last updated" date on the EULA
  • the only note on the download page that explains where to enter your licence key
  • some notes, statistics and labels on the home page

  (1.4.3)

• The main menu changes order. It is in a different order on different pages. (3.2.3)
• Jumping to the main content is awkward. There is no "skip to content" link, and most pages don't mark their main content, so screen reader users can't jump straight to it that way. You can still move through pages by heading. (1.3.1)
• On the Guides page, the menu shows which page you're on by colour only. This is not a WCAG failure on its own, but screen readers aren't told either.

Individual pages

• Home page: on a 320-pixel-wide screen the AI model guide tables are cut off. The "Size" column is hidden and can't be scrolled into view. (1.4.10)
• Home page: the link "Email your files to support@" is cut short, so it doesn't give the full address. (2.4.4)
• Download page: on a 320-pixel-wide screen the menu doesn't wrap. The page scrolls sideways, and the Guides, Discord and Buy links start off-screen. (1.4.10)
• Download page: a decorative arrow symbol is read out as part of a link name. (1.1.1)
• Guides: on a 320-pixel-wide screen, a long file path makes the page scroll sideways. (1.4.10)
• Discord link page: it sends you on to Discord after less than a second, with no way to stop or delay it. It has no site menu and no marked-up page regions. (2.2.1, 1.3.1)
• EULA: it has no marked-up page regions and no link back to the rest of the site. (1.3.1)
• Error pages:
  • The "page not found" and "not available" pages share the title "Not available", even though the first one's heading says "Page not found". (2.4.2)
  • These pages, and the trial-download "unavailable" page, don't mark their main content. (1.3.1)
  • On the trial-download "unavailable" page, the support email link is hard to tell apart from the text around it. (1.4.1)

What we plan to do on the website

• Rebuild the checkout window. Focus will move into it and stay there, Esc will close it, and closing it will return you to where you were. Every field will be connected to its label. Errors, the order confirmation and cart changes will be announced.
• Fix Report Studio. "Choose files" will work from the keyboard. The charts will get a text summary. The slider and zoom buttons will get labels.
• Fix the help chat. It will announce its answers, close with Esc and return focus when it closes. The message box will get a proper label and a clear focus outline.
• Make screenshots openable from the keyboard.
• Improve contrast. Faint grey text will meet the required contrast, field edges will be clearer, and links in text will be underlined.
• Tidy the page structure. The menu will be in the same order on every page, and every page will get a "skip to content" link and a marked-up main region.
• Fix narrow screens. Content that scrolls sideways or is cut off at narrow widths will be fixed.
• Replace the Discord redirect. It will become a link you choose to follow.
• Give each error page its own title.

Known limitations: Windows app

Using the app with a keyboard

• Buttons and checkboxes in the main window don't work from the keyboard. Space is used for play and pause everywhere in the main window, so pressing Space on a focused button or checkbox does nothing to it. Enter doesn't press it either.

  As a result, none of these can be used from the keyboard:

  • Generate from Video
  • Generate + Play (instant)
  • Connect
  • Test Stroke
  • Send Script to Device
  • Stop
  • Start Manual Mode
  • Play Pattern
  • Cancel
  • Vibration…
  • the checkboxes in the main window

  Menus, dropdown lists, number boxes and text fields do work. (2.1.1)

• Generation and batch jobs can't be cancelled from the keyboard. In the progress window, the Cancel button can't receive focus, and Enter and Esc are ignored on purpose to prevent accidental cancelling. The Cancel button in the main window is affected by the problem above. (2.1.1)
• Left and Right don't move sliders. Left and Right always jump the video 5 seconds, so they don't move a focused slider (seek, volume or intensity). Page Up and Page Down do move sliders. The seek slider only seeks when you release the mouse, so the arrow keys are the only way to seek from the keyboard. (2.1.1)
• In the clip review window, Left and Right don't move between clips. Keyboard focus starts on a label button, so the arrow keys move between buttons instead. Use the Back and Skip buttons. (2.1.1)
• Editing the timeline needs a mouse. The timeline can't receive keyboard focus. These all need a mouse:
  • clicking to seek
  • adding, moving and deleting points
  • selecting a region
  • zooming

  The region toolbar only appears after you select a region with the mouse. (2.1.1, 2.5.7)

• The motion-region box can only be placed by dragging. This applies in both the motion-region window and Live Track. Only its size can be changed from the keyboard, with + and -. (2.1.1, 2.5.7)
• Some controls show no keyboard focus. Buttons, checkboxes and sliders show no visible sign of it. We measured this in the main window, and the app's other windows use the same styling. Dropdown lists, number boxes and text fields do show focus. (2.4.7)
• Single-letter shortcuts can't be turned off or changed. F, M and T (and C, A, + and - while Live Track is on) work whenever focus isn't in a text field, so they are easy to trigger by accident. (2.1.4)
• Some instructions are only in tooltips. This covers timeline gestures, Live Track keys and the accuracy trade-offs. Tooltips don't appear when you move to a control with the keyboard. (3.3.2, 1.3.1)
• Keyboard shortcuts are hard to discover. Menus and buttons have no underlined access letters, and Space, the arrow keys, F, M and T aren't listed in any menu.
• Full-screen controls need the mouse. In full screen, the playback controls only appear when the mouse is near the bottom of the screen. The keyboard shortcuts still work.
• Some targets are very small. This applies to the motion-region resize handles and the timeline points. (2.5.8)

Using the app with a screen reader

• 22 controls have no name that a screen reader can announce. They are:
  • the playback speed, pattern, track label, accuracy, hardware, curve and teach dropdowns
  • the seek, volume, intensity, expansion, depth priority and manual speed sliders
  • the offset, minimum stroke and maximum stroke number boxes
  • the full-screen and mute buttons
  • the headset IP address, pose model and depth model fields
  • the generation progress bar

  (4.1.2)

• Several parts of the window are drawn by the app, so screen readers get nothing from them and the keyboard can't reach them. These are:
  • the timeline
  • the stroke preview
  • the sync status badge (its text is drawn as part of the picture, not as real text)
  • the video area
  • the drawing area in the motion-region window
  • the Live Track overlay, which also has no window title

  (4.1.2, 1.1.1, 1.3.1)

• Labels are not connected to their controls. The labels shown beside controls mostly aren't linked to them for screen readers. Only a few controls have a connected label. (1.3.1)
• Status changes are silent. Hints, device status, script status and the sync indicator change on screen without being announced. (4.1.3)
• Some errors appear only in the status bar. For example, a script that fails to upload to the device, a save or export that fails, or a frame that can't be read from the video. These messages aren't announced. (4.1.3)
• Some buttons have unclear names. They are:
  • the two "..." browse buttons
  • the "?" button
  • the icon-only full-screen and mute buttons
  • the "20ms" step buttons
  • the help panel's float and close buttons

  (4.1.2, 2.4.6)

Colour, contrast and size

• Some text is below the required contrast. This includes:
  • faint grey captions, including the header tagline and notes in the Vibration panel
  • white text on dark teal, used on the Connect, Generate, Send Script and Connect Headset buttons and the menu highlight
  • the progress bar percentage
  • the key hint in the clip review window
  • "No funscript loaded"

  (1.4.3)

• Control edges are hard to see. The edges of text fields, dropdown lists, checkboxes and slider tracks are very faint. A text field is hard to tell apart from the panel behind it until it has focus. (1.4.11)
• The timeline relies on colour.
  • Act type is shown only by the colour of its band: purple, orange, green or grey. Some neighbouring colours have low contrast with each other.
  • Green and orange can be hard to tell apart for people with red-green colour blindness (deuteranopia).
  • Confidence is shown only by fading.
  • Scene cuts are only small marks.
  • The only colour key is one sentence in the help panel.

  (1.4.1, 1.4.11)

• Windows contrast themes are ignored. The app always uses its own dark colours, whatever contrast theme you have chosen in Windows. (This affects 1.4.3 and 1.4.11.)
• The window can be too big for the screen. Its minimum size is 1100 by 750, and the main area doesn't scroll. On a 1080p screen at 150% scaling, the bottom of the window is cut off. At 200% scaling, both the width and the height are cut off. (1.4.10)
• Text sizes are fixed. They don't follow your system's font preferences, and some text is very small. They do grow with Windows display scaling. We haven't checked whether Windows' separate "Text size" setting has any effect. (1.4.4)

What we plan to do in the app

Safety comes first, so these are listed in order of priority:

1. Add a keyboard stop for the device. Add a keyboard shortcut that stops a connected device, and make Esc in the Vibration panel stop the vibration the same way the close button does.
2. Keep the device disengaged above 2x. Seeking and pausing and playing again should not start the device until the speed is back to 2x or below.
3. Make buttons and checkboxes work from the keyboard. Focused buttons and checkboxes should respond to Space and Enter.
4. Allow keyboard cancelling. Add a keyboard way to cancel a generation or batch job, with a confirmation so it can't happen by accident.
5. Show focus on every control.
6. Show important errors in a message box, not only in the status bar.
7. Name every control. Give each one a name that screen readers announce, using the tooltip text that already exists. Give the timeline, the stroke preview and the sync status a text description that stays up to date.
8. Connect visible labels to their controls.
9. Add text alternatives. Add a text readout of the act and stroke position at the current point in the video, and a text list of the generated segments.
10. Make editing work from the keyboard. Add keyboard ways to edit the timeline and position the motion region.
11. Add a setting to turn off single-letter shortcuts.
12. Fix the clip review arrow keys so Left and Right move between clips wherever keyboard focus is.
13. Fix colour and contrast. Raise the low-contrast colours, show act type with more than colour, and respect Windows contrast themes.
14. Fit smaller screens. Let the window fit on screens using higher display scaling.

The toolkit the app is built with doesn't currently give us a direct way to have Windows announce a status change, so we will look for another way to do that.

What this kind of product means for accessibility

AutoScript Sync analyses a video, creates a motion script from it, and plays that script on a connected device in time with the video. Some of this depends on sight by its nature:

• watching the video
• choosing the area of the picture to track, in the motion-region window or with Live Track
• judging which act a clip shows when you label clips in AI Bulk Learn
• reading the coloured timeline

The device's output is felt rather than seen.

What you can already do without relying on the picture:

• Script files: each script is saved as a text file (a .funscript file) next to the video.
• Exports: File > Export Script (as played)... saves a copy of the script. Help > Export Diagnostics… saves a diagnostics file.
• Quality report: Help > Last Generation Quality… shows the quality report for the last generation as text in a message box.
• Status as text: the time, device status and sync indicator are shown as text, although changes aren't announced yet.
• No need to draw a box: the app can find the motion region automatically.
• AI Bulk Learn: each clip shows the AI's guess as text, and the clip review window can be used from the keyboard, with the limits described above.

What is not available yet:

• a keyboard emergency stop for the device (see "Stopping a device" above)
• a text readout of the act and stroke position at the current point in the video
• a text list of the generated segments

Get help, ask for another format, or report a problem

Email support@autoscriptsync.com. It is our support address and the way to reach us about accessibility. The help chat on the website doesn't announce its answers to screen readers yet, so please use email.

It helps if you tell us:

• what you were trying to do
• the address of the web page, or which app window you were in
• what happened
• any assistive technology you use (for example a screen reader, voice control or a magnifier) and which browser
• the app version, if the problem is in the app. Help > About AutoScript Sync shows it.

If you need something from the website or the app in a different format, such as a plain-text version of a page or the guides, email us and tell us what format works for you.

We aim to reply as soon as we can.

How we assessed this

This statement is based on a self-assessment by the AutoScript Sync developer in September 2026.

Website

We tested a copy of the website running on the developer's own computer, not the live site. That copy doesn't apply the live server's own configuration settings. We used:

• automated checks with axe-core, run in the Chromium browser
• scripted keyboard tests, for example opening and closing the checkout window and the help chat
• checks at a screen width of 320 pixels
• a text-spacing test
• contrast calculations for text and background colour pairs, using the WCAG 2 contrast ratio and the APCA method

The Discord link page was checked from its source code only, because its automatic redirect stopped the automated test. Report Studio was checked as the finished page, because its source code is not kept with the rest of the site.

Not yet tested on the website:

• with a screen reader (such as NVDA, JAWS or VoiceOver)
• in Windows High Contrast or forced-colours mode
• on real phones or tablets. Narrow screens were checked only as a 320-pixel-wide browser window.
• with Lighthouse

Windows app

We used:

• a review of the source code for the main window and its dialogs, panels and overlays
• test scripts that build the app's windows off-screen with temporary settings, a stand-in video player and, for device checks, a stand-in device. The scripts send key presses and compare screenshots taken before and after a control receives focus.
• contrast calculations for the app's colours

Most of the app tests were run on a development copy that includes changes made after version 2.121.1. We re-checked the keyboard and device-stopping findings against the source code of version 2.121.1.

Not yet tested in the app:

• With a screen reader, or with a tool that inspects what Windows accessibility software sees. Which names a screen reader would announce was worked out from the rules of the toolkit the app is built with, so some findings may change once they are checked with a screen reader.
• With a real device.
• On a real screen, rather than off-screen. This includes whether Alt+F4 closes the Vibration panel the same way as its close button.
• The getting-started tour and the model download prompt.
• With Windows contrast themes. These were assessed from the source code only.

Reviewing this statement

We will update this statement whenever we fix one of the problems listed above, and review the whole statement at least once a year. The next full review is due by 14 September 2027.