Accessibility Statement for T‑Res


Last Updated: February 2026

Resilience Software is committed to ensuring that T‑Res, our web and mobile application for medical education, is accessible to all users, including individuals with disabilities. Accessibility is a core consideration in our product design and development process, and we recognize that achieving and maintaining accessibility is an ongoing effort.

Scope of This Statement

T‑Res currently consists of:

  1. A new system, actively under development and deployment
  2. A legacy system, which is being phased out and is planned to be fully sunset within the next year

This statement reflects the current, evidence‑based accessibility status of both systems.

Accessibility Standards

Resilience Software uses WCAG 2.1 Level AA as the primary accessibility standard for evaluating and improving T‑Res.

At this time:

  • Full WCAG 2.1 AA conformance has not been independently verified
  • Some areas of the application, particularly within the legacy system, are known to not conform to WCAG 2.1 AA

All statements below are based on documented testing results and internal assessment.

Accessibility Evaluation and Evidence New System

  • Automated testing of the new system was conducted using Axe DevTools.
  • No accessibility issues were flagged by automated Axe testing at the time of evaluation.

Important limitation: Automated testing does not detect all accessibility issues (e.g., screen reader behavior, complex keyboard interactions). Therefore, full accessibility conformance of the new system has not yet been fully verified through comprehensive manual or third‑party testing.

Status:

  • Automated testing: Completed
  • Manual testing: In progress / planned
  • Third‑party audit: Not yet conducted

Legacy System

Automated Axe DevTools testing identified numerous accessibility issues across legacy pages, including:

  • Missing alternative text
  • Missing or incorrect form labels
  • Color contrast failures
  • Landmark and structural markup deficiencies
  • Keyboard navigation issues in some components

These issues are documented in internal accessibility test reports.

Because the legacy system is scheduled to be sunset and replaced, Resilience Software’s primary remediation strategy is replacement rather than full remediation of legacy pages.

Remediation Strategy

Primary Strategy: Replacement

  • Legacy pages with known accessibility issues are being replaced with redesigned pages in the new system that follow current accessibility best practices.
  • Accessibility improvements are incorporated by default into new feature development.

Interim Remediation

  • If a client requires specific accessibility issues in the legacy system to be addressed prior to full replacement, Resilience Software can evaluate and remediate critical issues on a case‑by‑case basis.

Accessibility in the Development Lifecycle

Accessibility considerations are incorporated into development through:

  • Automated testing using Axe DevTools
  • Manual inspection during development and QA
  • Tracking of accessibility issues within the development workflow
  • Progressive improvement as features transition from legacy to new architecture

At present, formal accessibility acceptance criteria and third‑party audits have not yet been completed.

Documentation and Roadmap

A Voluntary Product Accessibility Template (VPAT / ACR) is planned but has not yet been finalized.

An accessibility roadmap exists internally and focuses on:

  • Replacing legacy pages
  • Completing additional manual testing
  • Evaluating third‑party accessibility audits once the new system is more fully deployed

Any future VPAT or conformance claims will be based solely on verified findings.

Feedback and Support

We welcome feedback regarding accessibility barriers.

Accessibility Contact

Resilience Software
support@t-res.net
1‑866‑694‑2323

We aim to respond to accessibility‑related inquiries within five business days.

Commitment

Resilience Software is committed to improving accessibility in a transparent and responsible manner. We believe that accessibility is best achieved through continuous evaluation, honest reporting, and iterative improvement rather than unsupported claims of compliance.