ScreenComply

    VPAT 2.4 INT

    Accessibility conformance report.

    ScreenComply was engineered to conform to WCAG 2.1 Level A and AA, the Revised Section 508 standards, and EN 301 549 as a requirement of federal deployment. Conformance was validated by the federal customer's internal accessibility review team.

    Request signed PDF →Accessibility & accommodations

    WCAG 2.1 A & AA · Revised Section 508 · EN 301 549 v3.2.1 · Report date 2026-06-17

    Report metadata

    What this report covers.

    Covers the candidate-facing flow (browser mode, desktop agent, Android app) and the institutional-facing web application at app.screencomply.ai. Underlying infrastructure accessibility (AWS, Cloudflare) is inherited from those providers' attestations.

    ProductScreenComply Web Application, Desktop Agent, Android App
    Version2026.06
    Report date2026-06-17
    Legal entityGuardian Robotics Contracting, Inc. d/b/a ScreenComply
    Contactinfo@screencomply.ai
    StandardsWCAG 2.1 A & AA · Section 508 (36 CFR Part 1194) · EN 301 549 v3.2.1
    Evaluation methodsProduct engineered to the Revised Section 508 and WCAG 2.1 AA requirements for federal deployment; conformance validated through the federal customer's internal accessibility review; manual keyboard-navigation testing; manual color-contrast inspection; and manual screen-reader testing with platform assistive technology (Windows Narrator and macOS VoiceOver). An independent third-party accessibility audit has not been conducted to date; if your institution requires validation by a specific auditor or testing organization, ScreenComply will arrange that audit as part of onboarding.

    Terms used

    How to read the conformance column.

    Supports

    The functionality has at least one method that meets the criterion without known defects, or meets the criterion 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.

    WCAG 2.1

    Web Content Accessibility Guidelines — Level A and AA.

    Both tables below evaluate the full WCAG 2.1 success-criteria set applicable to the product. AAA criteria are out of scope for this report.

    Table 1 — Success Criteria, Level A

    CriterionConformanceRemarks & explanations
    1.1.1 Non-text ContentSupportsNavigation icons carry accessible names. Charts and image elements in session reports provide text alternatives, and the underlying report data is available through a programmatically associated table.
    1.2.1 Audio-only and Video-only (Prerecorded)Not ApplicableThe product does not present prerecorded audio-only or video-only content to the candidate or reviewer.
    1.2.2 Captions (Prerecorded)Not ApplicableNo prerecorded audio content is presented.
    1.2.3 Audio Description or Media Alternative (Prerecorded)Not ApplicableSame as 1.2.2.
    1.3.1 Info and RelationshipsSupportsSemantic HTML (table, label, button, nav) is used throughout the web application. Custom widgets (calendar grid, score ring) expose their structure and state through the appropriate ARIA pattern.
    1.3.2 Meaningful SequenceSupportsDOM order matches visual order across the web application. No CSS reordering displaces content from its logical reading order.
    1.3.3 Sensory CharacteristicsSupportsInstructions do not rely on shape, color, or position alone.
    1.4.1 Use of ColorSupportsVerdict badges convey status through label text and an icon in addition to color. No information is conveyed by color alone.
    1.4.2 Audio ControlNot ApplicableThe product does not auto-play audio.
    2.1.1 KeyboardSupportsAll functionality, including calendar event chips and the session-report drawer, is operable through a keyboard interface.
    2.1.2 No Keyboard TrapSupportsKeyboard focus can move into and out of all components, including modals and the session-report drawer. Escape dismisses overlays.
    2.1.4 Character Key ShortcutsNot ApplicableNo single-character key shortcuts are defined.
    2.2.1 Timing AdjustableSupportsSession duration is configured by the institutional administrator at assessment creation time. There is no fixed candidate-facing countdown the candidate cannot extend. Extended-time accommodations are honored by setting a longer duration per assessment.
    2.2.2 Pause, Stop, HideNot ApplicableNo moving, blinking, scrolling, or auto-updating content is present that would require this criterion.
    2.3.1 Three Flashes or Below ThresholdSupportsNo content flashes.
    2.4.1 Bypass BlocksSupportsA keyboard-accessible skip-to-main-content link is provided.
    2.4.2 Page TitledSupportsEach page sets a descriptive title element.
    2.4.3 Focus OrderSupportsFocus order follows a meaningful sequence consistent with the visual layout across all components.
    2.4.4 Link Purpose (In Context)SupportsLink text is descriptive within its surrounding context.
    2.5.1 Pointer GesturesSupportsAll operations are achievable with a single point activation.
    2.5.2 Pointer CancellationSupportsClick handlers fire on the up-event, not the down-event, for all primary actions.
    2.5.3 Label in NameSupportsAccessible names match visible labels.
    2.5.4 Motion ActuationNot ApplicableNo motion-based input is used.
    3.1.1 Language of PageSupportsThe document html lang attribute is set.
    3.2.1 On FocusSupportsFocus does not initiate unexpected context changes.
    3.2.2 On InputSupportsInput does not initiate unexpected context changes.
    3.3.1 Error IdentificationSupportsForm errors are presented as text adjacent to the affected field.
    3.3.2 Labels or InstructionsSupportsForm inputs carry label associations.
    4.1.1 ParsingSupportsHTML is valid against the WHATWG parsing model in the rendered output.
    4.1.2 Name, Role, ValueSupportsStandard and custom controls (calendar grid, score ring, mode switch) expose an accessible name, role, and state to assistive technology.

    Table 2 — Success Criteria, Level AA

    CriterionConformanceRemarks & explanations
    1.2.4 Captions (Live)Not ApplicableNo live audio is presented.
    1.2.5 Audio Description (Prerecorded)Not ApplicableNo prerecorded video is presented.
    1.3.4 OrientationSupportsThe web application reflows correctly in both portrait and landscape orientations. The Android app is portrait-locked by design for proctoring constraints, consistent with other proctoring apps, and documented as a known accommodation request path.
    1.3.5 Identify Input PurposeSupportsautocomplete attributes are set on login and profile forms.
    1.4.3 Contrast (Minimum)SupportsText and interactive states meet or exceed the 4.5:1 ratio for normal text and 3:1 for large text.
    1.4.4 Resize TextSupportsText resizes to 200 percent without loss of content or functionality at common viewport widths.
    1.4.5 Images of TextSupportsNo images of text are used. All text is rendered as live text.
    1.4.10 ReflowSupportsContent reflows to a 320 CSS pixel width without horizontal scrolling.
    1.4.11 Non-text ContrastSupportsInteractive component boundaries and states meet the 3:1 non-text contrast ratio.
    1.4.12 Text SpacingSupportsThe application honors user-applied text spacing overrides without loss of content.
    1.4.13 Content on Hover or FocusSupportsHover content can be dismissed and persists while the pointer is over it.
    2.4.5 Multiple WaysSupportsSearch and navigation by section are available. Sitewide navigation is consistent.
    2.4.6 Headings and LabelsSupportsHeadings and labels describe the topic or purpose of the surrounding content.
    2.4.7 Focus VisibleSupportsA visible focus indicator is present on all interactive elements, including custom-styled controls.
    3.1.2 Language of PartsNot ApplicableThe product is currently English-only.
    3.2.3 Consistent NavigationSupportsNavigation order is consistent across pages.
    3.2.4 Consistent IdentificationSupportsComponents with the same functionality are identified consistently.
    3.3.3 Error SuggestionSupportsForm errors include a textual suggestion for correction.
    3.3.4 Error Prevention (Legal, Financial, Data)SupportsDestructive actions (delete a session, delete a member) require explicit confirmation.
    4.1.3 Status MessagesSupportsStatus messages are exposed to assistive technology through appropriate aria-live regions without moving focus.

    Revised Section 508

    This product is software accessed through a web browser.

    The following Section 508 sections apply. Chapter 4 (Hardware) is not applicable. Chapter 5 (Software) is discussed in prose below.

    Chapter 3 — Functional Performance Criteria

    CriterionConformanceRemarks & explanations
    302.1 Without VisionSupportsAll functionality is operable without vision through a screen reader. Report chart data is available through a programmatically associated data table.
    302.2 With Limited VisionSupportsContent reflows, meets contrast minimums, and supports magnification and text resize to 200 percent.
    302.3 Without Perception of ColorSupportsNo information is conveyed by color alone for primary decisions.
    302.4 Without HearingSupportsNo audio is required for product operation.
    302.5 With Limited HearingSupportsSame as 302.4.
    302.6 Without SpeechSupportsVoice input is not required.
    302.7 With Limited ManipulationSupportsAll functionality is operable by keyboard and single-point activation, and is compatible with platform switch-access and assistive-pointer features through the operating system accessibility tree.
    302.8 With Limited Reach and StrengthSupportsSingle-point activation throughout.
    302.9 Minimize Photosensitive Seizure TriggersSupportsNo content flashes.
    302.10 With Limited Cognition, Language, and LearningSupportsPlain-language copy, descriptive labels, consistent navigation, and descriptive error recovery are provided throughout.

    Chapter 5 — Software (502 Interoperability with AT, 503 Applications)

    DESKTOP AGENT AND ANDROID APP

    Applicable to the desktop agent and the Android app. The desktop agent inherits the operating system accessibility tree (Windows UI Automation and the macOS Accessibility API), providing interoperability with platform assistive technology. The Android app uses standard Android UI components, which are compatible with TalkBack when enabled on the candidate device.

    Disclosure — Android Accessibility Service permissionThe Android app's use of the Accessibility Service permission is for monitoring the candidate's device foreground application, not for providing accessibility to the candidate. This is a distinct technical use of the same permission, is disclosed to the candidate at session start, and is documented in our security and capability materials. We surface it here proactively so that a security reviewer does not have to discover it.

    Chapter 6 — Support Documentation and Services

    CriterionConformanceRemarks & explanations
    602 Support DocumentationSupportsCustomer-facing documentation (security overview, capability matrix, this VPAT) is provided as accessible markdown and HTML. PDFs published from these sources are tagged.
    603 Support ServicesSupportsCustomer support is reachable by email at security@screencomply.ai with a 2-business-day acknowledgement target.

    EN 301 549

    European harmonized standard.

    The product conforms to EN 301 549 to the extent that its specific clauses inherit WCAG 2.1 Level A and AA. The EN-only clauses (5.5 General, 5.6 Two-way voice communication, 5.7 Video capabilities) are not separately evaluated because the product does not provide two-way voice communication or video communication as a service.

    Need a signed copy?

    Request the current VPAT for procurement.

    This VPAT is updated on each material product change. Customers should request the current version when evaluating a renewal.

    Email security@screencomply.ai →Back to accessibility