Web Content Accessibility Guidelines (WCAG)

Prev Next

Plans supporting WCAG

Professional
Business
Enterprise






In the digital age, accessibility is not just a feature but a necessity. Ensuring that all users, regardless of their abilities, can access and use our products is a cornerstone of inclusive design. Document360 is compliant with WCAG 2.1 A and AA standards, reinforcing our commitment to accessibility and inclusivity.

For Your Information

This WCAG is available exclusively in KB Site 2.0, which is accessible for projects created after June 10th, 2024.


Implementing WCAG 2.1 A and AA in Document360

At Document360, we have aligned Document360 with WCAG 2.1 A and AA guidelines to ensure our knowledge base software is accessible to everyone. Here’s how we’ve achieved this:

  1. Text alternatives: We provide text alternatives for all non-text content, such as images and icons, ensuring that screen readers can convey the information to all users.

  2. Keyboard navigation: Document360 supports full keyboard navigation, enabling users to access all features and functions without using mouse.

  3. Readable text: We ensure that all text content is readable and understandable, using clear fonts, appropriate contrast ratios, and simple language to enhance readability.

WCAG 2.1


Key Principles of WCAG 2.1

WCAG 2.1 is organized around four core principles that guide the creation of accessible content:

  1. Perceivable: Information and user interface components must be presented to users in ways they can perceive. This includes providing text alternatives for non-text content.

  2. Operable: Interface components and navigation must be easy to use, which includes making all functionality available from a keyboard, giving users enough time to read and use content, and providing ways to help users navigate and find content easily

  3. Understandable: Information and the operation of the user interface must be understandable. This involves making text readable and comprehensible, ensuring web pages operate predictably.

  4. Robust: Content must be robust enough to be interpreted reliably by a wide range of user agents, including assistive technologies. This ensures compatibility with current and future technologies.

NOTE

For more information, read the WCAG 2.0 Guidelines.