Accessibility is not just a feature - it's a requirement for building a knowledge base that works for everyone. Document360 is compliant with WCAG 2.1 Level A and AA standards, ensuring that both the Knowledge base portal and the Knowledge base site are inclusive and usable by readers of all abilities.
Key principles of WCAG 2.1
WCAG 2.1 is organized around four core principles that guide the creation of accessible web content:
-
Perceivable — Information and interface components must be presented in ways users can perceive. This includes providing text alternatives for non-text content such as images and media.
-
Operable — Interface components and navigation must be operable by everyone. This means all functionality is available from a keyboard, users have enough time to read and interact with content, and clear navigation helps users find what they need.
-
Understandable — Information and interface behavior must be understandable. Text should be readable and comprehensible, and pages should operate in predictable ways.
-
Robust — Content must be robust enough to be reliably interpreted by a wide range of browsers and assistive technologies, both current and future.
For the full specification, read the WCAG 2.1 Guidelines published by the W3C.
How Document360 implements WCAG 2.1
Document360 supports WCAG 2.1 A and AA compliance through a combination of platform design, built-in features, and content authoring best practices. Here's what's built in:
| Feature | How it helps |
|---|---|
| Structured content and headings | Semantic heading levels help screen reader users navigate articles without reading every line. |
| Alt text for images | Every image in the editor supports an alt text field, ensuring non-visual readers receive the same information as sighted readers. |
| Keyboard-friendly navigation | All features on the Knowledge base site are accessible using only a keyboard — no mouse required. |
| Visible focus indicators | Buttons and links show a clear visual highlight during keyboard navigation so users always know where they are on the page. |
| Automatic color contrast | Custom themes include automatic color contrast adjustment to meet WCAG contrast requirements without manual checking. |
| Font size controls | Text size can be increased for better readability without breaking the page layout. |
| Mobile responsiveness | Content adapts correctly across screen sizes, from large monitors to mobile devices. |
| Skip to content links | Keyboard users can bypass repetitive header navigation and jump directly to the article content. |
Best practices for accessible content
Document360's platform handles the structural and technical side of accessibility, but the content you write matters just as much. A few practices that make a real difference:
- Use plain language. Avoid jargon and long, complex sentences. If a reader needs to re-read a sentence to understand it, simplify it.
- Write descriptive link text. "Learn more about configuring SSO" is far more useful than "click here" — especially for screen reader users who navigate by scanning a list of links.
- Use headings in order. Never skip heading levels (for example, going straight from H2 to H4). Screen readers use heading structure to navigate, and gaps break that flow.
- Always fill in alt text. Describe what the image shows, not what it is. "Settings panel with the Enable toggle highlighted" tells a reader something useful; "screenshot" does not.
- Don't rely on color alone. If color is being used to convey meaning — such as red for errors or green for success — also include a text label or icon so the information isn't lost for readers who can't distinguish colors.
For a deeper look at writing for accessibility, read the article on WCAG best practices for writers.