Carebeau Hair Treatment Wax provides your hair with glossy shine and restores damaged hair. Ideal for daily hair treatment or hair steaming, it delivers the best results. Available in various formulations such as Beer & Egg Yolk, Coconut, Papaya & Egg Yolk, and Pomegranate.
● Beer & Egg Yolk: Makes hair soft and smooth.
● Coconut: Helps hair become weighty and healthy.
● Papaya & Egg Yolk: Makes hair shiny, soft, and healthy.
● Pomegranate: Keeps hair colorful, shiny, and lively.
● Bergamot: Reduces dandruff and itching.
● Butterfly Pea: Helps maintain healthy, voluminous hair.
● Cherry Blossom: Enhances hair health and appearance.
● Goat Milk: Strengthens and moisturizes hair.
● Honey: Adds shine and helps maintain hair color.
● Oats: Smooths and detangles hair.
● Peppermint: Cools and nourishes the scalp.
● Sunflower: Moisturizes and softens hair.
● White Tea: Protects hair cells from aging.
● Yoghurt: Moisturizes and nourishes hair.
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Goat Milk
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Beer & Egg Yolk
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Papaya & Egg Yolk
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Peppermint
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - White Tea
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Oats
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Coconut
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Rice Milk
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Pomegranate
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Honey
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Yoghurt
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Cherry Blossom
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Bergamot
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Sun Flower
● Carebeau Hair Treatment Wax (500 ml) (x2 Units) - Butterfly Pea
● Carebeau Hair Treatment Wax (1000 ml) - Coconut
● Carebeau Hair Treatment Wax (1000 ml) - Beer & Egg Yolk
● Carebeau Hair Treatment Wax (1000 ml) - Papaya & Egg Yolk
● Carebeau Hair Treatment Wax (1000 ml) - Pomegranate
Apply Hair Treatment after shampoo leave for 10-15 minutes. Rinse off with water and set your style.
● 500 g x 2 Units: 13.37 kg
● 1,000 g: 12.71 kg
● 500 g x 2Units: 29 x 38.7 x 23.2 cm
● 1,000 g : 34.6 x 44 x 16.4 cm
-
● Beer & Egg Yolk: 10-1-6200032279
● Bergamot: 13-1-6500007697
● Butterfly Pea: 13-1-6500012497
● Cherry Blossom: 10-1-6100006468
● Coconut: 10-1-5865643
● Goat Milk: 10-1-5865643
● Honey: 10-1-5865643
● Oats: 10-1-5865643
● Papaya & Egg Yolk: 13-1-6200032997
● Peppermint: 10-1-6100039856
● Pomegranate: 10-1-5865643
● Rice Milk: 10-1-5865643
● Sunflower: 13-1-6500007698
● White Tea: 10-1-5865643
● Yoghurt: 10-1-5865643
● Beer & Egg Yolk: 8851427004957
● Bergamot: 8851427020629
● Butterfly Pea: 8851427020582
● Cherry Blossom: 8851427015755
● Coconut: 8851427001000
● Goat Milk: 8851427004971
● Honey: 8851427015038
● Oats: 8851427004940
● Papaya & Egg Yolk: 8851427004964
● Peppermint: 8851427004988
● Pomegranate: 8851427012648
● Rice Milk: 8851427012631
● Sunflower: 8851427020605
● White Tea: 8851427004933
● Yoghurt: 8851427015052
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
export@carebeau-enjoy.com
info@carebeau-enjoy.com
.webp)
.webp)
