Accessibility Conformance Report
Last updated: July 8, 2026
Product Information
Product: Loxtep
Description: Loxtep is an agentic data platform that provides governed context, semantic layer, ontology, and MCP/SDK interfaces for AI agents. This report covers the Loxtep web application (app.loxtep.io), marketing website (loxtep.io), and customer-facing documentation.
Version evaluated: Current production release (July 2026)
Report date: July 8, 2026
VPAT format: VPAT 2.5
Contact: accessibility@loxtep.io
Related: Accessibility Statement
Evaluation Methods
- Automated accessibility testing with axe-core and Lighthouse during CI and release QA
- Manual keyboard-only navigation testing on primary user workflows
- Screen reader testing with NVDA (Windows), VoiceOver (macOS/iOS), and TalkBack (Android)
- Code review against WCAG 2.1 Level A and AA success criteria
- Color contrast analysis on core UI components and marketing pages
Applicable Standards
- Web Content Accessibility Guidelines (WCAG) 2.1
- Revised Section 508 standards — 2018 (Chapter 3: Functional Performance Criteria and Technical Requirements, WCAG 2.0 Level A and AA mapped via WCAG 2.1)
- EN 301 549 V3.2.1 (2021-03) — Clause 9 Web (WCAG 2.1 Level A and AA)
Terms
- Supports: The functionality of the product has at least one method that meets the criterion without known defects.
- Partially Supports: Some functionality meets the criterion, but exceptions exist.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion does not apply to the product.
Conformance Summary
- Supports: 30
- Partially Supports: 13
- Does Not Support: 0
- Not Applicable: 7
Loxtep is working toward substantial conformance with WCAG 2.1 Level AA. This report reflects good-faith evaluation of the current production release and will be updated with major releases or at least annually.
WCAG 2.1 Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1Non-text Content (Level A) | Partially Supports | Decorative images are marked appropriately on marketing pages. Complex data visualizations, process graphs, and diagram-heavy platform views do not always provide complete text alternatives or long descriptions. |
| 1.2.1Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | The product does not include prerecorded audio-only or video-only content as a core function. |
| 1.2.2Captions (Prerecorded) (Level A) | Not Applicable | The product does not include prerecorded synchronized media as a core function. |
| 1.2.3Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | The product does not include prerecorded synchronized media as a core function. |
| 1.3.1Info and Relationships (Level A) | Supports | Semantic HTML, headings, labels, and ARIA roles are used to convey structure in core workflows and marketing pages. |
| 1.3.2Meaningful Sequence (Level A) | Supports | DOM order generally matches the visual and logical reading order on tested pages. |
| 1.3.3Sensory Characteristics (Level A) | Supports | Instructions do not rely solely on shape, size, visual location, orientation, or sound. |
| 1.4.1Use of Color (Level A) | Supports | Color is not the only visual means of conveying information in core forms and status indicators. |
| 1.4.2Audio Control (Level A) | Not Applicable | The product does not auto-play audio content. |
| 2.1.1Keyboard (Level A) | Partially Supports | Primary navigation, forms, and modal dialogs are keyboard operable. Some complex canvas, graph, and drag-and-drop interactions have limited keyboard alternatives. |
| 2.1.2No Keyboard Trap (Level A) | Supports | Keyboard focus can be moved away from tested components using standard navigation keys. |
| 2.1.4Character Key Shortcuts (Level A) | Supports | Where single-character shortcuts exist, they can be turned off, remapped, or are active only when the relevant component has focus. |
| 2.2.1Timing Adjustable (Level A) | Supports | Session timeouts provide warning and extension options where applicable. |
| 2.2.2Pause, Stop, Hide (Level A) | Supports | Auto-updating content can be paused or stopped, or updates are user-initiated. |
| 2.3.1Three Flashes or Below Threshold (Level A) | Supports | Tested UI does not contain content that flashes more than three times per second. |
| 2.4.1Bypass Blocks (Level A) | Supports | Skip navigation links and landmark regions are available on marketing and application pages. |
| 2.4.2Page Titled (Level A) | Supports | Pages have descriptive title elements that identify topic or purpose. |
| 2.4.3Focus Order (Level A) | Partially Supports | Focus order is logical in most workflows. Some dynamically injected panels and multi-step wizards may receive focus in non-ideal order. |
| 2.4.4Link Purpose (In Context) (Level A) | Supports | Link text describes purpose in context on tested pages. |
| 2.5.1Pointer Gestures (Level A) | Partially Supports | Single-pointer alternatives exist for most actions. Multi-point or path-based gestures in graph views may not have single-pointer equivalents. |
| 2.5.2Pointer Cancellation (Level A) | Supports | Activation occurs on the up-event, or a mechanism exists to abort or undo the action. |
| 2.5.3Label in Name (Level A) | Supports | Visible labels are included in the accessible name for tested form controls and buttons. |
| 2.5.4Motion Actuation (Level A) | Not Applicable | Functionality is not triggered by device motion or user motion. |
| 3.1.1Language of Page (Level A) | Supports | The default human language of each page is programmatically determined. |
| 3.2.1On Focus (Level A) | Supports | Receiving focus does not initiate a change of context on tested components. |
| 3.2.2On Input (Level A) | Supports | Changing a setting does not automatically cause a change of context without user confirmation. |
| 3.3.1Error Identification (Level A) | Supports | Form input errors are identified and described to the user in text. |
| 3.3.2Labels or Instructions (Level A) | Supports | Labels or instructions are provided when user input is required. |
| 4.1.1Parsing (Level A) | Supports | Markup follows HTML specifications with no duplicate IDs or invalid nesting in tested pages. |
| 4.1.2Name, Role, Value (Level A) | Partially Supports | Standard controls expose name, role, and value. Some custom components (charts, code editors, complex tables) may not expose full state to assistive technology. |
WCAG 2.1 Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4Captions (Live) (Level AA) | Not Applicable | The product does not include live synchronized media as a core function. |
| 1.2.5Audio Description (Prerecorded) (Level AA) | Not Applicable | The product does not include prerecorded synchronized media as a core function. |
| 1.3.4Orientation (Level AA) | Supports | Content does not restrict view to a single display orientation. |
| 1.3.5Identify Input Purpose (Level AA) | Partially Supports | Autocomplete attributes are applied to common contact and account fields. Not all custom enterprise form fields include programmatic input purpose. |
| 1.4.3Contrast (Minimum) (Level AA) | Partially Supports | Core text and UI meet 4.5:1 contrast on marketing pages and primary application screens. Some disabled states, chart labels, and tertiary UI elements may fall below required ratios. |
| 1.4.4Resize Text (Level AA) | Supports | Text can be resized up to 200% without loss of content or functionality on tested pages. |
| 1.4.5Images of Text (Level AA) | Supports | Text is used in place of images of text except for logos and essential branding. |
| 1.4.10Reflow (Level AA) | Partially Supports | Marketing and most application layouts reflow at 320px width. Some data-dense tables and graph canvases require horizontal scrolling. |
| 1.4.11Non-text Contrast (Level AA) | Partially Supports | Interactive controls and focus indicators generally meet 3:1 contrast. Some chart series, graph nodes, and inactive UI affordances may not. |
| 1.4.12Text Spacing (Level AA) | Supports | Content remains usable when user-defined text spacing is applied per WCAG requirements. |
| 1.4.13Content on Hover or Focus (Level AA) | Partially Supports | Most tooltips and popovers are dismissible and hoverable. Some data-preview overlays in platform views may not meet all hover/focus persistence requirements. |
| 2.4.5Multiple Ways (Level AA) | Supports | Users can reach content through navigation, search, and sitemap-style links where applicable. |
| 2.4.6Headings and Labels (Level AA) | Supports | Headings and labels describe topic or purpose on tested pages. |
| 2.4.7Focus Visible (Level AA) | Supports | Keyboard focus indicators are visible on interactive elements in core workflows. |
| 3.1.2Language of Parts (Level AA) | Supports | Passages in a different language are programmatically identified where they appear in tested content. |
| 3.2.3Consistent Navigation (Level AA) | Supports | Navigation mechanisms are repeated in a consistent order across pages within each site area. |
| 3.2.4Consistent Identification (Level AA) | Supports | Components with the same functionality are identified consistently across the product. |
| 3.3.3Error Suggestion (Level AA) | Partially Supports | Common form errors include suggestions for correction. Some complex configuration errors may describe the failure without a specific remediation hint. |
| 3.3.4Error Prevention (Legal, Financial, Data) (Level AA) | Partially Supports | Destructive and data-modifying actions in critical workflows support confirmation. Not all administrative operations include review-and-confirm steps. |
| 4.1.3Status Messages (Level AA) | Partially Supports | Toast notifications and inline success messages are announced in many flows. Some background job status updates are visual only. |
Legal Disclaimer
This report is provided for informational purposes to support procurement and accessibility reviews, including HECVAT assessments. It is based on internal and targeted third-party evaluation as of the report date. Conformance may vary by product version, configuration, and customer-specific customizations. For questions or to request this report in an alternate format, contact accessibility@loxtep.io.