Accessibility

Accessibility Conformance Report (WCAG 2.2 Level AA)

How the zasio.com website measures against every Level A and Level AA success criterion in WCAG 2.2, what we tested and how, and our plan for the remaining items. A quick page load can't show the testing behind a site, so this report sets it out criterion by criterion.

Report details

Product
The zasio.com public website (marketing pages, News & Insights articles, and documents hosted on it)
Report date
Applicable standard
Web Content Accessibility Guidelines (WCAG) 2.2, Level A and Level AA. Criteria are also reported against WCAG 2.0 and 2.1, which 2.2 includes.
Report format
Modelled on the VPAT® 2.5 (WCAG edition) Accessibility Conformance Report.
Overall result
Partially conformant with WCAG 2.2 Level AA. No criterion is rated Does Not Support; the partial ratings come from the known limitations listed below. We are working toward full conformance.
Scope
Every page in the site's sitemap, plus the PDF documents hosted on zasio.com. Out of scope: the customer portal (a separate application reached through "Log in"), third-party sites we link to, and the YouTube player itself.
Contact
connect@zasio.com or (800) 513-1000

Evaluation methods

  • Automated testing on every page of every release. axe-core 4.10.3 runs WCAG 2.0, 2.1 and 2.2 Level A and AA rules against every page in the sitemap, together with a reflow check at a 320 CSS pixel width. A release cannot ship while either check fails.
  • Keyboard-only testing of menus, dialogs, forms, carousels and media controls on representative page templates.
  • Focus visibility measured on every background colour, image and gradient the site uses, and hit-tested for anything covering a focused item.
  • Colour contrast measured from rendered pixels, including text over photographs and gradients that automated tools can't resolve.
  • Screen-reader accessibility-tree review of names, roles, states, headings, landmarks and live regions.
  • Text spacing, resize and zoom testing with the WCAG text-spacing values, browser zoom and browser text-size settings.
  • Captions and media alternatives reviewed for every self-hosted video, including a check for flashing content.
  • PDF remediation of hosted documents: tags, titles, language, headings, alt text and reading order, checked against the originals.
  • External-grader emulation: pages reviewed the way WAVE- and Lighthouse-style checkers grade them.

Automated tools catch only part of what WCAG asks for, which is why most of the results below also rest on manual testing and source review.

Conformance level terms

Supports
The functionality meets the criterion without known defects, or meets it with an equivalent facilitation.
Partially Supports
Some content or functionality does not meet the criterion. The remarks say which.
Does Not Support
The majority of the functionality does not meet the criterion.
Not Applicable
The criterion is not relevant to the website: it has no content of the kind the criterion covers.

Summary

Number of WCAG 2.2 criteria at each conformance level
Conformance levelLevel A (32)Level AA (24)
Supports2919
Partially Supports22
Does Not Support00
Not Applicable13

Level A includes 4.1.1 Parsing, which WCAG 2.2 removed as obsolete; it is counted as Supports for WCAG 2.0 and 2.1.

Table 1: Success criteria, Level A

WCAG 2.2 Level A success criteria: conformance of zasio.com
CriterionLevelWCAG versionConformanceRemarks
1.1.1 Non-text ContentA2.0SupportsEvery image on the site’s web pages has a text alternative or is marked decorative; legacy articles were reviewed, images given new alt text, and image-file names used as alt text were replaced with words. The 21 hosted PDFs that are real documents have alt text on every figure or mark it as an artifact (including a presenter business card and a signature block). One webinar slide uses a map of Asia as a backdrop to statistics that are given as text; the map is treated as decorative.
1.2.1 Audio-only and Video-only (Prerecorded)A2.0SupportsThere is no audio-only media. Silent videos have a text alternative next to them: the redaction demo clips are described in their captions, the silent VIA preview has a written description, and the Saudi Arabia Z-Byte has a text version.
1.2.2 Captions (Prerecorded)A2.0Partially SupportsSelf-hosted videos have reviewed WebVTT captions (re-cued into readable lines and checked against a second transcription) or, for music-only videos, music identification. Three caption lines are awaiting confirmation from the narrator. The 21 embedded YouTube recordings currently rely on YouTube’s automatic captions.
1.2.3 Audio Description or Media Alternative (Prerecorded)A2.0Partially SupportsSelf-hosted product videos have a written “What the video shows” or “What the demo shows” description next to the player. The embedded YouTube webinar recordings have not yet been reviewed for information that is shown but not spoken.
1.3.1 Info and RelationshipsA2.0SupportsWeb pages use real headings, lists, landmarks, labelled form fields and data tables with header cells. In legacy articles, 621 bold pseudo-headings became real headings, heading levels were normalized, and table images became HTML tables. The Data Processing Agreement PDF was re-exported with tagged headings; the one older PDF without paragraph structure (the 2021 ROT trivia sheet) has an accessible HTML version beside its link (a conforming alternate version).
1.3.2 Meaningful SequenceA2.0SupportsWeb page reading order matches the visual order (one page’s DOM order was corrected during the audit). The Data Processing Agreement PDF was re-exported from its Word source with accessibility tags (November 2026), so its reading order, including the signature block, follows the document.
1.3.3 Sensory CharacteristicsA2.0SupportsInstructions do not rely on shape, size, visual location, orientation or sound alone.
1.4.1 Use of ColorA2.0SupportsLinks in body text are underlined, including footnote links. Comparison tables say “Included” or “Not included” in text. Form errors are given in words, not colour alone.
1.4.2 Audio ControlA2.0SupportsVideos that start on their own are muted and decorative. Videos with sound start only when the visitor presses play.
2.1.1 KeyboardA2.0SupportsKeyboard-only testing (60 Tab presses per page on 13 representative templates) reached every link, button, menu, form field, dialog and media control. Menu panels open from a disclosure button as well as on hover.
2.1.2 No Keyboard TrapA2.0SupportsNo keyboard traps were found. Dialogs are native dialog elements that close with Escape and return focus; Escape also closes open menu panels and the phone menu.
2.1.4 Character Key ShortcutsA2.1SupportsThe site defines no single-character keyboard shortcuts.
2.2.1 Timing AdjustableA2.0SupportsThere are no time limits: forms do not expire and nothing advances on a timer. The quote carousel moves only when its buttons are pressed.
2.2.2 Pause, Stop, HideA2.0SupportsEvery auto-playing video and continuous animation has a visible pause control: the home hero, the Industries video, the Support and Software hub figures, the SOC 2 figure, the Information Governance 101 blocks, the tier comparison thumbnail and the Workflow demo (converted from an animated GIF to a video). Tested paused with no animation left running.
2.3.1 Three Flashes or Below ThresholdA2.0SupportsSelf-hosted video was checked for flashing. One product video (the 2023 preview) had a stripe transition that flashed about six times in a second at five points; every one was frame-blended and the result checked against the original.
2.4.1 Bypass BlocksA2.0SupportsA “Skip to content” link is the first Tab stop on every page and moves focus to the main content. Pages also use header, navigation, main and footer landmarks.
2.4.2 Page TitledA2.0SupportsEvery page has a unique, descriptive title (duplicate and truncated titles were fixed during the audit). Hosted PDFs have a document title and display it in the window bar.
2.4.3 Focus OrderA2.0SupportsFocus order follows the reading order. Dialogs move focus in when they open and return it to the trigger when they close.
2.4.4 Link Purpose (In Context)A2.0SupportsAutomated checks find no empty or generic link names. In legacy articles, 734 footnote links were named, 71 vague links rewritten, 53 more given a hidden destination, 41 PDF links labelled, and 142 new-tab cues added.
2.5.1 Pointer GesturesA2.1SupportsEverything works with a single tap or click; no multipoint or path-based gestures are used.
2.5.2 Pointer CancellationA2.1SupportsControls are native links and buttons that act on release, not on press.
2.5.3 Label in NameA2.1SupportsAccessible names were spot-checked against visible labels; where a control has visible text, its name contains it.
2.5.4 Motion ActuationA2.1Not ApplicableNothing on the site is operated by shaking or tilting the device.
3.1.1 Language of PageA2.0SupportsEvery page declares English. Hosted PDFs have their document language set.
3.2.1 On FocusA2.0SupportsMoving focus never changes the page, opens a window or submits a form.
3.2.2 On InputA2.0SupportsEntering data does not change context. The news filters update the list in place and announce the number of results.
3.2.6 Consistent HelpA2.2SupportsThe phone number, email address and Contact link appear in the same footer position and order on every page.
3.3.1 Error IdentificationA2.0SupportsEach form error is described in text and tied to its field. An invalid submit moves focus to the first field that needs attention; file-upload errors are announced.
3.3.2 Labels or InstructionsA2.0SupportsEvery form field has a visible label (the news search has a programmatic label as well); required fields are marked.
3.3.7 Redundant EntryA2.2SupportsAll forms are single-step, so nothing has to be entered twice.
4.1.1 ParsingA2.0Supports (2.0 and 2.1); obsolete in 2.2Removed from WCAG 2.2 as obsolete. For WCAG 2.0 and 2.1: duplicate ids in legacy content (22) were removed and invalid nesting in migrated privacy-notice markup was rebuilt.
4.1.2 Name, Role, ValueA2.0SupportsCustom controls expose their state: menu and year buttons use aria-expanded, filter chips use aria-pressed, dialogs are named, and embedded frames have titles. Automated checks report no violations.

Table 2: Success criteria, Level AA

WCAG 2.2 Level AA success criteria: conformance of zasio.com
CriterionLevelWCAG versionConformanceRemarks
1.2.4 Captions (Live)AA2.0Not ApplicableThe site has no live audio or video.
1.2.5 Audio Description (Prerecorded)AA2.0Partially SupportsSelf-hosted product videos have a written description of what is shown, but not a separate audio-description track. The embedded YouTube webinar recordings have not yet been reviewed for visual-only information.
1.3.4 OrientationAA2.1SupportsPages work in both portrait and landscape; nothing is locked to one orientation.
1.3.5 Identify Input PurposeAA2.1SupportsContact, job-application and newsletter fields that ask for the visitor’s own details carry autocomplete tokens (name, organization, job title, email, telephone).
1.4.3 Contrast (Minimum)AA2.0SupportsAutomated checks report no contrast failures on any page. Text over gradients and photographs, which automated tools cannot resolve, was measured from rendered pixels; the gold text colour and the Customers hero scrim were adjusted to reach at least 4.5:1.
1.4.4 Resize TextAA2.0SupportsText resizes to 200% with browser zoom and browser text-size settings without loss of content. Forcing the root font size to 200% (a test, not a browser setting) still scrolls sideways on some layouts; we are watching this.
1.4.5 Images of TextAA2.0Partially SupportsText is real text across the site’s templates and article bodies. In November 2026, 21 legacy article graphics that were text, tables or lists drawn as images (quote cards, tables, lists, step charts) were rebuilt as real HTML; remaining article images that show text are comics, photos, floor plans and diagrams where the picture carries the meaning, each with a text alternative, and logos are essential. Remaining exception: about 67 older article hero banners (webinar and event title cards) show the article’s title or event details as a graphic. The same text appears as real text on each page, and the banners are being replaced.
1.4.10 ReflowAA2.1SupportsEvery page is checked at a 320 CSS pixel width before each release and the release fails if any page scrolls sideways.
1.4.11 Non-text ContrastAA2.1SupportsForm-field borders and control boundaries measure at least 3:1 (3.58:1 or better). The focus indicator measures at least 3:1 on every background, including a white ring at 10:1 or better on dark bands.
1.4.12 Text SpacingAA2.1SupportsTested with the WCAG text-spacing values on representative templates; containers that clipped text (the quote carousel, a hero figure, link halos) were fixed.
1.4.13 Content on Hover or FocusAA2.1SupportsMenu panels stay open while the pointer is over them, and Escape closes them and returns focus to their trigger.
2.4.5 Multiple WaysAA2.0SupportsPages can be reached from the main menu, the footer, the HTML site map, and the News & Insights search.
2.4.6 Headings and LabelsAA2.0SupportsHeadings and labels describe their topic or purpose; empty headings were removed from legacy articles.
2.4.7 Focus VisibleAA2.0SupportsMeasured, not assumed: focus was traversed with the keyboard on 23 page templates at desktop and phone widths, and the indicator was detected by pixel comparison at each of 1,652 focus stops. Every interactive control (navigation and menu buttons, carousel, dialogs, forms, video and pause controls, footer links) shows a 2px focus ring: brand purple on light backgrounds and white on dark bands (10:1 or better against the band). Each release re-runs automated focus checks.
2.4.11 Focus Not Obscured (Minimum)AA2.2SupportsMeasured, not assumed: keyboard traversal forward and backward at 1280, 1100, 768 and 390 pixel widths and on short landscape screens (640 by 256 and 320 by 256), with and without the EU/UK cookie bar showing, found 0 focused elements hidden by the sticky header or the cookie bar. Scroll padding sized to the header and the cookie bar keeps focused items clear, and the header stops being sticky on very short screens.
2.5.7 Dragging MovementsAA2.2SupportsNo function needs dragging. The carousel and comparisons work with buttons.
2.5.8 Target Size (Minimum)AA2.2SupportsChecked on every page before each release. Targets are at least 24 by 24 CSS pixels or meet the spacing exception; inline text links are exempt.
3.1.2 Language of PartsAA2.0SupportsFrench and German passages and foreign phrases in articles are marked with their language.
3.2.3 Consistent NavigationAA2.0SupportsThe header, menus and footer are the same on every page, in the same order.
3.2.4 Consistent IdentificationAA2.0SupportsComponents with the same function use the same labels throughout the site.
3.3.3 Error SuggestionAA2.0SupportsError messages say what is needed and how to fix it, for example “Please enter your email address” for an empty field and “That doesn’t look like an email address, for example name@company.com” for a malformed one. Required fields are stated visibly at the top of each form.
3.3.4 Error Prevention (Legal, Financial, Data)AA2.0Not ApplicableThe site’s forms send enquiries, job applications and newsletter sign-ups. None makes a legal commitment or financial transaction, or changes or deletes stored data the visitor controls.
3.3.8 Accessible Authentication (Minimum)AA2.2Not ApplicableThe public website has no sign-in. The “Log in” link opens the customer portal, a separate application outside the scope of this report.
4.1.3 Status MessagesAA2.1SupportsForm sending and confirmation, newsletter sign-up, news filter results, carousel position and cookie choices are announced through live regions without moving focus.

WCAG 2.1 and 2.2 additions

The "WCAG version" column shows the version that introduced each criterion. A WCAG 2.0 report is the rows marked 2.0; a WCAG 2.1 report adds the rows marked 2.1.

Added in WCAG 2.1 (12): 2.1.4 Character Key Shortcuts, 2.5.1 Pointer Gestures, 2.5.2 Pointer Cancellation, 2.5.3 Label in Name, 2.5.4 Motion Actuation, 1.3.4 Orientation, 1.3.5 Identify Input Purpose, 1.4.10 Reflow, 1.4.11 Non-text Contrast, 1.4.12 Text Spacing, 1.4.13 Content on Hover or Focus, 4.1.3 Status Messages.

Added in WCAG 2.2 (6): 3.2.6 Consistent Help, 3.3.7 Redundant Entry, 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.3.8 Accessible Authentication (Minimum). WCAG 2.2 also removed 4.1.1 Parsing.

Known limitations and remediation plan

  • YouTube captions (1.2.2). The 21 recordings embedded from YouTube use YouTube's automatic captions. Plan: upload reviewed captions in YouTube Studio.
  • Caption confirmation (1.2.2). Three lines in our self-hosted captions are waiting for the narrator to confirm the wording. Plan: confirm and update the caption files.
  • Video descriptions (1.2.3, 1.2.5). Self-hosted product videos have written descriptions of what is shown, not audio-description tracks, and the YouTube webinar recordings have not yet been reviewed for visual-only information. Plan: review each recording and add descriptions where the narration doesn't cover what is on screen.
  • Images of text (1.4.5). About 22 diagrams, comics and quote graphics in older articles are images of text. Each has alt text with the full text; redrawing them as HTML would lose the graphic.
  • Five unavailable legacy documents. Five files from our previous site were saved as web pages rather than PDFs. Their links now point to text or current equivalents while we recover the originals.
  • Assistive-technology testing. A full pass with NVDA and VoiceOver on the main templates is planned, to confirm the accessibility-tree review in real screen readers.

If any of this content gets in your way, ask us and we will provide it in another format.

Contact

Questions about this report, or a barrier on zasio.com: email connect@zasio.com or call (800) 513-1000. See also our accessibility statement.

VPAT® is a registered service mark of the Information Technology Industry Council (ITI).