Tested interaction behavior / remaining manual checks
Accessibility in Holaryn Agent
Review the interaction mechanics designed into Holaryn Agent, the evidence recorded for specific environments, and the manual coverage that remains open.
Designed behavior
What the product is designed to support
Holaryn Agent uses semantic structure, keyboard-operable controls, visible focus, live status, responsive layouts, zoom, and reduced-motion handling as engineering requirements. Each mechanism still needs evidence for the specific product surface and test environment.
Keyboard and focus
Skip links, native controls, logical DOM order, focus-managed overlays, and visible focus indicators are product design requirements.
Recommended use: Rebind supported product shortcuts when defaults conflict with an operating system or assistive technology.
Limit: A documented keyboard path is evidence for that path, not proof that every workflow has completed manual keyboard review.
Inspect the exact release evidenceAnnouncements and status
Polite live regions and accessible names communicate streaming work, async changes, save state, and selected product notifications.
Recommended use: Keep the active surface open when a continuous status stream is needed; review durable run history for prior outcomes.
Limit: Announcement timing and verbosity can differ across browser, desktop shell, and screen-reader combinations.
Inspect the exact release evidenceReflow, zoom, and motion
Responsive layouts, desktop zoom controls, text scaling, and reduced-motion handling are covered by implementation rules and automated regressions.
Recommended use: Use native browser or desktop zoom and the operating system's reduced-motion preference.
Limit: Automated viewport and motion checks do not replace manual 200% text and 400% browser-zoom review.
Inspect the exact release evidenceChoose a surface
Surfaces and interaction guidance
Choose the product surface that fits the task, then use documentation for the same published Holaryn Agent release. Naming a surface does not mean every capability or operating system behaves identically.
Command line
Terminal output and command interaction retain textual status and do not require a pointer.
Recommended use: Use the command surface when a linear, text-first workflow is the clearest fit.
Limit: Exact terminal and screen-reader behavior still depends on the terminal, operating system, and configured assistive technology.
Inspect the exact release evidenceLocal web interface
Named landmarks, real labels, headings, live regions, focus-managed dialogs, and button alternatives support keyboard and screen-reader operation.
Recommended use: Use the skip link, workspace shortcuts, semantic controls, and the accessible terminal log view.
Limit: Specific implemented mechanics do not establish compatibility with every browser and assistive-technology pairing.
Inspect the exact release evidenceDesktop app
The desktop app wraps the same local web interface with native menus, persisted zoom, tray behavior, and operating-system notifications.
Recommended use: Use native menu commands for zoom and keyboard shortcuts when the desktop shell is preferred.
Limit: Notification announcement and native-shell behavior vary by operating system and assistive technology.
Inspect the exact release evidenceComputer use
The supervised computer-use surface exposes semantic roles and names beside a selected-window image and retains keyboard-operable supervision controls.
Recommended use: Use the semantic target list without relying on the screenshot when operating supported Windows applications.
Limit: Native computer use is a Windows-only beta. No macOS or Linux computer-use support is claimed.
Inspect the exact release evidenceInteraction contract
Keyboard, focus, announcements, reflow, and reduced motion
These mechanics work together: controls need names and states, focus needs a visible and logical destination, async work needs a restrained announcement, and layouts must remain operable without motion or horizontal document scrolling.
Keyboard: real controls and rebindable shortcuts remain alternatives to pointer-only operation.
Focus: overlays and page changes move or restore focus deliberately; visible focus is never color alone.
Status: polite live regions report relevant asynchronous changes without treating every stream token as a new alert.
Display: responsive reflow, native zoom, text scaling, and reduced-motion preferences remain part of the test boundary.
Product evidence
Testing evidence and current coverage
Completed means the named check ran in the stated environment. Partial means concrete mechanics or automated evidence exist but the full named matrix is open. Pending means no completed dated pass is claimed.
| Evidence | Status | Environment and date | Scope and limit | Source |
|---|---|---|---|---|
| Semantic web-interface mechanics | Partial | Published Nightly source and product browser gates |
Named landmarks/controls, focus management, live regions, heading structure, and keyboard alternatives are documented and exercised by automated scenarios. The refreshed external assistive-technology matrix remains incomplete. | Inspect the exact release evidence |
| Desktop zoom and notification mechanics | Partial | Published Nightly desktop guide |
Native zoom commands, persisted zoom, and announcement-oriented notification behavior are documented. Operating-system and assistive-technology combinations are not comprehensively verified. | Inspect the exact release evidence |
| Windows computer-use semantics | Partial | Windows-only beta at the published Nightly |
Semantic roles/names, target highlighting, keyboard supervision, and redacted step history for native computer use. No macOS or Linux native computer-use claim. | Inspect the exact release evidence |
| JAWS manual workspace matrix | Pending | JAWS 2025+ / Edge / Windows |
Refreshed end-to-end workspace review with current supported Windows/browser versions. The published verification record says this follow-up was not performed. | Inspect the exact release evidence |
| NVDA manual workspace matrix | Pending | Current NVDA / Firefox or Chrome / Windows |
Refreshed end-to-end workspace review with current supported Windows/browser versions. The published verification record says this follow-up was not performed. | Inspect the exact release evidence |
| VoiceOver manual workspace matrix | Pending | VoiceOver / Safari / current macOS |
Refreshed end-to-end workspace review on current Apple environments. The published verification record says this follow-up was not performed. | Inspect the exact release evidence |
| Orca manual workspace matrix | Pending | Orca / Firefox or Chromium / Linux |
A dated representative product pass has not been established by the reviewed release evidence. No broad Orca compatibility claim is made. | Inspect the exact release evidence |
Keep open work visible
Known limits
These limitations are part of the current assessment, not a hidden footnote.
- No formal product or website WCAG conformance statement is established.
- The refreshed JAWS, NVDA, and VoiceOver workspace matrix remains Pending; broad Orca compatibility is not claimed.
- Native computer use is a Windows-only beta, even though other agent surfaces run on Windows, macOS, and Linux.
- Automated axe, keyboard, reflow, and motion checks cannot reproduce every browser, operating-system, zoom, input, and assistive-technology combination.
- A specific documented behavior is evidence for that path and version, not a guarantee that every task or extension is accessible.
Privacy-safe reporting
Report an accessibility problem
Use Support for an accessibility problem. A useful report describes the environment and interaction without asking you to disclose a disability or include secrets and private content.
Include
- Product or website surface and exact version
- Operating system, browser, and assistive technology when relevant
- Steps to reproduce
- Expected and actual behavior
- Privacy-safe text or redacted evidence
Keep out
- Passwords, API keys, tokens, or private prompts
- Unredacted personal or customer data
- Disability or medical information
- Vulnerability detail—a security finding uses the private security path
Choose the Support reporting path or report a vulnerability privately.
Website evidence
Accessibility of this website
Website test results follow the same reporting rule: dated automated results remain separate from manual environments marked Pending. This page is included in the representative structure, axe, keyboard, and reflow tests.
| Evidence | Status | Environment and date | Scope and limit | Source |
|---|---|---|---|---|
| Automated semantics and axe baseline | Completed | Playwright Chromium and axe-core |
One H1, named landmarks/controls, unique IDs, metadata, and no serious/critical axe findings across representative routes. Automated scanning is a regression signal, not a conformance statement. | tests/browser/shared-shell.spec.js and Django structural response tests |
| Keyboard, no-JavaScript, motion, and narrow reflow | Completed | Isolated local Chromium server and deterministic database |
Skip focus, native mobile navigation, capability details/filters, reduced motion, and 320 CSS-pixel document reflow. The automated set does not cover every browser, zoom level, or input method. | Website locked browser regression harness |
| Manual keyboard and zoom matrix | Pending | Manual environment required |
Current Chrome and Firefox on Windows, 200% text zoom, and 400% browser zoom across primary journeys. Do not infer completion from the automated 320px reflow check. | docs/accessibility-verification.md manual entry point |
| Manual website assistive-technology matrix | Pending | Windows, macOS/iOS, and Linux environments |
NVDA, JAWS, VoiceOver, and Orca representative journeys for the exact deployable revision. No formal website accessibility conformance claim is made. | docs/accessibility-verification.md Pending matrix |