Accessibility at Foundry
This website is scanned with axe-core in light and dark at phone and desktop widths and has no serious or critical findings. The Foundry console started at 94 serious or critical findings in the same scan of 17 screens; after the repairs of 10/29/2026 the scan finds none, in light and dark, at phone and desktop widths, and we list what is still open below. We do not claim a WCAG conformance level.
What Foundry 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 console has a skip link to the main content, a main landmark, and labeled navigation regions. Every scrolling region (tables, JSON blocks, lists) is a named region a keyboard can reach, and the inventory table's header checkbox is its own control. A keyboard-only walkthrough of every flow has not been recorded.
Evidence
- frontend/src/components/ForgeLayout.tsx in the Foundry repo: the skip link, the main landmark, the labeled top and side navigation, and the phone drawer (menu button, Escape, backdrop; out of the tab order when closed)
- frontend/src/__tests__/scroll-regions.test.ts: every element that scrolls carries tabIndex 0, role region, and a name
- frontend/src/__tests__/inventory-select-all.test.tsx: the header checkbox is not inside a button and selects the visible rows
- axe-core 4.14.0 in the screenshot harness: scrollable-region-focusable and nested-interactive found 22 and 4 nodes before and none after (68 scans, 10/29/2026)
Screen reader landmarks and labels Partly supported
Landmarks are labeled, every icon button has a name, and axe-core finds no naming or label violation on any scanned screen. Nothing has been tested with a screen reader.
Evidence
- frontend/src/__tests__/a11y.test.tsx runs axe-core on the stacks route with no data
- frontend/src/__tests__/stack-resource-buttons.test.tsx: every icon button in the resource table has a name, and the releases screen has no second main landmark
- axe-core 4.14.0 in the screenshot harness: button-name (120 nodes before the fix) finds none in 68 scans
Contrast in light and dark Partly supported
Text contrast passes in light and dark. The console has real light, dark, and system themes on design-system tokens, a token-level test checks every text and tint pair at 4.5 to 1 in both, and the axe scan finds no color-contrast violation on any of the 17 screens. It was checked by tools, not by a person with low vision.
Evidence
- frontend/src/__tests__/theme-contrast.test.ts: reads global.css and the design-system tokens and requires 4.5 to 1 for text and 3 to 1 for control edges, in both themes
- frontend/src/__tests__/no-hardcoded-colors.test.ts: no raw hex or stock palette color in the console source
- axe-core 4.14.0 in the screenshot harness: color-contrast found 274 nodes before and none after (68 scans, 10/29/2026)
Reduced motion Not yet tested
The Renkara design system carries a reduced-motion rule that the console inherits. Foundry's own tests do not check it.
Text resize and zoom Not yet tested
Resizing text to 200 percent has not been tested.
Mobile and touch Partly supported
At 375 by 667 pixels none of the 17 scanned console screens scrolls sideways, in either theme. The side navigation is a drawer below 768 pixels, and tables scroll inside labeled regions. It was checked in a desktop browser at that width, not on a phone.
Evidence
- axe harness run, 10/29/2026: horizontal overflow in 0 of 17 screens at 375 px, in light and dark (it was 15 of 17 before)
- frontend/src/__tests__/forge-layout.test.tsx: the phone drawer and the full-width main region
- The screenshot harness fails the run if any view scrolls sideways at 375 px or any serious or critical violation appears
No WCAG conformance level is claimed for Foundry or its console. No one has audited either against WCAG or tested them with assistive technology. The figures below come from one automated axe-core 4.14.0 run (WCAG 2.0 to 2.2 A and AA rules plus best practices) in the screenshot harness, on a fictional StrataForge Robotics organization: 17 console screens, 375 and 1440 pixels, light and dark, 68 scans.
This website
What was checked on this site
- An axe-core scan of all 19 pages at 375 and 1440 pixels, in light and dark, finds no serious or critical violation and no horizontal overflow (the kit's shared test, run on 10/29/2026).
- Text and button colors are checked for 4.5 to 1 contrast against the design-system tokens in both themes.
- The product screenshots are captures of the real console in its light and dark themes, from the same sealed harness run as the scan above.
What does not work yet
- Heading levels skip on five console screens (stack detail, plan, costs, compliance, taxonomy), a moderate axe finding.
- No keyboard-only walkthrough of every flow, no screen reader test, no text-resize test, and no check on a physical phone.
- The accessibility checks are automated scans of a fictional organization; no one has audited the console against WCAG.
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 Foundry 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.