Enhancement Release 13.0.0 - AODA

Enhancement Release 13.0.0 - AODA

13.0.0 Go Live: September 24th, 2025

Ticket #

Summary

Description

Area of Impact

Ticket #

Summary

Description

Area of Impact

SD-71537

Equifax- Process Full Credit Files

Some credit files received from Equifax via the offline program were not processed correctly due to mismatches between file contents and database table definitions. This issue has now been resolved and all credit files will now be processes correctly.

Advisor profile-Credit History

SD-72018

Profile Settings- Mislabeled In-Trust Setting

The setting that allows clients provide or revoke In Trust access to APEXA staff was mislabeled on the UI. This has now been resolved and the setting is labelled correctly.

Client Profile- General Settings

SD-71714

Profile Settings- Mislabeled Agreement Setting

 The setting that allows APEXA staff enable HTML or PDF agreement versions for clients was mislabeled on the UI. This has now been resolved and the setting is labelled correctly.

APEXA Staff Profile- General Settings

SD-71233

AODA - Advisor Profile - Education History

2 instances of guideline 1.3.2 were resolved

  • Profile - Education Screen - Add Save & Cancel buttons

  • Profile - Education History Screen - Content after clicking an "Add" button

2 instances of guideline 2.4.3 were resolved

  • Focus Order

3 instances of guideline 4.1.2 were resolved

  • Profile - Education History Screen - Edit Button

  • Profile - Education History Screen - Designations - Add Button

  • Profile - Education History Screen - Designations - Remove Button

Regulatory -AODA 

SD-70461

AODA -AODA - Advisor Profile - Phone Number

2 instances of guideline 1.3.1 were resolved

  • Info and Relationships

    • Table Header

    • Click Here

1 instance of guideline 1.3.2 was resolved

  • Meaningful Sequence

    • Edit Button

    • Delete Button

    • Add Button

6 instances of guideline 2.4.3 were resolved

  • Focus Order

1 instance of guideline 2.4.4 was resolved

  • Link Purpose (In Context)

    • Click here link

Regulatory -AODA 

SD-70678 

AODA - Corporation Profile -Security Settings -Focus

2 instances of guideline 1.3.2 were resolved

  • Meaningful Sequence

    • Network Complexity (Issue #149)

      • Cancel

      • Save

2 instances of guideline 2.4.3 were resolved

  • Focus Order

2 instance of guideline 2.4.4 were resolved

  • Link Purpose (In Context)

    • Allowable IP

      • Click here button

    • Network CIDR

      • Cancel

      • Save

Regulatory -AODA 

SD-70686 

AODA -Corporation Profile -Settings -Focus

1 instance of guideline 1.3.2 was resolved

  • Meaningful Sequence

1 instance of guideline 2.3.4 was resolved

  • Focus Order

    • Add

      • Save

      • Cancel

Regulatory -AODA 

SD-70687

AODA- Corporation Profile -Internal Branch Codes -Focus 

1 instance of guideline 1.3.2 was resolved

  • Meaningful Sequence

    • Cancel Button

2 instances of guideline 2.4.3 were resolved

  • Focus Order

2 instance of guideline 2.4.4 were resolved

  • Link Purpose (In Context)

    • Add/Click Here & Edit

Regulatory -AODA 

SD-70681

AODA- Corporation Profile - Roles - Focus

1 instance of guideline 1.3.2 was resolved

  • Meaningful Sequence

    • Cancel Button

1 instance of guideline 2.4.3 was resolved

  • Focus Order

2 instances of guideline 2.4.4 were resolved

  • Link Purpose (In Context)

    • Roles Table

      • Click here

      • Add Role

Regulatory -AODA 

SD-70682

AODA- Corporation Profile -Users -Focus 

2 instances of guideline 1.3.2 were resolved

  • Meaningful Sequence

    • Add Role/ User

      • Cancel Button

    • Edit Role/ User

      • Cancel Button

2 instances of guideline 2.4.3 were resolved

  • Focus Order

1 instances of guideline 2.4.4 were resolved

  • User table

    • Click here button

Regulatory -AODA 

SD-71268

AODA- Advisor Profile - Employment History

 

4 instances of guideline 1.3.2 were resolved

  • Meaningful Sequence

    • Profile - Employment History Screen - Click Here button

    • Profile - Employment History Screen - Edit & Delete Buttons

    • Profile - Employment History Screen - Content after clicking an “Add” button

    • "Profile - Employment History Screen - "Remove" button in the screen after clicking the "Add/Click here" button

4 instances of guideline 2.4.3 were resolved

  • Focus Order

1 instance of guideline 4.1.2 was resolved

  • Name, Role, Value

    • Profile - Employment History Screen - Add Button

Regulatory -AODA 

SD-70917

AODA- Advisor Profile -Profile

1 instance of guideline 1.3.2 was resolved

  • Meaningful Sequence

    • Personal Information

      • Compliance

      • History

1 instance of guideline 2.4.3 was resolved

  • Focus Order

1 instance of guideline 2.4.4 was resolved

  • Link Purpose (In Context)

    • Notification table -click here

Regulatory -AODA 

SD-71274

AODA- Advisor Profile - Insurance History

1 instance of guideline 1.3.1 was resolved

  • Info and Relationships

    • Profile - Banking Information Screen - Last column in the Table header

2 instances of guideline 1.3.2 were resolved

  • Meaningful Sequence

    • Profile - Insurance History Screen - Edit & Delete Buttons

    • Profile - Insurance" screen - "Remove" button in the screen after clicking the "Add/Click here" button

1 instance of guideline 2.1.1 was resolved

  • Keyboard

    • Profile - "Insurance History" Screen - "Click Here" button

  • Link Purpose (In Context)

    • Notification table -click here

2 instances of guideline 2.4.3 were resolved

  • Focus Order

1 instance of guideline 2.4.4 was resolved

  • Link Purpose (In Context)

    • Profile - Insurance History -> Insurance History Table -> Click here

Regulatory -AODA 

SD-71684

AODA- Recurring Issue- Advisor Profile - Corporations

An existing template was utilized to resolve the violation below:

1 instance of guideline 1.1.1

  • Non-text Content - Icon

Regulatory -AODA 

SD-71812 

AODA: BUG- Incorrect Focus Order

Focus order in the “Add User” screen was misaligned. This has now been resolved

Regulatory -AODA 

SD-71807

AODA: BUG- Duplicate Logs Created For Screen Readers

Duplicate logs were created for screen readers when editing user roles in client profiles. This has now been resolved

Regulatory -AODA 

SD-71841

AODA: BUG- Missing Table Header Text

A table header text was missing in the Employment History page. This has now been resolved

Regulatory -AODA 

SD-71652

Technical -Feature Flags- Clean Up

Feature flags that are no longer required were deleted from the system

Technical -Internal 

Guideline List -Affected Guidelines

Description

Description

1.1.1 - Non-text Content - Level A - All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.

1.3.1 - Info and Relationships - Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text

1.3.2 - Meaningful Sequence - When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined

2.1.1 - Keyboard - All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints

2.4.3 - Focus Order - If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability

2.4.4 - Link Purpose (In Context) - The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

4.1.2 - Name, Role, Value - For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies