-
Search Results
-
Dear Enfold Team,
During accessibility testing of our website (https://restaurant-weichandhof.de) built with the Enfold theme, the AXE tool reported an issue concerning the built-in Scroll-to-Top button.
Specifically, the tool flags an error indicating that an element with aria-hidden=”true” is focusable. This error appears when the page is scrolled before starting the test (so the Scroll-to-Top button is visible). If the page is not scrolled prior to testing, the button is not visible and the error does not appear. This suggests the issue exists on every page but is only flagged depending on test conditions. This error really appears in EVERY SITE. Is there a way to fix it by not changing the ENDOLD-php-Code (> not consistent solutions for updates) ?
So I kindly ask you to review this ARIA issue and advise on how to ensure the Scroll-to-Top button meets WCAG 2.1 AA requirements.
Thank you in advance for your support.
Best regards, DianaTopic: Theme update
Hello we have enfold. It seems there was an update and it broke our landing page. We are struggling with the visibiilty of all features and need assistance to get it back up and running without issue. rtstracks.com
I just purchased the Enfold theme .. i have already used the theme before inthe past there is a drag and drop contact form now in the new theme i cannot see it Can anyone help me out where it is now.
Hi
Is it planned, that we can use Google reCAPTCHA alternatives with Enfold in the near future?For example Contact Form 7 implemented Cloudflare Turnstile:
Would be nice, if we could also use Google reCAPTCHA alternatives with Enfold.
Best regards
MikeTopic: lightbox issues
hi
I just took over a site that is using another theme together with Site Origin builder. (I am used to using enfold). I was having trouble with the lightboxes not working even though my images are set to open in a media file. Some of them work and some don’t, and sometimes the images seem to default back to no lightbox. I switched the theme to Enfold on a staging site, but the same thing is happening. I still have Site Origin installed since I don’t want to rebuild the whole site. Can you see if there is a conflict or what the issue is?
thanks for your help
NancyTopic: 2 Ränder
Hallo,
Ich hätte 2 Anliegen.
1) Auf meiner Website (Vorlage: Enfold Freelancer) wäre es ideal, wenn das Logo links am Rand ansteht. Geht das?
2) Bei schmäleren Fenstern ist der Abstand vom Text zum Rand viel zu breit. Besonders am Handy bleiben nur 2 Wörter nebeneinander stehen. Kann ich den Rand wo editieren oder könnt ihr mir ein CSS dafür schreiben? Ich habe den Eindruck, dass der Rand fix definiert ist. 10% würde besser passen.Vielen Dank für eure Hilfe!
lg alexDear Support Team,
I’m working on improving the accessibility of our website https://restaurant-weichandhof.de/candle-light-dinner/ and have encountered an issue with the Timeline element in the Enfold theme that causes errors in accessibility testing tools such as Google Lighthouse / WAVE ….
The Timeline element automatically generates the following heading structure: (Example: first milestone point)
<h2 class=”av-milestone-date”>Wertgutschein bestellen</h2>
<h4 class=”av-milestone-title”>direkt online · Sofortversand</h4>
As you can see, there is a heading level h2 directly followed by an h4, skipping h3 entirely. Lighthouse / WAVE flags this as a failure:
“Heading elements are not in a sequentially-descending order”
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies.
Unfortunately, there is no option within the Timeline element to control or override the heading levels, and no content can be inserted between the two to preserve proper hierarchy.
We are trying to follow WCAG 2.1 Level AA guidelines and ensure proper semantic heading order, but this structural limitation of the Timeline element makes it impossible.
Could you please help me in this issue?
Thank you very much for your support!
Best regards
DianaHi Enfold Support,
I’m experiencing a repeatable bug with the Enfold gallery — specifically when using image subtitles.
On a page with an Enfold gallery, each image has been given a subtitle (via the built-in options). Everything works fine initially. However, after I scroll past the first image and then scroll back up to it, the subtitle is suddenly replaced with the string “null” on the frontend.
This behavior suggests that the JavaScript responsible for handling image subtitles is not correctly preserving or restoring the subtitle data after the element is reloaded or redrawn (possibly due to lazy loading or Masonry reflow). It appears that the subtitle is being dynamically injected, but the value is lost or misread after scrolling, resulting in a “null” string being displayed instead.
This only happens after interaction — when returning to the image — and seems like a client-side rendering issue.
Could you please look into this? I’ve shared a few example pages in the private content. Thanks!
Best regards,
MartinHi,
We observed duplicate id-attributes in the mobile menu (hamburger-menu), similar to what is described in
This came up when trying to check and optimize website-compatiblity for screenreaders. Nodes of the main menu are copied over to the hamburger-menu. svg-icons (for the search) contain id-attributes which simply get duplicated – but obviously need to be transformed to become unique again.
A modification of this copy-behaviour would for example be possible in
wp-content/themes/enfold/js/avia-snippet-hamburger-menu.js
in function normalize_layout().Quick-and-dirty code for those replacements:
There was:
var menu2 = $(‘#header .main_menu’).clone(true),
ul = menu2.find(‘ul.av-main-nav’),
id = ul.attr(‘id’);We then added lines to search for the corresponding nodes in the HTML with jQuery and make replacements for all hits. ‘-hamburger’ is appended to the IDs.
var toChange;
toChange = menu2.find(‘[id^=av-svg-desc-‘);
toChange.each(function() {
$(this).attr(‘id’, $(this).attr(‘id’) + ‘-hamburger’);
});
toChange = menu2.find(‘[id^=av-svg-title-‘);
toChange.each(function() {
$(this).attr(‘id’, $(this).attr(‘id’) + ‘-hamburger’);
});
toChange = menu2.find(‘[aria-labelledby^=av-svg-title-‘);
toChange.each(function() {
$(this).attr(‘aria-labelledby’, $(this).attr(‘aria-labelledby’) + ‘-hamburger’);
});
toChange = menu2.find(‘[aria-describedby^=av-svg-desc-‘);
toChange.each(function() {
$(this).attr(‘aria-describedby’, $(this).attr(‘aria-describedby’) + ‘-hamburger’);
});It’s quite an edge case, but could potentially irritate a screen reader.
Viewing 30 results - 1,861 through 1,890 (of 244,163 total)


