<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
div.plaintext h1 { font-size: 1.4em; }
div.plaintext h2 { font-size: 1.2em; }
div.plaintext h3 { font-size: 1.1em; }
blockquote.embedded,div.plaintext blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
div.plaintext a { color: #3983C4; }
blockquote.embedded,div.plaintext blockquote a { color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote a { color: #BBBBBB; }
div.plaintext math[display="inline"] > mrow { padding:5px; }
div.plaintext div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="plaintext"><p dir="auto">reviewed. some comments:<br>
- would be good to have access to the data ( mongodb (or a dump of it)) so we can independently assess the numbers or test. It would also be useful to the actual sites owners that were tested. Currently, we and they don’t know who was tested and the actual results. <br>
- I agree that automation of these tests can not be done on all web sites, but if 50% were automated, then it is a big saving of time, especially if this survey is repeated.<br>
- yes, html5.3 needs to be defined as the new standard and that would resolve the issue of the html form for email addresses. However, even at standard level, it will take time to get it deployed. But that is not the end of it. it just scratches the surface. The fact that a browser accepts UTF8 on the left side of an email address by complying to HTML5.3 does not warrant that the processing of the form will work. In fact, it may be the inverse since the developer would receive UTF8 data it does not expect as the previous html was not enabling utf8 to be received from the user filling the form. On this, I would suggest to include the URL of the deployment page (while seems not updated since sep2018) for html5.3 in the report, so people can see the state of the deployment of this issue: <a href="https://w3c.github.io/test-results/html53/implementation-report.html">https://w3c.github.io/test-results/html53/implementation-report.html</a></p>
<p dir="auto">Regards, Marc.</p>
<p dir="auto">On 12 Jul 2019, at 11:19, Sarmad Hussain wrote:</p>
</div>
<blockquote class="embedded"><style scoped></style>
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">Dear all,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Please find attached a recent study undertaken on the request of UASG on the
<b>Global</b> <b>Evaluation of Websites for Acceptance of E-mail Addresses 2019</b>, for your review and feedback.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Please send your feedback on <a href="mailto:ua-discuss@icann.org">
ua-discuss@icann.org</a> list (visit <a href="https://uasg.tech/subscribe">https://uasg.tech/subscribe</a> to subscribe) by 29 July. We look forward to your input. <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Regards,<br>
Sarmad<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
</div>
</div></blockquote>
<div class="plaintext"><blockquote>
</blockquote><blockquote><p dir="auto">_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</p>
</blockquote></div>
</body>
</html>