Thank you, Kareem. Mind if I get your opinion on something? I'm thinking of doing another similar series and trying to figure out what type of component to evaluate. My first thought was tabs or accordions, but I think many (most?) major products are doing these well already. My next thought was sliders. You know, the things we all love to hate and just can't seem to get away from. There are lots of opportunities to learn from existing plugins and libraries like splide, glide, and swiper.js. So, what do you think? Tab, Accordion, or Slider?
@@AdamLoweIO Well, It's tough to answer you which is which... since each one has his prioritized element, etc... I think the best way to do so is by sharing a poll here on YT... And you'll get a variety of info and data to go with this. I can see that what you did knocked all the developers mentioned in the video to look for accurate and in-depth to ensure the work was done correctly. Some already acted immediately, and some are set on progress soon... The good ones will do it. Just a matter of time. However, This can go on with any builder... one element sets to be accessible is not going to solve every issue with accessibility if they only count on the pre-made elements being accessible. If you can, I suggest you go through a tutorial on building any needed element to be accessible. The developers who made the builders mentioned or not mentioned in the video will not babysit any user website, whether accessible or not. Your skills, Professionalism by the end of this will make it. Even if tomorrow we woke up & we have the menu 100% accessible. How about you build some custom cards, reviews, etc? If the builder legit, Provides the following, Blank Divs, Custom HTML Tags, HTML Attributes...etc., Then two elements will complete the job perfectly: Your level of professionalism & time. Here is a list of great things that can come out of this (Opportunities): 1. Learn by yourself to make the website accessible as possible. (NO BS, YOU need to if you're a PRO because if you miss this, you're not a PRO 😶) 1. Tutorial on how to build any accessible element/part of the website (this must only be for legit builders) - Can be shared by any dev YT channel. 2. One of the existing or not exist dev/users will hire good dev & build a plugin for a legit accessible menu etc... (Kevin, Bricksextras...anyone with a budget/time...) 3. Wait till one of the exit builders makes it all right ^__^ then you call it the best and most excellent builder according to your skills. That's all I have now. P.S. When I was in IC, I scoped over 30 websites from existing members... tbh the result was shocking! none of them had developed the website's proper structure or even followed Kevin's best practice tutorials!!! The personal, agency websites, as it is supposed to be your impression to the clients, Some of them just through a bunch of divs stacked on each other, and that's it! Even they was present themselves as good devs and skillful ones🤨 Once again, It will end on your desk and check your skills background, and professionalism...
Thanks, Sara! It looks like I might have gotten suckered into doing a part 1.5 with a few additional themes/builders. Part 2 will probably happen late next week so I can have time to fully evaluate them and figure out how to present all this data without putting people to sleep.
@@AdamLoweIO lol I get it! I've been using Kadence for years, so I appreciated it being included. Usually not much of a data person myself, but I'll be curious to see how everything stacks up. Thanks again for all of your efforts!
Thank you SO much! I will share this with Elementor and Bricks Builder. The more input they get, the better. I’m sure there are entries on their respective BR lists your video can be added to. ❤
@@AdamLoweIO I'm aware about the ones for Elementor. I'm one of the Volunteer community leaders chasing them about accessibility. Your video helps in empowering us to get the urgency of these issues across.
Thanks for your hard work on this Adam, I know how tedious it must have been. Unfortunately that seems to be the way with a11y. I'm a bit disappointed in the Bricks results, but it just goes to show how some things are better manually coded. Are you going to share your Accessibility Criteria and Test spreadsheet? I understand if you don't... it looks like it was a TON of work! 😅 Looking forward to the second instalment!
Thanks, Brian. I’m also disappointed in Bricks but I suspect Tom will catch wind of this and make the necessary changes eventually. And yes, I do plan to share my criteria in some form or another, I just haven’t figured out how yet. I also want to make sure that everything is 100% accurate and makes sense so I don’t end up accidentally spreading misinformation.
How to upgrade what to Tailwind? I have one in the pipeline about setting up the external tailwind compiler with Pinegrow, but I’m not sure I understand what you are looking for.
Thanks for the great video. I'm surprised and a little shocked at how poor the results are for most builders. Would have thought at least Bricks would do much better.
I was surprised with Bricks too, especially since it looks like Tom made an attempt. Elementor was the real shocker though. I can’t believe a builder as prominent as that one can’t even open its mobile menu via keyboard.
Elija and I had quick chat this morning because I saw the bit about tabs now working in the release notes and got excited. Apparently, this version addressed some of the issues, but they are still working on others. I haven't had a chance to test yet, though.
Thank you so much for all the work you put into this! I learned more in 10 minutes watching your video than I have in hours of research.
Excellent work and wonderful generosity! Thanks! I hope Louis from Oxygen and Breakdown, uh I mean Breakdance, sees this.
He has seen it and claims that they are working to improve it.
Very awesome information! Your hard work here is very much appreciated
WELL DONE Adam! Thank you... You're an authentic guy and transparent... keep doing what you're doing.
Thank you, Kareem. Mind if I get your opinion on something? I'm thinking of doing another similar series and trying to figure out what type of component to evaluate. My first thought was tabs or accordions, but I think many (most?) major products are doing these well already.
My next thought was sliders. You know, the things we all love to hate and just can't seem to get away from. There are lots of opportunities to learn from existing plugins and libraries like splide, glide, and swiper.js.
So, what do you think? Tab, Accordion, or Slider?
@@AdamLoweIO Well, It's tough to answer you which is which... since each one has his prioritized element, etc... I think the best way to do so is by sharing a poll here on YT... And you'll get a variety of info and data to go with this.
I can see that what you did knocked all the developers mentioned in the video to look for accurate and in-depth to ensure the work was done correctly. Some already acted immediately, and some are set on progress soon... The good ones will do it. Just a matter of time.
However, This can go on with any builder... one element sets to be accessible is not going to solve every issue with accessibility if they only count on the pre-made elements being accessible.
If you can, I suggest you go through a tutorial on building any needed element to be accessible.
The developers who made the builders mentioned or not mentioned in the video will not babysit any user website, whether accessible or not. Your skills, Professionalism by the end of this will make it. Even if tomorrow we woke up & we have the menu 100% accessible. How about you build some custom cards, reviews, etc?
If the builder legit, Provides the following, Blank Divs, Custom HTML Tags, HTML Attributes...etc., Then two elements will complete the job perfectly: Your level of professionalism & time.
Here is a list of great things that can come out of this (Opportunities):
1. Learn by yourself to make the website accessible as possible. (NO BS, YOU need to if you're a PRO because if you miss this, you're not a PRO 😶)
1. Tutorial on how to build any accessible element/part of the website (this must only be for legit builders) - Can be shared by any dev YT channel.
2. One of the existing or not exist dev/users will hire good dev & build a plugin for a legit accessible menu etc... (Kevin, Bricksextras...anyone with a budget/time...)
3. Wait till one of the exit builders makes it all right ^__^ then you call it the best and most excellent builder according to your skills.
That's all I have now.
P.S. When I was in IC, I scoped over 30 websites from existing members... tbh the result was shocking! none of them had developed the website's proper structure or even followed Kevin's best practice tutorials!!! The personal, agency websites, as it is supposed to be your impression to the clients, Some of them just through a bunch of divs stacked on each other, and that's it! Even they was present themselves as good devs and skillful ones🤨
Once again, It will end on your desk and check your skills background, and professionalism...
Great video, Adam!
Great information, thank you
THANK YOU FOR THIS!!!! 🙌
It was a fun project, and I learned a TON about the strengths and weaknesses of different platforms.
Wowza, really appreciate your hard work here and sharing with us. And looking forward to part 2!
Thanks, Sara! It looks like I might have gotten suckered into doing a part 1.5 with a few additional themes/builders. Part 2 will probably happen late next week so I can have time to fully evaluate them and figure out how to present all this data without putting people to sleep.
@@AdamLoweIO lol I get it! I've been using Kadence for years, so I appreciated it being included. Usually not much of a data person myself, but I'll be curious to see how everything stacks up. Thanks again for all of your efforts!
Great topic and information. Thank you.
Excellent video and information!! Thank you for doing all this research and sharing it.
I'm glad it was helpful! The more we all know, the better we can serve our customers and propel the industry forward.
Strong work. Thanks for putting this together 💪🏻
Great work buddy
Thank you so much for the awesome tut :)
Thanks for this. Very valuable info inhere.
Max MegaMenu has a setting to open sub-menu on click vs. hover but it is not the default. Thanks for creating this survey of menus!
Changing that setting affects the mouse behavior, but keyboard focus still automatically triggers the dropdown.
@@AdamLoweIO Thanks! Didn't realize that!
Thank you SO much! I will share this with Elementor and Bricks Builder. The more input they get, the better. I’m sure there are entries on their respective BR lists your video can be added to. ❤
I know someone already added a BR for Bricks, and I'm pretty sure I've seen multiple unresolved BRs about the Elementor issue.
@@AdamLoweIO I'm aware about the ones for Elementor. I'm one of the Volunteer community leaders chasing them about accessibility. Your video helps in empowering us to get the urgency of these issues across.
Very, very, very interesting.
I was surprised to see how some high-profile tools completely miss the mark.
Good stuff. It's interesting to see the wide range of accessibility for each builder. Can you add Beaver Builder to this?
Yeah, a few people have asked about it. I’ll do a quick test as a YT short and add the full results to the next part.
Thanks for your hard work on this Adam, I know how tedious it must have been. Unfortunately that seems to be the way with a11y. I'm a bit disappointed in the Bricks results, but it just goes to show how some things are better manually coded.
Are you going to share your Accessibility Criteria and Test spreadsheet? I understand if you don't... it looks like it was a TON of work! 😅
Looking forward to the second instalment!
Thanks, Brian. I’m also disappointed in Bricks but I suspect Tom will catch wind of this and make the necessary changes eventually.
And yes, I do plan to share my criteria in some form or another, I just haven’t figured out how yet. I also want to make sure that everything is 100% accurate and makes sense so I don’t end up accidentally spreading misinformation.
Very interesting! Thank you! Can you make the correct menu on the video? Especially closing on the ESC key.
That’s the plan. After I do part 2, I’ll walk through how to create an accessible menu with all the correct elements, attributes, etc.
Could you make a guide on how to upgrade to tailwind 3.2? I would appreciate it very much and others too.
How to upgrade what to Tailwind? I have one in the pipeline about setting up the external tailwind compiler with Pinegrow, but I’m not sure I understand what you are looking for.
Thanks for the great video.
I'm surprised and a little shocked at how poor the results are for most builders. Would have thought at least Bricks would do much better.
I was surprised with Bricks too, especially since it looks like Tom made an attempt. Elementor was the real shocker though. I can’t believe a builder as prominent as that one can’t even open its mobile menu via keyboard.
@@AdamSLowe Thanks, added it into the existing bug report.
FYI, Oxygen just released version 4.1 which addresses nav accessibility.
Elija and I had quick chat this morning because I saw the bit about tabs now working in the release notes and got excited. Apparently, this version addressed some of the issues, but they are still working on others. I haven't had a chance to test yet, though.
So basically a do it yourself step