Design goals
Public pages should support keyboard navigation, visible focus states, readable contrast, responsive layouts, semantic headings and descriptive link text.
Accessibility Statement
AICardAPI aims to make public pages and developer documentation usable by people with a range of abilities and devices. Production conformance should be validated with audits and ongoing remediation.
Developer documentation
Docs should use structured navigation, copyable examples, readable code blocks and stable headings that assist screen-reader and keyboard workflows.
Known limitations
Some demo or internal routes may need further review before public launch. Browser screenshot QA and assistive-technology testing should be added to the release checklist.
Feedback
Accessibility feedback should be submitted through the published contact or support channel with the page URL, browser/device details and a description of the issue.
Ongoing improvement
AICardAPI should review accessibility during design changes, component updates and public documentation releases.