Popular
- Manage License (Add on)
- Bulk Revoke
- Generating Access Code
- Direct Distribution (Add On)
- Creating Single User or Multiple Users (Bulk Upload)
- Admin Center and Profile and Settings
- Revoking Content
- Distributing Content
- Signing in to Kitaboo
- Promote User/Transfer
- Create Class/Update Class
- Selective Oneroster Sync with API/ZIP/SFTP
- Activated User – Definition & Billing Policy
- Understanding User Roles: Producer vs. Admin
- Auto Book Deletion Process
- Adding group with SAML
- Syncing Data with Clever
- Selective Oneroster Sync with API/ZIP/SFTP
- Syncing Data with PowerSchool
- Syncing Data with OneRoster
- Adding a Group
- Searching a Customer
- Issuing Licenses
- Editing a Customer
- Deactivating a Customer
- Adding a Google Classroom Customer
- Adding a OneRoster Customer
- Adding One roster 1.2
- Adding a LTI 1.3 Customer with OneRoster
- Adding a LTI 1.3 Customer
- Adding an LTI 1.1 Customer with OneRoster
- Adding LTI 1.1 Customers
- Sorting Customer and Group
- Enable K-AI at the content level
- Content Lifecycle Stages in Kitaboo for eBooks
- Creating a Fixed-layout Kitaboo eBooks
- Creating Fixed-layout ePub 3.0
- Upload 3rd Party ePub 2.0/3.0
- Creating a Course
- Activity or Gradable Activity Creation
- Authoring an ePub
- Creating a Video Book
- Creating an Audio Book
- Updating the Cover Image
- Editing a Fixed eBook
- Deleting and Deactivating Content
- Users Tab
- How to Edit and Delete a Category
- Clever Integration
- Classlink Integration
- Canvas LTI Integration
- Admin Center
- Analytics Tab
- Adding a Customer
- Creating Admin Accounts
WCAG compliance consists of two parts:
1) Reader Compliance
The default Kitaboo Reader is fully WCAG 2.2 compliant. It provides an accessible reading experience with:
-
Proper text and background color contrast.
-
Correct tabbing order for seamless navigation.
-
Keyboard accessibility, with shortcut keys for all major features.
-
Compatibility with leading screen readers such as JAWS and NVDA.
2) Content Compliance
While Kitaboo ensures reader-level compliance, publishers are responsible for ensuring that the input files meet WCAG content accessibility standards. This includes:
-
Correct font size and appropriate text/background color contrast.
-
Proper tagging of text for accessibility.
-
Logical reading order to ensure accurate interpretation by assistive technologies.
-
All images must include meaningful alternative text (alt text) to describe the content for non-visual users.
-
Audiobooks: A complete transcript must be uploaded.
-
Videobooks: Closed captions (CC) must be uploaded, and videos must have proper font size, with foreground and background color contrast compliant with WCAG 2.2 AA.
-
ePub: Must include correct font size, meaningful alt-text for images, and proper foreground/background color contrast as per WCAG 2.2 AA, along with proper structural tagging.