Accessibility
Accessibility Statement
Effective date: June 3, 2026
1. Our Commitment to Inclusion
We believe digital experiences should be accessible to everyone. We are committed to ensuring our website, medical-education platforms, and SaaS products are designed and maintained to be accessible to people with diverse abilities — including healthcare professionals, researchers, and job candidates.
2. Standards and Conformance
Knightlabs targets WCAG 2.2 Level AA as our primary standard. Our efforts align with:
- Canada: the Accessibility for Ontarians with Disabilities Act (AODA).
- United States: Section 508 of the Rehabilitation Act and the Americans with Disabilities Act (ADA).
- Europe: the European Accessibility Act (EAA) and EN 301 549.
3. Accessibility in AI & SaaS
- AI content generation: interfaces use semantic HTML and ARIA so outputs are readable by assistive technologies.
- Data visualization: our Insights dashboards use high-contrast palettes and text alternatives for complex charts.
- Recruitment: AI-assisted hiring tools are tested for keyboard-only navigation.
4. What this site implements
Specific features we have built into knightlabs.net as of the effective date below:
Navigation & structure
- A “Skip to content” link is the first interactive element on every page, letting keyboard users jump past navigation.
- Each page uses a single
<main>landmark, a<nav>landmark labelled “Primary,” and a<footer>landmark — so screen readers can move by region. - The active nav link is exposed with
aria-current=“page”, so assistive tech announces it as “current page.” - Icon-only buttons (cookie banner, Blue assistant, social links) carry descriptive
aria-labels. - The Blue assistant panel is announced as a
dialogwith its own label.
Keyboard & focus
- Every interactive element shows a visible magenta focus ring (
:focus-visible) at 2 px width and 3 px offset, well above the 2 px WCAG minimum. - Tab order follows reading order; no element is reachable only via mouse.
Motion & animation
- All scroll-reveal animations, hover transforms, and the Blue panel slide-in honour the operating system’s Reduce motion setting. Both CSS-driven transitions and JavaScript-driven motion respect the preference.
Colour & contrast
- Body and secondary text are tuned so paragraph copy and labels meet WCAG 2.2 AA contrast (4.5 : 1) on white backgrounds.
- Headings and large display text meet the AAA threshold (7 : 1).
- The site does not communicate state through colour alone — focus, active, and error states also change shape, icon, or text.
Forms & controls
- Every form field has a visible
<label>associated byhtmlFor. - Required fields are marked both visually (with an asterisk) and programmatically (
required). - Cookie consent categories are operable with keyboard, with the “Necessary” category disabled and clearly labelled “Always on.”
Internationalisation
- The
<html lang>attribute is set for every page (English or French) so screen readers pronounce the content with the correct phonetic rules.
5. Ongoing Efforts and Testing
- We integrate accessibility audits into our software development lifecycle.
- We conduct regular automated and manual testing by accessibility experts.
- We provide accessibility training for our design and engineering teams in Toronto and Chicago.
6. Feedback and Support
We welcome your feedback. If you encounter any accessibility barriers or need a document in an alternative format, email noreply@klabs.net. We aim to acknowledge all accessibility-related inquiries within three business days.