Accessibility

Everyone in command.

A defence system is only as strong as the people who can use it. We aim for WCAG 2.2 level AA across this website.

Send feedback Known limitations
Target WCAG 2.2 AA Updated 30 October 2026
Light
Ink on paper
19.8:1 AAA
Crimson on paper
5.9:1 AA
Dark
Ink on night
18.7:1 AAA
Crimson on night
6.2:1 AA
Focus

A 2 px ring, 3 px clear, on buttons and links. Text fields take an ink border and a soft halo.

Motion

Follows Reduce Motion. Anything that moves for longer than five seconds can be paused.

Contrast measured from the site’s own colour tokens. White on the crimson buttons is 5.9:1.

On this website

Built in, not bolted on.

Accessibility is part of the design rules every page is built from: the same structure, the same keys, the same contrast and the same care with motion, on every surface.

  • The keyboard, all the way

    Every link, button, menu and demo works from the keyboard, in reading order. A skip link at the top of each page jumps past the header to the content.

    TaborShift+Tab

  • Focus you can see

    A ring marks the button or link you are on, and text fields take an ink border with a soft halo, on white, night and crimson alike. The ring appears whenever you move with the keyboard.

    Taband watch the ring

  • Motion on your terms

    With Reduce Motion switched on, text appears without animation, films do not start by themselves, scroll-linked scenes settle into still layouts and demos move only when you ask.

  • Pause anything

    Visuals that move by themselves for longer than five seconds come with controls to pause them, and animation stops when it scrolls out of view.

  • Contrast in both themes

    Body text is 4.5:1 or better in light and dark. Crimson text switches to a lighter shade on dark surfaces so it keeps its contrast.

  • Words for every picture

    Images that carry meaning say what they show. Decorative films, grids and instrument overlays are hidden from screen readers, so they do not get in the way.

  • Consoles you can operate

    Every interactive console has a button for each action, a keyboard path, and a live region that announces what changed.

  • Your theme

    Light, dark or match your system, from the switch in the footer. Your choice stays in your browser and is never sent anywhere.

Keyboard

Every console has a keyboard path.

The maps, feeds and command panels across the site answer to the keys you already use everywhere else.

TaborShiftTab
MoveForward and back between links, buttons and consoles, in reading order.
EnterorSpace
ActPress a button: run a check, send a team, pause a film, open a menu.
ChooseMove between the options in a group, such as tabs, switches and the steps of a console.
Esc
CloseClose the menu and return focus to the button that opened it.

Try it on the egress map

The apps

Built on Apple’s accessibility.

The Vamocles apps for iPhone and Mac are available in preview.

Today

  • Standard controls that VoiceOver, Voice Control and Switch Control can read and operate
  • Most text follows your Dynamic Type size on iPhone
  • Vamo, the voice orb and other animated elements calm down when Reduce Motion is on
  • App Lock accepts Face ID, Touch ID or your passcode, or your account password on the Mac
  • Light, dark or match the system
  • Talk to Vamo in voice mode, or type instead

Not yet

  • A full VoiceOver audit of both apps
  • Dynamic Type for a few fixed-size labels
  • Spoken descriptions for every custom graphic and chart

Known limitations

Where we still fall short.

We would rather tell you than have you find out. These are the gaps we know about today.

  1. Instrument overlays are decorative

    The small readouts drawn over imagery and film, such as feed names, headings and markers, are hidden from screen readers. The text around each image gives the same information.

  2. Films are silent, without captions

    Every film on the site is silent and decorative. None of them says anything the page does not also say in words.

  3. Drawn maps are pictures

    Maps, radar sweeps and network drawings inside the demos are drawn images. Screen readers follow a demo through its buttons and its announcements, not through the drawing itself.

  4. Scroll-linked scenes

    A few sections move as you scroll, such as the run through every domain on the home page. With Reduce Motion on, or on a narrow screen, that run becomes a simple stacked list.

  5. Forms write an email

    The briefing form works with a keyboard and screen readers: errors are listed in a summary and next to each field, and the result is announced. If you would rather not use the form, write to hello@vamocles.com from wherever you read email.

  6. Menus need JavaScript

    Without JavaScript, every page still reads from top to bottom, but the header, the footer, the theme switch and the demos do not appear.

  7. No independent audit yet

    Our checks are our own: keyboard-only passes, Reduce Motion, both themes, phone widths and contrast against our colour tokens. An independent WCAG 2.2 audit has not been done yet.

Feedback

Tell us what gets in your way.

Write to hello@vamocles.com with “Accessibility” in the subject. If you need anything on this site in another format, ask, and we will find one that works for you.

Email hello@vamocles.com

It helps to include

  1. 01The page address, or the app and device
  2. 02What you were trying to do
  3. 03What happened instead
  4. 04Your browser and any assistive technology

About this statement

Standard
WCAG 2.2, level AA
Covers
vamocles.com, and the Vamocles apps for iPhone and Mac, available in preview
Relies on
HTML, CSS, JavaScript and WAI-ARIA
Last updated

How this site treats your data is on the Security page and in the privacy policy.