Skip to content

Commit 4b49fee

Browse files
wolfibDevtools-frontend LUCI CQ
authored andcommitted
[Docs] Add page zoom a11y policy doc
Bug: none Change-Id: If30469eef9bbb61d7234e2ee3116576dd90f4bac Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6105252 Auto-Submit: Wolfgang Beyer <[email protected]> Reviewed-by: Benedikt Meurer <[email protected]> Commit-Queue: Benedikt Meurer <[email protected]>
1 parent c7ac387 commit 4b49fee

File tree

6 files changed

+45
-0
lines changed

6 files changed

+45
-0
lines changed

docs/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,7 @@ below.**
5252
### Policies
5353

5454
* [Chromium DevTools Slow-Close Policy](./policy/slow-close.md)
55+
* [DevTools Page Zoom Accessibility Policy](./policy/gar-page-zoom-policy.md)
5556

5657
### Useful Commands
5758

docs/policy/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,3 +4,4 @@ This folder contains the policies relevant to the development of the Chromium
44
DevTools.
55

66
1. [Chromium DevTools Slow-Close Policy](./slow-close.md)
7+
2. [DevTools Page Zoom Accessibility Policy](./gar-page-zoom-policy.md)
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# DevTools Page Zoom Accessibility Policy
2+
3+
Chrome DevTools needs to fulfill the Google Accessibility Rating (GAR) criteria.
4+
5+
GAR Web’s page zoom criteria state: “Confirm the application is also usable []
6+
with page zoom enabled by 200% at a browser resolution of 1024x768 pixels. This
7+
width is the equivalent to resizing a browser window to 512 pixels…”
8+
9+
It is unclear what exactly this means for DevTools: DevTools can be opened as
10+
part of the main Chrome window (docked view) or as a separate standalone window
11+
(undocked view). In both cases the overall DevTools window/panel is resizable,
12+
and it contains sub-panels which are themselves resizable.
13+
14+
Docked DevTools, with top and bottom panel, top panel split vertically: <br>
15+
![Docked DevTools with multiple panels](./images/docked-devtools.png) <br>
16+
17+
Undocked DevTools, zoom factor 200%, with top and bottom panel, top panel
18+
split horizontally: <br>
19+
![Undocked DevTools with multiple panels](./images/undocked-devtools.png) <br>
20+
21+
As can be seen in the second screenshot above, with multiple panels open at the
22+
same time, there is not much space left for each panel.
23+
24+
Because of the panels’ resizability, we need to establish minimum panel sizes
25+
for GAR zoom testing. We have therefore agreed on the following criteria for
26+
a11y testing of DevTools with Page Zoom:
27+
28+
* DevTools should be opened in a separate window (=undocked view), with a
29+
resolution of 1024x768 pixels and a zoom factor of 200%.
30+
* When testing a panel in the top drawer (Elements panel, Network panel,
31+
Performance panel,…), the whole 1024x768 pixel window should be available for
32+
the panel. Bottom drawer panels should be closed by pressing ‘Esc’.
33+
* When testing a panel in the bottom drawer, the panel should not be smaller
34+
than half the size of the overall DevTools window (i.e. a height of 384 pixels
35+
at 200% zoom).
36+
37+
Undocked DevTools, 1024x768 pixels, zoom factor 200%, ready for page zoom a11y
38+
testing of the bottom panel: <br>
39+
![DevTools page zoom a11y testing](./images/devtools-gar-testing.png) <br>
40+
41+
## References
42+
43+
[Supported viewport sizes and zoom levels in Chrome DevTools](https://goo.gle/smoldevtools)
262 KB
Loading
681 KB
Loading
297 KB
Loading

0 commit comments

Comments
 (0)