Accessibility
Accessibility is a right, not a feature.
Approximately 25% of adults in the United States live with a disability. Every Lonia AI product is built to work for all of them — from the first line of code.
Our Commitment
Lonia AI is committed to ensuring that all of our products and digital properties are accessible to people with disabilities. We target WCAG 2.2 Level AA conformance and Section 508 compliance as minimum standards, not aspirational goals.
Accessibility at Lonia AI is not a retrofit. It is not a checkbox exercise performed after launch. It is a foundational architectural requirement that shapes every product from the earliest design decisions through development, testing, and deployment. We build accessibility in because it is the right thing to do, because it is increasingly the legal requirement, and because it produces better products for everyone.
Standards We Follow
We do not reference vague commitments to "accessibility best practices." We name the specific standards we follow and hold ourselves accountable to them.
WCAG 2.2 Level AA
The Web Content Accessibility Guidelines (WCAG) 2.2 Level AA is the internationally recognized standard for web accessibility. We design and develop all products to meet or exceed these criteria across all four principles: Perceivable, Operable, Understandable, and Robust.
Section 508
Section 508 of the Rehabilitation Act requires federal agencies and their contractors to make electronic and information technology accessible. Lonia products meet Section 508 requirements, making them suitable for government procurement and use.
How We Build Accessible Products
Accessibility is woven into our development process at every stage. Here are the specific practices we follow.
Semantic HTML and Structure
- Proper heading hierarchy (single H1, logical H2/H3 nesting) on every page
- Semantic landmark elements (nav, main, article, section, header, footer)
- ARIA labels and roles where semantic HTML alone is insufficient
- Descriptive alt text on all images (decorative images marked with empty alt)
- Proper form labels associated with their inputs
Keyboard and Navigation
- Full keyboard navigation for all interactive elements
- Visible focus indicators (3px solid outline) on all focusable elements
- Skip-to-content links on every page
- Logical tab order matching visual reading order
- No keyboard traps — users can always navigate away from any element
Visual and Display
- Sufficient color contrast ratios meeting WCAG 2.2 AA minimums (4.5:1 for normal text, 3:1 for large text)
- Information never conveyed by color alone
- Responsive design that works across screen sizes and zoom levels up to 200%
- Support for prefers-reduced-motion — all animations and transitions disabled when requested
- Dark color scheme designed for comfortable extended use
Assistive Technology
- Tested with screen readers including NVDA, JAWS, and VoiceOver
- Compatible with screen magnification software
- Designed to work with braille displays
- Voice control compatible
- High contrast mode support
How We Test
Automated testing catches approximately 30-40% of accessibility issues. We supplement automated testing with manual review and assistive technology testing.
Automated Scanning
Axe-core and Lighthouse audits run during development and as part of our build pipeline. These catch structural issues like missing labels, low contrast, and invalid ARIA.
Manual Review
Every page and feature is manually reviewed for keyboard accessibility, logical reading order, and screen reader compatibility before release.
Assistive Technology
We test with real assistive technology — screen readers, keyboard-only navigation, and magnification — not just automated tools that simulate them.
Report an Accessibility Issue
We take accessibility issues seriously. If you encounter any barrier while using our products or this website, we want to know about it immediately. Accessibility issues receive priority handling.
Email support@lonia.ai with "Accessibility" in the subject line.
When reporting an accessibility issue, it helps us if you include:
- The product or page where you encountered the issue
- What you were trying to do
- What happened instead
- The assistive technology you were using (if applicable)
- Your browser and operating system
We will acknowledge your report within two business days and work to resolve the issue as quickly as possible.