Hey you are welcome. I am happy you found it helpful. I just try to think of real life scenarios to share, things you will actually need when u work on your own projects :)
Just curious, I do not see any WCAG or Trap Keyboard for this navigation, so it begs the question.. .if we are using the same navigation for both desktop and mobile, how are you setting and removing the trap keyboard as well as the necessary WCAG elements on Mobile only, when the navigation is opened and closed by clicking on the button, and what happens to the Aria- attributes when you are on desktop? How will having those aria attributes affect your desktop nav in a screen reader? Would it be easier to create to navs - one for desktop and one for mobile so that you could create the necessary WCAG and set the trap keyboard for Mobile, and then you wouldn't have to create a ton of conditionals for the nav to work on desktop without affecting someones ability to use the navigation with a screen reader?
Hello my friend, you don´t have to build a component inside the nav bar. If you want to render a component/page, one way to develop that is to make a component and link it with an anchor element href attribute ''. The other way is to build routes with a router like 'react-router-dom-v6' and navigate with a url to the next component/page.
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
Thank you for the tutorial, it had helped to fix my project!
Hey you are welcome. I am happy you found it helpful. I just try to think of real life scenarios to share, things you will actually need when u work on your own projects :)
superb...thank you more of this 👍
Most welcome 😊
Wonderful tutorial, thank you very much... Keep then coming! XD
Thank you so much Lucas!! 💙 I am glad u enjoyed the video ☺️
Just curious, I do not see any WCAG or Trap Keyboard for this navigation, so it begs the question.. .if we are using the same navigation for both desktop and mobile, how are you setting and removing the trap keyboard as well as the necessary WCAG elements on Mobile only, when the navigation is opened and closed by clicking on the button, and what happens to the Aria- attributes when you are on desktop? How will having those aria attributes affect your desktop nav in a screen reader? Would it be easier to create to navs - one for desktop and one for mobile so that you could create the necessary WCAG and set the trap keyboard for Mobile, and then you wouldn't have to create a ton of conditionals for the nav to work on desktop without affecting someones ability to use the navigation with a screen reader?
Very nice tutorial
Brilliant. Thanks!
You're welcome! :)
Did you deploy on the Vercel?
i loved rita!!!
Thank you Andre 😊 !!
Which vs code theme you are using ? 🙂
Thanks Rita 😍😍
Hey, you are welcome 😊 I hope you found it helpful 😊
Super informative
Cool, but how to render a component/page inside the navbar? Do you have to build the pages there inside the "li"? Or the section?
Hello my friend, you don´t have to build a component inside the nav bar. If you want to render a component/page, one way
to develop that is to make a component and link it with an anchor element href attribute ''. The other way is to
build routes with a router like 'react-router-dom-v6' and navigate with a url to the next component/page.
very good !!
Thanks a lot!
thx for ur video!
your work is good but copying and pasting code is not a good thing. Next time work on it please
Thanks
Ur welcome :)