'Duplicate' field on Service creation

[adriannelee]

Description

As a screen reader, I need to be able to distinguish the service name and email address as 2 different fields when I create a service so that I don't input duplicate information and assume there's something wrong with the page.

WHY are we building?

• When 'service name' is interpreted as the email address field, it means the email address field looks like a duplicate field

WHAT are we building? Revisions to the "Create a service" screen, to the service name and the Sender address field.

VALUE created by our solution

• More accurate data and fewer instances where we have to watch and correct data
• Protect reputation as a product without many errors, increase trust

Documentation and Artifacts

Good docs, figma mockups, ADRs, screenshots etc.

Acceptance Criteria

Given some context, when (X) action occurs, then (Y) outcome is achieved

• [ ] When using a screen reader and only using the tab key or only navigating using the input fields, it's still clear the two fields are different.

• [ ] Generate appropriate log messages so that executions of this feature can be tracked

• [ ] Can misuse of this feature cause harm? If yes, create an alert

• [ ] Update the status of related findings, insights, and hypotheses on the Research Airtable

• [ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)

• A11y

• Bilingualism

• Privacy considerations

• Security controls in place

• Measuring success and metrics

Related Research Airtable records

• See above

QA Steps

• [ ] Tested in a realistic production scenario

[YedidaZalik]

Not adding to Ally stmt because has been addressed and it's a UX problem