Rich has proposed that we change the title to indicate the UAIG is specific to HTML. Cynthia is opposed to this idea. We do actually have HTML specific information in it though. Another idea discussed was keeping the bulk of the UAIG as technology neutral but moving the HTML specifics out into an HTML implementation guide. 

Rich's review comments related to this topic:

Title: 

<change>
A user agent developer's guide to understanding and implementing Accessible Rich Internet Applications
</change>

<to>
A user agent developer's guide to understanding and implementing Accessible Rich Internet Applications using HTML
</to>

In the Abstract:

<change>
The WAI-ARIA User Agent Implementation Guide defines how implementations should expose content to accessibility APIs, helping to ensure that this information appears in a manner consistent with author intent. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.
</change>

<to>
The WAI-ARIA User Agent Implementation Guide defines how implementations should expose content to accessibility APIs when applying WAI-ARIA markup to (X)HTML markup prior to HTML 5. This guide helps to ensure that this information appears in a manner consistent with author intent. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview. 
</to>

Introduction

<change rich: note should we state the versions of HTML this supports in the "Status of this Document" section vs. here?>
The WAI-ARIA User Agent Implementation Guide is intended to provide readers with an understanding of how to implement WAI-ARIA in user agents.
</change>
<to>
The WAI-ARIA User Agent Implementation Guide is intended to provide readers with an understanding of how to implement WAI-ARIA in HTML rendering user agents. This document is limited to HTML prior to version 5.
</to>

<change>
This guide assumes that a user agent already exposes static content to ATs via the accessibility API on a given platform.
</change>

<to>
This guide assumes that a user agent already exposes static HTML content to ATs via the accessibility API on a given platform.
</to>