DS data page redesign and accessibility fixes

[AnnaGingle]

Story

As a user working on the DS data page
I want the inputs to have clear instructions
so that I can avoid mistakes that could bring down my domain

Acceptance Criteria

• The changes match these designs. The following AC refer to numbered annotations in these designs.
• New empty state with new Add DS data primary button. Content changes. (1,2)
• View state with new edit & delete buttons on record card. Delete button triggers modal (8).
• Edit state for each card. (3, 4, 5, 6, 7, 9)
• Design: Content updates for view and edit state
• Registry error updates (10, 11)
• Add new record

Additional Context

No response

Issue Links

No response

Prioritization Comments

WCAG Conformance Level: 2.1 AA
WCAG Standard that applies:
Critical Failure if Not Met?: Yes
Prioritization: Blocker
Reason: The DS data page is a critical page that can cause system outage, therefore it is critical to provide clear instructions so that users do not input errors that will disrupt the entire system

• blocked by Redesign name servers page to hide IP address field #3067
• Blocked by Update DS data page with new design patterns used on name servers page update #3439

[gabydisarli]

Turned this into a sub-issue of #2368

[abroddrick]

@gabydisarli were the designs for this updated after the nameservers ticket was finished?

[gabydisarli]

@abroddrick no, its still blocked

[katypies]

This is an accessibility issue and a high impact, but it's not a result of our latest compliance audit, and therefore is not labeled for compliance. It's also quite large, and so not suited for the accessibility pod work.

[SamiyahKey]

This has been unblocked by #3067

[gabydisarli]

@SamiyahKey the ds data page redesign actually doesn’t reflect the new patterns we’ve created in the name servers page. It has issues with the technical parts that we encountered on the name servers page that need to be fixed before it can be implemented. I'm going to put blocked back on.

[katypies]

This ticket needs to be rewritten/updated to encompass the redesign work needed (design side) + spinning up a dev ticket.

[gabydisarli]

@katypies @Katherine-Osos @witha-c I've created a new sub-issue to capture the design work still needed here.