VIDIZMO Accessibility Conformance Report
VIDIZMO Accessibility Conformance Report
(Based on VPAT® Version 2.5)
Name of Product/Version:
- VIDIZMO EnterpriseTube (Enterprise Video Content Management)/v12.1
- VIDIZMO Digital Evidence Management System (DEMS)/ v12.1
- VIDIZMO Redactor/v12.1
- VIDIZMO Intelligence Hub/v12.1
- VIDIZMO AI Live Insight/v12.1
Report Date: July 13, 2026
Product Description
VIDIZMO is a secure, AI-powered enterprise content and digital-evidence platform for ingesting, storing, access-controlling, sharing, and analyzing digital content. The platform is delivered as a set of purpose-built products that share a common portal, security model, and AI services. This report covers the following products:
- VIDIZMO EnterpriseTube: Enterprise Video Content Management (EVCM): a secure video portal and media library with live streaming, on-demand playback, and content-management workflows for enterprises and institutions.
- VIDIZMO Digital Evidence Management System (DEMS): Secure evidence intake, chain of custody, access control, and case management for law-enforcement and government agencies.
- VIDIZMO Redactor: AI-assisted redaction of personally identifiable information (PII) across video, audio, images, and documents.
- VIDIZMO Intelligence Hub: A low-code/no-code AI agent builder consisting of a visual, node-based workflow editor, agent configuration, and a natural-language chatbot that turns video, document, and media libraries into content-aware conversational experiences.
- VIDIZMO AI Live Insight: A live surveillance product that connects IP cameras to the portal, runs real-time AI object detection on each feed, and surfaces detections as alerts and event-driven recordings through an operator dashboard, camera grid, and playback timeline.
Contact Information: VIDIZMO Support
Evaluation Methods Used
Preparing this conformance report involved testing the system using leading assistive technologies, including keyboard-only navigation and screen readers. These were complemented with manual inspection of the application's HTML controls using browser developer tools. The testing was performed on Windows 11 using Google Chrome version 150.0.7871.47.
Applicable Standards/Guidelines
This report covers the degree of conformance with the following accessibility standards/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A – Yes; Level AA – Yes; Level AAA – No |
| Web Content Accessibility Guidelines 2.1 | Level A – Yes; Level AA – Yes; Level AAA – No |
| Web Content Accessibility Guidelines 2.2 | Level A – Yes; Level AA – Yes; Level AAA – No |
| Revised Section 508 standards (published January 18, 2017, corrected January 22, 2018) | Yes |
| EN 301 549 Accessibility requirements for ICT products and services — V3.2.1 (2021-03) | No |
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.0 Level AAA.
WCAG 2.x Report
Tables 1 and 2 also document conformance with:
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
For convenience, each criterion is also cross-referenced to the corresponding EN 301 549 clauses (Chapter 9 – Web; Sections 10.1–10.4 of Chapter 10 – Non-Web documents; Sections 11.1–11.4 and 11.8.2 of Chapter 11 – Non-Web Software; and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation). VIDIZMO does not claim formal conformance to EN 301 549 in this report.
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Alternate text is provided for most images and non-text elements across the VIDIZMO platform, decorative icons are hidden from assistive technology, and VIDIZMO does not make use of CAPTCHA for any verification. However, a few exceptions include:
|
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO's product interface is not built around prerecorded audio-only or video-only media — its guided onboarding uses text-based tooltips rather than video. Any audio/video in the product is user-managed or AI-generated content (including live surveillance recordings), which is authored/evidence content; where audio is present, VIDIZMO provides captioning/transcript facilities (covered under authoring-tool provisions). |
| 1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO supports closed captions (CC) for prerecorded video. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO's product interface does not include prerecorded synchronized media (video with audio) that would require an audio description or media alternative — its guided onboarding uses text-based tooltips rather than video. Video-with-audio in the product is user-managed or AI-generated content (authored content), for which VIDIZMO provides transcript/caption facilities under authoring-tool provisions. |
| 1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Information, structure, and relationships are largely programmatically determinable. Form fields use associated label/id pairs, data tables use header cells and scope, and ARIA landmark roles (navigation, main, form, contentinfo) describe page regions. Note: hint and error text is not always programmatically tied to its field (see 3.3.2). |
| 1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: Content is presented in a meaningful reading and navigation sequence. |
| 1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: Instructions do not rely solely on sensory characteristics of components. |
| 1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: In most cases VIDIZMO does not use color as the sole means of conveying information — for example, severity/status indicators show a text label ("Critical", "High", etc.) alongside their color. Exceptions: disabled fields and inapplicable player controls (such as "view annotation") are indicated by grey color; some status indicators (a small severity dot / row tint, and the severity shown for already-ended items) are conveyed by color alone; and on the version 12.1 theme, some inline text actions shown in the primary orange (for example the Users toggle in User and Group Management) are set apart from the surrounding text by color alone, with no underline or other visual cue. Disabled state is exposed programmatically to assistive technology. |
| 1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: For audio that plays automatically, keyboard-operable controls are available to pause/stop playback and adjust volume. |
| 2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Most controls — buttons, links, toggles, dropdown menus, the media action ("three-dot") menu, the rich-text editor toolbar, and comment entry — are keyboard operable. Exceptions: reordering lists by dragging (quiz/survey questions, playlist and collection items, and similar lists) has no keyboard alternative; in the node-based workflow editor the toolbar and node library are keyboard accessible, but adding, connecting, and moving nodes on the canvas requires pointer dragging; in the live surveillance view the timeline scrubber and alert/event rows are not keyboard operable (seeking and filtering are available through toolbar buttons); some secondary links (comment reply, like, "show more", and the in-player text-overlay controls) cannot be reached by keyboard; and in the media Studio, redaction and annotation regions are drawn and moved with a pointer. |
| 2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: No keyboard traps were identified; no application code intercepts the Tab key to prevent focus from moving away. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: The media playback player provides single-character shortcuts — for example, Space or "k" to play/pause, "j"/"l" and the arrow keys to seek, the arrow keys for volume, "m" to mute, "c" for captions, and "f" for full screen. They are suppressed while the user is typing in a text field, but they stay active whenever the player is on the page rather than only when it has focus, and users cannot turn them off or remap them. The media Studio also provides single-character shortcuts — for example "m" to mute, Space to play/pause, the arrow keys to seek, Delete to remove the selected object, and Escape to cancel drawing, plus multi-key sequences for redaction/annotation classes — dispatched at the window level whenever the Studio scope is active, and users cannot turn them off or remap them. Its zoom shortcut (Ctrl/Cmd with "+", "-", or "0") is active only while the pointer is over the player. |
| 2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: By default VIDIZMO does not impose time limits on content. |
| 2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: The general portal does not contain moving, blinking, or auto-updating content. The live surveillance operator dashboard updates in real time as an essential, live monitoring activity, which is exempt under this criterion. |
| 2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: By default VIDIZMO does not contain content that flashes. |
| 2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: ARIA landmark roles (navigation, main, contentinfo) are now provided across the application, allowing assistive-technology users to jump between and bypass repeated regions. However, no visible "skip to main content" link is provided for sighted keyboard users, and the main landmark is defined per page rather than in the application shell, so it is not guaranteed on every route. |
| 2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO provides informative page titles. |
| 2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Focus generally follows a logical order that matches the visual presentation. Exceptions: focus is not reliably managed or returned in some overlays and within the date-picker/calendar widget, and modal dialogs rely on the underlying component library's default focus handling. |
| 2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Most links convey their purpose. Exceptions: some "three-dot" (⋮) action menus expose only an icon with no accessible name; links to help articles do not always indicate the destination or that they open an external window; and some HTML-editor options are represented only by "…". |
| 2.5.1 Pointer Gestures (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO does not require multipoint or path-based gestures to operate functionality. |
| 2.5.2 Pointer Cancellation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Web: Pointer inputs are reversible; actions complete on the up-event and can be aborted. |
| 2.5.3 Label in Name (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Where controls have visible text labels, the accessible name generally contains that text. Exceptions: some controls' accessible names are instructional rather than matching a visible label; and several toolbar controls in the live surveillance view use hard-coded English tooltips rather than the localized visible label. |
| 2.5.4 Motion Actuation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Not Applicable | Web: VIDIZMO does not include functionality that requires motion actuation. |
| 3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: The page declares a language (lang="en"). However, when a user switches the interface to another language, the document language attribute is not updated, so the programmatically-set language does not always match the displayed content language. |
| 3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: Receiving focus does not initiate an unexpected change of context. |
| 3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: Changing the setting of a user-interface component does not automatically cause an unexpected change of context. |
| 3.2.6 Consistent Help (Level A 2.2 only) | Supports | Web: A help/support mechanism (support pane, help site, and submit-ticket options) appears in a consistent location in the global top bar across pages when the corresponding features are enabled. |
| 3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: Form errors are clearly indicated and are announced to assistive technology via alert roles. |
| 3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Most forms provide labels or instructions where input is required. Exceptions: some fields do not indicate required formats (for example, navigation-menu and trusted-domain URL fields, and date fields in the limited-share dialog); error text is only rarely tied to its field programmatically; and the AI chat assistant's message input is an editable region with only a placeholder and no programmatic label. |
| 3.3.9 Redundant Entry (Level A 2.2 only) | Supports | Web: Previously entered information is auto-populated where applicable; no forced re-entry of information within a process was identified. |
| 4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Web: The application is built on Angular, whose template compiler enforces well-formed markup (complete tags, correct nesting). This criterion is obsolete as of WCAG 2.2. |
| 4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: ARIA roles, labels, and states are used broadly across menus, tabs, dialogs, and custom controls. Exceptions: some custom controls do not expose their state (for example, selected tabs do not set aria-selected, and dialogs do not set aria-modal); a number of div/span/icon click targets lack a role and accessible name (for example, the chat attachment ("+") menu trigger and the workflow editor's node-library toggle expose no accessible name, which screen readers announce only as "button"); the trial/upgrade button in the top bar is missing a correctly applied accessible name due to a coding error, so screen readers may not announce it correctly on any page; the collapsible sections on the Portal Settings and Control Panel pages contain controls nested in a way that assistive technologies may not interpret correctly; and the AI chat assistant's message input does not expose a programmatic name/role. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: VIDIZMO now supports live streaming and live surveillance. Live captions are available where the source or streaming workflow provides them; live surveillance camera feeds are video without narrated audio. Availability of live captions for a given live event should be confirmed per deployment. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO does not ship prerecorded audio content as part of the product interface. |
| 1.3.4 Orientation (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Web: Content is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: The purpose of most input controls is programmatically determinable, but common autocomplete tokens are not consistently applied to fields that collect user information. |
| 1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Most text meets the minimum contrast requirement. However, elements shown in the version 12.1 primary brand color (orange) do not provide enough contrast — for example, white text on the orange primary and trial/upgrade buttons and onboarding tooltips, orange link and tab text on a white background, and orange labels on a light-orange background. Choosing a darker primary shade, or a white or dark background for these elements (available through branding options), resolves this. |
| 1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: Text can be resized/magnified without loss of content or functionality. |
| 1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO does not use images of text other than logos, which are exempt. |
| 1.4.10 Reflow (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Web: Content reflows without loss of information or functionality and without requiring two-dimensional scrolling. |
| 1.4.11 Non-text Contrast (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: The version 12.1 theme does not always provide enough contrast for user-interface elements and their outlines; a white or dark background (available through branding options) can be used to comply. In addition, the missing focus indicator on buttons (see 2.4.7) affects how clearly a focused element stands out. |
| 1.4.12 Text Spacing (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO follows the recommended text-spacing guidelines. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Web: Content shown on hover or focus follows the dismissible/hoverable/persistent recommendations. |
| 2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: Multiple ways are provided to locate a page, except where a page is the result of a series of user actions. |
| 2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: Descriptive headings and labels help users understand page context. |
| 2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: A visible focus indicator is provided across most of the VIDIZMO platform, so keyboard users can see which element is focused. A known exception is that some buttons do not currently display a visible focus indicator. |
| 2.4.11 Focus Appearance (Level AA 2.2 only) | Partially Supports | Web: Where a focus indicator is present, it is generally clear; however, it is applied inconsistently, and on some buttons it is not shown (see 2.4.7). |
| 2.4.12 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Supports | Web: Focused components are generally not entirely hidden across the VIDIZMO platform. In some views, sticky top bars and editor ribbons may partially obscure a focused component. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Partially Supports | Web: Some dragging operations offer single-pointer alternatives (for example, file uploads provide a browse button, and the surveillance timeline supports click-to-seek). However, list reordering (quiz questions, channel/playlist items), the node-editor canvas, and timeline scrubbing do not provide a non-drag alternative. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Partially Supports | Web: Larger targets are used in most places across the VIDIZMO platform, but some are slightly below the recommended minimum size — for example, a client/portal link in the user list is a little smaller than the minimum and sits close to neighboring targets. Some compact icon-only controls also remain below the recommended minimum size. |
| 3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: Content is presented in a single active language selected by the user; no mixed-language passages requiring per-element language markup were identified. (See 3.1.1 regarding the page-level language attribute.) |
| 3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: Navigation mechanisms remain consistent across the site. |
| 3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: Components with the same functionality are identified consistently across the site. |
| 3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: When an input error is detected, the message provides specific suggestions for correction. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Web: VIDIZMO does not contain forms that create legal commitments or financial transactions. |
| 3.3.7 Accessible Authentication (Level AA 2.2 only) | Supports | Web: The primary sign-in uses a username and password, which is a cognitive function test; however, the credential fields allow paste (including from password managers) and an OTP (one-time passcode) sign-in alternative is provided, so an accessible authentication path that does not depend on recalling and transcribing a secret is available. |
| 4.1.3 Status Messages (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially Supports | Web: Toast notifications and form-validation errors now use live regions (alert/status roles) and are announced by screen readers. However, several asynchronous states are still not announced: page/upload progress indicators, the AI chat assistant's streamed responses, and the live surveillance operator dashboard's real-time alert and camera-health updates. |
Table 3: Success Criteria, Level AAA
Notes: VIDIZMO has not been evaluated for WCAG 2.x Level AAA conformance.
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | VIDIZMO partially supports use without vision. Exceptions include:
|
| 302.2 With Limited Vision | Partially Supports | VIDIZMO partially supports use with limited vision. Exceptions include:
|
| 302.3 Without Perception of Color | Partially Supports | A rating of Partially Supports has been given because, as described in 1.4.1 Use of Color, a few controls are greyed out to show disabled fields and detection severity in the live surveillance view is conveyed partly through color. |
| 302.4 Without Hearing | Supports | VIDIZMO does not require the use of hearing. |
| 302.5 With Limited Hearing | Supports | VIDIZMO does not require the use of hearing. |
| 302.6 Without Speech | Supports | VIDIZMO does not require speech input or control. |
| 302.7 With Limited Manipulation | Partially Supports | Web: Users who rely on keyboard navigation, speech recognition, or switch control will have difficulty operating some controls. A rating of Partially Supports has been given because:
|
| 302.8 With Limited Reach and Strength | Supports | VIDIZMO does not require fine motor controls. VIDIZMO also supports large screen touch displays that do not require fine motor controls. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially Supports | A rating of Partially Supports has been given because, as described in 2.4.4 Link Purpose, a few links provide no accessible names or inadequate names. |
Chapter 4: Hardware
Notes: VIDIZMO Video Platform is a web application and is not subject to the requirements under this section.
Chapter 5: Software
Notes: VIDIZMO Video Platform is a web application; conformance is reported in the WCAG 2.x section above (per 501.1 Scope).
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 601.1 Scope | Heading cell – no response required | Heading cell – no response required |
| 602 Support Documentation | Heading cell – no response required | Heading cell – no response required |
| 602.2 Accessibility and Compatibility Features | Supports | VIDIZMO provides electronic versions of all product support documentation related to its various products. End-users with disabilities can request additional product support documentation by opening a new case at https://help.vidizmo.ai |
| 602.3 Electronic Support Documentation | See WCAG 2.x section | See information in WCAG 2.x section |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Supports | End-users with disabilities can request additional product support documentation by opening a new case at https://help.vidizmo.ai |
| 603 Support Services | Heading cell – no response required | Heading cell – no response required |
| 603.2 Information on Accessibility and Compatibility Features | Supports | VIDIZMO provides electronic versions of all product support documentation related to product accessibility. Users with disabilities can request additional product support documentation by opening a new case at https://help.vidizmo.ai |
| 603.3 Accommodation of Communication Needs | Supports | Support service related to VIDIZMO Products can be found at our help website. Currently, telephone communication provision does not support TTY or relay services. Users with disabilities can open support request directly at https://help.vidizmo.ai |