Officelite coming soon. Responsive design + Accessibility
Design comparison
Solution retrospective
Features:
- Vanilla Javascript + Native CSS + Semantic HTML5.
- Responsive design + Mobile first approach.
- Form validation.
- Accessibility.
- Customised accessible drop down select element.
- Countdown to launch date (for presentation purpose: the date is set to 30 days in the future from the moment the user visits the website).
Accessibility question: I've spotted a bug: if I navigate through the site with the keyboard (using tab key), after arriving to the select element I can't go further or go back to other inputs. So to move back or forth I have to use the mouse... Any suggestions on how to fix this issue are highly appreciated!
Any other suggestions for improvement are also very welcome :)
Community feedback
- @Dev-MV6Posted 7 months ago
Hi there 👋
The reason you are unable to change the tab focus when it reaches the drop-down menu is that you are you using the
Event.preventDefault
method in yourhandleKeyPress
function which instructs the browser to not execute the default action for that event.In your case, you are telling the browser to prevent any default action when the
keydown
event is triggered on the target element, and the default action in this particular case is to change the tab focus, that's why when you press the Tab key, the focus gets stuck on the drop-down menu.Hope you find this helpful 👍
Marked as helpful0
Please log in to post a comment
Log in with GitHubJoin 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