Supports

The functionality of the product meets the criterion without known defects.

Partially Supports

Some functionality meets the criterion; known defects or gaps exist.

Does Not Support

The majority of product functionality does not meet the criterion.

Not Applicable

The criterion is not relevant to this product.

1.1.1 Non-text Content (A)

Partially Supports

Platform UI elements (buttons, icons, navigation) include ARIA labels and descriptive alt text. Images inserted into booklets by content authors rely on the author providing alt text; the platform provides the field and prompts for it but cannot enforce completion for user-generated content.

1.2.1 Audio-only and Video-only (A)

Partially Supports

The platform does not itself produce audio-only or video-only content. For media embedded by users, the platform does not auto-generate transcripts or audio descriptions; content authors are responsible for supplying alternatives.

1.2.2 Captions (Prerecorded) (A)

Partially Supports

Simplebooklet supports embedding videos from third-party sources (e.g. YouTube, Vimeo). Caption availability depends on the embedded source or the content author enabling them. The platform does not auto-generate captions.

1.2.3 Audio Description or Media Alternative (Prerecorded) (A)

Not Applicable

Simplebooklet does not produce synchronized media. Embedded video is user-sourced from third-party platforms.

1.2.4 Captions (Live) (AA)

Not Applicable

Simplebooklet does not offer live audio or video streaming.

1.2.5 Audio Description (Prerecorded) (AA)

Not Applicable

Simplebooklet does not produce or host synchronized media requiring audio descriptions.

1.3.1 Info and Relationships (A)

Supports

The editor and viewer use semantic HTML with appropriate heading hierarchy, landmark roles (main, nav, header, footer), and ARIA attributes to convey structure and relationships programmatically.

1.3.2 Meaningful Sequence (A)

Supports

Content is presented in a logical reading order in the DOM that matches the visual layout. Booklet page navigation follows a predictable sequence.

1.3.3 Sensory Characteristics (A)

Supports

Instructions and interface controls do not rely solely on sensory characteristics (shape, color, size, position). Buttons and controls include visible text labels or accessible names.

1.3.4 Orientation (AA)

Supports

The Simplebooklet editor and viewer support both portrait and landscape orientations and do not lock display to a single orientation.

1.3.5 Identify Input Purpose (AA)

Supports

Form inputs for account management and editor fields use standard HTML input types and autocomplete attributes where appropriate, enabling assistive technologies to identify input purposes.

1.4.1 Use of Color (A)

Supports

Color is not the sole means of conveying information. Interactive states, error messages, and status indicators include text labels or icons in addition to color.

1.4.2 Audio Control (A)

Supports

Simplebooklet does not auto-play audio by default. Where audio is present in a published booklet, user controls are provided to pause or stop playback.

1.4.3 Contrast (Minimum) (AA)

Supports

Default platform UI (buttons, menus, forms, navigation) meets the 4.5:1 minimum contrast ratio for normal text and 3:1 for large text. User-authored booklet content may vary based on author-chosen colors and is outside platform control.

1.4.4 Resize Text (AA)

Supports

Text throughout the platform UI can be resized up to 200% using browser zoom without loss of content or functionality.

1.4.5 Images of Text (AA)

Supports

Platform navigation and UI labels use real text rendered via CSS. Essential UI elements are not images of text.

1.4.10 Reflow (AA)

Partially Supports

The editor UI reflows appropriately at 320 CSS px equivalent width. The booklet viewer replicates a page-spread layout; at narrow viewports some complex booklet layouts may require horizontal scrolling. A single-page view mode is available to improve the narrow-screen experience.

1.4.11 Non-text Contrast (AA)

Supports

UI components — including button borders, form input outlines, focus indicators, and icons — meet the 3:1 contrast ratio against adjacent colors in the default platform theme.

1.4.12 Text Spacing (AA)

Supports

The platform interface does not prevent user-applied text spacing adjustments (line height, letter spacing, word spacing, paragraph spacing) as defined in the criterion. Content remains readable under these adjustments.

1.4.13 Content on Hover or Focus (AA)

Supports

Tooltips and contextual menus that appear on hover or focus are persistent, hoverable, and can be dismissed without moving pointer or keyboard focus.

2.1.1 Keyboard (A)

Partially Supports

Core navigation, account management, and booklet page navigation are fully keyboard accessible. Most editor functions are keyboard accessible. Some advanced drag-and-drop design operations in the editor require a mouse; keyboard-equivalent alternatives are provided for the majority of these functions. Ongoing improvements are underway for complete keyboard access across all editor tools.

2.1.2 No Keyboard Trap (A)

Supports

Keyboard focus is never trapped in a component without a way to move focus away. Modal dialogs return focus to the originating element on close.

2.1.4 Character Key Shortcuts (A)

Supports

Keyboard shortcuts use modifier keys (Ctrl, Alt, Shift). No single-character shortcuts are active without a modifier, preventing unintended activation by speech input users.

2.2.1 Timing Adjustable (A)

Not Applicable

Simplebooklet does not impose session time limits that affect content creation or viewing. Shared booklets do not expire without user action.

2.2.2 Pause, Stop, Hide (A)

Supports

Animated elements (e.g. page-turn transitions) are brief and do not distract. Auto-advancing slideshow mode in published booklets includes play/pause controls.

2.3.1 Three Flashes or Below Threshold (A)

Supports

Platform UI does not contain content that flashes more than three times per second. Third-party embedded media is outside Simplebooklet's direct control.

2.4.1 Bypass Blocks (A)

Supports

Skip navigation links and ARIA landmark regions are present in both the editor and viewer, allowing keyboard users to bypass repeated navigation blocks.

2.4.2 Page Titled (A)

Supports

All platform pages include descriptive, unique title elements. Published booklet viewer pages display the booklet title in the browser title bar.

2.4.3 Focus Order (A)

Supports

Interactive elements receive keyboard focus in a logical order that preserves meaning and operability, following the visual layout of the interface.

2.4.4 Link Purpose (In Context) (A)

Supports

Links are labeled to describe their destination or function from link text alone or from surrounding context. Icon-only links include aria-label attributes.

2.4.5 Multiple Ways (AA)

Supports

Published booklets are accessible via direct URL, platform search, and user profile pages. Multiple means of locating content are provided within the platform.

2.4.6 Headings and Labels (AA)

Supports

Headings and form labels throughout the editor and viewer are descriptive and meaningful. The heading hierarchy is logical and consistent across the platform.

2.4.7 Focus Visible (AA)

Supports

All interactive elements display a visible focus indicator when navigated by keyboard. Focus outlines meet minimum contrast requirements in the default platform theme.

3.1.1 Language of Page (A)

Supports

The lang attribute is correctly set on the html element for all platform pages. Published booklets default to the language set by the content author in their booklet settings.

3.1.2 Language of Parts (AA)

Supports

Passages in a language different from the page default are identified with appropriate lang attributes in platform UI. Multilingual user-created content is the responsibility of the content author.

3.2.1 On Focus (A)

Supports

Receiving focus does not initiate unexpected context changes. No element launches new windows, submits forms, or navigates pages merely upon receiving focus.

3.2.2 On Input (A)

Supports

Changing a form control's value does not automatically cause a context change unless the user has been advised of that behavior in advance. All form submissions require explicit user action.

3.2.3 Consistent Navigation (AA)

Supports

Navigation elements (top menu, sidebar, toolbar) appear in the same relative order and location throughout all platform pages. Navigation is predictable and consistent.

3.2.4 Consistent Identification (AA)

Supports

Interface components with the same function are identified consistently throughout the platform. Icons and button labels are used uniformly across pages.

3.3.1 Error Identification (A)

Supports

Form validation errors are identified in text, describing the field in error and the nature of the problem. Error messages are programmatically associated with the relevant input field.

3.3.2 Labels or Instructions (A)

Supports

All form inputs include visible labels. Required fields are clearly indicated. Instructions are provided where input format is constrained (e.g. date fields, password requirements).

3.3.3 Error Suggestion (AA)

Supports

When an input error is detected, the error message suggests how the user can correct it, except where doing so would compromise security (e.g. password or payment fields).

3.3.4 Error Prevention (Legal, Financial, Data) (AA)

Supports

Significant and irreversible actions — such as deleting a booklet or canceling a subscription — require explicit user confirmation before proceeding, reducing the risk of unintended data loss.

4.1.1 Parsing (A)

Supports

Platform pages use valid, well-formed HTML. Elements are correctly nested, IDs are unique within pages, and start/end tags are properly used.

4.1.2 Name, Role, Value (A)

Partially Supports

Standard HTML elements and ARIA roles are used to communicate name, role, and state for interactive UI components. Some custom-built editor canvas toolbar components are in the process of being updated with complete ARIA attributes to fully expose name, role, and value to assistive technologies.

4.1.3 Status Messages (AA)

Supports

Status messages — including save confirmations, upload progress, and error notifications — use appropriate ARIA live regions (aria-live, role='status', role='alert') so screen readers announce them without requiring focus to move to the message.