Don, It seems like a very good start. One limiting aspect here is the idea that it will limit its scan to local addresses. I appreciate the rationale behind it, but could this be expanded to allow the person requesting the scan to optionally specify additional urls to consider as “not-foreign (in the format of *.example.tld or explicit https://site.example.tld). This could allow a single scan to cover a web presence that is spread across multiple domains. Imagine a single , comma separated input field at the bottom of the form shown in the document that was attached. --Rich Richard Merdinger GoDaddy, LLC On 8/24/16, 2:35 AM, "Don Hollander" <ua-discuss-bounces@icann.org on behalf of don.hollander@icann.org> wrote: One of the projects in this year’s plan is to produce an automated tool to evaluate an application’s UA Readiness. Below, with permission, is a proposal that Zensar, an outsourcing application developer and management organisation, is building to evaluate client side web applications. Zensar is doing this of their own accord, but it is nice to see that they are making use of UASG material. If you’ve any comments I’d be happy to forward them. Please note that this does not address the server side issues. A similar scanning tool might be able to be developed for a variety of languages on the server side too. That is a bit in the future. Zensar expects to make this tool available publicly and it’s expected to be available by the ICANN Meeting in India in early November. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander