Purpose

This administrative page describes the role of the Divi Login Designer asset on the site and provides practical steps for administrators who review or update the login screens. It is not legal advice or a public-facing service description.

Accessibility & security considerations

Login pages should prioritise clear labeling, keyboard navigation, and compatibility with assistive technologies. When adjusting visual elements here, follow these minimum practices:
  • Ensure form fields have associated labels and meaningful aria attributes.
  • Maintain contrast ratios that meet WCAG AA standards for text and UI elements.
  • Do not expose sensitive configuration data in visible markup or comments.
  • Test keyboard focus order and visible focus indicators for each interactive control.

Maintenance checklist

Use this checklist before publishing changes to a login screen.

ItemWhy it mattersCompleted
Label verificationAccessibility and form clarity
Contrast checkReadability on varied devices
No plain API keysSecurity best practice
Focus states testedKeyboard users must see focus
Backup of current templateQuick rollback if needed

Update process

A concise sequence to follow when adjusting the login designer configuration.

1. Review
Confirm the purpose of the change and accessibility needs.
2. Stage
Apply changes to a staging environment; do not edit live pages directly.
3. Test
Verify labels, keyboard navigation, and contrast on multiple devices.
4. Backup
Export current template and store securely before publish.
5. Publish & Monitor
Publish during low-traffic windows and review logs for errors.

Related resources

Helpful links for administrators and colleagues who need legal, regulatory or practice-specific context.

FAQ

Who should update this page?
Site administrators or developers with access to the staging environment. Coordinate with IT and accessibility reviewers where available.
Is content on this page public?
No. This page documents administrative processes; do not copy internal configuration into public-facing pages.
Can I change logos or branding here?
Yes, but follow brand guidelines and verify contrast and alternative text. Avoid embedding sensitive links or tokens.
What if a login page breaks after a change?
Restore the backup template, clear caches, and review recent edits. If in doubt, revert to the last known good configuration and escalate to IT.
Does updating the login page affect authentication?
Visual and layout changes normally do not alter authentication flows, but never edit authentication scripts or API keys in this template without IT review.
Who to contact for legal questions about login policies?
For policy or compliance questions, contact the firm at info@trw.org or book time via Book consultation.
How often should login templates be reviewed?
Review at least annually or whenever there is a security, accessibility, or branding change.

Contact & next steps

If you need technical help with the Divi Login Designer asset or wish to discuss accessibility or compliance implications, use the contact options below.

Need assistance with policy or compliance?
We provide guidance on related legal and regulatory questions; use the links to reach the right team.

Legal-information disclaimer: This page provides administrative guidance for site maintenance and accessibility. It does not constitute legal advice. For advice on legal or regulatory issues, contact the firm directly at info@trw.org or schedule a consultation.