Adoption pack · AssisT 1.0.0
Everything you need to decide whether to recommend AssisT to your students, in one place. It is free, it is open source under the EUPL-1.2, there is no contract to sign and no account for anyone to create. What follows is the evidence, including the parts that are not finished.
Learning support officers, disability support officers, assistive technology officers, access and inclusion teams, and the IT and data protection colleagues they have to convince. In other words: the person who has to answer "is this safe, is it accessible, what does it cost, and who signs for it" before a tool can be recommended to a student.
AssisT is designed for students working inside a learning management system — Canvas, Moodle, Google Classroom — and on the web generally. It is used by neurodivergent students, dyslexic students, students with low vision, students with motor impairments, and students who simply read and write better with support. It does not require a diagnosis, a referral, or any record that a student is using it.
Twenty-nine supports in one extension, grouped as Reading, Writing, Seeing, Focus and Study, with twelve built-in profiles that configure them in one click.
Text-to-speech with synchronised word highlighting, reading mode, dyslexia reading modes (bionic, syllable, grammar colour), reading guide, speed reading, dictionary lookup, and translation into 14 languages.
Dictation with spoken editing commands, sticky notes and annotations, a citation manager covering four styles and ten source types, and Authorship Shield, which keeps a local record of how a piece of writing developed.
Five fonts including Lexend and OpenDyslexic, spacing controls and an interface that survives a student's own text-spacing overrides (SC 1.4.12), screen colour overlays, a magnifying lens, a custom cursor, and OCR that pulls text out of images in 14 recognition languages.
Focus mode, reduced motion, autoplay blocking, a simplified-interface level, a Pomodoro timer, Maths Support, and a mind map (beta) whose outline is a fully keyboard-driven ARIA tree.
AI is optional and off by default. Where a student wants it, it can run entirely on their own machine (Ollama), entirely in the browser (WebLLM), or through a cloud provider using the student's own API key. Full feature detail.
Alt+R for reading mode, Alt+Shift+D for the
dictionary, Escape to get out. There are 16 shortcuts and all of them are
re-bindable.
All 55 WCAG 2.2 Level A and AA criteria (self-assessed), in VPAT 2.5 format, with EN 301 549 and Section 508 mapping. A self-assessment by the developer, not an independent audit — it says so on the page, and it lists the gaps.
What is stored, where, and what leaves the device. Chrome permissions explained one by one. FERPA, COPPA and GDPR positions stated without overclaiming.
Force-install by extension ID through Chrome Enterprise, the one managed policy key that exists, and the settings we recommend for a disability service rollout.
Every third-party service AssisT can contact, what triggers it, exactly what is sent, a link to each provider’s terms, and whether it is opt-in. Fiavaion itself has no sub-processors.
EUPL-1.2: use, modify and redistribute under the same licence. No fee, no seat count, no renewal. The licence text itself is in the repository.
Also: LICENSE on GitHub
Channels, the 5-working-day acknowledgement for accessibility reports, how updates arrive, and an honest list of what is not promised.
Every release, what changed in it, and when. Useful if you need to show a committee that the tool is actively maintained.
Everything above is public and needs no request. Email us if you need something it does not cover — a written statement for procurement, an institution branding key for managed browsers, or a walkthrough for your team. The link opens a message with the subject and a short checklist already filled in.
Accessibility and institutional enquiries are acknowledged within 5 working days. See the support commitments for what that does and does not mean.
Nothing. There is no paid tier, no premium version, no per-seat licence, no institutional edition, and no renewal. Development is funded by voluntary contributions through Patreon, Buy Me a Coffee and GitHub Sponsors. Nothing in AssisT is held back behind a payment.
No. There is no account to create, no email address to hand over and nothing to sign in to. A student installs the extension and it works. That also means there is no roster to manage, no seats to reclaim, and no list of who is using it — including for us.
Not by default. Settings live in chrome.storage.local on the device; notes,
annotations, citations, mind maps and Authorship Shield history live on the device in
IndexedDB. Nothing syncs across devices and nothing reaches Fiavaion — we run no server
that could receive it.
Text leaves the device in three cases, all of them visible to the student at the moment they happen: a translation request, a dictionary lookup, and a cloud AI request if the student has configured a provider with their own API key. Each one sends only the text the student selected, directly to that provider. The sub-processor list names every one of them.
Fiavaion processes no personal data through AssisT, so we are neither controller nor processor and there is no data processing agreement to sign with us. If a student enables a cloud provider with their own key, that provider is that student's own sub-processor under the student's agreement with them. For FERPA: AssisT is designed with FERPA principles in mind — no student data is collected. We make no HIPAA claim.
AssisT is licensed under the EUPL-1.2, an EU-approved open source licence. You may use it, modify it, and redistribute it under the same licence, for any purpose, without asking us. The source is public. If the project stopped tomorrow your institution could fork and maintain it, and the copies already installed would keep working, because nothing depends on a server we operate.
Chrome and Edge, version 88 or later, on Windows, macOS, Linux and ChromeOS. There is no Firefox build and no Safari build. If your students are issued iPads, AssisT is not the tool for them.
Through the Chrome Web Store, silently, on Chrome's own update schedule. There is nothing for IT to repackage or push and nothing for the student to do. If you force-install AssisT by policy, updates still arrive the same way — see the managed deployment guide. Every release is listed in the changelog.
Yes, by extension ID through Chrome Enterprise, Chrome Browser Cloud Management, Group Policy or the equivalent Edge policy. One managed policy key exists — an optional institution branding key that applies your name and colours. It grants no other capability and gives the institution no visibility of student activity. See the managed deployment guide.
No. The Accessibility Conformance Report is a self-assessment by the developer. An independent specialist audit is planned but not commissioned, and there is no date for it. Screen-reader conformance testing with NVDA, JAWS and VoiceOver has not been done. We would rather you knew that now than found out during a pilot.
Page last updated 13 September 2026, for AssisT 1.0.0.