ClaruSigna aims to be a clear, readable, keyboard-friendly experience. This page describes the accessibility practices used on the site, known limitations, and how to request help.
Standards and Approach
The goal is to align with WCAG 2.2 Level AA where practical for a small, static informational site. Work is prioritized based on impact, clarity, and real user experience.
What’s Working Well
- Responsive layout that works across common device sizes
- Semantic HTML structure (headings, lists, landmarks)
- Readable typography and spacing
- Links and controls are standard HTML elements (better default accessibility)
Keyboard and Focus
You should be able to navigate the site with a keyboard. Primary expectation: visible focus indicators and predictable tab order.
- Use Tab to move forward through interactive elements
- Use Shift + Tab to move backward
- Use Enter or Space to activate buttons/links (depending on the control)
The Bot (Clarus)
The chatbot is provided via a modal dialog. It is intended to be usable with keyboard navigation and assistive technology.
Known limitations (still being improved):
- Focus trapping inside the modal may be incomplete depending on browser behavior
- Screen reader announcements for newly-added messages can be improved
- High-contrast needs vary by user; the site is continuously tuned based on Lighthouse/real feedback
Known Issues and Current Work
Accessibility is an ongoing effort. Current areas of focus include:
- Color contrast tuning for small text and muted UI elements
- Ensuring form inputs have explicit labels (not placeholder-only)
- Improving the bot experience for screen readers (live regions, focus behavior)
- Reducing motion and respecting
prefers-reduced-motion
Need Help or Want to Report an Issue?
If you run into an accessibility barrier, please reach out and include:
- The page URL
- What you were trying to do
- Your browser/device (if you know it)
- Assistive technology used (screen reader, keyboard-only, etc.)
Contact: howard@clarusigna.com
In Short
- This site is meant to be usable and readable by default
- Accessibility issues are treated as bugs
- If something blocks you, I want to know and fix it
Thanks for helping make ClaruSigna better.