Typing Agent Accessibility Conformance Report

Based on VPAT® 2.4 WCAG 2.1 and Revised Section 508 Edition

Name of Product/Version

Typing Agent 2025

Report Dates and Version

• Report Date: 9/5/2025
• Last Modified Date: 9/5/2025
• Version: typing agent -2025-1

Product Description

Typing Agent is a web-based educational platform designed to teach keyboarding, digital citizenship, and related curricula to K–12 students. We are committed to ensuring accessibility for all learners, including those with disabilities, and our system is developed in conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level A and AA and applicable provisions of Section 508 of the Rehabilitation Act.

Contact Information

Author Information

• Name: Scott Kintz
• Company: Typing Agent LLC
• Address: Typing Agent LLC PO BOX 1248 Snohomish, WA 98291-1248
• Email: support@typingagent.com
• Phone: (425) 880-2500
• Website: https://app.typingagent.com

Vendor Information

Notes

Our accessibility measures include support for screen readers (JAWS, VoiceOver, NVDA), closed captioning for multimedia, high-contrast display options, adjustable audio and narration features, dyslexia-friendly fonts, one-handed typing modes, and customizable student accommodations. Teachers and administrators can apply accessibility settings at the classroom or individual student level.

Typing Agent has completed an Accessibility Conformance Report (ACR) using the VPAT 2.3 template, with supporting documentation provided through an EqualWeb Web Accessibility Evaluation Report (July 2023). We maintain a formal accessibility policy and continuously update our platform based on compliance assessments and user feedback.

These measures reflect Typing Agent’s commitment to meeting Section 508 and WCAG standards, ensuring that students, teachers, and administrators can use our platform effectively and inclusively.

Evaluation Methods Used

Typing Agent’s accessibility evaluation was conducted using a combination of automated scanning tools, manual checks, and compliance reviews against recognized standards.

Automated Testing Tools

An EqualWeb Web Accessibility Evaluation Report (July 26, 2023) was completed, scanning app.typingagent.com against WCAG 2.1/2.2 Level A and AA and Section 508 requirements.

The scan reviewed 685 site pages with a recursive test of representative content, including login, student dashboard, lessons, reports, and administrative pages.

Results indicated 91.9/100 overall accessibility score, with low lawsuit risk and 28 accessibility errors identified for remediation.

Manual Verification & Assistive Technology Testing

Manual keyboard-only navigation tests and screen reader compatibility checks were performed using JAWS, NVDA, and VoiceOver.

Visual checks confirmed proper use of contrast ratios, text alternatives for images, ARIA attributes, and logical heading structures.

Representative Pages Reviewed

Student Interface: lesson modules, gamified learning activities, accessibility settings.

Teacher/Administrator Dashboard: classroom setup, reporting tools, and configuration screens.

Help and Policy Pages: end-user support documentation and system instructions.

Continuous Monitoring & Feedback Loop

Typing Agent maintains an accessibility policy and roadmap for ongoing compliance, ensuring updates based on user feedback and periodic re-evaluations.

EqualWeb accessibility guidelines are followed for new content, page structure, and PDF/Word accessibility.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline	Included In Report
Web Content Accessibility Guidelines 2.1	Table 1: Success Criteria, Level A Table 2: Success Criteria, Level AA Table 3: Success Criteria, Level AAA
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018	Chapter 3: Functional Performance Criteria (FPC) Chapter 4: Hardware Chapter 5: Software Chapter 6: Support Documentation and Services

Terms

The terms used in the Conformance Level information 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 be used only in WCAG 2.x Level AAA.

WCAG 2.1 Report

Table 1: Success Criteria, Level A

Notes:

Typing Agent is designed to conform with WCAG 2.0/2.1/2.2 Level A and AA requirements. Our most recent third-party evaluation (EqualWeb, July 2023) identified a small number of Level A issues, all of which have been addressed or scheduled for remediation:

Non-text Content (SC 1.1.1) – A limited number of images were missing alternative text attributes. Updates have been implemented to ensure all instructional and navigational images include appropriate alt text.

Info and Relationships (SC 1.3.1) – A few instances of incorrect heading structure and role attributes were flagged. These have been corrected to ensure semantic accuracy for screen readers.

Labels and Instructions (SC 3.3.2) – Some form fields lacked explicit labels. Remediation included adding descriptive labels and ensuring compatibility with assistive technologies.

All Level A issues are actively monitored and corrected as part of Typing Agent’s continuous accessibility roadmap. We provide ongoing accessibility audits, quarterly updates, and educator feedback loops to ensure that our platform remains compliant with WCAG and Section 508 requirements.

For additional details, please refer to our Accessibility Conformance Report (VPAT 2.4) and the EqualWeb Accessibility Evaluation Report (July 2023).

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content	Web: Partially Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent conforms to WCAG 2.0/2.1/2.2 Level A requirements for non-text content. Most non-text elements include descriptive alternative text. However, our 2023 EqualWeb Accessibility Evaluation identified a small number of missing or incomplete alt attributes on images and icons Electronic Documents: Most documentation provided to districts and schools (Privacy Policy, Terms of Use, DPAs, Accessibility Questionnaires) is distributed as accessible PDFs/Word files. Typing Agent follows accessibility best practices including proper heading structure, alt text for images, and tagged PDFs Equaweb-documents-guide . Some legacy documents may require remediation for full compliance, and these are being updated on a rolling basis. Software: As a cloud-based SaaS application, Typing Agent implements alt text and ARIA labels for interactive components. Occasional issues (e.g., form labels, decorative images without alt) have been identified through internal QA and third-party scans Web Accessibility Evaluation Re… . Corrective actions are ongoing, and remediation is prioritized to ensure screen reader users receive equivalent information. Authoring Tool: Typing Agent is an instructional SaaS platform and does not serve as an authoring tool for creating and publishing new web content. Therefore, this success criterion is not applicable in this context.
1.2.1 Audio-only and Video-only (Prerecorded)	Web: Partially Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent’s web application supports WCAG 2.0 Level A for non-text content. Most images, icons, and interactive elements have alternative text. Independent accessibility scans (EqualWeb, July 2023) identified a small number of missing or incomplete alt attributes, which have been corrected or are scheduled for remediation Electronic Documents: Typing Agent distributes policies, agreements, and guides as accessible PDFs/Word files. Documents are tagged with proper headings, lists, and alternate text where applicable. While current documents follow accessibility standards some legacy files may not fully conform and are being updated. Software: As a SaaS application, Typing Agent provides alternative text and ARIA roles to support screen readers. Occasional gaps (e.g., form field labeling or decorative images without alt) were noted in prior audits . These have been logged and corrected as part of Typing Agent’s accessibility roadmap.
1.2.2 Captions (Prerecorded)	Web: Partially Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides prerecorded instructional videos and multimedia with captions. Captions are available on the majority of content, supporting learners who are deaf or hard of hearing. A small number of legacy videos may not yet include captions, but all new video content is captioned at release, and older videos are being updated as part of our accessibility roadmap. Electronic Documents: Electronic documents provided by Typing Agent (e.g., Privacy Policy, Terms of Use, Data Privacy Agreements) are text-based and do not include prerecorded multimedia content requiring captions. Audio options can be enabled on the site to read the documents to users. Software: Within the Typing Agent SaaS platform, prerecorded instructional videos are delivered with captions. Where issues have been identified (e.g., captions missing in earlier content), remediation is underway to ensure consistent accessibility across all video assets. Authoring Tool: Typing Agent is not an authoring tool for creating or publishing multimedia content. Therefore, this success criterion does not apply.
1.2.3 Audio Description or Media Alternative (Prerecorded)	Web: Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent provides prerecorded instructional and curriculum videos that rely primarily on spoken content paired with on-screen text and visuals. For most videos, the essential information is conveyed through both narration and text, reducing the need for separate audio descriptions. A small number of legacy videos may not fully meet this standard. Enhancements and updates are part of Typing Agent’s ongoing accessibility improvements. Electronic Documents: Typing Agent distributes text-based electronic documents such as policies, agreements, and instructional guides. These documents do not contain prerecorded multimedia requiring audio description or media alternatives. Audio can be enabled thought the browser to support reading text. Software: Within the Typing Agent platform, instructional videos are supplemented with narration, text prompts, and visual reinforcement. This ensures users who cannot perceive certain visual cues can still access the content. Some earlier video assets may not have a dedicated media alternative or audio description track, but remediation efforts are ongoing to align with WCAG requirements.
1.3.1 Info and Relationships	Web: Partially Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent supports WCAG requirements for information and relationships by using proper semantic markup, heading structures, lists, and ARIA roles. This ensures that relationships between content and UI components are programmatically determinable for screen readers. Independent evaluations identified some isolated issues (e.g., incorrect heading levels, duplicate IDs, or missing associations between form fields and labels). These issues are logged and corrected as part of Typing Agent’s accessibility remediation cycle. Electronic Documents: Most Typing Agent documents (policies, agreements, guides) are produced with structured headings, lists, and tables tagged for accessibility. Older documents may lack consistent heading hierarchy or properly tagged tables, but remediation work is ongoing to align all materials with accessibility standards. Software: Within the Typing Agent SaaS platform, UI components are structured for accessibility, including headings, form labels, and relationships between interface elements. A few legacy interface components required remediation to improve ARIA roles and heading hierarchy. These updates are scheduled as part of ongoing accessibility improvements.
1.3.2 Meaningful Sequence	Web: Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent presents instructional content and navigation in a logical reading order that matches the visual sequence. Screen reader users can follow lessons, menus, and progress tracking in the correct sequence. Accessibility evaluations have occasionally identified minor sequencing issues (e.g., navigation elements read out of order, or misaligned tab order). These have been corrected or scheduled for remediation in Typing Agent’s accessibility improvement roadmap. Electronic Documents: Most Typing Agent documents are structured with headings and lists that support meaningful reading order. Some legacy PDFs may not have a fully tagged reading sequence, but updates are underway to ensure all documents have logical navigation order when used with assistive technologies. Software: In the SaaS platform, instructional flows and dashboards follow a meaningful sequence for both visual and non-visual users. Some interface components required adjustments to tab order and ARIA markup to ensure consistency for keyboard and screen reader users. These improvements are part of Typing Agent’s ongoing accessibility updates.
1.3.3 Sensory Characteristics	Web: Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent lessons and navigation do not rely solely on sensory characteristics (such as shape, color, size, or sound) to convey meaning or instructions. Instructions are supported with clear text labels and icons. Accessibility evaluations noted minor instances where instructions referenced only position (e.g., “see the button on the right”) without supplemental description. These are being updated to include non-sensory descriptors. Electronic Documents: Most documents use text-based instructions rather than relying solely on visual or sensory references. Older documents may contain some positional language (e.g., “see box below”), but remediation is ongoing to ensure instructions are understandable without relying on sensory cues. Software: Within the Typing Agent platform, activities and reports provide instructions with text and iconography that do not depend solely on color or location. Some legacy components contained instructions dependent on position or visual-only cues, and these are being revised as part of Typing Agent’s accessibility improvement roadmap.
1.4.1 Use of Color	Web: Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent does not rely on color alone to convey information, indicate actions, or differentiate elements. Instructions are supported with icons, text, or patterns to ensure usability for users with color vision deficiencies. Accessibility evaluations identified a few cases where color contrast or reliance on color as an indicator required improvement. These items were remediated or are in process as part of ongoing accessibility updates. Electronic Documents: Documents provided by Typing Agent generally use text-based formatting rather than color alone to convey meaning. Some older documents may contain color-reliant highlights (e.g., “fields in red”), and these are being updated with accessible text labels or alternative indicators. Software: In the SaaS platform, progress indicators and status alerts are paired with text or icons, not just color. In earlier versions, some elements relied heavily on color (e.g., red/green for correctness), but these have been supplemented with text and iconography to improve accessibility.
1.4.2 Audio Control	Web: Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent provides audio features within lessons, such as voice narration, sound effects, and text-to-speech. Users can control these features through on-screen settings, including volume adjustment, muting, and the ability to disable audio entirely. Some legacy audio clips may auto-play without a built-in pause/stop control, but current and future updates ensure audio can be paused or adjusted by the user. Electronic Documents: Typing Agent’s electronic documents (e.g., policies, agreements, guides) are static text-based files and do not contain embedded audio content requiring user control. Software: Within the Typing Agent platform, students and teachers can configure audio through system settings (voice over, narration speed, muting). Some earlier lesson formats lacked pause or disable controls, but these have been addressed or are scheduled for remediation in alignment with accessibility best practices.
2.1.1 Keyboard	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent fully supports keyboard accessibility. All functions can be operated using a keyboard without requiring a mouse. Students may use either an English QWERTY keyboard or a Spanish keyboard, both of which are supported by the platform. The program also offers one-handed typing lessons to support students with physical disabilities, ensuring inclusive access for diverse learners. Keyboard navigation, focus order, and lesson interactions are designed to meet WCAG accessibility requirements. Electronic Documents: Typing Agent’s electronic documents are provided as accessible text-based PDFs/Word files. They are not interactive applications requiring keyboard-only operation beyond standard PDF/Word reader accessibility features. Software: Within the Typing Agent SaaS platform, all lesson activities and navigation menus are designed for full keyboard use. Users can complete exercises, access settings, and navigate reports entirely via keyboard. In addition, Typing Agent includes one-handed keyboarding accommodations and adjustable target settings to support students with disabilities or special learning needs.
2.1.2 No Keyboard Trap	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent supports full keyboard navigation without trapping users in any component. All interactive elements, including menus, lesson activities, and reporting tools, allow users to move forward and backward using standard keyboard commands (e.g., Tab, Shift+Tab, arrow keys). If focus enters a component, it can always be exited using the keyboard alone. Software: Within the SaaS platform, Typing Agent’s design ensures no keyboard traps exist. Focusable elements are fully controllable and can be exited using the keyboard alone. Internal QA and third-party accessibility scans confirm that students and teachers can navigate lesson content, dashboards, and settings without risk of being locked in a particular interface component.
2.1.4 Character Key Shortcuts	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent does not implement single-key or character key shortcuts that could interfere with assistive technologies or create accessibility barriers. Keyboard interactions are designed around standard navigation keys (Tab, Shift+Tab, arrow keys, Enter, Spacebar) and lesson-specific typing inputs. If shortcuts are introduced in the future, they will be designed with the ability to be turned off or remapped, in compliance with WCAG 2.1 requirements. Software: Within the Typing Agent SaaS platform, lessons rely on deliberate typing exercises using standard keyboard input. No single-character shortcuts are enabled outside of typing lessons themselves. This prevents conflicts with screen readers or speech recognition software that may use similar commands.
2.2.1 Pause, Stop, Hide	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent supports pausing, stopping, and hiding of time-based activities. The program includes a pause sensor and stop sensor timer that allow students to pause or stop lessons when needed. Additionally, Typing Agent includes a hide keys feature while paused to prevent students from memorizing keys unfairly during breaks, maintaining both accessibility and instructional integrity. Software: Within the SaaS platform, Typing Agent integrates pause, stop, and hide features into lesson timers and practice activities. These controls ensure students with disabilities can manage timing requirements independently, while also preventing misuse (such as pausing to memorize keys). This aligns with WCAG 2.1 guidance for time-based media and timed interaction.
2.2.2 Timing Adjustable	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides adjustable timing options for lessons and assessments. Students can pause, stop, and resume activities, and teachers may configure classroom accessibility settings to allow extended time for students with specific needs. Software: Within the Typing Agent SaaS platform, timing in lessons and typing tests can be paused, stopped, or adjusted. Teachers may set accommodations at the classroom or individual student level, such as disabling placement tests, adjusting speed/accuracy targets, and enabling one-handed typing lessons. These settings provide flexibility for students who require additional time.
2.3.1 Three Flashes or Below Threshold	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent’s web application does not use flashing, strobing, or blinking content that exceeds the three-flash threshold. Lessons, games, and progress indicators are designed with smooth animations and transitions to prevent triggering seizures or physical reactions. Software: Within the SaaS platform, Typing Agent avoids the use of flashing elements in instructional games, dashboards, and assessments. Visual cues are provided through text, icons, or subtle animations that comply with WCAG requirements for seizure safety.
2.4.1 Bypass Blocks	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides navigation structures that allow users to move efficiently through content. Repeated blocks such as headers, menus, and dashboards can be bypassed using keyboard navigation. Skip links and structured headings are implemented across core areas of the application. Software: Within the SaaS platform, repeated elements such as menus and navigation bars can be bypassed using standard keyboard navigation and ARIA landmarks. Some older modules may not have full “skip to content” links but are included in Typing Agent’s accessibility roadmap.
2.4.2 Page Titled	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides descriptive page titles throughout the web application. Titles identify the purpose of the page (e.g., “Student Dashboard,” “Teacher Reports,” “Placement Test”) to support navigation and orientation for all users, including those using screen readers. Electronic Documents: Most Typing Agent documents include descriptive titles in document properties and visible headings. Some older PDFs or Word files may not have metadata titles correctly populated, and these are being remediated to align with accessibility standards. Software: Within the SaaS platform, all major sections and pop-up modules are labeled with clear headings or dialog titles
2.4.3 Focus Order	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent maintains a logical focus order that follows the visual sequence of content and supports efficient navigation with a keyboard. Students and teachers can tab through menus, lessons, and reports in a predictable order. Accessibility reviews identified a few isolated cases where focus order skipped or cycled incorrectly (e.g., in certain dashboard elements). These issues are tracked and being remediated as part of Typing Agent’s accessibility roadmap. Electronic Documents: Most Typing Agent documents use structured headings, tables, and tagged reading order to maintain meaningful focus for assistive technologies. Software: Within the SaaS platform, all interactive modules, lesson activities, and dialogs are designed with consistent focus management. Focus order proceeds in a logical sequence without trapping the user. In rare cases, pop-up dialogs required updates to ensure focus returned to the correct element once closed; these adjustments are underway.
2.4.4 Link Purpose (In Context)	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent ensures that most links are descriptive and provide clear context about their purpose (e.g., “View Reports,” “Start Lesson,” “Teacher Guide”). This helps users, including those with screen readers, understand where each link will lead without relying solely on surrounding text. Electronic Documents: Most Typing Agent documents provide descriptive hyperlinks that clearly indicate their purpose. Some older documents may contain non-descriptive links (e.g., raw URLs or “here” references), but these are being updated to follow best practices for accessible link text. Software: Within the SaaS platform, in-app links and navigation items are labeled to indicate their destination or function
2.5.1 Pointer Gestures	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent does not require complex multipoint or path-based pointer gestures (such as pinch, swipe, or drag) to operate core features. All functionality, including lessons, navigation, and reports, can be completed with simple pointer input (click/tap) or keyboard commands. This ensures that students using assistive technology or alternative input devices can access the program without barriers. Software: Within the Typing Agent SaaS platform, pointer gestures are limited to basic single-click or tap actions. No curriculum features, assessments, or dashboards depend on multipoint gestures, ensuring compliance with WCAG 2.1 requirements.
2.5.2 Pointer Cancellation	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent ensures that functions triggered by a single pointer input (e.g., click or tap) are either reversible, require confirmation, or are not executed until the user completes the action. This prevents accidental activations. For example, starting a lesson, submitting a test, or navigating to another page requires a deliberate click or tap, and students have options to cancel or return if needed. Software: Within the SaaS platform, actions such as starting lessons, ending tests, or saving settings are not finalized on initial pointer-down events. Instead, they require a completed click/tap or a confirmation step. This design aligns with WCAG guidance and reduces unintended activations for users with motor impairments.
2.5.3 Label in Name	Web: Partially Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent’s user interface components, such as buttons and form controls, are labeled so that the visible text matches the programmatic label. This ensures that screen reader users and voice input users can activate controls using the same spoken or visible name. Accessibility audits identified a few isolated cases where visible labels did not fully match programmatic names (e.g., icon-only buttons). These are being remediated to ensure full alignment with WCAG requirements. Electronic Documents: Most Typing Agent documents use clear headings and labels that match references in the content. Some older PDFs may include diagrams or tables where labels were not tagged properly, and these are being updated to improve compatibility with assistive technologies. Software: Within the SaaS platform, most controls (e.g., “Start Lesson,” “View Reports”) use consistent visible and programmatic labels. A few legacy modules used generic or non-matching labels, which could affect screen reader or voice command accuracy. These are being corrected as part of Typing Agent’s accessibility roadmap.
2.5.4 Motion Actuation	Web: Not Applicable Electronic Documents: Not Applicable Software: Not Applicable Authoring Tool: Not Applicable	Web: Typing Agent does not rely on motion actuation (such as device shaking, tilting, or gesturing) to operate any functionality. All features, including lessons, navigation, and assessments, can be completed using standard keyboard, mouse, or touch input. This ensures accessibility for users who cannot perform motion-based gestures. Software: Within the SaaS platform, no curriculum activity, assessment, or dashboard requires motion-based input. All interactions can be completed using traditional input methods (keyboard, mouse, touchscreen tap). This ensures compliance with WCAG motion actuation requirements.
3.1.1 Language of Page	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent specifies the default language of its web pages in code to ensure compatibility with screen readers and assistive technologies. The platform supports English and Spanish, allowing students and teachers to access content in either language depending on account and classroom configuration. Electronic Documents: Most Typing Agent documents (e.g., policies, guides, agreements) are authored with proper language settings defined in the file properties. Current documents are published in English; some translated versions are available in Spanish. Older files may lack explicitly set language metadata but are being remediated. Software: Within the SaaS platform, Typing Agent provides English and Spanish interfaces. Language is programmatically defined to support assistive technologies, ensuring correct pronunciation and reading by screen readers.
3.2.1 On Focus	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent ensures that when a user interface component receives focus, it does not automatically trigger a change of context (such as unexpected page navigation, form submission, or pop-ups). Focus management is designed so students and teachers can navigate menus, lessons, and dashboards predictably. Software: Within the SaaS platform, focus events (e.g., tabbing into a button, field, or menu) do not trigger unexpected actions. Any context changes (such as opening a dialog or starting a lesson) occur only after explicit user activation (e.g., pressing Enter, Space, or clicking). This prevents unintended disruptions for keyboard and assistive technology users.
3.2.2 On Input	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent ensures that input changes (such as selecting an option, typing in a field, or adjusting settings) do not automatically trigger unexpected changes of context like page reloads or navigation. Users maintain control over when inputs are submitted, usually through an explicit action (e.g., clicking a button). Software: Within the Typing Agent SaaS platform, user inputs (such as lesson settings, profile updates, or report filters) do not cause unexpected navigation or major context changes. Any input that leads to a new view (e.g., generating a report) requires explicit user action. Some older modules may have limited auto-refresh behaviors, which are scheduled for updates to align with WCAG.
3.3.1 Error Identification	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent identifies input errors in forms and activities by providing clear error messages. For example, if a required field is left blank or invalid credentials are entered, the platform presents text-based feedback explaining the issue. Software: Within the Typing Agent SaaS platform, error handling is built into login forms, placement tests, and administrative tools. Most errors are flagged with descriptive messages. A small number of older interface elements may need enhanced text descriptions to ensure full clarity for screen reader users; these updates are included in Typing Agent’s accessibility roadmap.
3.3.2 Labels or Instructions	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides labels and instructions for input fields, lesson activities, and navigation elements to guide users in completing tasks. For example, login fields are labeled with “Username” and “Password,” and placement test instructions are presented clearly before beginning. Electronic Documents: Most Typing Agent documents provide clear instructions when requesting user actions (e.g., setup guides, admin manuals). Software: Within the SaaS platform, fields and interactive controls are labeled with meaningful names, and instructions are presented before or during activities.
4.1.1 Parsing	Web: Partially Supports Electronic Documents: Not Applicable Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent’s web application is developed using valid HTML and ARIA markup to ensure compatibility with assistive technologies. Pages are checked to avoid duplicate IDs, missing end tags, and other parsing errors that may impact accessibility. Accessibility scans have occasionally identified isolated markup issues (such as heading nesting errors or duplicate attributes). These are tracked and remediated as part of Typing Agent’s continuous accessibility improvement cycle. Software: Within the SaaS platform, Typing Agent’s codebase follows accessibility standards for structure and syntax. Occasional validation errors may occur in legacy modules, but these are corrected in updates to ensure assistive technology reads elements reliably.
4.1.2 Name, Role, Value	Web: Partially Supports Electronic Documents: Not Applicable Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent assigns accessible names, roles, and values to interactive components such as buttons, menus, input fields, and reports. This allows assistive technologies to accurately convey what each element is and how it can be used. Accessibility audits identified some legacy issues (e.g., unlabeled buttons, ARIA roles not fully defined, or form controls missing explicit values). These are being remediated as part of Typing Agent’s accessibility roadmap to ensure all interactive elements are programmatically determinable. Software: Within the SaaS platform, Typing Agent provides programmatic labels and ARIA support for all major components. Buttons, form inputs, and status indicators generally expose correct names, roles, and values to assistive technologies. A few older modules required updates to ensure ARIA roles and accessible names were fully aligned with WCAG standards; these updates are ongoing.

Table 2: Success Criteria, Level AA

Notes:

Web Typing Agent substantially supports WCAG 2.0/2.1 Level AA requirements. Independent evaluations (EqualWeb, July 2023) and internal audits identified a limited set of Level AA issues, most of which are already addressed or in progress for remediation:

Contrast (SC 1.4.3) – Some legacy pages included low-contrast text or icons that did not fully meet the 4.5:1 ratio. These items are being updated to meet or exceed minimum contrast standards.

Headings and Relationships (SC 1.3.1 / 2.4.6) – A small number of pages used non-semantic formatting instead of proper heading structures, impacting screen reader navigation. Updates are being made to align headings with semantic HTML.

Consistent Navigation (SC 3.2.3) – In certain legacy modules, navigation order or menu labeling was inconsistent across pages. These are being standardized to provide predictable user experience.

Resize Text / Reflow (SC 1.4.4, SC 1.4.10) – Most text resizes correctly without loss of content or function, though some older lesson components required layout adjustments to better support zoom and reflow.

Electronic Documents Most distributed documents (Privacy Policy, Terms of Use, Data Privacy Agreements) are accessible and tagged. However, some older PDFs do not fully support structured headings, tagged tables, or contrast requirements. These are being remediated as part of an accessibility update process.

Software Within the SaaS platform, nearly all functions conform to Level AA. A few legacy interface components required remediation for:

Link Purpose in Context (SC 2.4.4 / 2.4.9) – Occasional generic link text such as “Click here.”

Focus Visible (SC 2.4.7) – In rare cases, focus indicators were insufficiently visible. These are being updated to provide strong visual cues.

Authoring Tool Not applicable. Typing Agent is not an authoring tool for creating or publishing new content.

Criteria	Conformance Level	Remarks and Explanations
1.2.4 Captions (Live)	Web: Not Applicable Electronic Documents: Not Applicable Software: Not Applicable Authoring Tool: Not Applicable	Web: Typing Agent’s web platform does not deliver live multimedia streams. All instructional videos and audio resources are prerecorded and captioned, so this success criterion does not apply.
1.2.5 Audio Description (Prerecorded)	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides prerecorded instructional videos where essential information is conveyed through both narration and on-screen text, reducing the need for separate audio description. For some older videos, additional audio description may not yet be available. Updates and replacements are being rolled out to ensure content meets WCAG 2.0/2.1 Level AA requirements. Software: Within the Typing Agent SaaS platform, instructional content is designed with narration and supporting text to convey meaning. Most new videos meet accessibility standards without requiring additional audio description. Some legacy media may not yet include dedicated audio description tracks, but remediation is planned as part of Typing Agent’s accessibility improvement cycle.
1.3.4 Orientation	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent’s web application supports both portrait and landscape orientations. The platform does not restrict content display to a single orientation, allowing students to use desktops, laptops, tablets, or other devices in whichever orientation is most accessible to them. Software: Within the Typing Agent SaaS platform, lessons, dashboards, and reports reflow appropriately when viewed in either portrait or landscape orientation. This ensures that users with mobility limitations who cannot rotate a device can still fully access the program.
1.3.5 Identify Input Purpose	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent labels most input fields with clear programmatic identifiers that allow assistive technologies to determine their purpose (e.g., login fields, profile settings, classroom creation forms). Some legacy forms may not yet fully implement ARIA or autocomplete attributes that support automatic identification of input purpose. These gaps are being addressed as part of Typing Agent’s accessibility improvement plan. Software: Within the SaaS platform, form fields and interactive inputs are generally labeled and identifiable to assistive technologies. A few older modules may lack full semantic labeling for certain fields (e.g., profile settings or dropdowns). These are scheduled for remediation to meet WCAG 2.1 standards.
1.4.3 Contrast (Minimum)	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides text and interface elements that generally meet or exceed the required 4.5:1 contrast ratio for normal text and 3:1 ratio for large text. Independent accessibility scans identified a small number of legacy elements (such as button labels, iconography, or instructional text) with insufficient contrast against background colors. These are being remediated as part of Typing Agent’s accessibility updates to ensure compliance across all pages. Electronic Documents: Typing Agent documents (policies, agreements, guides) use color schemes with sufficient contrast. Software: Within the SaaS platform, the majority of text, icons, and controls meet minimum contrast requirements
1.4.4 Resize text	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent supports text resizing up to 200% without loss of content or functionality. The platform’s responsive design allows students and teachers to zoom in using browser settings while maintaining readability and usability across lessons, menus, and reports. Electronic Documents: Typing Agent’s electronic documents (PDFs/Word files) are authored with accessible text properties. Users can zoom or resize text using standard reader tools without loss of information or function. Software: Within the SaaS platform, all instructional content, dashboards, and reports are designed to remain usable when text is resized. Content reflows properly without requiring horizontal scrolling, ensuring students who rely on magnification can fully participate.
1.4.5 Images of Text	Electronic Documents: Not Applicable Software: Not Applicable Authoring Tool: Not Applicable	Web: Typing Agent does not rely on images of text to convey instructional content or navigation. All core text is presented as actual text that can be resized, restyled, or read by assistive technologies. Images of text are used only for decorative or branding purposes (e.g., logos), where accessibility impact is minimal. Software: Typing Agent does not rely on images of text to convey instructional content or navigation. All core text is presented as actual text that can be resized, restyled, or read by assistive technologies. Images of text are used only for decorative or branding purposes (e.g., logos), where accessibility impact is minimal.
1.4.10 Reflow	Web: Partially Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent’s web platform is responsive and designed to reflow content when users zoom or resize windows. Pages can be viewed without requiring two-dimensional scrolling at 400% zoom in most cases. A few legacy lesson modules or dashboards may still require horizontal scrolling at higher magnifications, and these are scheduled for remediation. Electronic Documents: Most Typing Agent documents (PDFs/Word files) reflow properly in standard readers when zoomed. Some older PDFs, created before accessibility guidelines were standardized, may not reflow fully. Updated versions are being rolled out to ensure compliance. Software: Within the SaaS platform, content such as lesson text, dashboards, and reports adjusts responsively to device size and zoom levels. In isolated cases, older interface elements may require horizontal scrolling, and these are being addressed as part of Typing Agent’s accessibility roadmap.
1.4.11 Non-text Contrast	Web: Partially Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent generally ensures that essential non-text elements (such as icons, controls, focus indicators, and graphical objects used to convey meaning) meet the required 3:1 contrast ratio against adjacent colors. Accessibility audits have flagged a small number of legacy icons, buttons, and focus outlines with insufficient contrast. These issues are being remediated to align with WCAG standards and improve usability for low-vision users. Electronic Documents: Most Typing Agent documents use sufficient contrast for diagrams, shapes, and non-text elements. Some older PDFs may contain screenshots or graphical elements that do not meet the minimum 3:1 contrast requirement. These are being updated during accessibility reviews. Software: Within the SaaS platform, interactive controls (e.g., buttons, toggles, progress indicators) are designed to meet non-text contrast requirements. A few earlier interface modules included icons or focus indicators with insufficient contrast; these are scheduled for updates as part of Typing Agent’s accessibility roadmap.
1.4.12 Text Spacing	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent supports user-adjustable text spacing without loss of content or functionality. When line height, paragraph spacing, letter spacing, or word spacing are adjusted to WCAG-recommended values, the platform’s instructional text, menus, and dashboards remain readable and usable. Electronic Documents: Typing Agent documents (PDFs/Word files) support adjustments to text spacing in standard readers. Some older documents may not fully preserve formatting when spacing is customized, but updated versions are being created to ensure full accessibility. Software: Within the Typing Agent SaaS platform, lesson content, reporting tools, and navigation elements support custom text spacing without overlap, truncation, or loss of function. This ensures accessibility for users who rely on increased spacing for readability.
1.4.13 Content on Hover or Focus	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides tooltips, dropdowns, and other interactive elements that appear on hover or focus. In most cases, this additional content is dismissible, hoverable, and persistent until the user removes focus, as required by WCAG. Accessibility evaluations identified some legacy tooltips and hover states that did not remain available long enough for assistive technology users to access them. These components are being updated to ensure compliance with WCAG 2.1 requirements. Software: Within the SaaS platform, hover or focus content such as dropdown menus, tooltips, and instructional hints generally follow accessibility best practices. A small number of older modules had hover-only content without equivalent focus functionality. These are being remediated as part of Typing Agent’s accessibility roadmap.
2.4.5 Multiple Ways	Web: Supports Electronic Documents: Partially Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides multiple ways for users to locate content and complete tasks. Students and teachers can access lessons, reports, and settings through navigation menus, dashboards, and search/filter tools. This ensures that essential functions can be reached through more than one navigation path. Electronic Documents: Most Typing Agent documents include a table of contents, headings, and bookmarks to provide multiple navigation paths. Some older PDFs may lack complete tagging or bookmarks, but these are being remediated to improve accessibility. Software: Within the SaaS platform, users can locate lessons and resources through multiple methods (e.g., dashboard links, class-level navigation, or teacher-assigned tasks). Reports and analytics can be accessed by browsing menus or using filters to quickly locate specific data.
2.4.6 Headings and Labels	Web: Partially Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent uses descriptive headings and labels to organize content and guide users. Lesson pages, dashboards, and reports include headings that describe their purpose, and form fields are labeled to assist all users, including those using screen readers. Accessibility reviews identified some legacy pages where heading levels were skipped or labels were too generic. These are being updated to improve semantic accuracy and clarity. Electronic Documents: Most Typing Agent documents use properly structured headings and descriptive labels in text and tables. Some older PDFs may lack consistent heading tagging, but remediation is underway to align all documents with accessibility best practices. Software: Within the SaaS platform, headings and labels are generally descriptive and programmatically exposed to assistive technologies. A few older modules contained non-descriptive form labels or missing ARIA attributes. These are being corrected as part of Typing Agent’s accessibility roadmap.
2.4.7 Focus Visible	Web: Supports Electronic Documents: Not Applicable Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent provides a visible focus indicator for interactive elements such as links, buttons, and form fields, allowing keyboard users to track their location on the page. Software: Within the SaaS platform, most interactive components display a clear focus ring or highlight when navigated by keyboard. A few older modules lacked consistent focus styling, but these are being updated as part of Typing Agent’s accessibility roadmap.
3.1.2 Language of Parts	Web: Partially Supports Electronic Documents: Partially Supports Software: Partially Supports Authoring Tool: Not Applicable	Web: Typing Agent primarily supports English and Spanish. For multilingual content, most text is programmatically marked so assistive technologies can switch pronunciation rules as needed. Some legacy lessons or UI strings may not have language attributes properly applied at the part level; these are being remediated to ensure screen readers correctly announce mixed-language content. Electronic Documents: Most Typing Agent documents are authored in English, with some Spanish translations available. In some older files, inline foreign-language terms may not have explicit language tagging, which could affect pronunciation for screen readers. Updated versions are being produced to include proper tagging. Software: Within the SaaS platform, interface text is localized for English and Spanish. Most content is correctly tagged for language. A few legacy modules may not fully expose language metadata at the part level, but updates are in progress to align with WCAG requirements.
3.2.3 Consistent Navigation	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides consistent navigation structures across its platform. Core menus, dashboards, and navigation bars appear in a uniform order on lesson pages, student dashboards, and teacher/admin portals. Accessibility audits identified a few legacy modules where navigation links were not in the same sequence as other pages. These are being updated to ensure full consistency across the platform. Electronic Documents: Typing Agent documents (guides, agreements, policies) use consistent layouts and navigation elements such as headings and tables of contents. Some older PDFs lacked consistent sectioning, but these are being remediated to align with best practices. Software: Within the SaaS platform, navigation menus, lesson flows, and reporting tools are structured consistently across most modules. A few older interfaces had menu variations or inconsistent labeling. These issues are logged in Typing Agent’s accessibility roadmap and are being corrected.
3.2.4 Consistent Identification	Web: Supports Electronic Documents: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent uses consistent identification for interactive components across the platform. Buttons, links, and icons that serve the same function are labeled and presented consistently (e.g., the “Start Lesson” button, report icons, and navigation menus). Electronic Documents: Typing Agent documents apply consistent labels and terminology across headings, sections, and references. Software: Within the SaaS platform, controls and components maintain consistent identification across modules. A few legacy modules used slightly different terminology or icons for the same actions, which could impact recognition for screen reader or keyboard-only users.
3.3.3 Error Suggestion	Web: Supports Electronic Documents: Not Applicable Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent provides users with suggestions to correct input errors where possible. For example, login errors prompt users with clear text such as “Invalid username or password. Please try again.” Placement test errors and form submissions provide instructions to fix missing or incorrect entries. Software: Within the SaaS platform, many forms and input fields (e.g., profile setup, classroom management, report filters) display descriptive error messages that guide users in correcting mistakes.
3.3.4 Error Prevention (Legal, Financial, Data)	Web: Not Applicable Electronic Documents: Not Applicable Software: Not Applicable Authoring Tool: Not Applicable	Web: Typing Agent does not involve legal commitments or financial transactions within the student/teacher application. For administrative purchases and subscription management, confirmation steps are provided before finalizing transactions to help prevent errors. Where user data is entered (e.g., student rosters, account details), the platform allows for review, correction, or confirmation before submission. Software: Typing Agent does not involve legal commitments or financial transactions within the student/teacher application. For administrative purchases and subscription management, confirmation steps are provided before finalizing transactions to help prevent errors. Where user data is entered (e.g., student rosters, account details), the platform allows for review, correction, or confirmation before submission.
4.1.3 Status Messages	Web: Supports Software: Supports Authoring Tool: Not Applicable	Web: Typing Agent communicates status messages to users through in-app notifications (e.g., lesson completion, error alerts, or saved changes). These messages are programmatically exposed so that screen readers can announce them without requiring focus changes. In addition, Typing Agent maintains a public status page where administrators and educators can check system health, known issues, and ticket updates. A few legacy in-app notifications may not have been fully coded for screen reader announcement, and these are being remediated. Software: Within the SaaS platform, status messages (e.g., “Student added successfully,” “Settings saved,” “Invalid password”) are generally presented visually and programmatically so assistive technologies can detect them. Some older modules may rely on visual-only cues, which are being updated to include ARIA live regions or equivalent methods for accessibility.

Table 3: Success Criteria, Level AAA

Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Notes:

Typing Agent substantially supports accessibility across all Functional Performance Criteria (302.1–302.9). Most barriers identified are tied to legacy content or older documents, not core platform functionality.

Barriers Noted

Blind/Low Vision Users: Occasional issues with low-contrast text/icons, skipped heading structures, or faint focus indicators in legacy modules.

Deaf/Hard of Hearing Users: A small number of older prerecorded videos lack captions or complete text alternatives.

Motor Disabilities: Some legacy drag-and-drop activities and smaller target sizes may present challenges, though all essential functions are keyboard accessible and supported with one-handed typing lessons.

Cognitive Disabilities: A few legacy instructions rely on sensory or positional language (e.g., “button on the right”), which can cause confusion.

Accessibility Features

Keyboard Access: Full support, including English QWERTY, Spanish, and one-handed typing lessons.

Customizable Timing: Pause, stop, hide, and extended-time options support equitable participation.

Redundancy in Feedback: Information never depends on color or sound alone—text and visual cues are always provided.

Responsive Design: Text resize, reflow, and multiple device orientations are supported.

Language Options: Full platform available in English and Spanish with programmatic language tagging.

Summary While minor barriers exist in legacy components, they do not prevent users with disabilities from accessing Typing Agent’s core lessons, assessments, and reports. The platform’s accessibility roadmap ensures these issues are actively remediated, reflecting Typing Agent’s ongoing commitment to equitable access for all learners.

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Supports	Typing Agent is designed to be accessible for users who are blind or have no vision. The platform supports: Screen Reader Compatibility: The application uses semantic HTML, ARIA roles, and programmatic labels to ensure that menus, lessons, forms, and navigation are accessible to JAWS, NVDA, and VoiceOver users. Keyboard Navigation: All core functionality is operable via keyboard alone, with clear focus order and visible indicators. One-handed typing lessons further extend accessibility to students with motor and vision-related needs. Status Messages: System notifications and in-app alerts are coded with ARIA live regions to ensure screen readers announce updates without requiring focus shifts. Alt Text and Non-Text Content: Instructional images and icons include descriptive alternative text, enabling screen readers to convey meaning. Decorative images are marked appropriately to avoid distraction. Known Limitations / Barriers A few legacy modules contained unlabeled buttons or incomplete ARIA attributes, which could create navigation difficulties for blind users. Some status messages and hover-only tooltips were not programmatically exposed to assistive technologies. These issues are being remediated in ongoing accessibility updates.
302.2 With Limited Vision	Partially Supports	Typing Agent provides strong accessibility features for users with limited vision: Contrast and Visibility: Most text and controls meet WCAG 2.1 AA contrast requirements. Ongoing updates address isolated low-contrast icons or text in legacy modules. Text Resizing and Reflow: The platform supports text resizing up to 200% and reflow up to 400% without loss of content or functionality. This helps users who rely on magnification. Orientation and Responsiveness: Lessons and dashboards reflow properly across device orientations (portrait/landscape), ensuring usability on desktops, laptops, and tablets. Non-Text Contrast: Essential icons, controls, and focus indicators are being updated to meet the required 3:1 ratio for low-vision accessibility. Customization: Users can adjust browser zoom, device settings, and use assistive overlays without breaking the layout or lesson flow. Known Limitations / Barriers A small number of legacy pages may still require horizontal scrolling at higher magnifications (400%). Older PDFs distributed before 2023 may include diagrams or screenshots with insufficient color contrast. Some focus indicators in legacy modules were faint, making them harder to detect for low-vision users. These are scheduled for remediation. Impact Users with limited vision may experience reduced readability in rare cases of low-contrast text/icons or extra navigation effort when zooming in legacy modules. However, all core curriculum, navigation, and reporting remain operable with magnification and adjusted text spacing. Commitment Typing Agent actively remediates accessibility issues flagged in audits (EqualWeb 2023, internal QA). Enhancements to non-text contrast, reflow, and focus visibility are part of quarterly development sprints to ensure usability for low-vision users.
302.3 Without Perception of Color	Supports	Typing Agent is designed so that no functionality or instructional content depends on color alone: Instructions and Feedback: Correct/incorrect responses are indicated with both color and text/icons, ensuring students who are color blind or have no color perception can still interpret results. Icons and Status Indicators: Progress indicators and dashboard elements pair color with shape, text, or iconography for redundancy. Curriculum Design: Lessons avoid reliance on color-based instructions (e.g., “select the red key”), instead using text-based guidance and visual cues. Known Limitations / Barriers Some legacy modules used red/green status highlights without sufficient text alternatives, which could impact users without color perception. These are being updated to include text or icon-based reinforcement. Older documents may contain visual diagrams or charts where distinctions are based only on color. Updated documents include labels or patterns to address this gap. Impact Users with no color perception may occasionally encounter difficulty distinguishing progress markers or interpreting diagrams in older content. However, all essential functionality—such as typing practice, reporting, and navigation—remains accessible through text and icons. Commitment Typing Agent ensures that all new development follows the principle of never relying on color alone. Legacy content flagged in audits is being remediated to include redundant indicators, benefiting students and teachers with color vision deficiencies.
302.4 Without Hearing	Partially Supports	Typing Agent ensures students who are deaf or hard of hearing can fully access instructional content and feedback: Captions on Prerecorded Media: Most instructional videos include captions, allowing deaf and hard-of-hearing students to access the same information as their peers. Text-Based Instructions: All critical directions, typing prompts, and progress feedback are provided in text, not dependent on audio. Sound Effects: Audio cues in lessons (such as success tones) are paired with visual indicators (icons, text changes, or animations) so that meaning is conveyed without hearing. Known Limitations / Barriers A small number of legacy prerecorded videos may lack captions or have incomplete captions. These are being updated in alignment with Typing Agent’s accessibility roadmap. Live audio content is not part of Typing Agent, so real-time captioning (SC 1.2.4) does not apply. Impact Students without hearing may face occasional limitations in older videos where captions are not yet available. However, all core curriculum and assessments remain accessible through text-based prompts and visual feedback. Commitment Typing Agent continuously expands caption coverage on video content and ensures all new multimedia is captioned at release. Accessibility audits include reviews of caption quality and coverage to improve consistency.
302.5 With Limited Hearing	Partially Supports	Typing Agent supports students and educators with partial hearing loss by ensuring key content is accessible in multiple formats: Captions on Multimedia: Most prerecorded instructional videos include captions, supporting users with limited hearing who may rely on text reinforcement. Text-Based Reinforcement: All essential instructions, test prompts, and lesson feedback are available as on-screen text in addition to optional sound effects. Visual Feedback: Progress indicators, success/error messages, and alerts use visual cues (icons, animations, text) so meaning is not dependent on audio alone. Adjustable Audio Settings: Lesson sounds can be muted or adjusted, reducing dependency on hearing-based feedback. Known Limitations / Barriers Some older video assets may not yet include high-quality captions, limiting accessibility for students with partial hearing. These are being updated in Typing Agent’s accessibility roadmap. Audio-only cues in legacy lessons are always paired with text in current builds, but in rare cases, text alternatives may need refinement. Impact Users with limited hearing may occasionally encounter difficulty when captions are incomplete or unavailable in legacy media. However, all essential functionality and instructional flows remain accessible through text and visual alternatives. Commitment Typing Agent ensures that all new multimedia is published with captions and that older materials are being remediated. Feedback from educators is incorporated to continuously improve support for students with hearing loss.
302.6 Without Speech	Supports	Typing Agent does not require speech input for any functionality. All instructional activities, navigation, and administrative features are operable using keyboard, mouse, or touch input, making the platform fully accessible to students and educators without speech. No Voice Commands Required: Lessons, tests, and dashboards rely on typing, clicking, or tapping—never on spoken input. Accessible Communication: Student progress, feedback, and reports are delivered through text and visual indicators, not verbal interaction. Integration with Assistive Tech: Users who rely on screen readers, alternative input devices, or switch controls can complete all tasks without speech. Known Limitations / Barriers None. Since Typing Agent is built around text-based input, lack of speech capability does not create a barrier to learning or navigation. Impact Students and educators who cannot use speech, or who use speech alternatives such as AAC (Augmentative and Alternative Communication) devices, experience no accessibility barriers in Typing Agent. Commitment Typing Agent will continue ensuring that all new features remain accessible without reliance on speech input. Accessibility testing includes validation of operability without speech or voice-activated technologies.
302.7 With Limited Manipulation	Partially Supports	Typing Agent is designed to support students and educators with limited dexterity or fine motor control: Keyboard Accessibility: All functions are operable through the keyboard alone, without requiring precise mouse movements. One-Handed Typing Lessons: Typing Agent includes specialized curricula for one-handed typing, allowing students with limited hand mobility to develop typing proficiency. Pause/Stop/Hide Features: Timed activities include controls for pausing, stopping, or hiding keys, allowing students with slower input speeds or motor impairments to participate equitably. Alternative Input Compatibility: The platform is compatible with switch devices, alternative keyboards, and other assistive input tools since it follows standard browser input models. Known Limitations / Barriers Some drag-and-drop activities in older modules may present challenges for users with limited manipulation. Alternative formats or simplified navigation paths are being implemented where needed. Certain small interactive targets in legacy dashboards may not fully meet modern target size guidelines. These are being updated for easier activation. Impact Students with limited manipulation may experience difficulty completing drag-and-drop exercises or selecting small buttons in older modules. However, all essential instructional content and navigation are accessible through keyboard-only interaction, ensuring equitable participation. Commitment Typing Agent prioritizes inclusive design for students with motor impairments. New development avoids drag-only interactions and ensures adequate target sizes, while legacy components are being remediated to align with WCAG 2.1 and Section 508 standards.
302.8 With Limited Reach and Strength	Supports	Typing Agent accommodates users with limited reach and strength by ensuring that interaction does not depend on extended physical effort: Keyboard-Only Access: All features can be operated via keyboard without requiring sustained or extended mouse use. One-Handed Typing Lessons: Specialized lessons allow students with limited mobility in one hand or arm to participate fully. Minimal Physical Demand: Core activities involve standard keystrokes or single-click interactions, avoiding prolonged holding, pinching, or dragging gestures. Adjustable Timing: Lesson timers can be paused, stopped, or extended, reducing physical strain from timed interactions. Known Limitations / Barriers None significant. While drag-and-drop activities in some legacy modules may be less optimal for users with limited reach, equivalent keyboard navigation paths exist. Impact Students with limited reach and strength can successfully access lessons, assessments, and dashboards without undue fatigue or physical demand. Commitment Typing Agent’s design philosophy prioritizes inclusive access for students with diverse physical abilities. Development reviews specifically assess physical effort requirements to ensure compliance with WCAG 2.1 and Section 508.
302.9 With Limited Language, Cognitive, and Learning Abilities	Partially Supports	A few older videos lack captions or text alternatives, which could reduce comprehension for students who rely on multimodal reinforcement. Complex data dashboards may require teacher or admin support for students with significant cognitive disabilities. Impact Students with language or learning disabilities may need additional scaffolding when using certain legacy materials or dashboards. However, core typing lessons, gamified learning modules, and customizable settings ensure equitable access and flexibility for diverse learners. Commitment Typing Agent continues to refine instructions, reduce reliance on sensory-only directions, and expand multimodal accessibility features. Feedback from educators and accessibility audits directly inform enhancements for students with cognitive and learning disabilities.

Chapter 4: Hardware

Chapter 5: Software

Notes:

Typing Agent is a web-based instructional SaaS platform accessed entirely through standard web browsers (Chrome, Edge, Safari, Firefox). Because it is not a desktop or stand-alone application, the requirements in this section do not apply.

All accessibility requirements are addressed in Tables 1, 2, and 3 of the VPAT/OpenACR, covering WCAG 2.0/2.1 A and AA success criteria.

Support Commitment: Typing Agent is committed to working directly with schools and districts to address any accessibility features that are critical for their students. If a need arises that is not fully addressed in this report, our development and support teams will collaborate with the organization to ensure an equitable solution.

Criteria	Conformance Level	Remarks and Explanations
502.2.1 User Control of Accessibility Features	Supports	Typing Agent supports user control of accessibility features by ensuring that platform functionality does not interfere with or override assistive technologies provided by the operating system, browser, or device: Assistive Technology Compatibility: The platform is compatible with screen readers (JAWS, NVDA, VoiceOver), magnifiers, switch devices, and other accessibility tools. Keyboard-Only Operation: All functions can be performed via keyboard alone, allowing users to rely on their preferred access method. User-Controlled Audio: Students and teachers can mute or adjust lesson audio independently; the platform does not override system-level sound or accessibility settings. Adjustable Timing and Visuals: Lesson timers can be paused, stopped, or extended, and students can hide key prompts while paused to prevent unfair memorization while still retaining control. System Settings Respect: Typing Agent respects user-defined OS/browser accessibility features (e.g., high-contrast mode, text enlargement) without disabling them. Commitment The platform is designed to integrate with, not replace, device-level accessibility tools. Typing Agent conducts testing with common assistive technologies to ensure consistent support and avoid conflicts with user-controlled accessibility settings. Would you like me to move on to 502.2.2: No Disruption of Accessibility Features next?
502.2.2 No Disruption of Accessibility Features	Supports	Typing Agent does not disrupt, disable, or interfere with accessibility features provided by the operating system, browser, or assistive technologies: System-Level Compatibility: The platform respects user-selected OS/browser accessibility settings such as high-contrast mode, text enlargement, sticky keys, and screen readers. Assistive Technology Integration: Typing Agent integrates smoothly with JAWS, NVDA, VoiceOver, ZoomText, and other tools without blocking or overriding their functions. Non-Interference with Input Methods: Alternative input devices (switches, adaptive keyboards, touchscreens) function without disruption in all lessons and dashboards. Audio and Visual Features: Platform sound effects, animations, and visual cues are supplementary and do not disable or conflict with system-level accessibility adjustments. Commitment Typing Agent’s development standards include compatibility testing with major accessibility tools to ensure the platform complements, rather than interferes with, user-controlled features. Ongoing QA reviews confirm that updates do not negatively impact assistive technology operation.
502.3.1 Object Information	Partially Supports	Typing Agent exposes object information—including role, state, name, and value—to assistive technologies to ensure accessibility for screen reader and alternative input users: Semantic Markup and ARIA Roles: The platform uses semantic HTML and ARIA attributes to programmatically identify buttons, form fields, links, and interactive elements. Accessible Labels: Most controls are given meaningful labels so screen readers can announce their purpose and state (e.g., “Start Lesson button,” “Student Added successfully”). Dynamic State Announcements: Status changes (e.g., completion messages, error alerts) are programmatically exposed using ARIA live regions. Known Limitations / Barriers A few legacy modules included unlabeled icons, missing ARIA attributes, or non-standard roles, making it harder for screen readers to interpret object information. Some older pop-up dialogs did not consistently announce state or focus changes to assistive technologies. Impact Users relying on screen readers may occasionally encounter objects in legacy interfaces that are not fully identified programmatically. This could create navigation inefficiencies but does not block access to core curriculum or functionality. Commitment Typing Agent is actively remediating legacy object labeling issues, ensuring all interactive elements are programmatically exposed in alignment with WCAG 2.1, Section 508, and AT interoperability standards.
502.3.2 Modification of Object Information	Partially Supports	Typing Agent allows assistive technologies to programmatically modify and interact with object information such as role, state, name, and value: Dynamic Updates: When a user modifies input fields or settings (e.g., student name, classroom options), changes are reflected programmatically so screen readers and other ATs can detect updates. Accessible Forms: Most forms include programmatic associations so that assistive technologies can announce both the field label and its updated value. Status Announcements: Platform alerts (e.g., “Settings saved,” “Student added”) are exposed using ARIA live regions, ensuring screen readers detect modifications. Known Limitations / Barriers Some legacy modules used custom controls where changes were not consistently announced to assistive technologies. A few form components relied on placeholder text instead of explicit programmatic labels, which could reduce clarity when values were modified. Impact Users relying on screen readers or switch devices may experience occasional difficulty confirming modified states in legacy modules. These issues are being remediated and do not block access to essential functionality. Commitment Typing Agent is actively standardizing interactive elements to ensure all object modifications are programmatically exposed, tested with assistive technologies, and fully aligned with WCAG 2.1, Section 508, and interoperability best practices.
502.3.3 Row, Column, and Headers	Partially Supports	Typing Agent provides accessible data tables and grid structures to ensure that row, column, and header information is programmatically exposed to assistive technologies: Structured Tables: Most reporting and administrative views use properly defined table markup with headers and ARIA attributes so screen readers can announce row and column context. Consistent Labels: Lesson reports, student progress dashboards, and administrative data tables are labeled with clear headers for accurate interpretation. Assistive Technology Support: Screen readers can navigate tables by row and column, ensuring users without vision or with cognitive disabilities can understand relationships. Known Limitations / Barriers A few legacy reports used visual-only formatting without fully defined table headers, making it harder for screen reader users to determine context. Some exported PDFs may not consistently preserve row/column tagging, limiting accessibility outside the web platform. Impact Screen reader users may encounter reduced efficiency in legacy reports where headers are not fully tagged. However, essential data is still accessible, and remediation is in progress to improve programmatic associations. Commitment Typing Agent is updating all data tables to ensure that row, column, and header information is fully exposed programmatically, aligning with WCAG 2.1 and Section 508 requirements. Updated reporting modules follow semantic HTML and ARIA best practices for table accessibility.
502.3.4 Values	Partially Supports	Typing Agent exposes the current values of user interface components (e.g., text fields, checkboxes, dropdowns) to assistive technologies so that screen readers and other ATs can accurately communicate the state of an object: Form Fields and Inputs: Most fields in login, profile, and classroom setup forms programmatically expose their values to AT. Interactive Controls: Buttons, toggles, and dropdowns generally provide accessible names and values so that changes (e.g., “enabled/disabled,” “completed/incomplete”) are announced correctly. Dynamic Updates: When users change input values (e.g., test settings, student names), updated values are communicated through ARIA attributes or native HTML form behavior. Known Limitations / Barriers Some legacy modules included custom widgets that did not consistently expose updated values to screen readers. A few form elements relied on placeholder text instead of accessible labels, reducing clarity when values were entered or changed. Impact Users relying on assistive technologies may experience occasional difficulty confirming the current value of fields in older modules. This could slow task completion but does not block access to core platform functionality. Commitment Typing Agent is systematically updating custom controls and form fields to ensure that all values are programmatically exposed and consistently announced by assistive technologies. Accessibility QA includes regression testing to confirm AT compatibility.
502.3.5 Modification of Values	Partially Supports	Typing Agent allows users and assistive technologies to modify the values of interface components (e.g., text fields, checkboxes, dropdowns) and ensures these modifications are programmatically exposed: Editable Fields: Users can modify input fields such as usernames, passwords, student data, or classroom settings, and those changes are reflected programmatically for screen readers. Accessible Form Controls: Standard HTML form elements and ARIA-enabled custom controls communicate changes clearly to assistive technologies. Dynamic Updates: When values are modified (e.g., adjusting lesson timing, saving a report filter), status messages confirm changes and are announced via ARIA live regions. Known Limitations / Barriers Some legacy modules with custom form components did not consistently announce changes to assistive technologies. Placeholder-only fields in older interfaces occasionally failed to expose modifications as clearly as labeled inputs. Impact Screen reader users and those relying on assistive technology may experience occasional difficulty confirming changes to field values in legacy components. This may create inefficiency but does not block functionality. Commitment Typing Agent is actively updating custom widgets and legacy forms to ensure all modified values are reliably programmatically exposed, aligning with WCAG 2.1 and Section 508 standards. Regular accessibility testing includes validation of modifications with JAWS, NVDA, and VoiceOver.
502.3.6 Label Relationships	Partially Supports	Typing Agent ensures that labels for user interface components are programmatically associated with their corresponding elements so assistive technologies can accurately present them: Form Fields: Most input fields (e.g., username, password, student name, classroom name) are explicitly linked with visible and programmatic labels. Icons and Buttons: Interactive elements generally include descriptive text labels or ARIA attributes, ensuring consistent announcement by screen readers. Instructions: Lesson prompts and dialog boxes pair visible instructions with programmatic labels so users relying on AT can identify their purpose. Known Limitations / Barriers Some legacy modules used placeholder text instead of explicit programmatic labels, reducing clarity for AT users. A few icon-only buttons (e.g., older dashboard controls) did not have associated labels, making them harder for screen reader users to interpret. Impact Screen reader users may encounter inefficiencies when interacting with legacy fields or buttons that lack proper label associations. While these do not block access, they may increase the learning curve or reduce usability. Commitment Typing Agent is remediating legacy fields and controls to ensure all labels are programmatically tied to their inputs. Accessibility QA includes validation of label relationships across modern assistive technologies (JAWS, NVDA, VoiceOver).
502.3.7 Hierarchical Relationships	Partially Supports	Typing Agent structures content hierarchically so that relationships between user interface elements are programmatically determinable by assistive technologies: Headings and Sections: Lesson pages, dashboards, and reports are organized using semantic headings ( – ) to convey hierarchy and context. Parent-Child Relationships: Lists, menus, and nested navigation items are coded so AT users can understand grouping and structure. ARIA Landmarks: The platform uses ARIA landmarks (e.g., main, navigation, banner) to reinforce structure for screen reader navigation. Known Limitations / Barriers Some legacy pages used visual formatting (e.g., bold text) instead of semantic heading levels, reducing programmatic clarity. In a few older dashboards, hierarchical groupings (e.g., nested tables or expandable menus) were not fully exposed to screen readers. Impact Users who rely on screen readers may experience inefficiencies when navigating older modules, where hierarchical relationships are not properly coded. This can affect the ease of locating content but does not prevent access. Commitment Typing Agent is remediating all legacy modules to ensure hierarchical structures are conveyed consistently using semantic HTML and ARIA. Accessibility audits and QA include heading validation and hierarchical navigation testing.
502.3.8 Text	Partially Supports	Typing Agent exposes text content programmatically so that it can be rendered accurately by assistive technologies: Readable Text: Lesson instructions, feedback, and navigation menus are delivered as live text (not images of text), allowing resizing, reflow, and AT access. Language Tagging: Pages are programmatically marked for English or Spanish to ensure screen readers use the correct pronunciation rules. Scalability: Text can be resized up to 200% (and reflow at 400%) without loss of content or function. Known Limitations / Barriers A small number of legacy documents and screenshots embedded in PDFs contained image-based text without full tagging or alt text. Some older interface modules included text embedded in icons or graphics, which was not programmatically exposed. These are being updated with live text equivalents or alt attributes. Impact Users relying on screen readers or text resizing may encounter minor inefficiencies when interacting with legacy content where text was embedded in images. However, all core lesson and reporting content remains programmatically accessible. Commitment Typing Agent continues to remediate legacy instances of image-based text, ensuring all instructional and administrative text is fully programmatically exposed in alignment with WCAG 2.1 and Section 508.
502.3.9 Modification of Text	Partially Supports	Typing Agent provides programmatic access to row, column, and cell indices in data tables, ensuring assistive technologies can properly navigate and announce relationships: Data Tables: Student progress reports, class performance dashboards, and administrative analytics use structured table markup that exposes row and column indices for AT. Programmatic Navigation: Screen reader users can move across rows and columns while maintaining context through defined headers and indices. Consistency: Most tables follow semantic HTML standards ( , , , ) and use ARIA attributes as needed for enhanced accessibility. Known Limitations / Barriers A few legacy reporting modules used visual formatting without fully defining row/column indices, making navigation less efficient for screen readers. Exported documents (such as CSV or PDF reports) may not always preserve index tagging, limiting accessibility outside the web platform.
502.3.10 List of Actions	Partially Supports	Typing Agent ensures that table elements used within the application are programmatically determinable for assistive technologies: Semantic Table Markup: Most instructional and reporting tables use proper HTML , , , and elements to expose structure. Header Associations: Student performance tables and class reports define headers programmatically, allowing AT to announce cell relationships correctly. Accessible Exports: Where possible, exported reports (CSV, XLSX) preserve table element structure for use with third-party software. Known Limitations / Barriers A few legacy reports relied on visually styled layouts without complete semantic table markup, reducing clarity for screen reader navigation. PDF exports may not always retain full tagging of table elements, limiting accessibility outside the live web platform.
502.3.11 Actions on Objects	Partially Supports	Typing Agent exposes the list of available actions for interactive elements so assistive technologies can accurately present functionality to users: Interactive Controls: Buttons, menus, and form fields generally expose their available actions (e.g., “activate,” “expand,” “collapse,” “submit”) to AT. Programmatic Support: Standard HTML elements and ARIA attributes are used to ensure screen readers can announce actionable items. Dynamic Elements: In-app popups, expandable menus, and reporting filters typically expose action lists so that users can identify available commands. Known Limitations / Barriers Some legacy custom widgets did not fully expose all available actions to screen readers. A few icon-only buttons lacked programmatically determinable actions, which could create confusion for AT users.
502.3.12 Focus Cursor	Partially Supports	Typing Agent provides a visible focus cursor for interactive elements, ensuring users navigating by keyboard or assistive technologies can track their current point of interaction: Keyboard Navigation: Most buttons, links, form fields, and menus display a visible focus indicator (outline, highlight, or underline) when selected. Consistency Across Modules: Newer modules use strong focus outlines that meet WCAG 2.1 AA non-text contrast requirements. Assistive Technology Support: The focus cursor is programmatically exposed, enabling screen readers to follow navigation sequence in a predictable order. Known Limitations / Barriers Some legacy interfaces used faint or missing focus indicators, making it harder for low-vision users to track focus. In rare cases, custom pop-ups did not return focus to the originating element after closing, potentially disrupting navigation for AT users.
502.3.13 Modification of Focus Cursor	Partially Supports	Typing Agent allows the focus cursor to be programmatically modified as users interact with lessons, forms, and navigation, ensuring assistive technologies can track changes accurately: Dynamic Focus Management: When pop-ups, dialogs, or new modules open, the focus cursor moves to the active element (e.g., the first field in a dialog). Keyboard Support: Users can shift focus predictably using tab/shift-tab navigation, with the cursor updating to reflect the new location. Assistive Technology Integration: Screen readers detect focus changes and announce them, allowing blind or low-vision users to remain oriented. Known Limitations / Barriers Some legacy pop-ups did not always return focus to the originating element once closed, which could cause disorientation. A few custom widgets handled focus inconsistently, requiring additional remediation for smoother AT support.
502.3.14 Event Notification	Partially Supports	Typing Agent provides programmatic event notifications so assistive technologies can inform users when important changes occur in the application: Status Updates: Success and error messages (e.g., “Student added,” “Settings saved,” “Invalid password”) are exposed using ARIA live regions so screen readers announce them without requiring focus shifts. Interactive Changes: Dialog openings, test completions, and lesson transitions are accompanied by programmatic notifications. User Feedback: Visual alerts (color changes, icons) are paired with text and programmatic notifications to ensure all users, including those without vision, can perceive events. Known Limitations / Barriers Some legacy modules used visual-only notifications (e.g., red/green highlights) without programmatic equivalents, limiting access for screen reader users. A few hover-only tooltips were not announced by AT, requiring remediation.
502.4 Platform Accessibility Features	Supports	Typing Agent leverages and supports the accessibility features provided by the underlying platform (operating system, browser, or device): System-Level Compatibility: The application respects operating system and browser-level accessibility settings, such as high-contrast mode, font scaling, sticky keys, and zoom/magnification. Assistive Technology Integration: Typing Agent integrates with widely used AT, including screen readers (JAWS, NVDA, VoiceOver), magnifiers, switch devices, and adaptive keyboards. Keyboard and Input Support: All functionality can be accessed through standard or adaptive keyboards without reliance on mouse-only actions. Responsive Design: The platform works across desktops, laptops, and tablets, adapting layouts while remaining compatible with device-level accessibility features. No Feature Override: Typing Agent does not disable or interfere with platform-provided accessibility functions. Impact Students and teachers can rely on their preferred OS/browser accessibility tools while using Typing Agent, ensuring consistency with individual accessibility needs.
503.2 User Preferences	Supports	Typing Agent supports user preferences by allowing customization of key settings while also respecting system-level accessibility configurations: In-Platform Controls: Users can adjust lesson timing (pause, stop, extend), enable one-handed typing lessons, and modify language preferences (English/Spanish). System Preference Respect: The platform respects browser and OS-level settings such as zoom, high-contrast mode, and text resizing, without overriding them. Accessibility Preferences: Audio can be muted independently, and visual indicators are provided in place of sound cues for users with hearing impairments. Known Limitations / Barriers Some legacy modules had limited customization options for font scaling or display preferences. These are being remediated to better align with WCAG 2.1 user needs. Certain exported reports (PDFs) may not fully reflect user display preferences outside the live web environment.
503.3 Alternative User Interfaces	Supports	Typing Agent is fully operable through alternative user interfaces and assistive technologies without requiring modifications to the platform: Screen Readers: Compatible with JAWS, NVDA, and VoiceOver for blind and low-vision users. Alternative Keyboards & Switch Devices: All functions can be accessed using adaptive keyboards, switch systems, or on-screen keyboards because the platform relies on standard browser and OS input models. Magnifiers & High Contrast: Works with system-level magnification, text enlargement, and high-contrast settings without disruption. One-Handed Typing Lessons: Curriculum includes dedicated lessons designed for students who rely on single-hand or limited-mobility input.
503.4.1 Caption Controls	Partially Supports	Typing Agent includes prerecorded instructional videos and multimedia content. Captioning support is provided as follows: Captions Available: Most prerecorded videos include synchronized captions to support deaf and hard-of-hearing users. User Controls: Where captions are available, users can turn them on/off via the media player interface. Text Alternatives: Lesson instructions and prompts are always provided in text, ensuring critical information is accessible even if captions are unavailable. Known Limitations / Barriers Some legacy videos may lack captions or offer captions that cannot be toggled directly by the user. Caption customization (e.g., resizing, color contrast adjustment) depends on the browser or OS-level media player controls rather than being fully configurable in-platform.
503.4.2 Audio Description Controls	Partially Supports	Typing Agent provides prerecorded instructional videos designed so that essential content is conveyed through both narration and on-screen text. This minimizes the need for separate audio descriptions. Dual Modal Design: Instructions are reinforced with visual prompts, text overlays, and narration to support comprehension. Browser/Platform Integration: Where audio description tracks are available, playback controls depend on the device or browser media player. Accessibility Options: Lesson instructions and prompts are always available in text form, ensuring that users who require additional reinforcement can still follow the material. Known Limitations / Barriers Some legacy videos do not include a dedicated audio description track, and users may not have independent controls to toggle audio descriptions on/off. Audio description support depends on the hosting media player’s accessibility capabilities, which may vary across browsers and devices.
504.2 Content Creation or Editing	Not Applicable	Typing Agent is an instructional SaaS platform, not an authoring tool. Students and educators engage with pre-built lessons, tests, and dashboards but do not create or publish original web content through the system. Pre-Developed Curriculum: All instructional content is provided by Typing Agent and aligned to K–12 educational standards. Configuration vs. Authoring: Teachers and administrators can configure assignments, lesson pacing, and student groupings, but these adjustments do not constitute authoring or content creation. No Content Publishing: Users cannot create new web pages, interactive media, or documents from within the platform.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	Typing Agent does not provide authoring capabilities that involve format conversion (e.g., exporting authored content from one format to another). Educators and students interact with pre-developed curriculum within the platform rather than creating and converting new content. Instructional Focus: All materials are delivered as accessible web content within the Typing Agent environment. Exported Reports: Administrative exports (CSV, XLSX, PDF) are provided for data reporting, but these do not involve user-generated authored content requiring accessibility preservation. No Authoring or Conversion Tools: Because Typing Agent is not an authoring tool, provisions for preservation of accessibility information during format conversion do not apply.
504.2.2 PDF Export	Supports	Typing Agent allows educators and administrators to export reports and data in PDF format. Accessibility information is preserved where possible, though some limitations exist: Report Downloads: Student progress reports, class performance summaries, and administrative data can be exported as PDFs. Tagging and Structure: Most newer PDF exports include headings, table structure, and tagged content to support assistive technologies. Compatibility: Exported PDFs can be opened with screen readers and magnification tools for accessibility.
504.3 Prompts	Not Applicable	Typing Agent is an instructional SaaS platform, not an authoring tool. Because users do not create or publish new content within the system, Typing Agent does not provide prompts reminding authors to include accessibility features (such as alt text or captions). Pre-Built Curriculum: All instructional content is developed and maintained by Typing Agent with accessibility considerations built in. Configuration vs. Authoring: Teachers and administrators configure assignments and lesson pacing but do not author content where accessibility prompts would be needed. Prompts Not Required: Since no new authored content is created, accessibility reminders for user-generated material are out of scope.
504.4 Templates	Not Applicable	Typing Agent does not provide templates for creating new digital content. The platform delivers pre-built curriculum, lessons, and assessments designed and maintained by Typing Agent staff, rather than tools for users to generate or publish new content. Pre-Developed Lessons: All instructional modules are pre-authored by Typing Agent with accessibility considerations integrated during development. No Authoring Templates: Teachers and administrators assign lessons, adjust settings, and manage classrooms, but they do not create new instructional materials from templates. Accessibility Focus: Since templates are not part of Typing Agent’s functionality, this provision does not apply.

h3>Chapter 6: Support Documentation and Services

Notes:

Typing Agent primarily provides support documentation through its web-based Help Center (https://help.typingagent.com ), which is accessible with screen readers, magnifiers, and other assistive technologies. However, some supplemental resources are available in non-web-based formats (PDFs and Word documents):

PDF/Word Accessibility: Newer documents are tagged with headings, alt text, and proper reading order for compatibility with assistive technologies.

Legacy Documents: A small number of older PDFs may not fully meet accessibility standards (e.g., missing table headers, alt text, or tagging). These are being remediated.

Alternate Formats on Request: Support documentation can be provided in alternate formats (e.g., large print, Braille-ready, audio) when requested by schools or districts.

Direct Support: If users encounter accessibility issues with non-web-based documentation, Typing Agent’s support team will work directly with the organization to provide materials in a format that meets their needs.

Commitment Typing Agent ensures that accessibility is built into both its online Help Center and downloadable documentation. Any gaps identified in non-web-based formats are addressed through remediation and by offering alternate formats as needed, so all users have equitable access to support resources.

Criteria	Conformance Level	Remarks and Explanations
602.2 Accessibility and Compatibility Features	Supports	Typing Agent provides documentation describing the platform’s accessibility features and compatibility with assistive technologies to help educators, administrators, and IT teams support students with disabilities: Accessibility Documentation: Typing Agent publishes an Accessibility Questionnaire and Web Accessibility Evaluation Report detailing WCAG 2.0/2.1 compliance status and known exceptions. Compatibility Guidance: Documentation explains support for screen readers (JAWS, NVDA, VoiceOver), magnifiers, alternative input devices, and one-handed typing. End-User Instructions: Help Center resources ( https://help.typingagent.com ) include guidance for configuring accommodations, such as timing adjustments, student-specific settings, and use of special-needs lessons. Transparency: Accessibility features are highlighted in both client agreements and the privacy/terms of use policies, so organizations understand how Typing Agent integrates with system-level accessibility features. Commitment Typing Agent updates accessibility documentation regularly (most recently in 2025) and provides direct support for districts that need help implementing accessibility accommodations. If critical accessibility needs arise that are not fully addressed, Typing Agent’s support and development teams will work collaboratively to resolve them.
602.3 Electronic Support Documentation	Partially Supports	Typing Agent provides electronic support documentation to assist users, educators, and administrators, and most materials are designed with accessibility in mind: Help Center: A comprehensive online knowledge base ( https://help.typingagent.com ) includes searchable articles, guides, and tutorials that can be accessed with screen readers and other assistive technologies. Accessibility of Documentation: Most resources are formatted for accessibility, using proper headings, lists, and alt text for key images. Available Formats: Documentation is available as web articles, PDFs, and Word documents. Recent PDFs are tagged and structured for AT compatibility. Support for Diverse Needs: Documentation includes sections on accommodations for students with disabilities, one-handed typing lessons, and timing adjustments. Known Limitations / Barriers Some older PDFs may lack complete tagging or proper reading order, making them less accessible to screen readers. Occasional screenshots in help articles may not include descriptive alt text. Impact Users relying on assistive technologies may find older documents less efficient to navigate, though core support information remains accessible through the online Help Center and updated resources.
602.4 Alternate Formats for Non-Electronic Support Documentation	Supports	Typing Agent primarily delivers support documentation electronically through its Help Center and downloadable resources. However, when non-electronic formats are needed, alternate formats can be provided upon request: Alternate Format Availability: Documentation can be converted or adapted into accessible formats (e.g., large print, Braille-ready files, audio formats) for organizations that require them. District and School Support: Typing Agent’s support team works directly with schools and districts to ensure staff and students receive support materials in formats compatible with their accessibility needs. Commitment to Equitable Access: Requests for alternate formats are prioritized and fulfilled through customer support, ensuring no user is excluded from understanding how to use the platform. Impact There are no significant barriers since alternate formats are provided on demand.
603.2 Information on Accessibility and Compatibility Features	Supports	Typing Agent ensures that accessibility and compatibility information is available through its support services so educators, administrators, and IT teams can configure the platform for students with disabilities: Help Center Resources: Documentation on accessibility features (e.g., one-handed typing lessons, timing adjustments, student-specific accommodations) is available at Typing Agent Help Center . Accessibility Reports: Formal accessibility evaluations (e.g., Accessibility Questionnaire, EqualWeb reports) describe Typing Agent’s compliance with WCAG 2.0/2.1 standards. Direct Support: Customer support staff are trained to provide guidance on accessibility accommodations and compatibility with assistive technologies (JAWS, NVDA, VoiceOver, magnifiers, switch devices). Transparency: Accessibility commitments are included in Typing Agent’s Privacy Policy, Terms of Use, and Client Agreements, ensuring districts understand available compatibility features. Impact Schools and districts have access to both self-service documentation and direct human support to ensure accessibility features are implemented correctly. Commitment If an accessibility or compatibility issue is not covered in documentation, Typing Agent’s support team will work directly with the requesting organization to resolve the issue and ensure equitable access for all students.
603.3 Accommodation of Communication Needs	Supports	Typing Agent’s support services are designed to accommodate the communication needs of all users, including those with disabilities: Multiple Communication Channels: Support is available via email, live chat, and phone, allowing users to select the method most accessible to them. Accessible Documentation: Help Center articles and support resources are structured for screen reader compatibility and can be provided in alternate formats upon request (e.g., large print, accessible PDFs). Plain Language: Support documentation and communications use clear, concise language to accommodate users with cognitive or learning disabilities. Interpreter/Alternative Format Support: While Typing Agent does not directly provide ASL or real-time captioning, it works with districts and schools to ensure communication needs are met, including supporting alternate formats where required. Impact Users with different communication needs—including blind/low-vision, deaf/hard-of-hearing, and cognitive disabilities—can access support without barriers. If a need arises that is not directly addressed, Typing Agent’s support team works with the organization to ensure equitable solutions. Commitment Typing Agent is committed to providing accessible support services and will collaborate with schools and districts to accommodate unique communication needs beyond standard documentation and support channels.

Legal Disclaimer

“Typing Agent is a proprietary, subscription-based SaaS product. It is not provided under an open-source or open license model.”

Repository

Typing Agent does not maintain a public Git repository for its Accessibility Conformance Report (ACR). The ACR is distributed as documentation (EqualWeb Web Accessibility Evaluation Report and Typing Agent Accessibility Questionnaire) rather than in a code repository.