Need help? Email shivaji@ananyoo.com Contact

Bank2Trust Accessibility Audit: 14 Screens of an Enterprise Data Governance Platform Tested to WCAG 2.2 AA for a VPAT

,

Project details

  • Completed August 2026
  • Tools used Jaws, NVDA, Voiceover, Talkback, Color Contrast Analyzer, WebAIM WAVE, Google Lighthouse, Deque AXE
  • Tags
Start your audit

About the project

This Bank2Trust accessibility audit covered a SaaS data governance platform that sits on top of Microsoft 365 and Google Workspace and lets organisations share files and messages with external parties under strict control: identity checks, PIN and device registration, signing history and a full audit trail of who opened what and when. Enterprise and financial customers buy it for security and compliance, and their procurement teams increasingly ask for the same rigour on accessibility, in the form of a current VPAT.

An application like this is almost entirely interactive. File and folder rows, upload and download tabs, a message thread with replies, attachments and an emoji picker, a document viewer with a toolbar, time pickers for expiry dates and page after page of account settings. Every one of those components is custom built, so there is no browser default to fall back on, and a keyboard or screen reader user depends on the development team having wired each control correctly. That is where this audit focused.

StandardWCAG 2.2 AA + Section 508
PlatformCustom SaaS web application
TestingManual + Automated + VPAT
RegionUSA / Enterprise

Why accessibility matters for an enterprise data sharing platform

Bank2Trust is sold to banks, insurers and other regulated organisations, many of them in the United States, where Section 508 applies to anything bought by federal bodies and where large private buyers run the same accessibility checks in their vendor assessments. The WCAG 2.2 Level AA criteria are the standard every one of those assessments points to. There is also a plain workplace reason: the people who use the platform are employees and external partners who cannot choose a different tool, so if a blind compliance officer cannot open a shared folder or a keyboard user is trapped in the chat widget, the organisation has an accommodation problem as well as a procurement one.

Scope and standard

Our Bank2Trust accessibility audit assessed the application in the client's performance environment against WCAG 2.2 Level A and AA, mapped to the Section 508 criteria for the VPAT. We tested the 14 screens that make up the day to day product, plus the global header, navigation and chat widget that appear on every page:

  • Sharing: Shared with me, My shares, a shared folder with its file rows and actions, and the signing history view
  • Cloud and auditing: the cloud provider connection screen for OneDrive, the auditing history and the help centre
  • Account: settings, identities, PIN, devices, special devices, app registrations and utilities
  • Global elements: header, navigation, notifications and the chat widget, tested once and reported for every page

How we ran the Bank2Trust accessibility audit

  • Screen reader testing with JAWS and NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android, in both browse and focus modes, through every sharing, messaging and account workflow
  • Keyboard only operation of every screen, including file and folder rows, action tabs, the message editor and emoji picker, the document viewer toolbar, time pickers and suggestion lists, with attention to focus order, keyboard traps and a visible focus indicator
  • Colour contrast analysis of text, icons, status badges and form controls across the application's interface
  • Browser zoom to 400% and text spacing checks for low vision users, with data tables, dialogs and side panels checked at each size
  • Automated scans to catch missing names, labels and structure, each result confirmed by hand before it was logged
  • Mapping of every finding to the WCAG 2.2 success criterion and the matching Section 508 criterion, so the results could be written directly into the VPAT Accessibility Conformance Report

What accessibility means on each part of the site

Because users of this platform spend their day inside lists, dialogs and editors, our Bank2Trust accessibility audit paid most attention to the components that stand between a user and a shared file:

  • File and folder rows: each row and its download, upload, copy, move, duplicate and delete actions must be reachable from the keyboard and announced with a name and role, otherwise a screen reader user cannot open a single document.
  • Messaging: the reply, emoji and attachment controls must be focusable, the emoji picker needs proper semantics, and focus must never be stuck inside the message field or a hidden chat widget.
  • Document viewer: the toolbar controls and the undo button must be in the Tab order and announced, so a user can page through and annotate a document without a mouse.
  • Pickers and suggestions: time pickers for expiry dates and suggestion lists for recipients must work with the arrow keys and announce the selected value.
  • Account and security settings: the settings button, PIN and device forms and identity tables need labels, header cells and announced errors, because this is where access to the whole platform is controlled.

The barriers we logged were dominated by keyboard access in custom components: file rows, action tabs, toolbar controls, the emoji picker, time pickers and suggestion lists that could not be reached or operated from the keyboard, and focus trapped in a hidden chat widget and in the message editor. Alongside these were screen reader gaps, where controls had no accessible name or role or a table was read without structure, plus contrast and zoom issues in side panels and dialogs. Each barrier was recorded with the screen, the WCAG success criterion, the actual and expected result, a code snippet and a recommended fix, graded by severity so the product team could start with the critical keyboard blockers.

Outcome

This Bank2Trust accessibility audit gave the client a prioritised, developer ready list of every barrier across the 14 screens and a Section 508 VPAT Accessibility Conformance Report that states, criterion by criterion, where the platform supports, partially supports or does not support WCAG 2.2 AA. Every finding was confirmed with real assistive technology rather than taken from an automated scan alone, which is what lets the sales team put the ACR in front of a procurement reviewer with confidence and gives the engineering team a clear path to full conformance.

Services we provided for this client

Accessibility settings

Saved on this device. Change them any time.

Read our accessibility statement