Overview
The end-of-life date for the setting that allowed opt-in to a WCAG 2.2 AA-compliant Universal Login was July 31, 2025, but the removal of the setting will only start after the end of August. At that time, the setting will gradually cease to be available for tenants according to their environment deployment and rollout schedule. Once the ability to opt-in no longer applies to a given tenant, Universal Login prompts will render in WCAG 2.2 AA compliant mode by default.
The Dashboard will stop displaying the Enable WCAG 2.2 AA compliant UI for Universal Login toggle within Branding > Universal Login > Advanced options and applicable Management API endpoints will behave in alignment with the inability to configure this setting. More specifically, the endpoint (GET - /api/v2/prompts) will stop returning the property enable_ulp_wcag_compliance in the response content, and the endpoint (PATCH - /api/v2/prompts) will ignore the presence of that property in the request message content.
Tenants that have made extensive customizations to Universal Login via a custom page template may experience issues due to WCAG 2.2 AA compliant mode requiring changes to the HTML structure of Universal Login elements.
Applies To
- Management API
- Prompts
- End of Life (EOL)
Cause
Opting into the WCAG 2.2 AA-compliant mode was planned as a temporary capability. The goal was to allow flexibility in transitioning to the compliant mode in a more controlled manner.
The initial announcement listed February 23, 2025, as the date the setting would cease to be available. Later notifications extended the original deadline until July 31, 2025.
Solution
Integrations performing requests to (PATCH - /api/v2/prompts) should stop including the property enable_ulp_wcag_compliance in the request message, as attempts to set this option will have no effect. In addition, integrations should not expect the property to be available in the response of the (GET - /api/v2/prompts) endpoint.
Universal Login customizations performed using a custom page template may require adjustment if they depend on a specific HTML document structure that has changed to support WCAG 2.2 AA.