Accessibility Conformance Report

StoryAudit, WCAG edition. Based on VPAT® Version 2.5Rev.

Product: StoryAudit web app and website (storyaudit.app)
Version: October 2026 release
Report date: October 2, 2026
Contact: support@storyaudit.app

Summary

StoryAudit reviews, compares and documents Articulate Storyline courses from the .story file, in the browser. This report covers the website and the app's six tools: Compare, Health Check, Course Docs, Batch Check, Translation Check and Text Fixes. Account and billing screens provided by Clerk and Stripe are outside it.

Level A 32 criteria: 28 Supports, 4 Not Applicable.
Level AA 24 criteria: 21 Supports, 1 Partially Supports, 2 Not Applicable.
Open item 3.1.2 Language of Parts: text from a user's course is shown without a language tag.

How it was tested

Automated testing with axe-core 4.13 against the WCAG 2.0, 2.1 and 2.2 Level A and AA rules, on every website page, the sample report exports, and each app tool with the demo course loaded.
Keyboard testing of each page and tool: tab order, visible focus, focus hidden behind sticky headers, keyboard traps, and the menus, dialogs, drawers and tabs.
Layout and display checks at 320 CSS pixels wide, with increased text spacing, and for moving content.
Accessibility tree review of names, roles and states for controls, in Chromium.
Screen reader testing with VoiceOver on macOS is scheduled. This report will be updated with the results.

Applicable standards

Standards and guidelines covered by this report
Standard	Included in this report
Web Content Accessibility Guidelines 2.0	Level A: Yes. Level AA: Yes. Level AAA: No.
Web Content Accessibility Guidelines 2.1	Level A: Yes. Level AA: Yes. Level AAA: No.
Web Content Accessibility Guidelines 2.2	Level A: Yes. Level AA: Yes. Level AAA: No.

Terms

Supports: the functionality has at least one method that meets the criterion without known defects, or meets it with equivalent facilitation.
Partially Supports: some functionality does not meet the criterion.
Does Not Support: the majority of functionality does not meet the criterion.
Not Applicable: the criterion is not relevant to the product.
Not Evaluated: the product has not been evaluated against the criterion. Used only for Level AAA, which this report doesn't cover.

Table 1: Level A

WCAG 2.x Level A success criteria
Criteria	Conformance level	Remarks and explanations
1.1.1 Non-text ContentWCAG 2.0, 2.1, 2.2	Supports	Icons are hidden from assistive technology or have a text name. Charts have a text summary and a data table. Product screenshots on the website have alt text.
1.2.1 Audio-only and Video-only (Prerecorded)WCAG 2.0, 2.1, 2.2	Not Applicable	StoryAudit has no audio or video of its own. Media from a course the user opens plays as it was authored.
1.2.2 Captions (Prerecorded)WCAG 2.0, 2.1, 2.2	Not Applicable	As 1.2.1.
1.2.3 Audio Description or Media Alternative (Prerecorded)WCAG 2.0, 2.1, 2.2	Not Applicable	As 1.2.1.
1.3.1 Info and RelationshipsWCAG 2.0, 2.1, 2.2	Supports	Headings, lists, landmarks, data tables with header cells, and labeled form fields. Checked in the Chromium accessibility tree; a screen reader pass is scheduled.
1.3.2 Meaningful SequenceWCAG 2.0, 2.1, 2.2	Supports	Reading order follows the visual order.
1.3.3 Sensory CharacteristicsWCAG 2.0, 2.1, 2.2	Supports	Instructions don't rely on shape, color, size or position alone.
1.4.1 Use of ColorWCAG 2.0, 2.1, 2.2	Supports	Severity is shown with a text label and an icon as well as color. In Compare, removed text is struck through and added text is underlined.
1.4.2 Audio ControlWCAG 2.0, 2.1, 2.2	Supports	Nothing plays automatically. Course media plays only when the user starts it, with player controls.
2.1.1 KeyboardWCAG 2.0, 2.1, 2.2	Supports	All functions work from the keyboard. File drop areas open the file picker with Enter or Space.
2.1.2 No Keyboard TrapWCAG 2.0, 2.1, 2.2	Supports	Focus can move out of every component. Dialogs and drawers close with Escape and return focus to the control that opened them.
2.1.4 Character Key ShortcutsWCAG 2.1, 2.2	Supports	There are no single-character keyboard shortcuts.
2.2.1 Timing AdjustableWCAG 2.0, 2.1, 2.2	Supports	There are no time limits.
2.2.2 Pause, Stop, HideWCAG 2.0, 2.1, 2.2	Supports	No content moves, blinks or updates automatically, apart from progress indicators while a file is being read.
2.3.1 Three Flashes or Below ThresholdWCAG 2.0, 2.1, 2.2	Supports	No flashing content.
2.4.1 Bypass BlocksWCAG 2.0, 2.1, 2.2	Supports	Every page and app tool has banner, main and footer landmarks and a heading structure.
2.4.2 Page TitledWCAG 2.0, 2.1, 2.2	Supports	Page titles name the page, or the app tool and the file that's open.
2.4.3 Focus OrderWCAG 2.0, 2.1, 2.2	Supports	Focus order follows the layout. Dialogs move focus into the dialog when they open.
2.4.4 Link Purpose (In Context)WCAG 2.0, 2.1, 2.2	Supports	Link text describes its destination.
2.5.1 Pointer GesturesWCAG 2.1, 2.2	Supports	No multipoint or path-based gestures.
2.5.2 Pointer CancellationWCAG 2.1, 2.2	Supports	Actions run on release (standard click events).
2.5.3 Label in NameWCAG 2.1, 2.2	Supports	Accessible names contain the visible label text.
2.5.4 Motion ActuationWCAG 2.1, 2.2	Not Applicable	No functions use device motion.
3.1.1 Language of PageWCAG 2.0, 2.1, 2.2	Supports	Pages declare English.
3.2.1 On FocusWCAG 2.0, 2.1, 2.2	Supports	Focus never changes the context.
3.2.2 On InputWCAG 2.0, 2.1, 2.2	Supports	Changing a setting or filter updates results in place. Nothing navigates away on input.
3.2.6 Consistent HelpWCAG 2.2	Supports	The support email is in the same place in the footer on every page and in the app.
3.3.1 Error IdentificationWCAG 2.0, 2.1, 2.2	Supports	File errors are described in text and announced through a status message. Checked in the Chromium accessibility tree; a screen reader pass is scheduled.
3.3.2 Labels or InstructionsWCAG 2.0, 2.1, 2.2	Supports	Fields have labels. Drop areas say which file they take.
3.3.7 Redundant EntryWCAG 2.2	Supports	The reviewer name is remembered and isn't asked for again.
4.1.1 ParsingWCAG 2.0, 2.1	Supports	Removed in WCAG 2.2. For WCAG 2.0 and 2.1, the 2023 errata treat it as satisfied for content written in HTML.
4.1.2 Name, Role, ValueWCAG 2.0, 2.1, 2.2	Supports	Native controls are used where possible. Custom controls (tool tabs, drop areas, slide lists, info badges) expose a role, a name and their state. Checked in the Chromium accessibility tree; a screen reader pass is scheduled.

Table 2: Level AA

WCAG 2.x Level AA success criteria
Criteria	Conformance level	Remarks and explanations
1.2.4 Captions (Live)WCAG 2.0, 2.1, 2.2	Not Applicable	No live media.
1.2.5 Audio Description (Prerecorded)WCAG 2.0, 2.1, 2.2	Not Applicable	As 1.2.1.
1.3.4 OrientationWCAG 2.1, 2.2	Supports	Pages work in either orientation.
1.3.5 Identify Input PurposeWCAG 2.1, 2.2	Supports	The field for the reviewer's own name has autocomplete="name".
1.4.3 Contrast (Minimum)WCAG 2.0, 2.1, 2.2	Supports	Text meets 4.5:1, or 3:1 for large text, in automated and manual checks.
1.4.4 Resize TextWCAG 2.0, 2.1, 2.2	Supports	Text resizes to 200% without loss of content or function.
1.4.5 Images of TextWCAG 2.0, 2.1, 2.2	Supports	Text is real text. The website's product screenshots show the app as it looks, and the same information is in the page text.
1.4.10 ReflowWCAG 2.1, 2.2	Supports	Pages reflow at 320 CSS pixels with no horizontal scrolling. Wide data tables in the app scroll inside their own area, as the criterion allows.
1.4.11 Non-text ContrastWCAG 2.1, 2.2	Supports	Text field borders and focus indicators meet 3:1. Status icons always appear with a text label.
1.4.12 Text SpacingWCAG 2.1, 2.2	Supports	No content is lost with increased line, letter, word and paragraph spacing.
1.4.13 Content on Hover or FocusWCAG 2.1, 2.2	Supports	Info tooltips show on hover and focus, stay while the pointer is over them, and close with Escape.
2.4.5 Multiple WaysWCAG 2.0, 2.1, 2.2	Supports	Site navigation and footer links on every page. App tools are reachable from the tool tabs.
2.4.6 Headings and LabelsWCAG 2.0, 2.1, 2.2	Supports	Headings and labels describe their topic or purpose.
2.4.7 Focus VisibleWCAG 2.0, 2.1, 2.2	Supports	Every focusable element shows a visible focus indicator.
2.4.11 Focus Not Obscured (Minimum)WCAG 2.2	Supports	The app keeps the focused element clear of its sticky header and toolbars.
2.5.7 Dragging MovementsWCAG 2.2	Supports	Dragging files in is optional. Every drop area also opens a file picker.
2.5.8 Target Size (Minimum)WCAG 2.2	Supports	Targets are at least 24 by 24 CSS pixels, have enough space around them, or have an equivalent control that does. Links inside sentences are exempt.
3.1.2 Language of PartsWCAG 2.0, 2.1, 2.2	Partially Supports	Text from a user's course, including translations shown in Translation Check, is displayed without a language tag, so a screen reader reads it in the page language.
3.2.3 Consistent NavigationWCAG 2.0, 2.1, 2.2	Supports	Navigation is in the same place and order on every page.
3.2.4 Consistent IdentificationWCAG 2.0, 2.1, 2.2	Supports	Controls with the same function have the same label.
3.3.3 Error SuggestionWCAG 2.0, 2.1, 2.2	Supports	File errors say what went wrong and what to try.
3.3.4 Error Prevention (Legal, Financial, Data)WCAG 2.0, 2.1, 2.2	Supports	Purchases go through a checkout that can be reviewed before paying. Waiving findings in bulk asks for confirmation, and waivers can be undone.
3.3.8 Accessible Authentication (Minimum)WCAG 2.2	Supports	Sign-in is provided by Clerk and offers Google, Microsoft or email sign-in. None of them asks the user to solve a puzzle or recall something StoryAudit set.
4.1.3 Status MessagesWCAG 2.1, 2.2	Supports	Loading progress, results and export messages are announced through status regions without moving focus. Checked in the Chromium accessibility tree; a screen reader pass is scheduled.

Table 3: Level AAA

Not evaluated.

Notes

Not covered by this report: account and billing screens provided by Clerk and Stripe, apart from the sign-in methods described under 3.3.8; PDF files made with the browser's print function; and the content of the Storyline courses people open, which StoryAudit shows as authored.
Platform: StoryAudit runs in a desktop or laptop browser. Testing used Chromium at desktop width and at 320 CSS pixels wide.
Reporting a problem: email support@storyaudit.app. Accessibility fixes are listed in the changelog.
Legal disclaimer: this report describes StoryAudit as tested on the date above. It is provided for information and is not a warranty. “VPAT” is a registered service mark of the Information Technology Industry Council (ITI).

↑ Back to top