Forum Discussion
Setting html lang="it" language code for GDPR Privacy
Hi there,
I think I'm not the only one who has understood that from today it is not possible to select the type of language from within the various Articulate 360 tools (Storyline and RISE) so as not to have problems not only with the users' browsers for predisposition of the language, but above all for the GPDR Privacy regulations!
I created a website completely with RISE in 2018!
When I went to activate the IUBENDA licenses for the management of GDPR Privacy compliance (despite having no content in English, other than a simple logo) I discovered from a non-compliance report from IUBENDA, that I had the <tag html lang = " en "> easily publishable from Chrome with CTrl + U (see screenshot)!
I made the change by entering this code
<html lang = "en" class = "">
<head>
<html lang = "it">
<meta http-equiv = "Content-Language" content = "en-US" />
I discovered, from a further and subsequent report of non-compliance by IUBENDA, that compliance is not demonstrated by the source code (as I knew up to that moment), but by what appears with the inspection of the code obtainable in Chrome with the right key mouse and inspect (see screenshot)!
Indeed even today with inspect appears
<html lang = "en"
I did a check now to see if this problem can be solved directly from within RISE before the automatic publication of the HTML code of the page!
The URL of the web page is:
http://todste.it/content/corsi-attivita-progetti/index.html#/
You can easily check it too!
How do you think I address, or have you already addressed this problem, given that, if I do not change the language, I am forced to add the English language to the Iubenda Privacy & Cookie Policy license of the domain?
URL > http://todste.it/content/corsi-attivita-progetti/index.html#/
Thank you
source code page
Hi Stefano! I see you’ve already submitted a feature request to my team to update the source language of your content. We’ll let you know if we make a change that helps!
Hi Angelo,
I hope to receive a solution as soon as possible, because at this moment the stetod.it domain does not comply with the GDPR Privacy regulations!
I would be forced to add a license to manage content in English when in reality there is none!Thank you
Dearest Angelo,
2 months have already passed and I have not had any response!
On all of my websites, I manage compliance with the GDPR Privacy regulations through IUBENDA licenses.
This is the usual non-compliance communication that the IUBENDA control service urges me to resolve:
>>>> START EMAIL
"Dear Stefano,from a scan of your site, todste.it, we found that a translation of the privacy policy is not available for some languages, putting your compliance at risk.
Here are the languages you should add to your policy: English (US).
A company received a € 750,000 fine for a missing language in its policy!
Edit your policy and add missing languages → "
>>>> END OF EMAILI tried to edit the HTML code but it seems compliance is determined not by the source code published by the Browser but by what is published by the Browser Inspector!
You can check it out too!
If you publish the site todste.it from Chrome and publish the html code with the inspection show the html tag with lang = "en" (see attached image)
How can I solve the problem?
I tried to verify but from RISE there doesn't seem to be any option to manage the language published by the browser!
Thank you
I forgot:
the modification on the html code of the home-page already activated is the following:
<html lang = "en" class = "">
<head>
<html lang = "it">
<meta http-equiv = "Content-Language" content = "en-US" />
<meta http-equiv = "X-UA-Compatible" content = "IE = edge, chrome = 1">
<meta name = "viewport" content = "width = device-width, initial-scale = 1, maximum-scale = 1">
<meta charset = "utf-8">Hi Stefano,
We don't have any new updates to share on this feature request, and it is currently still under consideration. For your reference, here's how we prioritize feature requests. We'll let you know if there are any updates!
Hi JOE,
I am very sorry and surprised to see that none of your users have had or have this problem! And even worse that none of you have foreseen it!
Given the predominance at the international level of the management of the GDPR Privacy regulations!
Unfortunately, if you can't find me some solution to automated management without any management of the publication language from RISE, I have only two alternatives:
01 - I await your update to which you have in no way defined any type of time limit. So it is not excluded that maybe years can pass! In this case I am subject to an administrative penalty for not having managed the second language, even in the absence of web content in English. Just because the Inspection feature tag used for regulatory compliance has the lang = "en" attribute in the html tag! A company received a € 750,000 fine for a missing language in its policy!
02 - I totally delete all the pages produced in RISE So I am forced to redo the whole Website.
03 - I add the use of the EN language to the site, using a paid license activated with IUBENDA without having any type of content in English!
