MD-Settings: Label toggle button in Accessibility section.

chrome/browser/resources/settings/a11y_page/a11y_page.html

Index: chrome/browser/resources/settings/a11y_page/a11y_page.html
diff --git a/chrome/browser/resources/settings/a11y_page/a11y_page.html b/chrome/browser/resources/settings/a11y_page/a11y_page.html
index cd50d93f0ff60431afc5c94de00c23514dd89fd4..ffd329ff18f58deea07e84cbc15523a549af73e7 100644
--- a/chrome/browser/resources/settings/a11y_page/a11y_page.html
+++ b/chrome/browser/resources/settings/a11y_page/a11y_page.html
@@ -18,15 +18,11 @@
     <settings-animated-pages id="pages" current-route="{{currentRoute}}"
         section="a11y">
       <neon-animatable route-path="default">
-        <div class="settings-box first">
-          <div id="optionsInMenuLabel" class="start">
-            $i18n{optionsInMenuLabel}
-          </div>
-          <settings-toggle-button id="optionsInMenuToggle"
-              pref="{{prefs.settings.a11y.enable_menu}}"
-              aria-labelledby="optionsInMenuLabel">
-          </settings-toggle-button>
-        </div>
+        <settings-toggle-button id="optionsInMenuToggle"
+            class="settings-box"

[Dan Beam, 2017/04/07 18:55:03]

i suppose this could work but we've got a lot of other 

<div class="settings-box">
  <settings-toggle-button ...>
  </settings-toggle-button>
</div>

in the rest of the code.  class="settings-box" maybe change rules in the future
and you might want to stick with how most of the other code works because it
might apply styles in a different way than you'd expect without breaking
anything

+            label="$i18n{optionsInMenuLabel}"
+            pref="{{prefs.settings.a11y.enable_menu}}">
+        </settings-toggle-button>
         <div id="subpage-trigger" class="settings-box two-line"
             on-tap="onManageAccessibilityFeaturesTap_" actionable>
           <div class="start">