Replace accessibility-developer-tools submodule with accessibility-audit directory containing just …

third_party/accessibility-audit/README.chromium

Index: third_party/accessibility-audit/README.chromium
diff --git a/third_party/accessibility-audit/README.chromium b/third_party/accessibility-audit/README.chromium
new file mode 100644
index 0000000000000000000000000000000000000000..f0ba1bfdf6d305cfdc0deb9376054abd274b1870
--- /dev/null
+++ b/third_party/accessibility-audit/README.chromium
@@ -0,0 +1,16 @@
+Name: Accessibility Audit library, from Accessibility Developer Tools
+Short Name: accessibility-audit
+URL: https://github.com/GoogleChrome/accessibility-developer-tools/
+Version: 0
+Revision: 1932e35896baf576c64ec8ddade00cfb68f81610
+License: Apache 2.0
+License File: LICENSE
+Security Critical: no
+
+Description:
+Library of accessibility-related testing and utility code.
+
+This version has been built from the revision linked in the comment at the top of the axs_testing.js file (the revision information is added automatically by the build process). See README.md in original project for build instructions.

[darin (slow to review), 2013/09/13 07:18:23]

nit: maybe some 80-column line breaking would be nice here.

[darin (slow to review), 2013/09/13 07:18:23]

Note: The security team previously raised concerns about third-party JS
libraries being checked into Chrome that are the result of a build procedure.
The code can be difficult to audit in that form.

You might take a look at how this was handled for Polymer (see
src/third_party/polymer). It has a build.log file that provides information that
would be helpful to someone trying to re-create the bits that are committed into
the Chromium tree.

That said, this seems like test-only code, so there may be much less of an
issue.

[aboxhall, 2013/09/13 22:47:22]

Done.

[aboxhall, 2013/09/13 22:47:22]

Thanks - I did see the polymer example. The version link in the generated file
is my "poor man's" version of that - if you check out the repository at that
version and follow the build instructions, you should end up with the same
thing.

Do you think that will suffice? If not, it should be fairly straightforward to
add a build.log file in the same way.

+
+Local Modifications:
+No modifications.