Responsive contact form

Solution retrospective
I'm proud that I was able to easily build the layout for the contact form and understood how to correctly use semantic HTML to improve accessibility.
What challenges did you encounter, and how did you overcome them?There wasn't any particular challenge that was difficult
What specific areas of your project would you like help with?- Is my use of
aria-describedby
,aria-required
, andaria-invalid
appropriate and sufficient for this form? Are there other ARIA attributes or techniques I could use to further enhance accessibility, especially for the custom radio/checkbox controls or the toast notification? - Are there ways to make my custom radio button and checkbox styling more robust or cross-browser compatible? Are there potential accessibility issues with hiding the native input and relying solely on CSS for the visual representation?
Please log in to post a comment
Log in with GitHubCommunity feedback
- P@AnjelToppo
You made an excellent attempt at completing this challenge overall.
However, I noticed that the screen reader is not reading the success message toaster.
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord