Skip to main content

Accessibility Conformance Report (VPAT®)

VPAT® Version: 2.5 (WCAG)
Product name: SpeechGradebook
Product version: Hosted web application (current production)
Product description: AI-assisted speech evaluation platform for instructors, admins, and Practice users
Vendor: ValidBound LLC
Report date: July 2026
Contact: speechgradebook.com/contact (note Accessibility)

Related public statement: Accessibility Statement.

:::note Evaluation basis This ACR is a self-assessment by ValidBound based on design standards, internal review, and assistive-technology spot checks. It is not a third-party certified audit. Institutions may request clarification or schedule a deeper review via the contact form. :::

Evaluation methods used

  • Manual keyboard navigation of primary instructor and Practice workflows
  • Spot checks with screen readers (NVDA and/or VoiceOver) on core screens
  • Automated checks for contrast and common issues on primary views
  • Review against WCAG 2.1 Level A and AA success criteria
  • Review of known limitations (user-uploaded media, third-party embeds)

Applicable standards / guidelines

Standard / guidelineIncluded in report
WCAG 2.1 Level AYes
WCAG 2.1 Level AAYes
WCAG 2.1 Level AAANo
Revised Section 508Reported separately on request
EN 301 549Not evaluated

Terms

TermMeaning
SupportsFunctionality meets the criterion without known exceptions in primary product UI
Partially SupportsSome functionality meets the criterion; exceptions or limitations exist
Does Not SupportMajority of functionality does not meet the criterion
Not ApplicableCriterion is not relevant to the product

WCAG 2.1 report summary

Conformance levelOverall remarks
Level APartially Supports — Core navigation, forms, and structure are designed for accessibility; some dynamic evaluation and chart views need continued hardening
Level AAPartially Supports — Contrast, resize, and focus patterns target AA; complex analytics and user-generated video remain the main gaps

Table 1: Success criteria, Level A

CriteriaConformanceRemarks and explanations
1.1.1 Non-text ContentPartially SupportsProduct icons and UI images use alt text or ARIA labels. Charts may include text alternatives; decorative icons use aria-hidden. User-uploaded speech video may lack captions (instructor/student content).
1.2.1 Audio-only and Video-only (Prerecorded)Partially SupportsPlatform UI does not rely on audio-only instruction. Uploaded speech media is user-generated; captions/transcripts are encouraged but not guaranteed by the platform.
1.2.2 Captions (Prerecorded)Partially SupportsSame as above for user-uploaded recordings.
1.2.3 Audio Description or Media Alternative (Prerecorded)Partially SupportsUser-generated media; alternatives depend on instructor-provided materials.
1.3.1 Info and RelationshipsSupportsSemantic HTML, headings, labels, and landmarks are used across primary screens.
1.3.2 Meaningful SequenceSupportsReading and focus order follow visual structure on primary flows.
1.3.3 Sensory CharacteristicsSupportsInstructions do not rely on shape, size, or sound alone.
1.4.1 Use of ColorSupportsStatus and meaning are not conveyed by color alone (text/icons used with color).
1.4.2 Audio ControlSupportsNo auto-playing audio in the product shell.
2.1.1 KeyboardPartially SupportsPrimary actions and navigation are keyboard reachable. Some chart and advanced analytics interactions may be less efficient by keyboard.
2.1.2 No Keyboard TrapSupportsFocus can move away from components using standard keys.
2.1.4 Character Key ShortcutsSupportsNo single-character shortcuts that conflict with AT by default.
2.2.1 Timing AdjustableSupportsNo unexpected short timeouts that block core tasks; auth sessions follow platform session policy.
2.2.2 Pause, Stop, HideSupportsMotion is limited; prefers-reduced-motion is respected where animations are used.
2.3.1 Three Flashes or Below ThresholdSupportsUI does not include flashing content above thresholds.
2.4.1 Bypass BlocksSupportsSkip link and landmark regions available on app shells.
2.4.2 Page TitledSupportsPages and major views use descriptive titles.
2.4.3 Focus OrderSupportsFocus order is logical on primary workflows.
2.4.4 Link Purpose (In Context)SupportsLink text is descriptive in context.
2.5.1 Pointer GesturesSupportsMultipoint/path gestures are not required for core tasks.
2.5.2 Pointer CancellationSupportsActivation occurs on up-event patterns consistent with standard controls.
2.5.3 Label in NameSupportsVisible labels match accessible names for primary controls.
2.5.4 Motion ActuationSupportsDevice motion is not required to operate the UI.
3.1.1 Language of PageSupportslang attribute set on document.
3.2.1 On FocusSupportsFocusing controls does not unexpectedly change context.
3.2.2 On InputSupportsChanging settings does not unexpectedly force navigation without user action.
3.3.1 Error IdentificationSupportsForm errors are identified in text.
3.3.2 Labels or InstructionsSupportsForm controls have labels/instructions.
4.1.1 ParsingSupportsHTML is authored for valid structure; issues are fixed as found.
4.1.2 Name, Role, ValuePartially SupportsStandard controls expose name/role/value. Some custom components and dynamic regions continue to be improved for AT.

Table 2: Success criteria, Level AA

CriteriaConformanceRemarks and explanations
1.2.4 Captions (Live)Not ApplicableNo live broadcast media product feature.
1.2.5 Audio Description (Prerecorded)Partially SupportsDepends on user-provided media alternatives.
1.3.4 OrientationSupportsContent usable in portrait and landscape.
1.3.5 Identify Input PurposePartially SupportsCommon auth fields supported; some institutional forms may lack full autocomplete taxonomy.
1.4.3 Contrast (Minimum)SupportsBody and interactive text target WCAG AA contrast ratios.
1.4.4 Resize TextSupportsText can be resized up to 200% with relative units on primary layouts.
1.4.5 Images of TextSupportsUI text is real text, not images of text (except logos).
1.4.10 ReflowPartially SupportsPrimary views reflow; dense analytics tables may require horizontal scroll on small viewports.
1.4.11 Non-text ContrastPartially SupportsInteractive controls target AA; some chart glyphs may fall short in edge themes.
1.4.12 Text SpacingSupportsContent remains usable when spacing is adjusted within WCAG limits.
1.4.13 Content on Hover or FocusPartially SupportsMenus/tooltips are dismissible; ongoing review for all hover content.
2.4.5 Multiple WaysSupportsNavigation, search (where available), and direct links provide multiple paths.
2.4.6 Headings and LabelsSupportsHeadings and labels describe topic/purpose.
2.4.7 Focus VisibleSupportsVisible focus indicators on interactive elements.
3.1.2 Language of PartsPartially SupportsPage language set; rare mixed-language content may not mark language changes.
3.2.3 Consistent NavigationSupportsPrimary nav patterns are consistent across the app.
3.2.4 Consistent IdentificationSupportsComponents with the same function are identified consistently.
3.3.3 Error SuggestionSupportsError messages suggest corrections where known.
3.3.4 Error Prevention (Legal, Financial, Data)Partially SupportsDestructive actions use confirmation; consent and agreement flows use explicit confirmation.
4.1.3 Status MessagesPartially SupportsMany status updates are announced; some asynchronous evaluation progress messages continue to be improved.

Known limitations

  • User-uploaded speech video may lack captions. Where the SpeechGradebook evaluation pipeline produces a transcript of the speech, that transcript can partially mitigate accessibility for prerecorded media, but it is not a full substitute for instructor-provided captions on all uploads.
  • Third-party content (for example external links opened from the product) is outside ValidBound’s control.
  • Course Insights / dense charts may offer a weaker experience with some assistive technologies than core evaluation flows.
  • Older browsers may lack support for modern accessibility APIs.

Remediation and feedback

Report accessibility barriers via the contact form or see the Accessibility Statement. Target response: within 5 business days.

VPAT® is a registered trademark of the Information Technology Industry Council (ITI). This document uses the VPAT structure for institutional accessibility review. Conformance claims reflect ValidBound’s self-assessment as of the report date and may change as the product evolves.