From lpalmaro on contrast issues:
All text on all pages must meet an absolute min contrast level of 4.5:1, and I spot a lot of instances where this is not the case. For example, the text on the About UI that says "Open the Help App" and "Google Chrome is made possible....". It seems that all of the supporting info is too light (for context, I can't read it unless I zoom way in), but there are other instances where this seems to be the case, too. Similarly, the blue used in the "Add a Device" buttons and other similar ones. Please check contrast on each page. Here is one tool to check contrast [1], but there are many out there, including as part of the Chrome accessibility developer tools audit (extension).

[1] http://webaim.org/resources/contrastchecker/

This is partly a bug on the mocks (where it shows low-contrast text), but we should be using the specs instead of the mocks for color values.

I guess the AI is for the devs to check these things on the implemented pages (particularly in the common styles), and either fix or file bugs on bettes@ for the issues we find.

We can close this bug. Common styles (if using the spec) are all a11y compliant. 

https://folio.googleplex.com/chrome-ux-specs-and-sources/Chrome%20Inner%20Pages/03-Settings/specs#%2FSPEC-settings_color.png%3Fz=width&c=show

bettes@: this is not just about the style, but also how all users can accomplish tasks successfully (whether using mouse, keyboard, screen reader, blind, sighted, w/ a tremor, etc.)

 Issue 621821  has been merged into this issue.

 Issue 622755  has been merged into this issue.

 Issue 621402  has been merged into this issue.

 Issue 622276  has been merged into this issue.

 Issue 626891  has been merged into this issue.

I sincerely hope that this, and other accessibility bugs will be looked at and addressed before md-settings goes live. There are still many unlabeled buttons, and a keyboard user or a switch user cannot begin to navigate the UI as most controls are not even in the tab order. Thanks.

Old/classic-is broadly accessible/usable, so GAR-4, and I am surprised to see md-settings regresse and target GAR-1?

I don't think old options is GAR 4

Who's best owner?

hcarmona@ for now

Any update? How can we help to ensure that these accessibility items are fixed for md-settings?

Thanks!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ff2e5c72ba330412f724b23e2b79d302460060ef

commit ff2e5c72ba330412f724b23e2b79d302460060ef
Author: hcarmona <hcarmona@chromium.org>
Date: Thu Apr 13 04:16:31 2017

MD-Settings: A11y - Label drop down menus.

R=stevenjb@chromium.org
BUG= 603620 , 626882 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2810003003
Cr-Commit-Position: refs/heads/master@{#464293}

[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/app/settings_strings.grdp
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/appearance_page/appearance_page.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/device_page/display.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/passwords_and_forms_page/address_edit_dialog.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/passwords_and_forms_page/credit_card_edit_dialog.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/people_page/import_data_dialog.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/printing_page/cups_add_printer_dialog.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/privacy_page/privacy_page.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/search_page/search_page.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/site_settings/media_picker.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/site_settings/media_picker.js
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/resources/settings/site_settings/site_details_permission.html
[modify] https://crrev.com/ff2e5c72ba330412f724b23e2b79d302460060ef/chrome/browser/ui/webui/settings/md_settings_localized_strings_provider.cc

hcarmona@: all the blockers for this bug are now fixed.  can we mark this fixed?  have we reached GAR1 yet?

SGTM, marking as fixed.