--- a/ARIA/1.0/tests/test-files/_/555.htm Wed May 01 11:22:01 2013 -0700
+++ b/ARIA/1.0/tests/test-files/_/555.htm Wed May 01 11:26:58 2013 -0700
@@ -1,4 +1,4 @@
-<p>Expect to see the text 'Test Content' (not the default unlabeled text field) in between the next two paragraphs. If it does render, the name computation should expose 'Test Content' to th accessibility APIs. This does not render in most browsers (shows the field, not the replacement text) so it's probably not CR-required.</p>
-<p>The content-replaced image button immediately follows this paragraph.</p>
+<p>Expect to see the text 'Test Content' (not the default unlabeled input) in between the next two paragraphs. If it does render, the name computation should expose 'Test Content' to th accessibility APIs. This does not render in most browsers (shows the field, not the replacement text) so it's probably not CR-required.</p>
+<p>The content-replaced input immediately follows this paragraph.</p>
<form><input type="any" id="test" style="content: 'Test Content';"></form>
-<p>The content-replaced image button immediately precedes this paragraph.</p>
+<p>The content-replaced input immediately precedes this paragraph.</p>
--- a/ARIA/1.0/tests/test-files/_/654.htm Wed May 01 11:22:01 2013 -0700
+++ b/ARIA/1.0/tests/test-files/_/654.htm Wed May 01 11:26:58 2013 -0700
@@ -1,4 +1,4 @@
-<p>Expect to see the text 'Test Content' (not the default unlabeled text field) in between the next two paragraphs. If it does render, the name computation should expose 'Test Content' to th accessibility APIs. This does not render in most browsers (shows the field, not the replacement text) so it's probably not CR-required.</p>
-<p>The content-replaced image button immediately follows this paragraph.</p>
+<p>Expect to see the text 'Test Content' (not the default unlabeled input) in between the next two paragraphs. If it does render, the name computation should expose 'Test Content' to th accessibility APIs. This does not render in most browsers (shows the field, not the replacement text) so it's probably not CR-required.</p>
+<p>The content-replaced input immediately follows this paragraph.</p>
<form><input type="text" id="test" style="content: 'Test Content';"></form>
-<p>The content-replaced image button immediately precedes this paragraph.</p>
+<p>The content-replaced input immediately precedes this paragraph.</p>
--- a/ARIA/1.0/tests/test-files/_/655.htm Wed May 01 11:22:01 2013 -0700
+++ b/ARIA/1.0/tests/test-files/_/655.htm Wed May 01 11:26:58 2013 -0700
@@ -1,4 +1,4 @@
-<p>Expect to see the text 'Test Content' (not the default unlabeled text field) in between the next two paragraphs. If it does render, the name computation should expose 'Test Content' to th accessibility APIs. This does not render in most browsers (shows the field, not the replacement text) so it's probably not CR-required.</p>
-<p>The content-replaced image button immediately follows this paragraph.</p>
+<p>Expect to see the text 'Test Content' (not the default unlabeled input) in between the next two paragraphs. If it does render, the name computation should expose 'Test Content' to th accessibility APIs. This does not render in most browsers (shows the field, not the replacement text) so it's probably not CR-required.</p>
+<p>The content-replaced input immediately follows this paragraph.</p>
<form><input type="password" id="test" style="content: 'Test Content';"></form>
-<p>The content-replaced image button immediately precedes this paragraph.</p>
+<p>The content-replaced input immediately precedes this paragraph.</p>