> ## Documentation Index
> Fetch the complete documentation index at: https://docs.praxis-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# WCAG Compliance

> Web Content Accessibility Guidelines (WCAG) 2.0/2.1 Level A & AA Conformance.

## Overview

Praxis AI's "Pria" Generative AI Digital Twin is designed with accessibility at its core, ensuring all users can effectively interact with educational and professional assistance features. Our platform conforms to WCAG 2.0 and 2.1 Level A and Level AA standards.

**Product Evaluated:** Pria Generative AI Digital Twin\
**Evaluation Date:** September 1, 2025\
**Contact:** David James Clarke IV ([humans@praxis-ai.com](mailto:humans@praxis-ai.com))

## Conformance Levels

Our evaluation uses the following conformance terminology:

* **Supports** - The functionality meets the criterion without known defects
* **Partially Supports** - Some functionality does not meet the criterion
* **Does Not Support** - The majority of functionality does not meet the criterion
* **Not Applicable** - The criterion is not relevant to the product
* **Not Evaluated** - The criterion has not been evaluated

## WCAG 2.0/2.1 Level A Compliance

### Perceivable

**1.1.1 Non-text Content** - **Supports**\
All non-text content including images and icons includes descriptive alt text and ARIA labels.

**1.2.1-1.2.3 Audio and Video Content** - **Not Applicable**\
No prerecorded audio-only or video-only content is present.

**1.3.1 Info and Relationships** - **Supports**\
Information structure and relationships are programmatically determinable.

**1.3.2 Meaningful Sequence** - **Supports**\
Content is presented in a meaningful sequence that preserves meaning.

**1.3.3 Sensory Characteristics** - **Supports**\
Instructions do not rely solely on sensory characteristics.

**1.4.1 Use of Color** - **Supports**\
Color is not used as the only visual means of conveying information.

**1.4.2 Audio Control** - **Not Applicable**\
No audio plays automatically.

### Operable

**2.1.1 Keyboard** - **Supports**\
All functionality is available via keyboard interface.

**2.1.2 No Keyboard Trap** - **Supports**\
Keyboard focus can be moved away from any component using standard methods.

**2.1.4 Character Key Shortcuts** - **Supports**\
Character key shortcuts can be turned off or remapped.

**2.2.1 Timing Adjustable** - **Not Applicable**\
No time limits are set on content.

**2.2.2 Pause, Stop, Hide** - **Not Applicable**\
No auto-updating content is present.

**2.3.1 Three Flashes or Below Threshold** - **Not Applicable**\
No content flashes more than three times per second.

**2.4.1 Bypass Blocks** - **Supports**\
Mechanisms are available to bypass repeated blocks of content.

**2.4.2 Page Titled** - **Supports**\
Web pages have descriptive titles.

**2.4.3 Focus Order** - **Supports**\
Focusable components receive focus in an order that preserves meaning.

**2.4.4 Link Purpose (In Context)** - **Supports**\
The purpose of each link is determined from link text or context, enhanced with icons.

### Input Modalities (WCAG 2.1)

**2.5.1 Pointer Gestures** - **Supports**\
All functionality using multipoint or path-based gestures can be operated with a single pointer.

**2.5.2 Pointer Cancellation** - **Supports**\
Functions triggered by single-pointer activation can be cancelled.

**2.5.3 Label in Name** - **Supports**\
User interface components with text labels include the label text in the accessible name.

**2.5.4 Motion Actuation** - **Supports**\
Functionality triggered by device motion can be disabled and operated through user interface components.

## WCAG 2.0/2.1 Level AA Compliance

### Perceivable

**1.4.3 Contrast (Minimum)** - **Supports**\
Text and images of text have a contrast ratio of at least 4.5:1.

**1.4.4 Resize Text** - **Supports**\
Text can be resized up to 200% without loss of content or functionality.

**1.4.5 Images of Text** - **Supports**\
Text is used rather than images of text where possible.

**1.4.10 Reflow (WCAG 2.1)** - **Supports**\
Content reflows to a single column without horizontal scrolling at 320 CSS pixels width.

**1.4.11 Non-text Contrast (WCAG 2.1)** - **Supports**\
User interface components and graphical objects have a contrast ratio of at least 3:1.

**1.4.12 Text Spacing (WCAG 2.1)** - **Supports**\
No loss of content or functionality occurs when users adjust text spacing properties.

**1.4.13 Content on Hover or Focus (WCAG 2.1)** - **Supports**\
Additional content triggered by hover or focus is dismissible, hoverable, and persistent.

### Operable

**2.4.5 Multiple Ways** - **Supports**\
Multiple ways are available to locate web pages within the platform.

**2.4.6 Headings and Labels** - **Supports**\
Headings and labels describe topic or purpose, with all input elements having associated labels.

**2.4.7 Focus Visible** - **Supports**\
Keyboard focus is consistently visible throughout the interface.

### Understandable

**3.1.2 Language of Parts** - **Not Applicable**\
Language of passages cannot be programmatically determined.

**3.2.3 Consistent Navigation** - **Supports**\
Navigation mechanisms appear in the same relative order across pages.

**3.2.4 Consistent Identification** - **Supports**\
Components with the same functionality are identified consistently.

**3.3.3 Error Suggestion** - **Supports**\
When input errors are detected, suggestions for correction are provided.

**3.3.4 Error Prevention (Legal, Financial, Data)** - **Supports**\
Mechanisms for reviewing, confirming, and correcting information are provided before finalizing submissions.

### Robust

**4.1.3 Status Messages (WCAG 2.1)** - **Supports**\
Status messages are programmatically determined and presented to assistive technologies without receiving focus.

## Testing Methodology

Our accessibility evaluation employed:

* **Manual Testing** - Expert review of interface components and interactions
* **Automated Testing** - Scanning tools to identify common accessibility issues
* **Assistive Technology Testing** - Verification with screen readers and other assistive technologies

## Technical Implementation

Pria is built using HTML5 and follows modern web standards to ensure:

* Semantic HTML structure
* ARIA labels and roles where appropriate
* Keyboard navigation support
* Responsive design that adapts to different screen sizes and zoom levels
* Clear focus indicators
* Descriptive text alternatives for non-text content

## Resources

* [WCAG 2.0 Guidelines](https://www.w3.org/TR/WCAG20/)
* [WCAG 2.1 Guidelines](https://www.w3.org/TR/WCAG21/)
* [Understanding WCAG 2.1](https://www.w3.org/WAI/WCAG21/Understanding/)

## Contact

For questions about accessibility or to report accessibility issues:

**David James Clarke IV**\
Email: [humans@praxis-ai.com](mailto:humans@praxis-ai.com)

***

*Last Updated: September 1, 2025*