Enhancement Release 12.19.0 - AODA
12.19.0 Go Live: September 3rd, 2025
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
SD-65684 | Attestation/ ASQ Questions | A bug was identified whereby the ASQ Sponsorship questions (21-23) were prepopulated during Advisor onboarding. This has now been fixed to default to blank | Advisor profile- Onboarding |
SD-71325 | Attestation- Name Change | The name change rejection banner was not properly aligned on the UI during the attestation process. This issue has been resolved | Advisor profile-Attestation- Name Change |
SD-70819 | AODA – Recurring Issue -Standardize Pop-Ups | A standardized template to resolve recurring instances of the following AODA guidelines was created.
| Regulatory -AODA |
SD-71004 | AODA – Recurring Issue - Meaningful Sequence | A standardized template to resolve recurring instances of the following AODA guideline was created:
| Regulatory -AODA |
SD-70796 | AODA - Recurring Issue- Meaningful text for buttons and links | A standardized template to resolve recurring instances of the following AODA guideline was created:
| Regulatory -AODA |
SD-70005 | AODA -Corporation Profile -Account Activity | 1 instance of guideline 1.3.1 was resolved
1 instance of guideline 4.1.2 was resolved
| Regulatory -AODA |
SD-70006 | AODA -Corporation Profile -Tag Admin | 1 instance of guideline 1.1.1 was resolved
2 instances of guideline 1.3.1 were resolved
6 instances of guideline 1.3.2 were resolved
6 instances of guideline 2.4.3 were resolved
1 instance of 2.4.4 were resolved
2 instances of guideline 2.5.3 were resolved
2 instances of guideline 4.1.2 were resolved
| Regulatory -AODA |
SD-70459 | AODA -Advisor Profile -Address | 2 instances of 1.3.1 were resolved
1 instance of guideline 2.1.1 was resolved
1 instance of guideline 2.4.7 was resolved
9 instances of 3.3.2 were resolved
| Regulatory -AODA |
SD-71248 | AODA: BUG- Fix Misplaced Table Header Cell Names Across APEXA | Table header cell names were misplaced across APEXA. This has now been resolved | Regulatory -AODA |
SD-71277 | AODA: BUG- Misaligned Table Headers | Table header values were misaligned with the content of the table. This issue has been resolved | Regulatory -AODA |
SD-70958 | AODA: BUG - Corporation Profile -Roles | The “Click here" link below the Roles table was not accessible when tabbing through via keyboard. This has now been resolved | Regulatory -AODA |
SD-71250 | AODA: BUG- Fix Missing Labels in Radio Buttons | Some labels were missing from the radio buttons, which prevented them from being highlighted as expected. This has now been resolved | Regulatory -AODA |
SD-67657 | Technical | The Send Bulk Onboarding Emails Job was enhanced to improve performance | Technical -Internal |
Guideline List -Affected Guidelines
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.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. |
2.5.3 - Label in Name - Level A(Added in 2.1) - For user interface components with labels that include text or images of text, the name contains the text that is presented visually |
3.3.2 - Labels or Instructions - Labels or instructions are provided when content requires user input |
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 |