Skip to main content
App Logo
NativeSpeech
ContactPricing

Accessibility Conformance Report

VPAT® Version 2.5Rev — WCAG Edition
56
Criteria evaluated (A & AA)
50
Supports
1
Partially Supports
5
Not Applicable

Report Information

Name of Product/Version
NativeSpeech (web application), evaluated May 2026 release
Report Date
May 2026
Product Description
NativeSpeech is an AI-powered web application for improving speaking skills and fluency in multiple languages. It provides AI-generated stories and dialogs, text-to-speech playback, real-time speech scoring and pronunciation assessment, and interactive practice tools.
Contact Information
support@nativespeech.app
Notes
This report covers the publicly accessible web pages of the product (home, pricing, contact, FAQ, privacy policy, terms of service, AI pronunciation checker, read-anything, story, and text-to-speech). It addresses WCAG 2.x Level A and Level AA. Level AAA was not evaluated and is out of scope; the Level AAA table has been omitted in accordance with the VPAT instructions for removing a level that is not reported.

Evaluation Methods Used

Conformance was evaluated by testers familiar with the product's common flows, using a combination of automated tooling and manual inspection. Testing was performed in a headless Chromium browser (via Playwright) in both light and dark color schemes. The automated suite comprises five complementary passes, all of which pass on every evaluated page:
  • axe-core (WCAG 2.0/2.1 A and AA rule sets plus best practices) — 22 page renders, 0 violations.
  • Keyboard audit — focus-indicator visibility, tab order, positive-tabindex detection, keyboard reachability, and modal focus-trap behavior.
  • Screen-reader (accessibility-tree) audit — accessible names, form labels, heading structure, and image alternatives.
  • WAVE-equivalent error checks — grouping (fieldset/role), broken ARIA references, orphaned/empty labels, and skip-link targets.
  • Visual audit — WCAG 1.4.10 Reflow at a 320px viewport and WCAG 1.4.12 Text Spacing (injecting the required spacing overrides and checking for clipped content).
Manual review supplemented the automated passes for criteria that cannot be fully automated (e.g. meaningful sequence, sensory characteristics, consistent navigation/identification, error prevention, and authentication).

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standards/guidelines:
Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0 (ISO/IEC 40500)
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

The terms used in the Conformance Level column are defined as follows:
Supports
The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criterion.
Does Not Support
The majority of product 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. This can only be used in WCAG Level AAA criteria.

WCAG 2.x Report

Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: Success Criteria, Level A

CriteriaConformance LevelRemarks and Explanations
Guideline 1.1 Text Alternatives
1.1.1 Non-text Content (Level A)
Supports
All informative images include text alternatives and icon-only controls (buttons, tabs, the voice recorder) expose an aria-label. Verified with automated axe-core and accessibility-tree (screen-reader) scans across all public pages; no missing-alt or missing-name violations were found.
Guideline 1.2 Time-based Media
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Not Applicable
The product contains no prerecorded audio-only or video-only content. Spoken audio is synthesized on demand from user/AI text via text-to-speech and is not prerecorded media.
1.2.2 Captions (Prerecorded) (Level A)
Not Applicable
The product contains no prerecorded synchronized media (video with audio).
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Not Applicable
The product contains no prerecorded synchronized media.
Guideline 1.3 Adaptable
1.3.1 Info and Relationships (Level A)
Supports
Form fields are programmatically labelled, headings use semantic levels, grouped controls (e.g. the billing-cycle toggle) use role="group" with an accessible name, and tab interfaces expose proper ARIA. Verified with axe-core and a WAVE-equivalent check (fieldset/group, label, and ARIA-reference checks all pass).
1.3.2 Meaningful Sequence (Level A)
Supports
DOM order matches the visual reading order on all pages; the keyboard focus-order audit found a logical sequence on every page tested.
1.3.3 Sensory Characteristics (Level A)
Supports
Instructions and controls are identified by text labels and accessible names rather than relying solely on shape, size, color, or position.
Guideline 1.4 Distinguishable
1.4.1 Use of Color (Level A)
Supports
State and meaning are conveyed by text and icons in addition to color (e.g. status notifications pair color with an icon and message). axe-core color-use checks pass.
1.4.2 Audio Control (Level A)
Supports
No audio plays automatically. Text-to-speech playback is user-initiated and provides explicit Pause and Stop controls on the Story and Text-to-Speech pages.
Guideline 2.1 Keyboard Accessible
2.1.1 Keyboard (Level A)
Supports
All interactive functionality is operable by keyboard. The Story source tabs were updated for Tab/Arrow navigation, and the voice-recorder controls (rendered as images by a third-party library) were patched with tabindex, role="button", and Enter/Space handlers. The keyboard audit passes on all pages.
2.1.2 No Keyboard Trap (Level A)
Supports
Focus can move into and out of all components. Overlays/modals trap focus only while open and are dismissible with Escape; the modal-focus-trap check passes.
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)
Supports
The product implements no single-character key shortcuts, so there is nothing that could be triggered inadvertently.
Guideline 2.2 Enough Time
2.2.1 Timing Adjustable (Level A)
Supports
No time limits are imposed on reading or interacting with content. Session/token refresh is handled transparently in the background and does not impose a user-facing time limit.
2.2.2 Pause, Stop, Hide (Level A)
Supports
Text-to-speech playback can be paused and stopped. There is no auto-updating, blinking, scrolling, or moving content that runs longer than five seconds outside of user control.
Guideline 2.3 Seizures and Physical Reactions
2.3.1 Three Flashes or Below Threshold (Level A)
Supports
The product contains no flashing content.
Guideline 2.4 Navigable
2.4.1 Bypass Blocks (Level A)
Supports
A "Skip to main content" link is provided as the first focusable element and targets the page's <main> landmark. The WAVE-equivalent skip-link check confirms the target resolves.
2.4.2 Page Titled (Level A)
Supports
Every page sets a descriptive document title via next/head, with a meaningful site-level default applied where a page does not override it.
2.4.3 Focus Order (Level A)
Supports
Focus order is logical and preserves meaning; verified by the keyboard focus-order audit. No positive tabindex values are used.
2.4.4 Link Purpose (In Context) (Level A)
Supports
Links have descriptive text or accessible names. The accessible-name (screen-reader) audit found no empty-name links.
Guideline 2.5 Input Modalities
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)
Supports
No path-based or multipoint gestures are required; all actions are achievable with a single pointer activation.
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
Supports
Activation occurs on the up-event (click), consistent with the component library defaults, allowing users to abort by moving away before release.
2.5.3 Label in Name (Level A 2.1 and 2.2)
Supports
The accessible name of each control contains its visible text label; icon-only controls use aria-labels that describe their visible purpose.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
Supports
No functionality is operated by device motion or user motion, so there is no motion-only actuation to disable.
Guideline 3.1 Readable
3.1.1 Language of Page (Level A)
Supports
The default human language of each page is set programmatically via <html lang="en">.
Guideline 3.2 Predictable
3.2.1 On Focus (Level A)
Supports
Moving focus to a component does not trigger a change of context. The Story source tabs were specifically corrected so that focusing a tab no longer activates it; activation now requires Enter/Space.
3.2.2 On Input (Level A)
Supports
Changing a form control (e.g. language or voice selection) updates the relevant preview but does not cause an unexpected change of context such as navigation or form submission.
3.2.6 Consistent Help (Level A 2.2 only)
Supports
Help mechanisms (a persistent feedback button and a Contact link in the footer) appear in a consistent location across pages via the shared layout.
Guideline 3.3 Input Assistance
3.3.1 Error Identification (Level A)
Supports
Input errors are identified in text by the form components and by status notifications; errors are not indicated by color alone.
3.3.2 Labels or Instructions (Level A)
Supports
All form inputs provide a label or aria-label. The screen-reader and WAVE-equivalent form-label checks pass with no unlabelled fields (including conditionally-rendered fields on the Story page).
3.3.7 Redundant Entry (Level A 2.2 only)
Supports
No process requires the user to re-enter information already provided earlier in the same process.
Guideline 4.1 Compatible
4.1.1 Parsing (Level A)
Supports
For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. For WCAG 2.2 the criterion is obsolete and removed. No duplicate-ID or markup-parsing violations were reported by axe-core.
4.1.2 Name, Role, Value (Level A)
Supports
Interactive components expose a correct name, role, and value/state. Icon-only buttons are labelled, the tab interface uses correct ARIA, and grouped controls use appropriate roles. Verified by axe-core and the accessibility-tree audit.

Table 2: Success Criteria, Level AA

CriteriaConformance LevelRemarks and Explanations
Guideline 1.2 Time-based Media
1.2.4 Captions (Live) (Level AA)
Not Applicable
The product contains no live audio or video content.
1.2.5 Audio Description (Prerecorded) (Level AA)
Not Applicable
The product contains no prerecorded synchronized media.
Guideline 1.3 Adaptable
1.3.4 Orientation (Level AA 2.1 and 2.2)
Supports
Content is not restricted to a single display orientation; the responsive layout functions in both portrait and landscape and was verified to reflow at a 320px viewport width.
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)
Supports
Inputs that collect information about the user expose an appropriate autocomplete purpose (e.g. name on the account and contact forms; email on the contact form; email/password on the authentication flow provided by the identity provider).
Guideline 1.4 Distinguishable
1.4.3 Contrast (Minimum) (Level AA)
Supports
Text and images of text meet the 4.5:1 (or 3:1 for large text) contrast ratio. axe-core contrast checks pass across all pages in both light and dark color schemes.
1.4.4 Resize text (Level AA)
Supports
Text is specified in relative units and can be resized up to 200% via browser zoom without loss of content or functionality; the layout reflows responsively.
1.4.5 Images of Text (Level AA)
Supports
Text is rendered as real text rather than images of text; no images of text are used to convey information.
1.4.10 Reflow (Level AA 2.1 and 2.2)
Supports
Content reflows without requiring horizontal scrolling at 320 CSS pixels of width. An automated reflow audit at 320px passes on all pages after resolving grid-gutter, list-wrapping, and slider-mark overflow issues.
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
Supports
User-interface components and focus indicators meet the 3:1 non-text contrast requirement; verified by axe-core.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
Supports
No loss of content or functionality occurs when users apply the WCAG text-spacing metrics (line height 1.5, paragraph spacing 2x, letter spacing 0.12em, word spacing 0.16em). An automated check that injects these overrides and inspects every overflow-clipped container for hidden text passes on all pages.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
Supports
Tooltips and popovers triggered on hover/focus are dismissible (Escape), hoverable, and remain visible until dismissed or the trigger is no longer hovered/focused, per the component library behavior.
Guideline 2.4 Navigable
2.4.5 Multiple Ways (Level AA)
Supports
More than one way is available to locate pages: persistent header navigation and a footer link list, in addition to direct URLs.
2.4.6 Headings and Labels (Level AA)
Supports
Headings and labels are descriptive. The screen-reader audit confirms a coherent heading structure with no level skips.
2.4.7 Focus Visible (Level AA)
Supports
A visible focus indicator is present for all keyboard-focusable elements; the keyboard audit's focus-indicator check passes on all pages, including a custom focus ring added to the voice-recorder controls.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
Supports
When an element receives focus it is not entirely hidden by author-created content; there are no sticky overlays that fully obscure focused components.
Guideline 2.5 Input Modalities
2.5.7 Dragging Movements (Level AA 2.2 only)
Supports
The only drag-based control (the speaking-speed slider) can also be operated by keyboard arrow keys and by clicking a position on the track, so dragging is not the only means of operation.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)
Supports
Interactive targets meet the 24x24 CSS pixel minimum. For example, the voice-recorder control presents a 40x40px target, and standard buttons exceed the minimum.
Guideline 3.1 Readable
3.1.2 Language of Parts (Level AA)
Partially Supports
The application interface (chrome) is correctly identified as English via <html lang="en">. However, dynamically generated target-language practice content (e.g. AI-generated stories or dialogs in a language other than the page language) is not yet wrapped in an element carrying a programmatic lang attribute for that passage. Remediation: tag generated practice passages with the lang of the selected practice language. This does not affect the English user interface.
Guideline 3.2 Predictable
3.2.3 Consistent Navigation (Level AA)
Supports
Navigation (header and footer) is presented in the same relative order and location across pages via a shared layout component.
3.2.4 Consistent Identification (Level AA)
Supports
Components with the same functionality (e.g. Listen, Download, Save/Share actions) are identified consistently across the product.
Guideline 3.3 Input Assistance
3.3.3 Error Suggestion (Level AA)
Supports
When input errors are detected and a correction is known, the form components and notifications describe the problem and suggest how to correct it in text.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Supports
Financial transactions are handled by third-party payment providers that supply confirmation and reversibility. Destructive data actions (e.g. account/content deletion) require explicit confirmation before they are committed.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
Supports
Authentication uses email and password (and federated sign-in) provided by the identity provider. No cognitive function test (such as a puzzle or CAPTCHA) is required, and password entry supports paste and password managers.
Guideline 4.1 Compatible
4.1.3 Status Messages (Level AA 2.1 and 2.2)
Supports
Status messages are presented through a notification region exposed with role="status" and aria-live="polite", so assistive technologies announce them without moving focus.

Table 3: Success Criteria, Level AAA

Level AAA was not evaluated and is out of scope for this report. In accordance with the VPAT instructions, the Level AAA criteria table has been omitted.

Legal Disclaimer

This Accessibility Conformance Report is provided for informational purposes and represents the product's accessibility status as of the report date. Accessibility is assessed on an ongoing basis and findings may change as the product evolves. This document does not constitute a warranty or legally binding statement.