[META] Assess conformance with WCAG SC 2.4.7 "Focus Visible"

	A	B	C
1	This is a testing tracker for Drupal core issue #3163810, [META] Assess conformance with WCAG SC 2.4.7 "Focus Visible". Issue: https://www.drupal.org/project/drupal/issues/3163810 Success Criterion: https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html
2
3
4
5
6
7
8	INITIAL SETUP
9	1	Open simplytest.me
10	2	Select "Drupal core", version 9.4.x-dev (at the very bottom of the dropdown)
11	3	After test site loads, sign in as "admin" (password is also "admin")
12	4	On /admin/appearance, install Claro, then set the admin theme to Claro at the bottom of the page
13
14	TESTING A PAGE
15	1	Open the page path indicated in column A
16	2	Starting at the page breadcrumbs, tab through each focusable element on the page (links, buttons, dropdowns, form fields... anything interactive)
17	3	Look for a visual border around the element when it has focus, and/or a vertical bar in the text field to indicate the user can insert text
18	4	If you do not see any visible focus on the element when it has focus, add a comment to the test results cell in this spreadsheet, and explain which element failed (by link/button text, field label, or other description)
19	5	If you note any other WCAG failures or issues while testing for 2.4.7 (like 2.4.3 "Focus Order"), please note those as well in a comment.
20	6	Be sure to open all accordions/hidden sections and test within them. If you can't open a section with the keyboard (space bar) or open a link (Enter key), note that as a failure.
21	7	For pages with views (like admin/content), be sure to add dummy content in order to test the items within the view, sortable view columns, buttons, etc.
22	8	Once you finish testing the page, type "Passed" in the test results cell if every element passed. Otherwise, type "Failed (see comment)".
23	9	Repeat for the next page path in the next row
24
25	EXAMPLE TEST RESULTS
26		Page Path	Chrome + Mac (Desktop)
27		admin/path1	Passed
28		admin/path2	Failed (see comment)
29
30	AFTER NOTING A FAILURE
31	1	Open an issue ticket for that failure, noting the page path(s), element(s) without visible focus, and screenshot(s) if possible
32	2	Add the Drupal.org issue # and link in a new comment on that specific test results cell
33
34	WHAT NOT TO TEST (as of 9.4.x)
35	X	Toolbar at the top
36	X	Settings tray / off-canvas (black dialog on the right side of the screen)
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100