What about accessibility? Will it be quick for keyboard users to reach it when it's down there at the bottom? How quickly will screen readers point out it is existing for blind users? Where does it exist in the DOM? Personally I think this navigation is in the way. You want to read what is below, but there's a big navigation element that is covering it. I'd be more concerned about how it affects accessibility though. To be fair, Antler is having some issues already there, try to tab around the page. There's no indication that you are targeting the Locations drop down menu. When you keep tabbing and it gets to the map, you get stuck there for ages to continue past it since it tabs to every single dot link with them seemingly being doubled up with a # link, or maybe those are location pages without content available, at any rate, a lot of tabbing. It only tabs to one blog entry and you can't navigate left and right with the arrow keys to select other blog posts. There's no indication that the user has tabbed to the little dots nor the left and right arrow icons below the blog posts. Not that it matters, you can't navigate to anything but the first entry in the list of them anyways. At the bottom of the page there's a few invisible links to Facebook, Instagram, Twitter and Linkedin before it tabs to the SVG icons that links the same things (except FB.)
This nav is definetly experimental. It may not be ideal for people using screen readers or keyboard only. The goal is to increase scroll depth and try something new. I think overall, it will help more users!
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
Wow fantastic tutorial😇
@@akbarbadsha25 thanks 🙏
You rocks as always ❤
@@worksmart8166 thanks so much ❤️
Great tutorial! thank you ❤
thanks so helpful! Could you please explain how to do in framer too? Thanks!
@@riccardotosatto3264 I really need to learn Framer 😅
Framer is same as figma@@finndollimore
What about accessibility? Will it be quick for keyboard users to reach it when it's down there at the bottom? How quickly will screen readers point out it is existing for blind users? Where does it exist in the DOM? Personally I think this navigation is in the way. You want to read what is below, but there's a big navigation element that is covering it. I'd be more concerned about how it affects accessibility though.
To be fair, Antler is having some issues already there, try to tab around the page. There's no indication that you are targeting the Locations drop down menu. When you keep tabbing and it gets to the map, you get stuck there for ages to continue past it since it tabs to every single dot link with them seemingly being doubled up with a # link, or maybe those are location pages without content available, at any rate, a lot of tabbing. It only tabs to one blog entry and you can't navigate left and right with the arrow keys to select other blog posts. There's no indication that the user has tabbed to the little dots nor the left and right arrow icons below the blog posts. Not that it matters, you can't navigate to anything but the first entry in the list of them anyways. At the bottom of the page there's a few invisible links to Facebook, Instagram, Twitter and Linkedin before it tabs to the SVG icons that links the same things (except FB.)
This nav is definetly experimental. It may not be ideal for people using screen readers or keyboard only.
The goal is to increase scroll depth and try something new. I think overall, it will help more users!