Skip to content
KnowledgeCity
Legal

Accessibility Statement

Last updated: January 2026

Our commitment

KnowledgeCity is committed to making our platform and digital content accessible to as many people as possible, regardless of ability or assistive technology. Accessible design is part of how we build — not an afterthought.

We aim to provide an equivalent experience to all users, including those who:

  • Use screen readers or other assistive technology
  • Navigate by keyboard
  • Need higher contrast, larger text, or reduced motion
  • Have temporary or situational limitations (e.g., a broken mouse, a noisy environment, bright sunlight)

Standards we follow

We design and build to meet Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities.

This includes practices such as:

  • Sufficient color contrast for text and meaningful UI elements
  • Keyboard operability for all interactive features
  • Programmatic labels for form fields, buttons, and navigation
  • Visible focus indicators
  • Captions for prerecorded video, and transcripts where appropriate
  • Responsive layouts that work at zoom levels up to 200%
  • Avoiding reliance on color, motion, or sound as the only means of conveying information

Scope

This statement applies to:

  • www.knowledgecity.com — our public marketing site
  • The KnowledgeCity Learner Portal — where end users take courses
  • The KnowledgeCity LMS Admin panel — where admins manage learners, content, and reporting

Third-party content embedded in our platform (such as videos hosted outside our infrastructure, or content provided by clients) may not meet the same standards. Where this is the case, we work with partners to improve accessibility over time.

Known limitations

We are continuously improving and disclose known limitations transparently. We will list specific limitations here after each formal audit.

Assessment approach

Our accessibility approach combines:

  • Automated scanning during build (e.g., axe, Lighthouse)
  • Manual testing with screen readers (NVDA, VoiceOver) and keyboard-only navigation
  • Periodic third-party accessibility audits
  • Feedback from users — see "Reporting an issue" below

Reporting an issue

If you encounter an accessibility barrier — anything that prevents you from accessing content or functionality — please contact us. We treat accessibility reports as priority issues.

We aim to acknowledge accessibility reports within two business days and to share a target resolution timeline within five business days.

Formal complaints

If you are not satisfied with our response, you may file a complaint with the appropriate regulatory authority in your jurisdiction. In the United States, you may contact the U.S. Department of Justice Civil Rights Division. In the European Union, you may contact your national accessibility or equality body.

Updates to this statement

We review this statement at least annually and update it after significant changes to our platform or after each formal accessibility audit. The "Last updated" date above reflects the most recent revision.