Accessibility is part of public-site quality and procurement readiness.
LionServe AI is committed to making the public website usable for people with disabilities and to treating accessibility as part of quality, governance, procurement readiness, and due diligence.
Access should be engineered into the experience.
The site is built with semantic headings, landmarks, keyboard-operable links and controls, focus states, and readable content hierarchy. That work should continue as pages, forms, and public documents expand.
Target standard
LionServe intends the public website to move toward WCAG 2.2 AA and Section 508-aligned accessibility through semantic structure, keyboard access, visible focus states, sufficient contrast, and plain interaction patterns.
Current conformance posture
The public site has been built with accessibility-aware components and spot-checked during development. It should be treated as not yet third-party audited until a formal accessibility audit or ACR/VPAT process is completed.
No overlay shortcut
Accessibility should be built into the site rather than outsourced to an overlay widget that masks structural issues without fixing them.
Forms and routing
Public forms should expose labels, required states, validation errors, status messages, and keyboard-operable controls so serious inquiries can be submitted without mouse-only dependence.
Documents and PDFs
Public documents should be reviewed for accessible structure before publication. If a document blocks access, LionServe will work to provide a reasonable alternative format when requested.
Ongoing review
Accessibility is treated as an operating discipline. Future pages should be reviewed during verification, not treated as a final polish pass.
Accessibility documentation should be available through the federal contact path.
For procurement inquiries, LionServe can discuss accessibility status, known limitations, alternative access needs, and future ACR/VPAT requirements through the appropriate contact channel.
- Accessibility-aware build; formal third-party audit not yet represented.
- Accessibility reports receive direct review and reasonable follow-up.
- June 2026
Accessibility issues should have a direct route.
If any public page, form, or document blocks access, report the issue with the page URL, assistive technology if relevant, and a concise description of the barrier. LionServe will make reasonable efforts to provide alternative access while the issue is reviewed.
Email: tre.smith@lionserve.ai