Manuelle bedingte Textumbrüche gibt es in vielen Layout Programmen, und soweit ich weiß, auch Word hat soetwas im Programm.
Die automatische Silbentrennung in Browsern funktioniert zwar, ist sogar viel besser geworden, aber selbst die Trennung gemäß Duden ist leider nicht immer schön zu nennen – orthographisch richtig aber unschön.
Ich war überrascht wie dudenkonform die Browser (Test erfolgte mit Firefox) zB: “Aufmerksamkeitsdefizit-Hyperaktivitätsstörung” das trennen.

Nun der Ausweg – dear Rikard – ist bedingte Silbentrennungen manuell zu setzen : softhyphen – daher auch das html entity: &s hy; (­ ) natürlich ohne leerstelle – aber die Boardsoft würde das wahrscheinlich sofort umwandeln.
Leider ist es so, dass viele der ALB (Advanced Layout Builder) Element Eingabefelder die Funktion zwar erhalten, aber deren Sichtbarkeit im Backend obfuskieren.

Eine Lösung ist das wunderbare Tool ( Plugin ) von Günter zu nutzen und um einige html entities zu erweitern. Ausserdem habe ich das Plugin von Günter dahingehend noch verändert nicht mehr 3# vor und nach dem Ersatzcode zu setzen sondern nur eines:
Original File: auf Enfold Github
Edited File : https://pastebin.com/RfmWQRvN

Ist das Plugin aktiviert kann man dann statt : ­ #shy# setzen.
Diese Einsetzungen in Worten bleiben auch im Backend sichtbar erhalten und sind somit auch editierbar/verschiebbar etc.

Das oben erwähnte Wort würde man als zB entsprechend setzen:
Aufmerksamkeits#shy#defizit-Hyper#shy#aktivitäts#shy#störung

________________

Manual conditional text breaks exist in many layout programs, and as far as I know, Word also has something like that in its program.
The automatic hyphenation of browsers works, has even become much better, but even the separation according to Duden is unfortunately not always nice to call – orthographically correct but unattractive.
I was surprised how the browsers (test was done with Firefox) separate e.g.: “Aufmerksamkeitsdefizit-Hyperaktivitätsstörung” in conformity with Duden.

Now the way out – dear Rikard – is to set conditional hyphenation manually : soft hyphen – hence the html entity: &s hy; (­ ) of course without a space – but the boardsoft would probably convert that immediately.
Unfortunately, many of the ALB (Advanced Layout Builder) element input fields preserve the function but obfuscate its visibility in the backend.

One solution is to use the wonderful tool ( plugin ) from Günter and extend it with some html entities. In addition, I have the plugin from Günter still changed to no longer put 3# before and after the replacement code but only one:
Original File: on Enfold Github
Edited File : https://pastebin.com/RfmWQRvN

If the plugin is activated you can then put #shy# instead of : ­.
These insertions in words also remain visible in the backend and are thus also editable/moveable etc.

One would set the word mentioned above as e.g. accordingly ( German long Word ):
Aufmerksamkeits#shy#defizit-Hyper#shy#aktivitäts#shy#störung.

sorry didn’t see that its external links ( or on different page)

you have set the acceptance button – that is absolutely the right way.
Only if the acceptance : “Ich stimme der Datenschutzerklärung zu.” is marked the submit will work ;)

Edit : ok it does not send – on page / tab2 of contact form 7 “Mail” have you any error messages? – because cf7 is very sensitive if the recipient address does not correlate with the domain.

Rikards way is the best – give a custom-class to your slider and let it be part of the selector to the heading you like to change
the custom-class will be on the slider itself (

.custom-class .avia-caption-title {
    color: red;
}

(maybe an !important is neccessary)

btw: there is no class : avia-caption on the tree there is : slideshow_caption

Edit: sorry on easy slider there is avia-caption class !

___________
next if you like to influence it in dependency to the slide you had to insert slide class ( slide-1, slide-2 etc.)

.custom-class .slide-1 .avia-caption-title {
    color: red;
}

_____________

BUT: there is the way in the slider ALB Element itself to change the font-color:
On Styling Tab you got:

Edit: sorry on easy slider there is this option missing – only for full-screen or full-width slider

_________
offtopic:
well this is not the right way.
There are attribute selctors that could be used. – You find a good list f.e. here https://developer.mozilla.org/en-US/docs/Web/CSS/Attribute_selectors
but even those selectors are outside the curly brackets f.e.:

.anotherelement img[src*="yourpic"] {
your css code here …
}

that littel asterisk means : contains at least one occurrence of value (yourpic) within the string
the list is big see link above ( *, $, ^, ~, |, etc. pp )

hm – the button color of the non hovered state can you try the li itself – not the anchor!

.av-share-box ul li.av-share-link {
    background-color: #eee;
}

in your case this would be:
( do not forget to change back the Element Visibility )

@media only screen and (max-width: 767px) {
	.responsive .avia_responsive_table .avia-data-table tr.avia-heading-row th {
		display:none
	}

	.avia-table-6 tr:nth-of-type(2) td:nth-of-type(1):before { content: 'DI-bokser:'; font-size: 14px; font-weight: 700; text-transform: capitalize; } 
	.avia-table-6 tr:nth-of-type(2) td:nth-of-type(2):before { content: 'Shure:'; font-size: 14px; font-weight: 700; text-transform: capitalize; } 
	.avia-table-6 tr:nth-of-type(2) td:nth-of-type(3):before { content: 'DPA:'; font-size: 14px; font-weight: 700; text-transform: capitalize;} 
	.avia-table-6 tr:nth-of-type(2) td:nth-of-type(4):before { content: 'Sennheiser'; font-size: 14px; font-weight: 700; text-transform: capitalize;} 
	.avia-table-6 tr:nth-of-type(2) td:nth-of-type(5):before { content: 'AKG:'; font-size: 14px; font-weight: 700; text-transform: capitalize;} 

	.avia-table-6 tr:nth-of-type(4) td:nth-of-type(1):before { content: 'Audio Technica:'; font-size: 14px; font-weight: 700; text-transform: capitalize;} 
	.avia-table-6 tr:nth-of-type(4) td:nth-of-type(2):before { content: 'Neuman:'; font-size: 14px; font-weight: 700; text-transform: capitalize;} 
	.avia-table-6 tr:nth-of-type(4) td:nth-of-type(3):before { content: 'Beyer Dynamic:'; font-size: 14px; font-weight: 700; text-transform: capitalize;} 
	.avia-table-6 tr:nth-of-type(4) td:nth-of-type(4):before { content: 'Diverse'; font-size: 14px; font-weight: 700; text-transform: capitalize;} 
	.avia-table-6 tr:nth-of-type(4) td:nth-of-type(5):before { content: ''; font-size: 14px; font-weight: 700; text-transform: capitalize;} 
}

well the first thing they did not think of – is that there could be more heading rows than one!

so this rule affects only the first heading-row:

@media only screen and (max-width:767px) {
	.responsive .avia_responsive_table .avia-data-table tr:first-child th {
	  display:none
	}
}

put in your quick css:

@media only screen and (max-width:767px) {
	.responsive .avia_responsive_table .avia-data-table tr.avia-heading-row th {
	  display:none
	}
}

the next thing is the wrong heading ( maybe one update will fix that – it will always take only the first heading-row )
because heading in responsive case comes via pseudo container – we had now to find the rules for that …
just looking to find a solution

Edit: hm – guess there is no simple solution for tables with multiple heading-rows.
Guess you had to setup two tables for that – one for wider screens and the other for your mobile version.
There is an option on the alb element on Advanced – Element Visibility
The first one got 3 columns and 2 heading rows –
The mobile one got 6 columns and 1 heading row

see here: https://webers-testseite.de/tables/

the whole Enfold Options are language specific on WPML. You can see that in the upper left corner – there are flags indicating the independent use of Enfold Options for languages.
So even the Quick Css fields are different when you switch languages in Enfold Options. Some say this is a bug – I think it’s an added benefit.
I always style all my settings for my main language first – even with all the quick css I need.
Then I sync the settings by exporting the theme settings file – switch to the other language in the backend – and load the theme settings file into the new language. – This for each language you have.
After that, if you want to style the language differently you can start customizing.

so I suspect that in your main language you have set the Footer settings to German and left them at a different setting in the other language.

So if there are any quick css entries afterwards, you have to remember to add them for the other languages as well. In this case I do not go over the theme settings files but transfer them manually.

well the a[href*=".webp"] is allready included to 4.8.0-dev-6 but the a[href*=".webp?"] is missing – so wait til next update and change it on your parent theme file : avia-snippet-lightbox.js yourself without the child-theme construct from above and the next update will bring it back.

Well a lot of the other mates do not.
And with one post so far, I just wanted to make sure it wasn’t due to such a trivial error.

3a) if you like to have your own “backlink” you can insert this to your child-theme functions.php:

/**  new backlink in copyright insertion*/
function new_nolink(){
$kriesi_at_backlink = "<a href='https://your-wanted-backlink-path'>Your Backlink Text</a>";
return $kriesi_at_backlink;
}
add_filter("kriesi_backlink","new_nolink");

alternative the newest way :

add_filter( 'kriesi_backlink', 'my_own_backlink', 10, 1);
function my_own_backlink($link){ 
  $theme_string = 'Custom Backlink Text'; 
  $backlink_url = 'Backlink URL';
  $no = "rel='nofollow'";
  $link = " - <a {$no} href='{$backlink_url}' target='_blank'>{$theme_string}</a>";
  return $link;
}