Accessibility goals, known media-tool barriers and a route for reporting issues on Vaultxon. This page describes the current browser-based release and its known limits.
Accessibility goals
Vaultxon aims to make navigation and core tasks usable without a mouse wherever the browser and media API allow it. Pages should use a meaningful heading structure, readable contrast, visible keyboard focus, descriptive control labels and text status messages for progress and errors. Colour alone should not communicate whether an operation succeeded.
The interface includes navigation and page landmarks intended to help users move between tools and documentation. These design intentions are not a claim that every page or operation has passed a formal accessibility conformance audit.
Media-specific limitations
File pickers, media playback, canvas previews, downloads and browser recording controls can behave differently across operating systems, browsers and assistive technologies. A waveform is not a full text alternative for audio, and a thumbnail does not describe every part of a video. Long processing tasks may also consume significant memory or time.
Where an operation cannot be completed with a particular browser or assistive setup, the page should explain the limitation and avoid announcing success before an output exists. Browser-native dialogs may have their own accessibility behavior outside the direct control of this site.
How to report a barrier
Email support@vaultxon.com with the page address, the control or step that caused difficulty, what you were trying to do, and the browser or assistive technology involved if known. Describe the result you expected and what happened instead. Do not include private media or personal information that is not needed to reproduce the issue.
Clear reports help us distinguish a website defect from a limitation in a browser, device or third-party API. We may ask for more details or suggest a different supported workflow; a report does not create a guaranteed fix date.
Ongoing review
Accessibility is an ongoing practice. Changes to a tool, stylesheet, navigation menu or browser API can introduce new barriers, so important workflows should be checked when they change. Priority should be given to problems that prevent a visitor from selecting a file, understanding an error, downloading a result or reaching privacy and terms information.
If you discover a page that is difficult to read or operate, please send a report through the Contact page. We aim to improve the experience over time and to describe limitations honestly rather than claim unverified compliance.