Accessibility

Last updated 5 November 2026.

Uzu should work for everyone, including people who use a keyboard instead of a mouse, a screen reader, or zoom. Our target is WCAG 2.2 level AA, the usual standard for accessible websites. We are not there yet. This page says what works, what does not, and how to tell us about a problem.

What works today

• Signing in, signing up and setting your password work with a keyboard and a screen reader. Every field has a label, and Tab reaches every button and link.
• A visible outline shows where the keyboard is, on every page and in every colour theme.
• Buttons that show only an icon have a name a screen reader reads out.
• Form fields across the app have a label a screen reader reads out.
• Tab reaches the values you edit in place, the calendar's days and filters, and the file picker on Import.
• Pop-up windows are announced as pop-ups. The keyboard stays inside one while it is open, Escape closes it, and the keyboard goes back to the button that opened it.
• Headers that stay at the top of a list while you scroll do not cover the item the keyboard is on.
• Each change to the app is checked automatically for missing labels and for common accessibility problems.

What does not work yet

• Moving and resizing the tiles on the dashboard needs a mouse.
• Some of the optional colour themes show accent text with less contrast than the standard asks for on some backgrounds. The default Dark theme and the Light theme pass.
• The iPhone app has not been tested with VoiceOver yet. Some of its pictures have no description, and some rows are smaller than Apple's recommended tap size.

Tell us about a problem

Email hello@vendorvault.dev. Say which page you were on, what you were trying to do, and what you use (a screen reader, the keyboard, zoom, or something else). A person reads every message and will answer, and we will tell you when it is fixed.