New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 666131 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Task
Launch-M-Approved: 57-Dev , 57-Beta , 57-Stable-Exp , 57-Stable

Blocking:
issue 665622



Sign in to add a comment

Accessibility Review: ADB and Fastboot in container

Project Member Reported by lpalmaro@chromium.org, Nov 17 2016

Issue description

Please submit! 

0. Is your feature still on track to launch by your specified milestone? If
not, please update the milestone accordingly.

1. Does your feature introduce any new UI or modify any existing UI? If
not, you're done!

2. What are the platforms that have new or modified UI that needs to be
tested? Windows, Mac OS X, Linux Desktop, Chrome OS, Android, iOS

3. Give instructions for how someone could test your feature, including
minimum revision / build number, any command-line flags needed, and exactly
how to trigger the feature.

4. Link to any mocks or UI design documents.

5. Can you completely interact with your UI and use your feature using only
the keyboard? Is it always visually clear which item has focus?

6. Please list any nonstandard keys a user would have to press to interact
with your UI using the keyboard, i.e. any keys other than Tab, Space,
Enter, and arrow keys.

7. If your feature has any web component to it, does it pass an
Accessibility Developer Tools Audit? Install the extension (available at
https://chrome.google.com/webstore/detail/accessibility-
developer-t/fpkknkljclfencbdbgkenhalefipecmb?hl=en), open Dev Tools, click
on the Audits tab, then run an Accessibility audit. Please list any
warnings and errors here and an explanation of why they don't apply. (That
link works on the open web. Try the internal beta version to run the audit
on webui or on apps: https://chrome.google.com/webstore/a/google.com/detail
/accessibility-developer-t/lfcjaoacndhilkpdhgnfjnienfoibnaa.)

8. Are you using color, sound, or an image/graphic as the primary way to
communicate any information? If so, what alternative have you provided for
users who have trouble seeing or hearing?

9. Google has launched the company-wide Google Accessibility Rating (GAR)
at goto/gar-web. It provides an immensely helpful guide for designing and
implementing features with accessibility in mind, and ensuring that your
primary use cases are accessible. Based on the doc, please provide a rough
estimate of the GAR level at which your feature is (Level 1, 2, 3, 4, or
5).

 

Comment 1 by hannia@chromium.org, Nov 22 2016

Labels: Proj-Containers Launch-M-Approved-57-Dev Launch-M-Approved-57-Beta Launch-M-Approved-57-Stable-Exp Launch-M-Approved-57-Stable
Status: Fixed (was: Assigned)
Our feature does not add any new UI or modify existing UI. They are only command line tools. One pager  here
https://docs.google.com/a/google.com/document/d/1sUPXXzLHMRaW8uPi3alYAYNafdZZEOEFO6NE3c9sFB8/edit?usp=sharing
Perfect - thanks! 

Comment 4 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58
Labels: Review-Accessibility Type-Task

Comment 6 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 7 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 8 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 9 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)
Components: OS>Systems>Containers
Labels: -Restrict-View-Google

Sign in to add a comment