This article clarifies which WCAG 2.0 accessibility requirements are handled through Helpjuice's frontend implementation and which are the responsibility of content authors.

Understanding these distinctions will help you determine what accessibility changes to request from Helpjuice support versus what elements you must manage through your content creation process.

As the frontend of the Knowledge Bases are built on top of the requirements submitted through a Customization Request, the responsibility of making sure the topics cover WCAG 2 requirements are from the requester of the Customization Request.

Principle 1: Perceivable

1.1 Text Alternatives

Helpjuice Implementation:

• Built-in alt text fields in the content editor
• System-generated images (icons, UI elements) have appropriate alt text

Content Author Responsibility:

• Providing meaningful alt text for all images in knowledge base articles
• Creating descriptive text alternatives for charts, diagrams, and other visual content
• Ensuring complex images have extended descriptions when needed

1.2 Time-based Media

Helpjuice Implementation:

• Video player with caption support
• Support for embedding accessible media players

Content Author Responsibility:

• Creating or obtaining captions for videos
• Providing transcripts for audio content
• Ensuring audio descriptions are available for video when needed
• Creating text alternatives that serve the same purpose as time-based media

1.3 Adaptable

Helpjuice Implementation:

• Responsive layout that adapts to different screen sizes
• Semantic HTML structure for platform components
• Proper reading sequence in the platform's HTML

Content Author Responsibility:

• Using proper heading hierarchy (H1, H2, H3, etc.) in content
• Creating properly structured tables with headers
• Not relying solely on visual formatting to convey meaning
• Ensuring content makes sense in a linear reading order

1.4 Distinguishable

Helpjuice Implementation:

• Platform-wide color contrast compliance
• Resizable text without loss of content or functionality
• No automatic audio playback in the platform itself

Content Author Responsibility:

• Ensuring sufficient color contrast in custom content (e.g., colored text)
• Not using color alone to convey meaning
• Checking that text over background images is readable
• Controlling audio in embedded media

Principle 2: Operable

2.1 Keyboard Accessible

Helpjuice Implementation:

• All platform functionality available via keyboard
• No keyboard traps in the interface
• Keyboard shortcuts (if available) can be modified

Content Author Responsibility:

• Ensuring custom interactive elements in content are keyboard accessible
• Testing embedded tools or applications for keyboard accessibility

2.2 Enough Time

Helpjuice Implementation:

• Session timeout warnings
• No timing-based content restrictions in the platform

Content Author Responsibility:

• Avoiding time-limited content unless absolutely necessary
• Providing options to extend time limits in custom interactive content

2.3 Seizures and Physical Reactions

Helpjuice Implementation:

• No flashing content in the platform interface

Content Author Responsibility:

• Not including content that flashes more than three times per second
• Avoiding content with rapid flashing animations or transitions
• Ensuring embedded videos don't contain seizure-inducing content

2.4 Navigable

Helpjuice Implementation:

• Consistent navigation structure
• "Skip to content" links
• Descriptive page titles
• Focus indicators
• Breadcrumb navigation options

Content Author Responsibility:

• Writing descriptive, unique headings for content sections
• Creating meaningful link text (avoiding "click here" or "read more")
• Adding anchor links for long content pages
• Creating logical content organization

2.5 Input Modalities

Helpjuice Implementation:

• Support for various input devices
• Properly sized touch targets
• Gesture alternatives

Content Author Responsibility:

• Ensuring custom interactive elements don't require complex gestures
• Providing alternatives for motion-activated features in content

Principle 3: Understandable

3.1 Readable

Helpjuice Implementation:

• Language detection and language attributes in HTML
• Support for specifying content language

Content Author Responsibility:

• Writing in clear, concise language
• Defining unusual terms and abbreviations
• Avoiding or explaining jargon
• Indicating language changes within content
• Using appropriate reading level for your audience

3.2 Predictable

Helpjuice Implementation:

• Consistent navigation and layout
• No unexpected changes when elements receive focus
• Consistent identification of components

Content Author Responsibility:

• Using consistent formatting throughout content
• Avoiding unexpected changes in context based on user input
• Being consistent in terminology and labeling

3.3 Input Assistance

Helpjuice Implementation:

• Error identification in forms
• Labels and instructions for input fields
• Error prevention for important transactions

Content Author Responsibility:

• Providing clear instructions for interactive content
• Ensuring forms embedded in content have proper error handling
• Including help text for complex interactions

Principle 4: Robust

4.1 Compatible

Helpjuice Implementation:

• Valid HTML throughout the platform
• Complete start and end tags
• Proper parent-child relationships in HTML
• ARIA implementation where appropriate

Content Author Responsibility:

• Ensuring custom HTML in content is valid
• Testing embedded applications for compatibility with assistive technologies
• Not breaking the underlying platform HTML structure

Requesting Accessibility Changes

Changes to Request from Helpjuice

• Platform-level accessibility improvements (frontend)
• Navigation structure modifications
• Form accessibility enhancements
• Color contrast issues in the default interface (frontend)
• Keyboard navigation problems
• Screen reader compatibility for system elements

Changes You Need to Handle Internally

• Alt text for content images
• Caption and transcript creation
• Content structure and heading hierarchy
• Link text quality
• Content readability and language
• Accessibility of embedded media and interactive elements