WCAG Edition (Based on VPAT® Version 2.5 Rev)

LEVO Accessibility Conformance Report

Levo is committed to building technology that is accessible to everyone, including people with disabilities, and to helping our customers meet global accessibility requirements.

‍Levo Accessibility Conformance Reports (ACRs) describe how the Levo.ai platform supports recognized international accessibility standards, including the Web Content Accessibility Guidelines (WCAG) 2.0, 2.1, 2.2, US Section 508, ETSI EN 301 549 and other applicable accessibility regulations.

More about ARCs

Product Information

Name of Product / Version: Levo.ai Platform v1.2.757
Report Date: December 17, 2025

Product Description:
Levo.ai is a runtime security platform that unifies API and AI security for modern, cloud-native applications. It provides deep visibility and proactive protection across the technology stack, enabling enterprises to innovate rapidly without compromising security.

‍

Accessibility Policy Statement

Levo.ai is committed to providing an accessible user experience for all users, including individuals with disabilities. Levo’s policy is to remediate accessibility issues as soon as they are identified, particularly issues that represent failures of WCAG success criteria or that create barriers to accessing content or functionality.

Accessibility issues that do not result in blocked content are documented and addressed during regular maintenance cycles. Priority is given to issues that impact core workflows or essential user interactions.

‍

Contact Information

For accessibility related questions or feedback, please contact: support@levo.ai

‍

Notes on Evaluation Scope

  • This application is a web based software platform accessed via modern web browsers.
  • Testing was conducted using the latest versions of Chrome, Firefox, Safari, and Microsoft Edge.
  • Interaction methods include keyboard and mouse input.
  • No additional hardware is required. Users may access the platform with assistive technologies supported by modern browsers (for example, screen readers, screen magnifiers, or alternative input devices).
  • Evaluation focuses on the frontend user experience only.
  • The platform does not include audio only, video only, or multimedia content as part of its core user experience.

‍

Evaluation Methods Used

Levo.ai follows an accessibility-by-design approach across its product lifecycle.

Evaluation methods include:

‍

  • Internal accessibility testing conducted annually using standardized accessibility checklists aligned with WCAG success criteria
  • Keyboard-only navigation testing
  • Screen reader compatibility checks during feature development
  • Manual inspection of semantic structure, labels, focus order, and contrast
  • Accessibility considerations during design and development of new UI components
  • Ongoing review of customer and user feedback related to accessibility

‍

Results in this report are assessed against WCAG 2.0, 2.1, and 2.2 Level A and Level AA success criteria. Where required, these results are also mapped to the applicable requirements of the US Revised Section 508 Standards and ETSI EN 301 549.

‍

Any accessibility feedback received from customers is reviewed, evaluated, and incorporated into future product improvements where applicable.

‍

Applicable Standards and Guidelines

Standard / Guideline Level Included
WCAG 2.0 Level A, Level AA
WCAG 2.1 Level A, Level AA
WCAG 2.2 Level A, Level AA
WCAG Level AAA Not Evaluated

‍

Conformance Terminology

  • Supports: The product meets the criterion without known accessibility barriers.
  • Partially Supports: Some functionality does not fully meet the criterion.
  • Does Not Support: Most functionality does not meet the criterion.
  • Not Applicable: The criterion does not apply to the product.
  • Not Evaluated: Used only for WCAG Level AAA criteria.

‍

WCAG 2.2 Conformance Report

All success criteria are evaluated in accordance with WCAG 2.2 conformance requirements, including full pages, complete processes, and accessibility-supported technologies.

‍

Table 1: Success Criteria – Level A

Criteria Conformance Level Remarks
1.1.1 Non-text Content Partially Supports Most images include descriptive alternative text. Form buttons and inputs provide accessible labels. Minor improvements are in progress for a small number of decorative or contextual images.
1.2.1 Audio-only and Video-only (Prerecorded) Not Applicable The platform does not include audio-only or video-only content.
1.2.2 Captions (Prerecorded) Not Applicable No prerecorded video or audio content is present.
1.2.3 Audio Description or Media Alternative (Prerecorded) Not Applicable No prerecorded multimedia content is present.
1.3.1 Info and Relationships Partially Supports Semantic structure is largely implemented. Some UI components require additional enhancements to improve compatibility with assistive technologies.
1.3.2 Meaningful Sequence Supports Content order is logical and preserved programmatically.
1.3.3 Sensory Characteristics Supports Instructions do not rely solely on shape, color, or location.
1.4.1 Use of Color Supports Color is not used as the sole means of conveying information.
1.4.2 Audio Control Not Applicable No audio content is present.
2.1.1 Keyboard Supports All interactive functionality is operable using a keyboard interface.
2.1.2 No Keyboard Trap Supports No keyboard traps are present.
2.1.4 Character Key Shortcuts Not Applicable No single-character keyboard shortcuts are implemented.
2.2.1 Timing Adjustable Not Applicable No time-based content or time limits are present.
2.2.2 Pause, Stop, Hide Not Applicable No moving, blinking, or auto-updating content is present.
2.3.1 Three Flashes or Below Threshold Not Applicable No flashing content is present.
2.4.1 Bypass Blocks Supports Headings and landmarks enable users to bypass repeated content.
2.4.2 Page Titled Supports Pages include descriptive and meaningful titles.
2.4.3 Focus Order Supports Keyboard focus order follows a logical and predictable sequence.
2.4.4 Link Purpose (In Context) Supports Link text clearly conveys purpose.
2.5.1 Pointer Gestures Supports All functionality operates without multipoint or path-based gestures.
2.5.2 Pointer Cancellation Supports Standard browser interactions are preserved.
2.5.3 Label in Name Supports Accessible names include the visible label text.
2.5.4 Motion Actuation Supports No functionality is triggered by device motion.
3.1.1 Language of Page Supports Page language is programmatically defined using the HTML lang attribute.
3.2.1 On Focus Supports Focus does not trigger unexpected context changes.
3.2.2 On Input Supports Input does not cause automatic context changes.
3.2.6 Consistent Help (2.2) Supports Help mechanisms and error guidance are presented consistently.
3.3.1 Error Identification Supports Errors are clearly identified and communicated to users.
3.3.2 Labels or Instructions Supports Form controls include clear labels or instructions.
3.3.7 Redundant Entry (2.2) Supports Users are not required to re-enter previously provided information unnecessarily.
4.1.1 Parsing Supports WCAG 2.0 and 2.1 parsing requirements are met. This criterion is obsolete in WCAG 2.2.
4.1.2 Name, Role, Value Supports UI components expose appropriate name, role, and value information to assistive technologies.

‍

Table 2: Success Criteria – Level AA

Criteria Conformance Level Remarks
1.2.4 Captions (Live) Not Applicable No live audio content is present.
1.2.5 Audio Description (Prerecorded) Not Applicable No prerecorded multimedia content is present.
1.3.4 Orientation Supports Content functions in both portrait and landscape orientations.
1.3.5 Identify Input Purpose Supports Input fields use appropriate autocomplete attributes where applicable.
1.4.3 Contrast (Minimum) Supports Text and interactive elements meet minimum contrast requirements.
1.4.4 Resize Text Partially Supports Text can be resized using browser zoom without loss of content or functionality. No custom text resizing controls are provided.
1.4.5 Images of Text Not Applicable Images of text are not used.
1.4.10 Reflow Supports Content reflows appropriately without horizontal scrolling.
1.4.11 Non-text Contrast Supports Icons and UI controls maintain sufficient contrast.
1.4.12 Text Spacing Supports Text spacing adjustments do not cause loss of content or functionality.
1.4.13 Content on Hover or Focus Supports Hover and focus content remains visible until dismissed by the user.
2.4.5 Multiple Ways Supports Users can locate content through navigation menus and search.
2.4.6 Headings and Labels Supports Headings and labels are descriptive and organized logically.
2.4.7 Focus Visible Supports Keyboard focus is visually apparent.
2.4.11 Focus Not Obscured (2.2) Supports Focused elements are not hidden by other content.
2.5.7 Dragging Movements (2.2) Not Applicable Dragging gestures are not required.
2.5.8 Target Size (2.2) Supports Pointer targets meet minimum size requirements or include sufficient spacing.
3.1.2 Language of Parts Not Applicable Content is presented in a single language (en-US).
3.2.3 Consistent Navigation Supports Navigation remains consistent across pages.
3.2.4 Consistent Identification Supports Components with the same functionality are consistently identified.
3.3.3 Error Suggestion Supports Error correction suggestions are provided where applicable.
3.3.4 Error Prevention Not Applicable No legal, financial, or irreversible transactions are present.
3.3.8 Accessible Authentication (2.2) Supports Password managers and copy/paste are supported. Single sign-on is available.
4.1.3 Status Messages Not Applicable No dynamic status messages requiring programmatic announcement are present.

‍

Level AAA

Level AAA success criteria are outside the scope of this evaluation.

‍

Legal Disclaimer

This Accessibility Conformance Report represents a good-faith voluntary assessment of the Levo.ai platform’s conformance with the Web Content Accessibility Guidelines (WCAG) as of the report date. The information provided is for informational purposes only and does not constitute a warranty or guarantee of compliance. Levo.ai assumes no legal liability for errors or omissions in this report.

‍

‍

Understanding ACRs

Learn more about Accessibility Conformance Reports (ACRs), the accessibility standards Levo uses when developing the Levo.ai platform, and how conformance with standards is assessed.

‍

What is an Accessibility Conformance Report?

Levo Accessibility Conformance Reports (ACRs) document the degree of conformance of the Levo.ai platform to recognized accessibility standards. Levo uses the Voluntary Product Accessibility Template (VPAT), a widely adopted template developed by the Information Technology Industry Council (ITI), to prepare most new reports. Any exceptions identified during evaluation are documented, and explanatory remarks are provided to describe the impact, scope, and remediation approach.

‍

Which accessibility standards are used to assess products and services?

Levo assesses the Levo.ai platform using the accessibility standards below, as applicable based on product scope and customer requirements:

  • ‍Web Content Accessibility Guidelines (WCAG) are internationally adopted technical standards for making web content accessible. Each guideline includes testable success criteria. Levo assesses the platform against WCAG Level A and Level AA criteria. WCAG is developed and maintained by the World Wide Web Consortium (W3C), an international organization for the development of web standards.‍
  • US Section 508 requirements support accessibility for individuals with disabilities in Information and Communication Technology (ICT) procured and used by US federal agencies. The Section 508 standards and guidance are maintained by the US Access Board and include scoping and technical requirements that help agencies develop, procure, maintain, and use accessible ICT.‍
  • ETSI EN 301 549 is a European-developed accessibility standard for ICT products and services created by European Standards Organizations, including CEN, CENELEC, and ETSI. The standard incorporates WCAG requirements for web accessibility and is commonly used in public procurement across the European Union and in other jurisdictions.

‍

How does Levo evaluate the accessibility of its products and services?

Levo evaluates accessibility through a combination of automated testing and manual review. Testing commonly includes keyboard-only navigation, focus visibility and order checks, semantic structure validation, labels and accessible-name review, color contrast verification, and testing with assistive technologies (for example, screen readers) where appropriate. Findings are documented in the ACR and prioritized for remediation based on user impact and severity.