Accessibility at Lattice
Lattice's visualizer uses native controls with accessible names, a page heading, and focusable scrolling regions, and axe-core finds no violations in it in light and dark. The graph itself is a canvas you drive with a mouse, so picking a symbol has no keyboard path yet. We do not claim a WCAG conformance level for the product.
What Lattice supports today
Each line says what the product does, how we know, and where to look. “Not yet tested” means exactly that: we have not checked, and we do not claim it.
Keyboard operation Partly supported
The repository, kind, and package menus, the blast-radius checkbox, the theme toggle, the symbol panel, and its scrolling regions are native controls or focusable regions that Tab reaches. The graph canvas is mouse-only, so selecting a symbol has no keyboard path yet.
Evidence
- lattice.spec.ts in the screenshot harness: a scripted Tab walk reaches Repository, Symbol kind, Package, blast radius, and the theme toggle, in that order
- DetailPanel.test.tsx in the Lattice frontend tests: the symbol panel and the signature box take keyboard focus
- The visible focus ring was not measured, and a person has not walked every flow by keyboard.
Screen reader landmarks and labels Partly supported
Every menu has a name, the page has one h1, and axe-core finds no violations in the populated visualizer in either theme. The graph is a canvas with a text label only; the symbol panel and the MCP tools return the same facts as text. It has not been tested with a screen reader.
Evidence
- lattice.spec.ts in the screenshot harness runs axe-core on the populated visualizer (a symbol selected, blast radius on) in light and dark: zero violations on 10/29/2026
- Controls.test.tsx and GraphCanvas.test.tsx in the Lattice frontend tests: accessible names for the menus and the canvas label
Contrast in light and dark Partly supported
The axe-core color-contrast rule passes on the interface in both themes. The colors drawn inside the canvas (node kinds and the blast-radius ramp) were not measured for contrast.
Evidence
- axe-core color-contrast rule in the harness's lattice.spec.ts, light and dark
Reduced motion Supported
Nothing in the visualizer animates. Its stylesheet has no transitions or animations, and the canvas redraws only in response to input.
Evidence
- The Lattice frontend's global.css has no transition, animation, or keyframes rules (read 10/29/2026)
Text resize and zoom Not yet tested
Resizing text to 200 percent has not been tested in the visualizer.
Mobile and touch Partly supported
The visualizer page does not scroll sideways at 375 by 667. It is a desktop tool. The canvas pans with a mouse drag and zooms with the wheel, with no touch gestures, and touch target sizes were not measured.
Evidence
- lattice.spec.ts in the screenshot harness: zero horizontal overflow at 375 by 667
No WCAG conformance level is claimed for Lattice. The checks below are automated (axe-core) plus a scripted Tab walk and a phone-width overflow test. No one has audited Lattice against WCAG or tested it with a screen reader.
What does not work yet
- Symbols on the graph canvas cannot be selected, panned, or zoomed from the keyboard.
- The colors drawn on the canvas have not been checked against a contrast ratio.
- Touch panning and pinch zoom are not supported, and touch targets were not measured.
- Lattice has not been tested with a screen reader, and 200 percent text resize has not been tested.
How this site is built and checked
This site targets WCAG 2.2 level AA. That is a target we build and test toward, not a certification, and no one has audited it for conformance.
Structure
A skip link, labeled landmarks (header, navigation, main, footer), one h1 per page, and headings that do not skip levels.
Keyboard and focus
Links and buttons are native elements, so they work from the keyboard. Focus is drawn as a visible ring, and the menu closes with Escape.
Contrast
Text meets 4.5 to 1 in both the light and dark themes, checked against the stylesheet by the test suite.
Motion
Transitions and animation switch off when your system asks for reduced motion.
Small screens and zoom
Layouts hold at 375 pixels wide with no sideways scrolling, text resizes with the browser, and touch targets are at least 44 pixels.
Automated scan
Every page is scanned with axe-core at 375 and 1440 pixels in light and dark, and the checks fail on any serious or critical violation. Automated tools find only part of the problems, so this is a floor, not proof.
Images
Every product screenshot has a text description and comes in a light and a dark version that follows your theme.
Your theme choice
The theme follows your system setting until you pick one with the button in the header.
Tell us what is in your way
If something here or in Lattice does not work for you, write to Renkara Media Group. Say what you were doing, what you used, and what happened, and a person will answer.
Statement last reviewed 10/29/2026.