Multi-step subscription form built with Vue 3 and BEM

Solution retrospective
I am most proud of implementing high-level Web Accessibility (A11y) standards. Instead of using custom div-based controls, I refactored the project to use native hidden inputs and semantic Definition Lists (<dl>). Next time, I would like to try Pinia for better state management across different form steps.
What challenges did you encounter, and how did you overcome them?The main challenge was integrating the third-party vue-tel-input library while preserving dynamic ARIA error announcements. I overcame this by wrapping my component configurations inside Vue computed properties and properly passing dynamic attributes to the inner native input fields.
What specific areas of your project would you like help with?I would appreciate feedback on my CSS layout and Vue 3 composition architecture.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Snezana’s solution.
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