Built to be used by everyone.

We build against the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. We have not commissioned an independent audit, so we do not claim formal conformance. What follows is what the site does, not what we would like it to do.

• Keyboard. Every link, button and form field can be reached and operated with a keyboard alone, and each one shows a visible focus ring when it has focus. A “Skip to content” link is the first thing you reach on every page.
• Reduced motion. If your device asks for reduced motion, the site listens. The entrance sequence is skipped rather than played, scroll animation is switched off, the 3D piece stops turning on its own, and decorative movement does not run.
• Screen readers. Photographs carry descriptions written from the real piece and its real material. Purely decorative images are hidden from the reading order rather than announced as noise, and the entrance describes itself as it moves.
• Both themes. The site ships a dark and a light view, and text contrast is checked in both rather than only in the one it was designed in.
• Layout. Photographs are shown at their own measured proportions instead of being cropped to fit, so nothing important is cut off when the page is zoomed or the window is narrow.

These are real and we would rather name them than let you find them:

• The 3D piece on the home page is turned by dragging. There is no keyboard equivalent for rotating it. A still photograph of the same piece is shown to anyone whose browser cannot run it, but a keyboard user on a working browser gets the model and no way to turn it.
• The entrance sequence clears a circle of frosted glass around the pointer. With no pointer it drifts on its own so nothing is lost, but the effect is not something you can direct without one.
• We have not tested with every screen reader. Our checking has been with keyboard navigation and the accessibility tree, not with the full range of assistive technology people actually use.

If something here is hard or impossible to use, we want to hear about it — especially the parts we have not thought of. Write to connect@vihacollective.com or use the contact page, and describe what you were trying to do and what got in the way. We will reply, and we will tell you honestly whether and when we can fix it.