DS data page: No error messages for empty fields and deletion when adding DS data record 3 and beyond

[AnnaGingle]

Current Behavior

When a user attempts to add a 3rd DS data record (or any subsequent record after 3) but does not fill out the required fields for DS data record 3 and then clicks "Save," the form automatically deletes DS data record 3 without displaying any error messages.

This behavior violates Section 508 Trusted Tester IDs 3.3.1-error-identification (WCAG 3.3.1) and 3.3.4-error-prevention (WCAG 3.3.4).

DS.data.record.-.error.identification.issue.mov

Expected Behavior

When a user creates a new record and they did not fill out the required fields. The user presses save and they are thrown errors prompting the user to fill out the required fields.

Steps to Reproduce

1. Create and fill out all the required fields for 2 DS data records
2. Create a third DS data record and do not fill out any fields for that record
3. Press save

Environment

Environment: Staging
Browser: Chrome

Additional Context

No response

Issue Links

• ⏬ Caused by DS data page cancel button resets form DS data page cancel button resets form #2700
• 🔄 Relates to DS data page: Associate delete button with according DS record DS data and nameservers: Associate form elements with corresponding record  #2773
• 🚫 This shouldn't be worked on until DS data page redesign and accessibility fixes #2911 and When entering name servers, don't show the IP address field by default #2368 are complete, since they may resolve this issue.

Prioritization Comments

WCAG Conformance Level: 2.1 AA
WCAG Standard that applies:
3.3.1 - Error Identification (Critical)
3.3.4 - Error Prevention (Critical, partially supports)
Critical Failure if Not Met?:
Prioritization: High/Must Do
Reason: This issue impacts both user experience and accessibility by failing to inform users of required field errors before automatically deleting their input. This can lead to user confusion and frustration, as well as a loss of entered data without warning, which is especially problematic for users with disabilities who rely on error prompts for navigation and form completion.

[gabydisarli]

Note: this may resolve itself once the updates in #2911 are implemented. @abroddrick

[lizpearl]

Sprinted this ticket in 60 but also added refinement so we check whether the updates in #2911 fixes this one. The parent ticket (#2368) appears to be the sprinted ticket but we should check on that status

[h-m-f-t]

This is slotted for 61 (Jan 6), but our portended fix is in 62...

[PaulKuykendall]

This is slotted for 61 (Jan 6), but our portended fix is in 62...

We'll look at this in Sprint Planning today.

[PaulKuykendall]

Move to Sprint 63, because 2911 might resolve this