In a previous review, I noticed that the way we have semantically set up our CTA button on the domain dashboard is not in line with USWDS recommendations. In voice over, the button is read off as a link, not a button. There is also a different order that this element is read that is opposite how USWDS has their button set up. This seems to be an issue with how the page was designed initially where this button got a <a> tag rather than a <button> tag. In USWDS, the label gets read off first, but in ours it's last. See the below examples for reference.
Additionally we may want to do a deeper dive of our buttons set up with VO on other pages to make sure they are set up correctly.

our button (button label last)

uswds button (button label first)

Originally posted by @gabydisarli in #1256 (comment)

Slack thread

Acceptance Criteria:

• Update the element style for CTA button "Start a new domain request" on the domain dashboard from < a > to < button >

Prioritization Comments

WCAG Conformance Level: 2.1 AA
WCAG Standard that applies:
4.1.2 Name, role, value (Critical)
3.3.2 Labels/Instructions (Critical)
Critical Failure if Not Met?: Yes
Prioritization: High/Must Do
Reason: buttons are not semantically correct, this would normally be a blocker, however enough context is given to the user relying on a screen reader in this case.