West Midlands | ITP-May-2025 | Jonathan Boahene | Form-Control

[Abayie]

Learners, PR Template

Self checklist

• I have committed my files one by one, on purpose, and for a reason
• I have titled my PR with REGION | COHORT_NAME | FIRST_NAME LAST_NAME | PROJ_NAME
• I have tested my changes
• My changes follow the style guide
• My changes meet the requirements of this task

Changelist

This PR introduces a structured and accessible HTML form for product selection. The form collects customer identity, preferred product colour and size, and delivery date. It includes:
-Semantic structure using "section", "fieldset", and appropriate headings.
-Validated input fields for name and email with patterns and required attributes.
-Radio buttons for colour choice, dropdown for size selection, and date input for delivery.
-Form accessibility and usability enhancements (e.g., autocomplete, legend, label pairing).
This sets the foundation for collecting user preferences in a clean and organized format, ready for styling or backend integration.

Questions

To make it easier I deleted the previous PR and created this new

[netlify]

✅ Deploy Preview for cyf-onboarding-module ready!

Name	Link
🔨 Latest commit	2109609
🔍 Latest deploy log	https://app.netlify.com/projects/cyf-onboarding-module/deploys/6844a87510b26b0008ec81f2
😎 Deploy Preview	https://deploy-preview-718--cyf-onboarding-module.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	2 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 89 (🟢 up 3 from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[cjyuan]

Branch "fixed".

1. Can you improve the Lighthouse Accessibility score to 100?
2. According to https://validator.w3.org/, there is no errors but there are several warnings. Can you fix the warnings?

Note: This is a continuation of the review made in #633

[Abayie]

On my end here lighthouse accessibility score is 100
Also as the validator only giving warnings and are no errors, I suggest we leave this at that, if I decide to implement those suggestions in this case it changes the logic of my entire form's accessibility implementation with "div's" being suggested

[cjyuan]

Are you referring to the Accessibility score reported by the Lighthouse tool in your browser’s DevTools, or the score shown by Netlify? If possible, could you share a screenshot of the score from your browser’s Lighthouse panel? This is what I see:

It's an easy fix. So I will go ahead and mark this PR as "Complete" first.