Open FranECross opened 5 months ago
@Mottie @jilladams Here's the ticket mentioned today in Slack. I'm cross posting the ticket link in the convo, too.
Thanks Fran! When we refine this, first step I'm thinking is for Randi / Chris to sign off on how much if any of this got done under the other components ticket(s) for Find a Form updates.
@jilladams Great point! I added a sentence to the description regarding checking to see if the recent component work took care of any of this.
@FranECross to look into this to get more details on the exact issue and then determine ownership of the fix, if any is needed. This is a change to dev only; not a prod issue. Low priority.
Status
[2024-07-02] @FranECross to look into this to get more details on the exact issue and then determine ownership of the fix, if any is needed. This is a change to dev only; not a prod issue. Low priority.
Description
Rob Garrison discovered that the file noted below has the following issues (but maybe some of them were taken care of in the recent component work?):
<!DOCTYPE html>
at the top of the pagesrc/applications/find-forms @department-of-veterans-affairs/vfs-public-websites-frontend @department-of-veterans-affairs/va-platform-cop-frontend
User story
AS A PO/PM I WANT the find-forms file to be correctly using components SO THAT Veterans don't encounter visual or assistive tech issues when viewing the page
Engineering notes / background
Analytics considerations
Quality / testing notes
Acceptance criteria