Accessibility

Loclavis should be usable by as many people as possible, including with a keyboard, a screen reader, heavy magnification or a sensitivity to motion. This page describes honestly what is in place and what is still open.

This version dates from: 26 August 2026

What we are aiming for

We want protecting and reopening files with Loclavis to work regardless of how you operate it. Accessibility is not a one off project for us but something we check on every change.

What we follow

Our target standard is the Web Content Accessibility Guidelines version 2.2 at level AA. We test continuously in an automated way and by hand in samples.

We do not claim to be fully accessible, and we hold no external certification. No full third party audit has taken place. Where we have not checked something, it is listed below.

Using a keyboard

The whole main flow works without a mouse: choose a file, type or generate a password, protect, download the result and run the follow up actions. Decryption works the same way.

• Tab moves you forward, Shift and Tab move you back.
• Buttons and links activate with Enter, and buttons also with the space bar.
• Move between the Protect and Decrypt sections with the arrow keys; Home and End jump to the first and last section.
• Escape closes notes that have appeared.
• Dropping files with a mouse is an extra way, never the only one. There is always a button to choose files.
• There is no point at which keyboard operation gets stuck.

Visible focus

Whatever you have moved to always carries a clear outline, in both the light and the dark appearance. After actions that replace parts of the interface, focus stays somewhere sensible rather than being lost.

Screen readers

We reach for ordinary HTML first and add to it only where that is genuinely needed.

• Actions are real buttons and navigation is real links. Both carry a meaningful name.
• Every input has a visible label, and any extra hint is tied to the field itself.
• Progress, success and errors are announced in a region screen readers read out, so you do not have to go looking for them.
• Every page has exactly one main heading and a sensible outline. There are regions for navigation, content and footer, plus a skip link to the content.
• The explanatory graphics are hidden from screen readers because the same content sits directly below them as text.

Magnification and small screens

The pages work from a width of 320 pixels and at 200 percent magnification without needing horizontal scrolling. Text is not cut off and the layout adapts. Very wide content such as tables can be moved within its own area.

Colour and contrast

We watch for sufficient contrast on text, borders and the focus outline, in both appearances. Important information is never carried by colour alone: success, warning and error always come with text and a symbol as well.

Motion

The explanatory graphics are animated very sparingly. Each movement runs once and lasts a fraction of a second. If your operating system is set to reduce motion, it is dropped entirely. Nothing animates permanently and nothing flashes.

Using it with limited dexterity

Controls are large enough on touch devices and are not crowded together. No function is reachable only by hovering with a mouse or only by dragging. Every drag action has an equivalent button.

Known limitations

These points are known to us and not yet fully checked:

• We have not walked through every single page manually with the common screen readers. The main flow has been checked; the pure content pages not in full depth.
• Operation has been checked automatically in Chromium and Firefox browsers. We have no test result for Safari yet.
• A file protected with a PDF password is opened by your PDF application, not by us. How accessible that password prompt is lies outside our control.
• Very large files can take a long time on weaker devices. Progress is announced, but we cannot shorten the wait itself.

Found a barrier?

Please write to us if you run into something that stops you using the service. Describe briefly which page it concerns, what you use to operate the page and what did not work. We will look into it and come back to you.

Contact: tshfm78@gmail.com