At Bridge, we are committed to making our platform accessible to all users. Our goal is to strengthen your confidence in our accessibility efforts, ensuring our platform meets the WCAG 2.2 Level AA standards.

At Bridge, we’re thrilled to continue being a champion of an accessibility centered approach that benefits everyone! We firmly believe that designing and developing software to be accessible not only empowers individuals with disabilities but also enhances the experience of all users. Our mission is to create an online learning environment that’s intuitive, flexible and engaging for every learner to unlock the full potential of every user.

Additionally, we acknowledge the significance of accessibility standards established by various regulatory bodies. These include the European Accessibility Act (EAA), which sets requirements for digital products and services across the European Union. Additionally, we recognize the standards set by the U.S. Department of Justice, which mandates that state and local governments ensure accessibility for people with disabilities on their websites and mobile applications.

By following these regulations and the Web Content Accessibility Guidelines (WCAG) 2.1 & 2.2 Level AA standards, we will ensure that our e-learning platforms and digital content are perceivable, operable, and understandable for all users, regardless of their abilities. Our ongoing and proactive approach to accessibility will not only ensure legal compliance but also reflects our commitment to creating an inclusive digital environment that benefits all learners.

Historically, Bridge has demonstrated a commitment to accessibility through several key actions:

External Auditing: We have previously contracted for externally conducted VPAT assessments based on WCAG 2.1 standards, covering our entire Bridge product line. The most recent was performed in 2022. However, there's room for improvement in specifying impacts on particular product areas and user groups.

User Feedback: Our development team prioritizes accessibility-related issues, treating them as critical bugs that could impede workflow execution.

Design Philosophy: We embrace an accessibility-first approach, integrating inclusive design principles from the earliest stages of conceptualization. This proactive strategy ensures that accessibility is a fundamental consideration in our process, driving the creation of features that are inherently usable by the widest range of users possible.

Development and Quality Assurance: Our teams utilize accessibility-supportive tools and frameworks. Testing protocols include both automated and manual evaluations, with specific attention to screen reader compatibility (JAWS for windows and VoiceOver for Mac).

Staff Training: We maintain an annual accessibility compliance training program for all employees.

These efforts have demonstrated our ongoing commitment to creating inclusive digital experiences. However, there are opportunities for enhancement, particularly in the areas of product-specific accessibility documentation, more granular user impact analysis and open communication with our community. Therefore, we designated an Accessibility Task Force to drive forward a more encompassing accessibility implementation plan.

We recognize that accessibility is not a one-time effort but an ongoing journey. Bridge established an Accessibility Task Force with representatives from design, development, QA, support, and management. In order to underscore our commitment and continually increase customer confidence, we have developed an implementation plan to chart a path toward excellence in accessibility.  

Phase 1:  Completed

Strengthen Current Process Integration and Tool Enhancement (Jan. -March. 2025)

1. Continue driving progress with conformance improvement for issues identified in the prior VPAT of 2022.
2. Improve communication to users that the Accessibility Dark Mode is how users can engage with the platform in high contrast, exceeding standards, at a 7:1 ratio.
3. Enforce accessibility checkpoints in the software development lifecycle, re-emphasizing early-stage design considerations
4. Enhance the feedback review process to prioritize accessibility issues effectively and track resolution for accessibility bug types.
5. Implement additional automated accessibility testing tools to complement existing ones.
6. Review and update guidelines for manual testing with assistive technologies, expanding beyond JAWS and VoiceOver.
7. Reinforce use of the centralized accessibility resource hub for designers and developers.

Phase 2: Completed

Assessment and Gap Analysis (March -June)

1. Obtain an updated, externally performed WCAG 2.2 Level AA audits of each separate Bridge products offering, clearly indicating area of the product and user(s) impacted. Starting with Learn LMS focusing on the learning user.
2. Analyze the audit results for each of the above VPATs. Perform user impact analysis and identify specific areas of improvement to make thematic progress.
3. Assess the effectiveness of the current feedback review process from support.
4. Evaluate the integration of accessibility in the existing design and development approach.
5. Review current development and QA tools and identify and implement any new tools for accessibility support into the current operations.

Strategy Development (June- July) 

1. Define specific, measurable accessibility goals aligned with WCAG 2.2 Level AA standards for each product as the external results of the product specific VPAT conformance becomes available.
2. Develop a detailed timeline for remediation and ongoing monitoring. - available below

Phase 3:  Underway

Updated Implementation and Remediation (July - Sept)

1. Address high-priority accessibility issues identified in the initial audit.
2. Implement accessibility improvements in the design and development processes.
3. Create a communication plan for internal and external stakeholders, clearly indicating where and when updates will be available, as well as how customers can provide feedback.
4. Enhance documentation and user guides to include detailed accessibility features.
5. Develop and implement a robust feedback mechanism for users to report accessibility issues.
6. Conduct regular progress reviews with the Accessibility Task Force.

Phase 4: 

Monitoring and Continuous Improvement (Ongoing)

1. Implement monthly automated accessibility scans across all digital assets.
2. Conduct quarterly manual testing with various assistive technologies.
3. Establish a bi-annual review cycle for accessibility policies and procedures.
4. Engage with external accessibility experts and users with disabilities for ongoing feedback.
5. Implement a public-facing accessibility scorecard on the company website.

Audit and Assessment

Link to comprehensive VPAT(s)
(https://community.bridgeapp.com/hc/en-us/articles/32295548169107-Bridge-Voluntary-Product-Accessibility-Template)

Bridge is dedicated to meeting WCAG standards. 

Honouring full transparency, and showing our current progress, Bridge Learn for learners has the following issues. 

Bridge has completed work on Bridge Learn for Learner users to conform to WCAG 2.1 & 2.2 Level AA. An externally conducted VPAT is underway to confirm compliance as of December 2025. *Updated Dec. 2025

WCAG 2.1

• 1.1.1 (Non-text Content)
  • Remediation plan: Images must be provided with alternative text that can be read by screen reader programs. If the image is purely decorative, then it must be hidden from screen reader programs. The alternative text should be specified in the alt attribute. If the image only needs to be hidden from screen reader programs, the aria-hidden attribute can be used for this purpose. If the element can be activated, then it must be given a role, for example role="button".
  • Bridge Learn

• If Bride Advanced Media purchased

• 1.4.11 (Non-text Contrast)
  • Remediation plan: Elements have insufficient color contrast. Adjust foreground and background colors to meet required contrast ratios (e.g., 4.5:1).
  • Bridge Learn

• 1.4.3 (Contrast (Minimum))
  • Remediation plan: Adjust background color to #0076bf and the original foreground color to #ffffff to meet a contrast ratio of 4.83:1.
  • Bridge Learn

• 2.1.1 (Keyboard)
  • Remediation plan: Regardless of the method used, the result should always be identical, and the appearance of focus should be uniform. The "Skill building page" should open consistently.
  • Bridge Learn

• 2.1.2 (No Keyboard Trap)
  • Remediation plan: Investigate potential software errors.
  • Bridge Learn

• 2.4.3 (Focus Order)
  • Remediation plan: TAB order should follow the natural top to bottom, left to right movement. All clickable items should be included in the TAB order as well.
  • Bridge Learn

• 2.4.4 (Link Purpose (In Context))
  • Remediation plan: Each link name should be unique and describe the purpose of that individual link.
  • Bridge Learn

• 2.4.6 (Headings and Labels)
  • Remediation plan: Headings on the page must start at level 1 and must not skip any level. The HTML tags H1…h6 are used to structure the page, with no breaks. The page may contain one h1 element, namely the document title.
  • Bridge Learn

• 2.4.7 (Focus Visible)
  • Remediation plan: Include a close option in the TAB sequence within the window. The location of focus should always be known and seen. Make every TAB step clearly visible. Focus should be more obvious, and the logical order of TAB sequence may be Search bar first, and Export, Grid, Filter on the right hand side after that. Focus should be obvious. Cannot rely on color only for information; focus should be obvious.
  • Bridge Learn

• 3.2.1 (On Focus)
  • Remediation plan: Ensure that when a component receives focus, it does not initiate a change of context.
  • Bridge Learn

• 3.3.2 (Labels or Instructions)
  • Remediation plan: The "More Actions" button needs to be given an algorithmically identifiable label. The "Delete" button needs to be given an algorithmically identifiable label. The "Download PDF" button needs to be given an algorithmically identifiable label. All buttons need to be given algorithmically identifiable labels.
  • Bridge Learn

• 4.1.2 (Name, Role, Value)
  • Remediation plan: The menu button needs to be given an algorithmically identifiable label. The "Helpful Resources" toggle button needs to be given an algorithmically identifiable label. The "Apps & Settings" toggle button needs to be given an algorithmically identifiable label. The "Clear search" button needs to be given an algorithmically identifiable label. The "Click to Search" button needs to be given an algorithmically identifiable label. The "More Actions" button needs to be given an algorithmically identifiable label. The "Delete" button needs to be given an algorithmically identifiable label. The "Download PDF" button needs to be given an algorithmically identifiable label. All buttons need to be given algorithmically identifiable labels. Provide algorithmically identifiable label, role, and status for elements. Give clickable elements algorithmically identifiable labels. The sortable items need to have labels that can be read by screen reader programs (e.g., using aria-label).
  • Bridge Learn

• If Bridge Advanced Media Purchased

WCAG 2.2

• 4.1.3 (Status Messages)
  • Remediation plan: The displayed messages should be automatically read by a screen reader (e.g., using the aria-live attribute). The screen reader should be allowed to read out the active state of menu items (e.g., using the aria-current attribute). The user should be notified when a link opens in a new window (e.g., by including an "Opens in new window" icon).
  • Bridge Learn