Forum Replies Created
-
Posts
-
Hello Ismael,
Thank you for providing that solution. It works!
Please find below some links related to focus elements.
Here are some references:
https://kma.global/wp-content/uploads/2019/07/WCAG_2.1_Checklist.pdf
https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html
https://usability.yale.edu/web-accessibility/articles/links
https://dockyard.com/blog/2020/04/28/designing-for-accessibility-focus-statesHey @Yigit,
Sorry for the late response, here is what is happening that I don’t see happening in other themes and sites that are keyboard accessible…
When you tab throughout the menus on a site, the link is mark with an a:focus, and it needs a border, colour, etc to comply, when you do it right know the border makes the menu/text shift, so every time you hit the tab to go to the next menu link, the text drops down.
I’m glad you guys are finally looking into keyboard accessibility and compliance as that is the only thing this theme is missing. I really hope the new version comes out soon so I can purchase a license as now every site has to be and meet WCAG 2.1 AA Accessibility.
Thanks again.
Hey @Yigit,
Thank you for looking into this. It is working with some funny things happening in between but it is a move in the right direction. I feel more confident to in purchasing the theme again for future project. Hopefully the new version is release soon.
When do you think that version will be out/released?
Thanks again.
Hello,
You are not getting any errors because the page is password protected as it is a test page with the forms as requested to figure out the problem, so the way you looking at it is not going to show any “Know Problems” and errors.
Please use the admin info I send you, make the test page public by removing the password while you test it and you will see the errors. Attached is a screen shot of what you will see.
Thanks.
Hello Ismael,
Yes, I did use gravity forms to test it and show you that when using those forms it passes the accessibility test.
I have created a test page with the same two forms but with the enfold ones. Is there anything that you can do to pass the accessibility test?
Thanks.
Hello Ismael,
Thanks for your response, but because it is showing the error they are still reluctant on approving it. I did a test with gravity forms and it’s passing. Would you be able to help me getting the form for the newsletter in the center and the whole width?
Thank you.
Hi Yigit,
Thanks for looking into this. Everything seems to be working now. It’s weird that it wasn’t working without having to add the css but anyways it’s working now. I really appreciate the support, great as always.
You can close this ticket now!
Hi Mike,
Thanks for all of your support during this process. I really appreciated, top notch Enfold support like always.
The CSS provided didn’t work, but I was able to fix it using a filter from the article you shared.You can now close this ticket!
Thanks again!
After trying a bunch of things I was able to solve the issue. Most of the links and articles online provided work for regular themes but the Sorting By options comes from the Enfold theme itself so it doesn’t work with what you find online. You can close this ticket now. Thanks.
So the solution is to target the the enfold hook – avf_wc_product_order_dropdown_frontend.
// Modify the default WooCommerce orderby dropdown // // Options: menu_order, popularity, rating, date, price, price-desc // In this example I'm removing date & product id but you can remove any of the options function my_woocommerce_catalog_orderby( $orderby ) { unset($orderby["date"]); unset($orderby["id"]); return $orderby; } add_filter( "avf_wc_product_order_dropdown_frontend", "my_woocommerce_catalog_orderby", 20 );You can remove date or more by simply adding:
[‘default’] for’Default
[‘menu_order’] for Custom
[‘title’] for Name
[‘price’] for Price
[‘date’] for Date
[‘popularity’] for Popularity (sales)’
[‘rating’] for Average rating
[‘relevance’] for Relevance
[‘rand’] = for Random
[‘id’] for Product IDHope that helps!
Hello Mike,
Thanks again, that worked perfectly.
After reviewing the whole process in mobile I had two issues with the same zoom effect on mobile input text in some fields. One was in Calculate shipping before proceeding to checkout. I was able to fix that one with:
@media only screen and (max-width: 479px) {
.woocommerce-shipping-calculator .input-text {
font-size: 16px !important;
}
}
But I still have the zoom effect at the end of the checkout in the credit card payment input fields, please see image Img_10. I would need to increase the input text size to avoid the zoom effect. I couldn’t figure out what class to target after many tries.Thanks again for looking into this.
Hi Mike,
Like always thanks for the support, the fix for the second Issue worked perfectly!!!
The first one, I may have not explained my self correctly:
So in “My account page”, you will notice that the two columns have a light grey background Img_8 (I added circles so you can see that the grey covers the whole columns individually, the image Img_9 was only as reference so you can see better the color background as the light grey can be hard to see but is there. I believe the background shouldn’t be in the column but instead it should be the background color of the login and register form only. I updated two images to the same folder I have shared with you so you can see what I mean. What I would like to do is to have that background color for the forms only (bordered area) and not the columns. Img_9 has now notes that I think explains better the issue and what I would like to achieve.Thank you again for the great support!
Hello Mike,
As always THANK YOU very much for your help. That worked perfectly.
It took me some time to respond because I was trying to fix two things myself but after trying a bunch of things I’m giving up, I couldn’t figure out what classes to target without damaging other areas.So in the same section that we just made the change, you will notice that the two columns have a light grey background, I believe the background shouldn’t be in the column but instead it should be the background color of the login and register form. I added two images to the same folder I have shared with you so you can see what I mean. Img_8 and Img_9 shows the light grey, and I changed the color (Img_9) so you can see it better. what I would like to do is to have that background color for the forms only and not the columns. Thank you.
MOBILE: Also after fixing the issue #1, where I mentioned that I was having a zoom affect in the mobile browser, after research I found out that if the mobile browser thinks that your font is too small it will create that effect when selecting or typing information. So I was able to fix Issue #1 with:
/*increase text size on drop down text – avoid apple to zoom text*/
#top select {
font-size: 16px;}Now in the store side, I couldn’t figure out what classes to target to increase the size in the input text of the apply coupon and on the fillable fields in the check out page information. Images Img_10 and Img_11 shows the sections. So what I would like to do is to increase the size of the input text fields in mobile so I don’t get that effect every time someone needs to type their information. Your help will be very appreciated. If we get this two things fixed that site will look perfect and the user experience will be great.
If you have any questions do not hesitate to contact me.
Hi Mike,
Thanks a lot!Issue #2 and #3 were solved. I really appreciate your help and how those were solved.
The one left is Issue #4, do you have any ideas how to fix that one?Hello,
Thanks for looking into these issues. After trying a bunch of things, I was able to fix the Issue #1 myself.Could you help me with the other issues (#2, #3, #4)? I really would like your help in those. Thank you.
Hello Mike,
Thanks for your response. I applied the changed suggested and it didn’t fix the issue. I put back the original header.php to avoid confusions as the solution didn’t work. Also I want to let you know that I haven’t modified any code of the theme. I fixed the login credentials.Thank you for looking into these issues.
Hi Rikard, thanks for your response, it wasn’t that but I found the issue, it was related of the status of the portfolio entry. You can mark this as solve. Thanks again for the support.
Hi Victoria, thanks for your response. I disabled Suhosin and it didn’t work, updated to php7 and still doesn’t work. Can you please take another look and see what the problem is? Thank you again for your help.
Hi Mike,
Thanks for looking into this. Hopefully this issue is solved in later updates and that all the features ca be used. There are a lot of post related to this issue, hopefully it gets fixed soon.
Thanks again.Hi, I’m not using the layerslider in any of my pages on the site. I saw the same error that you published as well, but don’t know what to do wit it. I also did the test by disabling the plugins but that didn’t resolve the issue either.
I followed the different post regarding this issue and tried their suggestions but again it didn’t work either.
Could you take a look at it again?
Thanks.Hi Basilis,
I don’t have any cache or optimization plugins. I did disable all plugins to test again but the error is still there. The only way the issue gets fixed is by changing the theme. Can you please look at it again? it is not a plugin issue.
Thanks.
One more questions is there a way to add a button to the masonry gallery caption, like “View Project”?
Hi,
The issue I’m having is that when you run my website through http://wave.webaim.org for accessibility (required by the client) the first two errors that show are that the menu when mobile is missing title and that there is empty links. Going through the forum I found the fix for it that you guys have provided to other members, like in my previous post, but then reviewing those changes I noticed that when you do that the mobile menu gets ruin because you see the words “menu” and “close menu”. So my questions is how do I hide those while on mobile or how do I fix it so I don’t get the empty link errors ? I really need help with this, so any advice, help is highly appreciated as the project is going to be audited for accessibility.
And I’ve see in to happen every time I use an Icon element.
