Keyboard navigation
Interactive controls on the web app and this site are reachable and operable with a keyboard alone — links, buttons, forms, and dialogs — with a visible focus indicator as you move.
An assistant everyone can use.
Tase is committed to making its website, web app, and mobile apps accessible to people with disabilities. This statement describes the standard we hold ourselves to, what works today, where we still fall short, and how to reach us when something blocks you.
Our standard
WCAG 2.1 Level AA is our target.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across our digital services. This statement is prepared with regard to the European Accessibility Act (Directive (EU) 2019/882), which applies to consumer digital services in the European Union from 28 June 2025, and the harmonized requirements of EN 301 549.
Today, Tase is partially conformant with WCAG 2.1 Level AA: most content and functionality meets the standard, and the known exceptions are listed below. Accessibility is reviewed as part of ongoing development — including automated checks in our release pipeline — not as a one-off project.
What works today
Built to work with the tools you already use.
Screen readers
Pages use semantic HTML landmarks, headings, labels, and alt text so screen readers such as VoiceOver, NVDA, and TalkBack can announce content and controls meaningfully.
Text resizing
Layouts are built with relative units and responsive containers, so text can be enlarged with browser zoom or system text-size settings without content being cut off.
Dark and light themes
Every screen ships in both a dark and a light theme, and the interface follows your system preference automatically so you can pick whichever is more comfortable to read.
Reduced motion
Entrance animations and transitions honor your operating system’s “reduce motion” preference — when it is on, content renders statically instead of animating into view.
Assistive tech on iOS
The Tase iOS app builds on Apple’s native accessibility stack, including VoiceOver, Dynamic Type, and system contrast settings, and we keep improving coverage release by release.
Known limitations
Despite our best efforts, some parts of Tase are not yet fully accessible. We list them here honestly, and we are actively working to close each one:
- Some text placed over translucent “glass” surfaces may fall below the WCAG AA contrast ratio in certain theme combinations. We are auditing these surfaces and raising contrast where needed.
- Voice conversations are real-time audio; live captions for the assistant’s spoken replies are not available yet. The same assistant is fully usable over text chat.
- A few complex interactive views (for example, charts and drag-to-reorder lists) do not yet expose complete non-visual alternatives. Underlying data remains available in accessible list form.
- Third-party content embedded from other platforms (such as app-store badges or shared media) may not meet the same standard; we cannot always control its markup.
Something blocking you? Tell us.
If you encounter an accessibility barrier anywhere in Tase — a control you cannot reach, content you cannot perceive, a flow you cannot complete — email us. We aim to respond within 5 business days, and reported barriers are prioritized in our fix queue.
support@tase.appIf you are in the European Union and are not satisfied with our response, you may also contact the market surveillance or enforcement authority responsible for the European Accessibility Act in your member state.
This statement was prepared on 13 July 2026 and last reviewed on 13 July 2026. It is reviewed whenever the product changes materially. See also our Privacy Policy and Security & Privacy pages.