Accessibility Statement

Last updated: 2026-07-31How accessible APERTURESyndicate is today, measured against WCAG 2.2 AA — what works, what does not, and how to tell us when something blocks you.

Accessibility Statement

APERTURESyndicate OÜ wants everyone to be able to use APERTURESyndicate, including people who navigate by keyboard, use a screen reader, need larger text, or find motion uncomfortable.

This statement covers the platform at aperturesyndicate.com and its subdomains — the main site, the documentation you are reading, Resonance, ASAI, ASVentor, Lysicon Quanture, and the subscription and checkout flows.

This is a self-assessment, not a certificate. It was written by reviewing our own code and interface, not by an external auditor, and it is deliberately specific about failures. If it reads as unflattering in places, that is because the alternative — a page claiming full conformance — would be untrue.

The standard we aim at

We use WCAG 2.2 level AA (and, through it, the European standard EN 301 549) as our target. The European Accessibility Act, Directive (EU) 2019/882, has applied to e-commerce services since 28 June 2025, and it is the reason this page exists in the form it does.

One thing we will not hide behind: as a micro-enterprise — two people, and below every threshold the Directive uses — we understand that the Act's service obligations do not strictly bind us. We are publishing this statement and working to the standard anyway. Being too small to be obliged is not the same as being too small to care, and a person who cannot use the seek bar does not care about our headcount.

Current status: partially conformant with WCAG 2.2 AA. Parts of the platform meet the standard; the specific parts that do not are listed below.

What works today

These are things we have verified in our own code, not aspirations:

  • You can turn animation off. Resonance has a real switch in Settings that reduces every animation and transition across the app, applied before the first paint so nothing flashes on the way. Most of our other applications — the main site, ASAI, ASVentor, the SYNX portal, ASMusic, the Etherane and subscription pages — respect your operating system's "reduce motion" setting automatically.
  • Playback is keyboard-operable in Resonance, through shortcuts for play and pause, next and previous track, seeking, volume, mute, like, shuffle and repeat. They can be remapped in Settings, they follow physical keys rather than keyboard layout, and they stand down while you are typing in a text field.
  • Sliders that matter use real controls. Equaliser bands, volume and playback speed are native range inputs, which means arrow keys work without us having to reinvent them.
  • Escape closes overlays in the Resonance panels and tuners and across most of ASAI. Dialogs in ASAI are built on an accessible dialog library, so focus is trapped inside them and returned when they close.
  • Focus is visible. The main site and the documentation draw a clear focus ring on keyboard navigation, and Resonance does not suppress the browser's own.
  • Pages have structure. The main site and this documentation use real landmarks — navigation, main content, footer — and declare a page language, so a screen reader announces the right voice and can jump between regions.
  • Decorative visuals are hidden from assistive technology. The animated backgrounds and profile effects are marked as decorative, so a screen reader skips them instead of reading noise.

What does not work yet

Known failures, stated plainly. Each is something we can reproduce.

Navigation and focus

  • There is no "skip to content" link anywhere. A keyboard user must tab through the whole header on every page. (WCAG 2.4.1)
  • The shared navigation bar and footer — used by every public application — have had no accessibility work. The mobile menu and the user dropdown cannot be dismissed with Escape and do not manage focus. (2.1.2, 2.4.3)
  • Dialogs outside ASAI do not trap focus. The Resonance panels close on Escape, but Tab can still walk behind them, and focus is not restored to the control that opened them. (2.4.3)
  • Some controls are built from generic elements with a click handler and are therefore invisible to keyboard and screen-reader users. (2.1.1, 4.1.2)
  • Form fields on the main site suppress the default focus ring and signal focus only through a border colour change. (2.4.7)

Resonance player

  • The seek bar and the volume bar respond to pointer input only. They have no keyboard behaviour and no accessible name or value, so a screen reader cannot read or set the playback position. The global shortcuts partly compensate, but the widgets themselves are inaccessible. (2.1.1, 4.1.2)
  • Several transport buttons carry a tooltip but no accessible label. (4.1.2)

Feedback and status

  • Status messages are not announced. Toasts, errors and background progress appear visually with no live region, so a screen-reader user is not told that something succeeded or failed. (4.1.3)

Content and media

  • Video content ships without captions or transcripts. No caption tracks exist anywhere on the platform. Synchronised lyrics in Resonance provide text for music, but that is not a substitute for captions. (1.2.2, 1.2.3)
  • The interactive plot charts in ASAI have no text alternative and no keyboard path — they carry information and are currently mouse-only. (1.1.1, 2.1.1)
  • Reordering by drag-and-drop has no keyboard alternative in several places, including profile blocks, chat lists and the local-track manager. (2.5.7)

Documentation site and colour

  • This documentation site does not declare a page language and does not honour "reduce motion", even though it is published in more than one language. (3.1.1, 2.3.3)
  • Secondary grey text in the light theme is borderline for contrast, and on the secondary background it falls below the 4.5:1 requirement. We have measured this, not guessed it, and it needs a palette fix rather than a note. (1.4.3)
  • Colour contrast across the whole platform has not been audited systematically, so more failures likely exist than the one we can name.

Testing

  • We have not tested with screen readers systematically, and no external accessibility audit has been carried out. Our assessment is a code and interface review by the team that built it, which is the weakest form of testing there is.

What we are doing about it

In rough order of how much difference each makes: a skip link and keyboard handling in the shared navigation bar; accessible names, keyboard control and value announcement for the Resonance player sliders; focus trapping and focus restoration for the remaining hand-built dialogs; a live region for status messages; a contrast fix for secondary text; language and reduce-motion support on this documentation site.

We are not attaching dates to those, because a two-person company that publishes a roadmap of deadlines it then misses has told you nothing useful. This page will be updated as items move from the list above to the list before it.

Tell us when something blocks you

If any part of the platform is unusable for you — a control you cannot reach, a page a screen reader cannot make sense of, text you cannot read — write to [email protected] with "Accessibility" in the subject line.

Please include, as far as you can: the page or screen, what you were trying to do, what happened instead, and the browser and assistive technology you use. Any of those helps; none is required, and a one-line message is a perfectly good report.

We acknowledge accessibility reports quickly and give you a substantive answer within 30 days, telling you either that it is fixed, or what we are going to do and roughly when. If a request needs longer, we say so rather than going quiet. We accept reports in English or Estonian.

If we do not respond, or the answer does not satisfy you, you can raise the matter with the Estonian authority responsible for consumer protection and market surveillance, Tarbijakaitse ja Tehnilise Järelevalve Amet (TTJA): https://www.ttja.ee · [email protected].

About this statement

This statement was prepared on 31 July 2026 by self-assessment: a review of our own source code and interfaces against WCAG 2.2 AA. It applies to aperturesyndicate.com and its subdomains. It will be reviewed whenever a listed item is fixed, and at least once a year.

APERTURESyndicate OÜ · Registry code 17384111 · Priisle tee 8, Lasnamäe linnaosa, Tallinn, Harju maakond, 13914, Estonia · [email protected]

Accessibility Statement | AS Docs