-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathITL_AI-Inclusive-Design-Sprints_Windows_exclusions.html
More file actions
5073 lines (4915 loc) · 390 KB
/
ITL_AI-Inclusive-Design-Sprints_Windows_exclusions.html
File metadata and controls
5073 lines (4915 loc) · 390 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Examples of potential exclusions for Windows 11 - Inclusive Tech Lab</title>
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.1/normalize.min.css">
<style>
body {font: 1rem/1.1 sans-serif; margin:2rem;}
h2 {margin-top: 3rem;}
h3 {font-size:1rem; margin-bottom:0rem;}
ul {margin-top:0.3rem;}
</style>
</head>
<body>
<main>
<h1>Examples of potential exclusions for Windows 11 - Inclusive Tech Lab</h1>
<article id="taskbar-jump-lists" aria-labelledby="taskbar-jump-lists-h">
<h2 data-principle="pattern" id="taskbar-jump-lists-h">Taskbar Jump Lists</h2>
<p class="user-action" data-principle="user-action">User right-clicks a pinned or running app to access recent files or tasks.</p>
<section id="taskbar-jump-lists-perceivable" aria-labelledby="taskbar-jump-lists-perceivable-h">
<h3 id="taskbar-jump-lists-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Taskbar Jump Lists is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Taskbar Jump Lists reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Taskbar Jump Lists dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Taskbar Jump Lists lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Taskbar Jump Lists can obscure information during interaction.</li>
</ul>
</section>
<section id="taskbar-jump-lists-operable" aria-labelledby="taskbar-jump-lists-operable-h">
<h3 id="taskbar-jump-lists-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Taskbar Jump Lists are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Taskbar Jump Lists are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Taskbar Jump Lists reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Taskbar Jump Lists are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Taskbar Jump Lists changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="taskbar-jump-lists-understandable" aria-labelledby="taskbar-jump-lists-understandable-h">
<h3 id="taskbar-jump-lists-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Taskbar Jump Lists use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Taskbar Jump Lists are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Taskbar Jump Lists lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Taskbar Jump Lists are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Taskbar Jump Lists aren't explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="drag-and-drop-file-operations" aria-labelledby="drag-and-drop-file-operations-h">
<h2 data-principle="pattern" id="drag-and-drop-file-operations-h">Drag-and-Drop File Operations</h2>
<p class="user-action" data-principle="user-action">User drags files between folders or onto applications.</p>
<section id="drag-and-drop-file-operations-perceivable" aria-labelledby="drag-and-drop-file-operations-perceivable-h">
<h3 id="drag-and-drop-file-operations-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Drag-and-Drop File Operations is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Drag-and-Drop File Operations reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Drag-and-Drop File Operations dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Drag-and-Drop File Operations lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Drag-and-Drop File Operations can obscure information during interaction.</li>
</ul>
</section>
<section id="drag-and-drop-file-operations-operable" aria-labelledby="drag-and-drop-file-operations-operable-h">
<h3 id="drag-and-drop-file-operations-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Drag-and-Drop File Operations are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Drag-and-Drop File Operations are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Drag-and-Drop File Operations reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Drag-and-Drop File Operations are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Drag-and-Drop File Operations changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="drag-and-drop-file-operations-understandable" aria-labelledby="drag-and-drop-file-operations-understandable-h">
<h3 id="drag-and-drop-file-operations-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Drag-and-Drop File Operations use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Drag-and-Drop File Operations are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Drag-and-Drop File Operations lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Drag-and-Drop File Operations are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Drag-and-Drop File Operations aren't explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="file-explorer-tabs" aria-labelledby="file-explorer-tabs-h">
<h2 data-principle="pattern" id="file-explorer-tabs-h">File Explorer Tabs</h2>
<p class="user-action" data-principle="user-action">User opens, switches, or rearranges tabs within File Explorer.</p>
<section id="file-explorer-tabs-perceivable" aria-labelledby="file-explorer-tabs-perceivable-h">
<h3 id="file-explorer-tabs-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in File Explorer Tabs is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in File Explorer Tabs reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in File Explorer Tabs dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in File Explorer Tabs lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in File Explorer Tabs can obscure information during interaction.</li>
</ul>
</section>
<section id="file-explorer-tabs-operable" aria-labelledby="file-explorer-tabs-operable-h">
<h3 id="file-explorer-tabs-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in File Explorer Tabs are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in File Explorer Tabs are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in File Explorer Tabs reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in File Explorer Tabs are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in File Explorer Tabs changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="file-explorer-tabs-understandable" aria-labelledby="file-explorer-tabs-understandable-h">
<h3 id="file-explorer-tabs-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in File Explorer Tabs use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to File Explorer Tabs are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in File Explorer Tabs lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in File Explorer Tabs are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in File Explorer Tabs aren't explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="task-manager-process-view" aria-labelledby="task-manager-process-view-h">
<h2 data-principle="pattern" id="task-manager-process-view-h">Task Manager Process View</h2>
<p class="user-action" data-principle="user-action">User opens Task Manager to monitor or end running processes.</p>
<section id="task-manager-process-view-perceivable" aria-labelledby="task-manager-process-view-perceivable-h">
<h3 id="task-manager-process-view-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Task Manager Process View is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Task Manager Process View reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Task Manager Process View dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Task Manager Process View lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Task Manager Process View can obscure information during interaction.</li>
</ul>
</section>
<section id="task-manager-process-view-operable" aria-labelledby="task-manager-process-view-operable-h">
<h3 id="task-manager-process-view-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Task Manager Process View are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Task Manager Process View are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Task Manager Process View reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Task Manager Process View are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Task Manager Process View changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="task-manager-process-view-understandable" aria-labelledby="task-manager-process-view-understandable-h">
<h3 id="task-manager-process-view-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Task Manager Process View use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Task Manager Process View are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Task Manager Process View lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Task Manager Process View are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Task Manager Process View aren't explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="credential-manager-and-saved-passwords" aria-labelledby="credential-manager-and-saved-passwords-h">
<h2 data-principle="pattern" id="credential-manager-and-saved-passwords-h">Credential Manager and Saved Passwords</h2>
<p class="user-action" data-principle="user-action">User views, edits, or removes stored credentials in Windows.</p>
<section id="credential-manager-and-saved-passwords-perceivable" aria-labelledby="credential-manager-and-saved-passwords-perceivable-h">
<h3 id="credential-manager-and-saved-passwords-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Credential Manager and Saved Passwords is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Credential Manager and Saved Passwords reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Credential Manager and Saved Passwords dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Credential Manager and Saved Passwords lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Credential Manager and Saved Passwords can obscure information during interaction.</li>
</ul>
</section>
<section id="credential-manager-and-saved-passwords-operable" aria-labelledby="credential-manager-and-saved-passwords-operable-h">
<h3 id="credential-manager-and-saved-passwords-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Credential Manager and Saved Passwords are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Credential Manager and Saved Passwords are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Credential Manager and Saved Passwords reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Credential Manager and Saved Passwords are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Credential Manager and Saved Passwords changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="credential-manager-and-saved-passwords-understandable" aria-labelledby="credential-manager-and-saved-passwords-understandable-h">
<h3 id="credential-manager-and-saved-passwords-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Credential Manager and Saved Passwords use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Credential Manager and Saved Passwords are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Credential Manager and Saved Passwords lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Credential Manager and Saved Passwords are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Credential Manager and Saved Passwords aren't explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="screen-snipping-tool" aria-labelledby="screen-snipping-tool-h">
<h2 data-principle="pattern" id="screen-snipping-tool-h">Screen Snipping Tool (Win + Shift + S)</h2>
<p class="user-action" data-principle="user-action">User captures a screenshot region and annotates or saves the result.</p>
<section id="screen-snipping-tool-perceivable" aria-labelledby="screen-snipping-tool-perceivable-h">
<h3 id="screen-snipping-tool-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Screen Snipping Tool is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Screen Snipping Tool reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Screen Snipping Tool dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Screen Snipping Tool lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Screen Snipping Tool can obscure information during interaction.</li>
</ul>
</section>
<section id="screen-snipping-tool-operable" aria-labelledby="screen-snipping-tool-operable-h">
<h3 id="screen-snipping-tool-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Screen Snipping Tool are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Screen Snipping Tool are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Screen Snipping Tool reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Screen Snipping Tool are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Screen Snipping Tool changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="screen-snipping-tool-understandable" aria-labelledby="screen-snipping-tool-understandable-h">
<h3 id="screen-snipping-tool-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Screen Snipping Tool use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Screen Snipping Tool are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Screen Snipping Tool lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Screen Snipping Tool are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Screen Snipping Tool aren't explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="device-manager-hardware-tree" aria-labelledby="device-manager-hardware-tree-h">
<h2 data-principle="pattern" id="device-manager-hardware-tree-h">Device Manager Hardware Tree</h2>
<p class="user-action" data-principle="user-action">User browses, updates, or troubleshoots device drivers in Device Manager.</p>
<section id="device-manager-hardware-tree-perceivable" aria-labelledby="device-manager-hardware-tree-perceivable-h">
<h3 id="device-manager-hardware-tree-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Warning icons on failing devices are small yellow triangles without text labels; users with low vision miss the alert.</li>
<li data-principle="perceivable">Tree-view expand/collapse arrows are tiny and lack visible focus rings; state changes aren't obvious.</li>
<li data-principle="perceivable">Driver update status appears as a brief toast that fades before users notice it.</li>
<li data-principle="perceivable">Error-state devices rely on a yellow-vs-green icon distinction alone; color-blind users can't differentiate.</li>
<li data-principle="perceivable">The properties dialog layers multiple tabs with dense text; critical information is buried visually.</li>
</ul>
</section>
<section id="device-manager-hardware-tree-operable" aria-labelledby="device-manager-hardware-tree-operable-h">
<h3 id="device-manager-hardware-tree-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Expanding nested device categories requires precise clicks on small arrow glyphs; mis-clicks collapse the wrong branch.</li>
<li data-principle="operable">"Update driver" and "Uninstall device" are adjacent with no confirmation spacing; accidental selection is easy.</li>
<li data-principle="operable">Right-click context menus dismiss if the pointer drifts slightly; users with tremor lose access.</li>
<li data-principle="operable">Scanning for hardware changes has no keyboard shortcut; users must navigate the Action menu each time.</li>
<li data-principle="operable">The properties dialog requires tabbing through many controls to reach driver details; keyboard navigation is lengthy.</li>
</ul>
</section>
<section id="device-manager-hardware-tree-understandable" aria-labelledby="device-manager-hardware-tree-understandable-h">
<h3 id="device-manager-hardware-tree-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Device names use hardware IDs ("PCI\VEN_8086&DEV_A370") instead of friendly names; users can't identify their hardware.</li>
<li data-principle="understandable">"Roll Back Driver" doesn't explain what version it will restore or what changes will revert.</li>
<li data-principle="understandable">Error codes (e.g., "Code 43") appear without plain-language descriptions or suggested next steps.</li>
<li data-principle="understandable">"Disable device" vs. "Uninstall device" consequences aren't distinguished; users risk removing drivers permanently.</li>
<li data-principle="understandable">The difference between "Update driver automatically" and "Browse my computer" isn't explained in context.</li>
</ul>
</section>
</article>
<article id="disk-management-console" aria-labelledby="disk-management-console-h">
<h2 data-principle="pattern" id="disk-management-console-h">Disk Management Console</h2>
<p class="user-action" data-principle="user-action">User creates, resizes, or formats drive partitions.</p>
<section id="disk-management-console-perceivable" aria-labelledby="disk-management-console-perceivable-h">
<h3 id="disk-management-console-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Partition color-coding (blue for primary, green for extended) carries no text legend on the volume bar itself.</li>
<li data-principle="perceivable">Unallocated space appears as a thin black sliver between partitions; users with magnification may not spot it.</li>
<li data-principle="perceivable">Volume health indicators rely on icon overlays that blend into the toolbar at standard DPI.</li>
<li data-principle="perceivable">The graphical disk map uses proportional sizing; very small partitions are nearly invisible.</li>
<li data-principle="perceivable">Status text ("Healthy", "At Risk") appears in a narrow column that truncates without tooltip on hover.</li>
</ul>
</section>
<section id="disk-management-console-operable" aria-labelledby="disk-management-console-operable-h">
<h3 id="disk-management-console-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Right-clicking a partition to extend or shrink requires targeting a narrow graphical bar; keyboard selection is indirect.</li>
<li data-principle="operable">"Delete Volume" is one click away from "Extend Volume" in the context menu with no undo or confirmation delay.</li>
<li data-principle="operable">Initializing a new disk requires choosing MBR vs. GPT in a modal with no back button; wrong choice requires reformatting.</li>
<li data-principle="operable">Resizing a volume uses a spinner control with no direct text entry; precise sizing is tedious with arrow keys.</li>
<li data-principle="operable">The console is an MMC snap-in; standard Windows keyboard shortcuts like Ctrl+Z don't apply.</li>
</ul>
</section>
<section id="disk-management-console-understandable" aria-labelledby="disk-management-console-understandable-h">
<h3 id="disk-management-console-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Simple", "Spanned", and "Striped" volume types are listed without explaining redundancy or data-loss risk.</li>
<li data-principle="understandable">"MBR" and "GPT" partition styles use acronyms without inline definitions; users can't make an informed choice.</li>
<li data-principle="understandable">"Shrink Volume" dialog shows "available shrink space" without explaining why it differs from free space.</li>
<li data-principle="understandable">Drive letter assignment doesn't warn that some apps hardcode paths and may break after a change.</li>
<li data-principle="understandable">"Active" partition marking has no explanation of what it controls or when it matters.</li>
</ul>
</section>
</article>
<article id="taskbar-calendar-and-clock-flyout" aria-labelledby="taskbar-calendar-and-clock-flyout-h">
<h2 data-principle="pattern" id="taskbar-calendar-and-clock-flyout-h">Taskbar Calendar and Clock Flyout</h2>
<p class="user-action" data-principle="user-action">User clicks the clock to view date, calendar, and upcoming events.</p>
<section id="taskbar-calendar-and-clock-flyout-perceivable" aria-labelledby="taskbar-calendar-and-clock-flyout-perceivable-h">
<h3 id="taskbar-calendar-and-clock-flyout-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Today's date highlight is a thin circle that blends into the grid; users with low vision miss which day is current.</li>
<li data-principle="perceivable">Event previews truncate after a few words with no tooltip; users can't read full event titles without clicking through.</li>
<li data-principle="perceivable">The month transition animation slides quickly; users relying on magnification lose their place in the calendar grid.</li>
<li data-principle="perceivable">Tiny left/right arrows for month navigation have no text labels; screen magnifier users may not find them.</li>
<li data-principle="perceivable">Secondary time zones display in a smaller font below the primary clock; the hierarchy isn't visually distinct.</li>
</ul>
</section>
<section id="taskbar-calendar-and-clock-flyout-operable" aria-labelledby="taskbar-calendar-and-clock-flyout-operable-h">
<h3 id="taskbar-calendar-and-clock-flyout-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Calendar grid cells aren't individually focusable with Tab; arrow-key navigation requires discovering the pattern.</li>
<li data-principle="operable">Clicking an event opens the Calendar app full-screen; there's no inline expansion to preview details without leaving the flyout.</li>
<li data-principle="operable">The flyout dismisses on any click outside it; users who accidentally tap the desktop must reopen and re-navigate.</li>
<li data-principle="operable">Adding a new event from the flyout requires a multi-step redirect to the Calendar app; there's no inline creation.</li>
<li data-principle="operable">Scrolling through months requires repeated arrow clicks; there's no jump-to-month or keyboard shortcut.</li>
</ul>
</section>
<section id="taskbar-calendar-and-clock-flyout-understandable" aria-labelledby="taskbar-calendar-and-clock-flyout-understandable-h">
<h3 id="taskbar-calendar-and-clock-flyout-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Events from multiple accounts are color-coded but the legend is only visible inside the full Calendar app, not the flyout.</li>
<li data-principle="understandable">"Focus time" blocks from Outlook appear without explaining how they interact with Windows Focus Assist.</li>
<li data-principle="understandable">All-day events and timed events are listed together with no visual grouping; the schedule structure is unclear.</li>
<li data-principle="understandable">The flyout shows a notification count badge but doesn't explain its relationship to Action Center alerts.</li>
<li data-principle="understandable">Time zone labels use abbreviations (PST, EST) without full names; users in non-US zones may not recognize them.</li>
</ul>
</section>
</article>
<article id="onedrive-sync-status-overlay" aria-labelledby="onedrive-sync-status-overlay-h">
<h2 data-principle="pattern" id="onedrive-sync-status-overlay-h">OneDrive Sync Status Overlay</h2>
<p class="user-action" data-principle="user-action">User monitors or troubleshoots file sync status from the system tray OneDrive icon.</p>
<section id="onedrive-sync-status-overlay-perceivable" aria-labelledby="onedrive-sync-status-overlay-perceivable-h">
<h3 id="onedrive-sync-status-overlay-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Sync progress uses a tiny circular spinner on the tray icon; users can't distinguish syncing from idle at a glance.</li>
<li data-principle="perceivable">File-level sync icons (green check, blue arrows, red X) are 12-pixel overlays on Explorer thumbnails; they're invisible at standard scaling.</li>
<li data-principle="perceivable">Conflict notifications appear as brief toasts that vanish before users notice a file version mismatch.</li>
<li data-principle="perceivable">The "paused" state looks nearly identical to "up to date" in the tray icon; only a subtle pause glyph differs.</li>
<li data-principle="perceivable">Bandwidth throttling status is shown only inside the settings panel; there's no tray-level indicator of reduced speed.</li>
</ul>
</section>
<section id="onedrive-sync-status-overlay-operable" aria-labelledby="onedrive-sync-status-overlay-operable-h">
<h3 id="onedrive-sync-status-overlay-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Clicking the tray icon opens a flyout, but navigating to sync errors requires scrolling a list with no filter or search.</li>
<li data-principle="operable">Pausing and resuming sync requires right-clicking the tray icon and finding the option in a nested menu.</li>
<li data-principle="operable">Resolving a file conflict opens a browser-based comparison with no way to resolve inline from the desktop.</li>
<li data-principle="operable">"Free up space" on individual files requires right-clicking each one; there's no batch selection in the flyout.</li>
<li data-principle="operable">The settings dialog is a separate window that doesn't persist position; users must reopen and relocate it each time.</li>
</ul>
</section>
<section id="onedrive-sync-status-overlay-understandable" aria-labelledby="onedrive-sync-status-overlay-understandable-h">
<h3 id="onedrive-sync-status-overlay-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Files On-Demand" status icons (cloud, solid green, green outline) aren't defined anywhere in the flyout or tooltip.</li>
<li data-principle="understandable">"Available when offline" vs. "Always keep on this device" aren't distinguished in plain terms; the difference is unclear.</li>
<li data-principle="understandable">Sync error messages reference SharePoint library permissions without explaining how to resolve them locally.</li>
<li data-principle="understandable">"Personal Vault" lock/unlock state isn't reflected in the tray flyout; users don't know if sensitive files are exposed.</li>
<li data-principle="understandable">Storage quota warnings use percentages without showing absolute values; users can't gauge how many files fit.</li>
</ul>
</section>
</article>
<article id="windows-terminal-profile-switcher" aria-labelledby="windows-terminal-profile-switcher-h">
<h2 data-principle="pattern" id="windows-terminal-profile-switcher-h">Windows Terminal Profile Switcher</h2>
<p class="user-action" data-principle="user-action">User selects, configures, or switches between shell profiles in Windows Terminal.</p>
<section id="windows-terminal-profile-switcher-perceivable" aria-labelledby="windows-terminal-profile-switcher-perceivable-h">
<h3 id="windows-terminal-profile-switcher-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Profile tabs use small colored underlines to indicate the active shell; the color distinction is subtle at default scaling.</li>
<li data-principle="perceivable">Command output scrolls rapidly with no visual pause indicator; users with low vision lose context in fast-moving text.</li>
<li data-principle="perceivable">The dropdown profile menu shows shell names but not icons at higher DPI; profiles look identical.</li>
<li data-principle="perceivable">Bell/alert events in terminal flash the tab title briefly; users not watching the tab bar miss the notification.</li>
<li data-principle="perceivable">Split-pane dividers are a 1-pixel line; users with magnification can't perceive the boundary between panes.</li>
</ul>
</section>
<section id="windows-terminal-profile-switcher-operable" aria-labelledby="windows-terminal-profile-switcher-operable-h">
<h3 id="windows-terminal-profile-switcher-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Opening a new tab in a specific profile requires a dropdown hover-then-click sequence; keyboard shortcuts vary by configuration.</li>
<li data-principle="operable">Resizing split panes requires dragging a nearly invisible divider; there's no keyboard-based resize command exposed in the UI.</li>
<li data-principle="operable">Copying text selection requires a right-click or Ctrl+C that can conflict with terminal SIGINT; users inadvertently kill processes.</li>
<li data-principle="operable">Profile settings are in a JSON file by default; GUI settings exist but don't cover all options, forcing manual editing.</li>
<li data-principle="operable">Switching between tabs has no visual animation or audio cue; users lose track of which profile is active.</li>
</ul>
</section>
<section id="windows-terminal-profile-switcher-understandable" aria-labelledby="windows-terminal-profile-switcher-understandable-h">
<h3 id="windows-terminal-profile-switcher-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Default profile" vs. "startup profile" isn't distinguished; users can't predict which shell launches on open.</li>
<li data-principle="understandable">Color scheme names ("One Half Dark", "Tango") don't describe contrast levels or suitability for low vision.</li>
<li data-principle="understandable">"Shell integration" and "experimental features" toggles lack inline descriptions of what they enable.</li>
<li data-principle="understandable">The relationship between Windows Terminal settings and individual shell configs (e.g., PowerShell profile.ps1) isn't explained.</li>
<li data-principle="understandable">"Quake mode" and "focus mode" are named without describing their visual behavior or how to exit them.</li>
</ul>
</section>
</article>
<article id="startup-apps-configuration" aria-labelledby="startup-apps-configuration-h">
<h2 data-principle="pattern" id="startup-apps-configuration-h">Startup Apps Configuration</h2>
<p class="user-action" data-principle="user-action">User enables, disables, or reviews apps that launch at sign-in.</p>
<section id="startup-apps-configuration-perceivable" aria-labelledby="startup-apps-configuration-perceivable-h">
<h3 id="startup-apps-configuration-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Impact ratings ("High", "Medium", "Low") in Task Manager use text only in a narrow column that truncates on smaller displays.</li>
<li data-principle="perceivable">The Settings startup list and Task Manager startup tab show different app sets with no visual indication of overlap.</li>
<li data-principle="perceivable">Disabled apps are greyed out but remain in the same list position; the visual difference from enabled is minimal.</li>
<li data-principle="perceivable">Publisher names are truncated without tooltips; users can't identify unfamiliar apps to decide whether to keep them.</li>
<li data-principle="perceivable">New apps added to startup don't trigger a notification; users don't perceive changes to their boot sequence.</li>
</ul>
</section>
<section id="startup-apps-configuration-operable" aria-labelledby="startup-apps-configuration-operable-h">
<h3 id="startup-apps-configuration-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Toggling an app requires finding it in an unsorted or alphabetical list with no search or filter option in Settings.</li>
<li data-principle="operable">Task Manager and Settings both control startup apps but neither links to the other; users must know both locations.</li>
<li data-principle="operable">There's no "disable all" or batch-select option; users must toggle each app individually across a long list.</li>
<li data-principle="operable">Removing a startup entry entirely (not just disabling) requires navigating to the app's own settings or the registry.</li>
<li data-principle="operable">Right-clicking for "Open file location" in Task Manager opens Explorer but doesn't highlight the target file consistently.</li>
</ul>
</section>
<section id="startup-apps-configuration-understandable" aria-labelledby="startup-apps-configuration-understandable-h">
<h3 id="startup-apps-configuration-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Startup impact" doesn't define what "High" means in seconds, CPU, or memory; users can't judge the real cost.</li>
<li data-principle="understandable">The difference between "Startup apps" in Settings and the "Startup" tab in Task Manager isn't explained anywhere.</li>
<li data-principle="understandable">Some entries show as "Not measured" for impact; users don't know if these are safe to leave enabled.</li>
<li data-principle="understandable">UWP apps and Win32 apps are mixed in the same list without indicating which type affects boot differently.</li>
<li data-principle="understandable">Disabling an app doesn't explain whether it can still run later or if background tasks are also stopped.</li>
</ul>
</section>
</article>
<article id="file-properties-and-security-permissions" aria-labelledby="file-properties-and-security-permissions-h">
<h2 data-principle="pattern" id="file-properties-and-security-permissions-h">File Properties and Security Permissions</h2>
<p class="user-action" data-principle="user-action">User views or modifies file attributes, sharing, and access permissions.</p>
<section id="file-properties-and-security-permissions-perceivable" aria-labelledby="file-properties-and-security-permissions-perceivable-h">
<h3 id="file-properties-and-security-permissions-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">The Security tab lists permission entries in a dense ACL grid; "Allow" and "Deny" checkboxes are closely packed and hard to scan.</li>
<li data-principle="perceivable">Inherited vs. explicit permissions use the same checkbox style; there's no visual cue that some entries can't be changed here.</li>
<li data-principle="perceivable">The "Advanced" security dialog opens a separate window with smaller text and more columns; information density increases sharply.</li>
<li data-principle="perceivable">File attribute checkboxes (Read-only, Hidden) at the bottom of the General tab are easy to overlook below the larger fields.</li>
<li data-principle="perceivable">Sharing status ("Not shared" vs. share path) is plain text with no icon; users scanning quickly miss the sharing state.</li>
</ul>
</section>
<section id="file-properties-and-security-permissions-operable" aria-labelledby="file-properties-and-security-permissions-operable-h">
<h3 id="file-properties-and-security-permissions-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Editing permissions requires clicking "Edit", then "Add", then typing exact user/group names; there's no browse-and-pick flow.</li>
<li data-principle="operable">"Take ownership" is buried three dialogs deep (Properties → Security → Advanced → Owner); the path is non-discoverable.</li>
<li data-principle="operable">Applying permissions recursively to subfolders requires a checkbox in the Advanced dialog that's easy to miss.</li>
<li data-principle="operable">Removing a user from the ACL requires selecting the row and clicking "Remove" with no undo; mistakes require re-adding manually.</li>
<li data-principle="operable">The "Share" tab and "Security" tab control overlapping access but are managed independently with no cross-reference.</li>
</ul>
</section>
<section id="file-properties-and-security-permissions-understandable" aria-labelledby="file-properties-and-security-permissions-understandable-h">
<h3 id="file-properties-and-security-permissions-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Full control", "Modify", and "Write" permissions overlap in scope; users can't tell which to grant for simple file editing.</li>
<li data-principle="understandable">"Special permissions" is listed as a category but clicking it opens an entirely new grid of granular options without explanation.</li>
<li data-principle="understandable">Inherited permissions are described as "inherited from parent object" without naming the parent or explaining how to override.</li>
<li data-principle="understandable">"Effective Access" tab requires selecting a user first but doesn't explain why results might differ from the visible checkboxes.</li>
<li data-principle="understandable">"Read & Execute" vs. "Read" vs. "List folder contents" distinctions aren't clarified; users over- or under-grant access.</li>
</ul>
</section>
</article>
<article id="recycle-bin-management" aria-labelledby="recycle-bin-management-h">
<h2 data-principle="pattern" id="recycle-bin-management-h">Recycle Bin Management</h2>
<p class="user-action" data-principle="user-action">User restores, permanently deletes, or configures Recycle Bin behavior.</p>
<section id="recycle-bin-management-perceivable" aria-labelledby="recycle-bin-management-perceivable-h">
<h3 id="recycle-bin-management-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Recycle Bin icon switches between empty and full states, but the two icons are similar at small taskbar sizes.</li>
<li data-principle="perceivable">Deleted file original-location paths are shown in a narrow column that truncates; users can't see where the file came from.</li>
<li data-principle="perceivable">"Date Deleted" and "Date Modified" columns look identical in formatting; users confuse when the file was changed vs. removed.</li>
<li data-principle="perceivable">File type icons in the Recycle Bin don't preview content; users can't visually confirm they're restoring the right version.</li>
<li data-principle="perceivable">The "Size" column for Recycle Bin items shows individual file sizes but not cumulative space used without scrolling to properties.</li>
</ul>
</section>
<section id="recycle-bin-management-operable" aria-labelledby="recycle-bin-management-operable-h">
<h3 id="recycle-bin-management-operable-h">Operable</h3>
<ul>
<li data-principle="operable">"Restore all items" is a single click with no confirmation; users accidentally restore hundreds of files to scattered locations.</li>
<li data-principle="operable">Selecting multiple non-adjacent files for restoration requires Ctrl+Click precision; there's no checkbox mode like modern Explorer.</li>
<li data-principle="operable">"Empty Recycle Bin" is destructive and immediate; there's no secondary confirmation differentiating it from restoring.</li>
<li data-principle="operable">Per-drive Recycle Bin size limits are configured in a properties dialog that's hard to discover from the desktop icon.</li>
<li data-principle="operable">There's no search or filter within the Recycle Bin; finding a specific deleted file requires manual scrolling.</li>
</ul>
</section>
<section id="recycle-bin-management-understandable" aria-labelledby="recycle-bin-management-understandable-h">
<h3 id="recycle-bin-management-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Restore" places files back to their original location, but if that folder was also deleted, the error message doesn't explain next steps.</li>
<li data-principle="understandable">The difference between "Delete" (send to Recycle Bin) and "Shift+Delete" (permanent) isn't surfaced in any UI tooltip.</li>
<li data-principle="understandable">Per-drive storage allocation for the Recycle Bin is shown in megabytes without context of total drive capacity.</li>
<li data-principle="understandable">"Don't move files to the Recycle Bin" setting doesn't warn that this makes all future deletes permanent immediately.</li>
<li data-principle="understandable">Items deleted from network drives or removable media bypass the Recycle Bin silently; users assume they can recover them.</li>
</ul>
</section>
</article>
<article id="windows-fonts-and-typography-settings" aria-labelledby="windows-fonts-and-typography-settings-h">
<h2 data-principle="pattern" id="windows-fonts-and-typography-settings-h">Windows Fonts and Typography Settings</h2>
<p class="user-action" data-principle="user-action">User installs, previews, or removes fonts from the system.</p>
<section id="windows-fonts-and-typography-settings-perceivable" aria-labelledby="windows-fonts-and-typography-settings-perceivable-h">
<h3 id="windows-fonts-and-typography-settings-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Font preview cards show a single sample sentence at one size; users can't gauge legibility at the sizes they actually use.</li>
<li data-principle="perceivable">Installed vs. available-to-download fonts are mixed in the same grid with only a small cloud icon differentiating them.</li>
<li data-principle="perceivable">Variable font weight ranges are represented by a slider with no numeric label; users can't perceive exact weight values.</li>
<li data-principle="perceivable">The font detail page shows character maps in a small grid; individual glyphs are hard to distinguish at default scaling.</li>
<li data-principle="perceivable">Font family groupings collapse variants (Bold, Italic, Light) under one card; users don't perceive how many styles are installed.</li>
</ul>
</section>
<section id="windows-fonts-and-typography-settings-operable" aria-labelledby="windows-fonts-and-typography-settings-operable-h">
<h3 id="windows-fonts-and-typography-settings-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Installing a font from a downloaded file requires right-click → "Install for all users"; drag-and-drop to the Settings font page sometimes fails silently.</li>
<li data-principle="operable">Uninstalling a font has no undo; users who remove a system font must re-download and reinstall it manually.</li>
<li data-principle="operable">Searching the font list filters in real time but clears when navigating away; users must retype after viewing a font's detail page.</li>
<li data-principle="operable">There's no way to preview a font against custom sample text directly from the grid; users must click into each font individually.</li>
<li data-principle="operable">Font settings in the modern Settings app and the legacy Fonts control panel coexist; changes in one aren't always reflected in the other.</li>
</ul>
</section>
<section id="windows-fonts-and-typography-settings-understandable" aria-labelledby="windows-fonts-and-typography-settings-understandable-h">
<h3 id="windows-fonts-and-typography-settings-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Font metadata labels like "OpenType Variable" and "TrueType" aren't explained; users can't determine compatibility with their apps.</li>
<li data-principle="understandable">"Install for all users" vs. default install scoping isn't clarified; users don't know if other accounts can see their fonts.</li>
<li data-principle="understandable">The relationship between per-user fonts and app-specific font caches isn't described; some apps don't show newly installed fonts.</li>
<li data-principle="understandable">"Font settings" includes a "Restore default font settings" button with no description of what it resets or which custom fonts it affects.</li>
<li data-principle="understandable">ClearType tuning is in a separate wizard with no link from the Fonts page; users don't know font rendering can be adjusted.</li>
</ul>
</section>
</article>
<article id="sound-output-device-switcher" aria-labelledby="sound-output-device-switcher-h">
<h2 data-principle="pattern" id="sound-output-device-switcher-h">Sound Output Device Switcher</h2>
<p class="user-action" data-principle="user-action">User selects or switches between audio output devices from the taskbar or Settings.</p>
<section id="sound-output-device-switcher-perceivable" aria-labelledby="sound-output-device-switcher-perceivable-h">
<h3 id="sound-output-device-switcher-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">The active output device is indicated by a small checkmark in the volume flyout; it's easy to miss among multiple devices.</li>
<li data-principle="perceivable">Device names are often generic ("Speakers", "Headphones") with no brand or port identifier; users can't tell which is which.</li>
<li data-principle="perceivable">When a Bluetooth device connects and auto-switches output, there's no persistent banner confirming the routing change.</li>
<li data-principle="perceivable">Volume level bars in the device list are thin and lack numeric readouts; users can't precisely perceive current levels.</li>
<li data-principle="perceivable">The flyout closes after selecting a device with no confirmation tone or visual flash; users aren't sure the switch took effect.</li>
</ul>
</section>
<section id="sound-output-device-switcher-operable" aria-labelledby="sound-output-device-switcher-operable-h">
<h3 id="sound-output-device-switcher-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Renaming an audio device requires navigating into Settings → Sound → Device properties; there's no rename option in the flyout.</li>
<li data-principle="operable">Setting a device as "Default" vs. "Default communication device" requires the legacy Sound control panel; the modern UI doesn't expose both roles.</li>
<li data-principle="operable">Disconnecting a Bluetooth audio device from the volume flyout isn't possible; users must go to Bluetooth settings separately.</li>
<li data-principle="operable">Per-app audio routing is buried in Settings → Sound → Volume mixer; there's no way to assign an app to a device from the taskbar.</li>
<li data-principle="operable">Testing a device plays a generic tone with no visual indicator of which speaker is active; users must listen to confirm.</li>
</ul>
</section>
<section id="sound-output-device-switcher-understandable" aria-labelledby="sound-output-device-switcher-understandable-h">
<h3 id="sound-output-device-switcher-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Default device" vs. "Default communication device" roles aren't explained; users don't know why Teams uses a different output than Spotify.</li>
<li data-principle="understandable">"Spatial sound" options appear per-device but don't describe the audible effect or which content benefits from it.</li>
<li data-principle="understandable">Devices listed as "Disconnected" remain in the list indefinitely; users don't know if they can be safely removed or will reconnect.</li>
<li data-principle="understandable">Sample rate and bit depth options ("16 bit, 48000 Hz") in device properties use technical terms without explaining quality tradeoffs.</li>
<li data-principle="understandable">"Exclusive mode" checkboxes don't explain that enabling them lets apps lock out other audio sources.</li>
</ul>
</section>
</article>
<article id="family-safety-and-child-account-controls" aria-labelledby="family-safety-and-child-account-controls-h">
<h2 data-principle="pattern" id="family-safety-and-child-account-controls-h">Family Safety and Child Account Controls</h2>
<p class="user-action" data-principle="user-action">User configures screen time limits, content filters, or activity reports for a child account.</p>
<section id="family-safety-and-child-account-controls-perceivable" aria-labelledby="family-safety-and-child-account-controls-perceivable-h">
<h3 id="family-safety-and-child-account-controls-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Activity report summaries use stacked bar charts with thin color segments; distinguishing app categories is difficult at a glance.</li>
<li data-principle="perceivable">Screen time remaining shows as a small countdown in the system tray; children and parents can't perceive it without hovering.</li>
<li data-principle="perceivable">Content-blocked notifications appear briefly and use generic wording; users can't tell which specific filter triggered the block.</li>
<li data-principle="perceivable">App usage percentages are displayed in a dense table without visual bars; comparing relative usage across apps is hard.</li>
<li data-principle="perceivable">Location sharing status is a toggle with no visible confirmation of the child's current position in the parent view.</li>
</ul>
</section>
<section id="family-safety-and-child-account-controls-operable" aria-labelledby="family-safety-and-child-account-controls-operable-h">
<h3 id="family-safety-and-child-account-controls-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Setting per-app time limits requires navigating into each app individually; there's no batch-select to apply the same limit to a group.</li>
<li data-principle="operable">Extending a child's screen time when they send a request requires the parent to open the Family Safety app or website; there's no inline approval from the notification.</li>
<li data-principle="operable">Age-rating content filters use different scales (ESRB, PEGI) but the selection interface doesn't explain which standard applies in which region.</li>
<li data-principle="operable">Removing a family member from the group requires signing into the Microsoft account website; it can't be done from Windows Settings.</li>
<li data-principle="operable">Overriding a blocked website requires typing the exact URL into an allow-list; there's no "allow this site" button from the block screen.</li>
</ul>
</section>
<section id="family-safety-and-child-account-controls-understandable" aria-labelledby="family-safety-and-child-account-controls-understandable-h">
<h3 id="family-safety-and-child-account-controls-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Web browsing" filters only apply to Edge; the scope limitation isn't stated clearly, leading parents to assume all browsers are filtered.</li>
<li data-principle="understandable">"Screen time" vs. "App and game limits" are separate controls with overlapping effect; parents can't predict which rule takes priority.</li>
<li data-principle="understandable">"Activity reporting" doesn't explain what data is collected or how long it's retained; privacy implications are unstated.</li>
<li data-principle="understandable">"Content restrictions" references age ranges but doesn't describe what content types each age threshold blocks.</li>
<li data-principle="understandable">The difference between "Family group" in Windows Settings and the Family Safety app on the web isn't clarified; settings appear in both with inconsistent detail.</li>
</ul>
</section>
</article>
<article id="registry-editor" aria-labelledby="registry-editor-h">
<h2 data-principle="pattern" id="registry-editor-h">Registry Editor (regedit)</h2>
<p class="user-action" data-principle="user-action">User navigates, creates, or modifies registry keys and values.</p>
<section id="registry-editor-perceivable" aria-labelledby="registry-editor-perceivable-h">
<h3 id="registry-editor-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">The tree hierarchy is deeply nested with identical folder icons at every level; users lose visual context of their depth.</li>
<li data-principle="perceivable">Value names and data are displayed in a list with no type-based highlighting; DWORD, String, and Binary entries look the same until clicked.</li>
<li data-principle="perceivable">The address bar shows the full registry path in small text that truncates; users can't see the complete key location.</li>
<li data-principle="perceivable">Modified values don't show a timestamp or "changed" indicator; users can't perceive which entries were recently edited.</li>
<li data-principle="perceivable">The Favorites menu stores bookmarked paths as plain text names; there's no visual preview or grouping of saved locations.</li>
</ul>
</section>
<section id="registry-editor-operable" aria-labelledby="registry-editor-operable-h">
<h3 id="registry-editor-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Navigating to a known path requires manually expanding each tree node; pasting a path into the address bar is the only shortcut but isn't discoverable.</li>
<li data-principle="operable">There's no undo after editing or deleting a value; mistakes require manually re-creating the key or restoring from a backup.</li>
<li data-principle="operable">Exporting a single key produces a .reg file, but importing it back doesn't warn about overwriting existing values.</li>
<li data-principle="operable">Find (Ctrl+F) searches linearly through the entire registry with no progress bar; long searches appear frozen.</li>
<li data-principle="operable">Creating a new key or value requires right-clicking in the correct pane; the context menu differs between the tree and list panels.</li>
</ul>
</section>
<section id="registry-editor-understandable" aria-labelledby="registry-editor-understandable-h">
<h3 id="registry-editor-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Data types (REG_DWORD, REG_SZ, REG_BINARY) use internal names without explaining what kind of data each stores.</li>
<li data-principle="understandable">HKEY root names (HKEY_LOCAL_MACHINE, HKEY_CURRENT_USER) don't explain their scope or when to use which hive.</li>
<li data-principle="understandable">Hexadecimal vs. decimal value entry is toggled by radio buttons in the edit dialog; users unfamiliar with hex enter wrong values.</li>
<li data-principle="understandable">"Default" values that appear in every key aren't explained; users don't know if editing them has system-wide consequences.</li>
<li data-principle="understandable">The relationship between Group Policy settings and their underlying registry keys isn't documented within the editor.</li>
</ul>
</section>
</article>
<article id="installed-apps-and-default-programs" aria-labelledby="installed-apps-and-default-programs-h">
<h2 data-principle="pattern" id="installed-apps-and-default-programs-h">Installed Apps and Default Programs</h2>
<p class="user-action" data-principle="user-action">User uninstalls apps, resets defaults, or manages optional features.</p>
<section id="installed-apps-and-default-programs-perceivable" aria-labelledby="installed-apps-and-default-programs-perceivable-h">
<h3 id="installed-apps-and-default-programs-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">App list entries show name and size but truncate publisher information; users can't identify unfamiliar apps at a glance.</li>
<li data-principle="perceivable">Storage size values use abbreviated units (MB, GB) in a narrow column; apps near size boundaries (999 MB vs. 1.0 GB) look disproportionate.</li>
<li data-principle="perceivable">"Modified" dates blend into the row without emphasis; users can't quickly spot recently changed or updated apps.</li>
<li data-principle="perceivable">The "Sort by" and "Filter by" dropdowns are small icon-only buttons above the list; their function isn't apparent without hovering.</li>
<li data-principle="perceivable">Optional Features installation progress shows no per-feature status; users waiting for multiple features see one generic bar.</li>
</ul>
</section>
<section id="installed-apps-and-default-programs-operable" aria-labelledby="installed-apps-and-default-programs-operable-h">
<h3 id="installed-apps-and-default-programs-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Uninstalling an app sometimes opens the app's own uninstaller with a different UI; the experience is inconsistent and occasionally modal.</li>
<li data-principle="operable">Resetting default apps requires selecting each file type or protocol individually; there's no "reset all to Windows defaults" single action.</li>
<li data-principle="operable">"Advanced options" for each app opens a separate page with no back shortcut; users must use the browser-style back arrow.</li>
<li data-principle="operable">Searching the app list clears when users click into an app and return; the filter must be retyped.</li>
<li data-principle="operable">Optional Features install with no cancel button once started; users must wait for completion even if the wrong feature was selected.</li>
</ul>
</section>
<section id="installed-apps-and-default-programs-understandable" aria-labelledby="installed-apps-and-default-programs-understandable-h">
<h3 id="installed-apps-and-default-programs-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Default apps" shows apps by category (email, browser, maps) but doesn't explain what file types or links each category covers.</li>
<li data-principle="understandable">"Repair" vs. "Reset" options for Store apps aren't distinguished; users don't know that Reset deletes app data while Repair doesn't.</li>
<li data-principle="understandable">"Optional features" mixes system components (OpenSSH, Notepad) with language packs without explaining their purpose or dependencies.</li>
<li data-principle="understandable">"App execution aliases" are listed by command name without explaining that they control which app launches when typing a name in Terminal.</li>
<li data-principle="understandable">"Offline maps" storage location can be changed, but the setting doesn't explain whether downloaded maps transfer or re-download.</li>
</ul>
</section>
</article>
<article id="file-explorer-details-pane-and-preview-pane" aria-labelledby="file-explorer-details-pane-and-preview-pane-h">
<h2 data-principle="pattern" id="file-explorer-details-pane-and-preview-pane-h">File Explorer Details Pane and Preview Pane</h2>
<p class="user-action" data-principle="user-action">User enables the preview or details pane to inspect file content and metadata without opening.</p>
<section id="file-explorer-details-pane-and-preview-pane-perceivable" aria-labelledby="file-explorer-details-pane-and-preview-pane-perceivable-h">
<h3 id="file-explorer-details-pane-and-preview-pane-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">The preview pane renders documents at a fixed small size; users with low vision can't zoom the preview independently of the main view.</li>
<li data-principle="perceivable">Details pane metadata (dimensions, date taken, authors) uses small grey text that's hard to read against the panel background.</li>
<li data-principle="perceivable">The pane toggle buttons in the toolbar are unlabeled icons; users can't tell which activates Preview vs. Details without trial.</li>
<li data-principle="perceivable">Image previews don't adapt to high-contrast mode; photos with dark backgrounds become indistinguishable from the pane itself.</li>
<li data-principle="perceivable">Video previews auto-play silently with no playback indicator; users don't perceive that motion is happening in the pane.</li>
</ul>
</section>
<section id="file-explorer-details-pane-and-preview-pane-operable" aria-labelledby="file-explorer-details-pane-and-preview-pane-operable-h">
<h3 id="file-explorer-details-pane-and-preview-pane-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Resizing the preview pane requires dragging a thin splitter bar; there's no keyboard command to set pane width.</li>
<li data-principle="operable">The preview pane doesn't support keyboard scrolling for multi-page documents; users must click inside the pane first to gain focus.</li>
<li data-principle="operable">Editing metadata in the details pane (tags, comments) requires clicking into tiny inline text fields; Tab order between fields is inconsistent.</li>
<li data-principle="operable">Toggling the pane off and on resets its width to the default; users must re-drag to their preferred size each time.</li>
<li data-principle="operable">File types without a registered previewer show a blank pane with no message; users don't know if the file is empty or unsupported.</li>
</ul>
</section>
<section id="file-explorer-details-pane-and-preview-pane-understandable" aria-labelledby="file-explorer-details-pane-and-preview-pane-understandable-h">
<h3 id="file-explorer-details-pane-and-preview-pane-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">"Preview pane" and "Details pane" are mutually exclusive but the UI doesn't explain this; users try to enable both and one silently deactivates.</li>
<li data-principle="understandable">Metadata fields in the details pane differ by file type with no explanation; users expect the same fields across all files.</li>
<li data-principle="understandable">"Remove Properties and Personal Information" link doesn't clarify which metadata is considered personal or what removing it affects.</li>
<li data-principle="understandable">Preview rendering depends on installed codecs and apps, but failures show no guidance on what to install.</li>
<li data-principle="understandable">"Rating" stars in the details pane apply to the file's metadata, but it's unclear whether this syncs across devices or apps.</li>
</ul>
</section>
</article>
<article id="taskbar-overflow-menu" aria-labelledby="taskbar-overflow-menu-h">
<h2 data-principle="pattern" id="taskbar-overflow-menu-h">Taskbar Overflow Menu</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures taskbar overflow menu.</p>
<section id="taskbar-overflow-menu-perceivable" aria-labelledby="taskbar-overflow-menu-perceivable-h">
<h3 id="taskbar-overflow-menu-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Taskbar Overflow Menu is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Taskbar Overflow Menu reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Taskbar Overflow Menu dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Taskbar Overflow Menu lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Taskbar Overflow Menu can obscure information during interaction.</li>
</ul>
</section>
<section id="taskbar-overflow-menu-operable" aria-labelledby="taskbar-overflow-menu-operable-h">
<h3 id="taskbar-overflow-menu-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Taskbar Overflow Menu are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Taskbar Overflow Menu are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Taskbar Overflow Menu reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Taskbar Overflow Menu are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Taskbar Overflow Menu changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="taskbar-overflow-menu-understandable" aria-labelledby="taskbar-overflow-menu-understandable-h">
<h3 id="taskbar-overflow-menu-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Taskbar Overflow Menu use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Taskbar Overflow Menu are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Taskbar Overflow Menu lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Taskbar Overflow Menu are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Taskbar Overflow Menu aren’t explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="notification-toasts" aria-labelledby="notification-toasts-h">
<h2 data-principle="pattern" id="notification-toasts-h">Notification Toasts</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures notification toasts.</p>
<section id="notification-toasts-perceivable" aria-labelledby="notification-toasts-perceivable-h">
<h3 id="notification-toasts-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Notification Toasts is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Notification Toasts reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Notification Toasts dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Notification Toasts lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Notification Toasts can obscure information during interaction.</li>
</ul>
</section>
<section id="notification-toasts-operable" aria-labelledby="notification-toasts-operable-h">
<h3 id="notification-toasts-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Notification Toasts are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Notification Toasts are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Notification Toasts reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Notification Toasts are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Notification Toasts changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="notification-toasts-understandable" aria-labelledby="notification-toasts-understandable-h">
<h3 id="notification-toasts-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Notification Toasts use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Notification Toasts are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Notification Toasts lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Notification Toasts are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Notification Toasts aren’t explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="quick-settings-panel" aria-labelledby="quick-settings-panel-h">
<h2 data-principle="pattern" id="quick-settings-panel-h">Quick Settings Panel</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures quick settings panel.</p>
<section id="quick-settings-panel-perceivable" aria-labelledby="quick-settings-panel-perceivable-h">
<h3 id="quick-settings-panel-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Quick Settings Panel is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Quick Settings Panel reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Quick Settings Panel dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Quick Settings Panel lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Quick Settings Panel can obscure information during interaction.</li>
</ul>
</section>
<section id="quick-settings-panel-operable" aria-labelledby="quick-settings-panel-operable-h">
<h3 id="quick-settings-panel-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Quick Settings Panel are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Quick Settings Panel are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Quick Settings Panel reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Quick Settings Panel are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Quick Settings Panel changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="quick-settings-panel-understandable" aria-labelledby="quick-settings-panel-understandable-h">
<h3 id="quick-settings-panel-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Quick Settings Panel use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Quick Settings Panel are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Quick Settings Panel lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Quick Settings Panel are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Quick Settings Panel aren’t explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="start-menu-search-results" aria-labelledby="start-menu-search-results-h">
<h2 data-principle="pattern" id="start-menu-search-results-h">Start Menu Search Results</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures start menu search results.</p>
<section id="start-menu-search-results-perceivable" aria-labelledby="start-menu-search-results-perceivable-h">
<h3 id="start-menu-search-results-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Start Menu Search Results is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Start Menu Search Results reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Start Menu Search Results dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Start Menu Search Results lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Start Menu Search Results can obscure information during interaction.</li>
</ul>
</section>
<section id="start-menu-search-results-operable" aria-labelledby="start-menu-search-results-operable-h">
<h3 id="start-menu-search-results-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Start Menu Search Results are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Start Menu Search Results are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Start Menu Search Results reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Start Menu Search Results are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Start Menu Search Results changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="start-menu-search-results-understandable" aria-labelledby="start-menu-search-results-understandable-h">
<h3 id="start-menu-search-results-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Start Menu Search Results use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Start Menu Search Results are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Start Menu Search Results lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Start Menu Search Results are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Start Menu Search Results aren’t explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="file-explorer-navigation-pane" aria-labelledby="file-explorer-navigation-pane-h">
<h2 data-principle="pattern" id="file-explorer-navigation-pane-h">File Explorer Navigation Pane</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures file explorer navigation pane.</p>
<section id="file-explorer-navigation-pane-perceivable" aria-labelledby="file-explorer-navigation-pane-perceivable-h">
<h3 id="file-explorer-navigation-pane-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in File Explorer Navigation Pane is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in File Explorer Navigation Pane reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in File Explorer Navigation Pane dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in File Explorer Navigation Pane lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in File Explorer Navigation Pane can obscure information during interaction.</li>
</ul>
</section>
<section id="file-explorer-navigation-pane-operable" aria-labelledby="file-explorer-navigation-pane-operable-h">
<h3 id="file-explorer-navigation-pane-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in File Explorer Navigation Pane are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in File Explorer Navigation Pane are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in File Explorer Navigation Pane reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in File Explorer Navigation Pane are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in File Explorer Navigation Pane changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="file-explorer-navigation-pane-understandable" aria-labelledby="file-explorer-navigation-pane-understandable-h">
<h3 id="file-explorer-navigation-pane-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in File Explorer Navigation Pane use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to File Explorer Navigation Pane are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in File Explorer Navigation Pane lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in File Explorer Navigation Pane are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in File Explorer Navigation Pane aren’t explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>
<article id="system-dialog-prompts-uac" aria-labelledby="system-dialog-prompts-uac-h">
<h2 data-principle="pattern" id="system-dialog-prompts-uac-h">System Dialog Prompts (UAC)</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures system dialog prompts (uac).</p>
<section id="system-dialog-prompts-uac-perceivable" aria-labelledby="system-dialog-prompts-uac-perceivable-h">
<h3 id="system-dialog-prompts-uac-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Secure desktop dimming reduces contrast for dialog text and buttons.</li>
<li data-principle="perceivable">Badge icons for app publisher trust are small and ambiguous.</li>
<li data-principle="perceivable">No visual indicator shows microphone or camera access during prompts.</li>
<li data-principle="perceivable">Color states of “Yes/No” appear similar under certain color filters.</li>
<li data-principle="perceivable">Long file paths wrap poorly, hiding critical verification info.</li>
</ul>
</section>
<section id="system-dialog-prompts-uac-operable" aria-labelledby="system-dialog-prompts-uac-operable-h">
<h3 id="system-dialog-prompts-uac-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Keyboard focus can trap on background elements after prompt dismissal.</li>
<li data-principle="operable">Tab order skips the certificate details link for quick verification.</li>
<li data-principle="operable">Touch target for expanding “Show more details” is too narrow.</li>
<li data-principle="operable">External keyboard shortcuts are disabled on secure desktop unexpectedly.</li>
<li data-principle="operable">Switch access users lack a simple path to copy the file hash.</li>
</ul>
</section>
<section id="system-dialog-prompts-uac-understandable" aria-labelledby="system-dialog-prompts-uac-understandable-h">
<h3 id="system-dialog-prompts-uac-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Terms like “verified publisher” lack inline explanation or examples.</li>
<li data-principle="understandable">Risk level isn’t graded; all prompts appear equally severe.</li>
<li data-principle="understandable">Error states reference certificates without guidance to resolve.</li>
<li data-principle="understandable">Button labels don’t describe the consequences of each action.</li>
<li data-principle="understandable">No summary clarifies why the prompt appeared or how to prevent it.</li>
</ul>
</section>
</article>
<article id="lock-screen-and-sign-in-flow" aria-labelledby="lock-screen-and-sign-in-flow-h">
<h2 data-principle="pattern" id="lock-screen-and-sign-in-flow-h">Lock Screen and Sign-in Flow</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures lock screen and sign-in flow.</p>
<section id="lock-screen-and-sign-in-flow-perceivable" aria-labelledby="lock-screen-and-sign-in-flow-perceivable-h">
<h3 id="lock-screen-and-sign-in-flow-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Background imagery reduces contrast of the date/time and notifications.</li>
<li data-principle="perceivable">Caps Lock and keyboard layout indicators are subtle and easy to miss.</li>
<li data-principle="perceivable">Credential errors appear briefly and fade before they are read.</li>
<li data-principle="perceivable">PIN and password fields lack clear visible focus for low-vision users.</li>
<li data-principle="perceivable">Biometric prompts have minimal on-screen feedback when unavailable.</li>
</ul>
</section>
<section id="lock-screen-and-sign-in-flow-operable" aria-labelledby="lock-screen-and-sign-in-flow-operable-h">
<h3 id="lock-screen-and-sign-in-flow-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Swipe-to-dismiss lock screen conflicts with screen reader gestures.</li>
<li data-principle="operable">Keyboard focus can land behind the password field after layout switches.</li>
<li data-principle="operable">External keyboards don’t always wake the display before input is lost.</li>
<li data-principle="operable">Switch control users struggle to select alternate sign-in methods.</li>
<li data-principle="operable">Timeouts occur while locating security keys or phone sign-in confirmations.</li>
</ul>
</section>
<section id="lock-screen-and-sign-in-flow-understandable" aria-labelledby="lock-screen-and-sign-in-flow-understandable-h">
<h3 id="lock-screen-and-sign-in-flow-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Error copy like “Something went wrong” lacks recovery steps.</li>
<li data-principle="understandable">Biometric fallback order is unclear; users don’t know the next option.</li>
<li data-principle="understandable">Language and keyboard layout switching lacks contextual help.</li>
<li data-principle="understandable">No guidance for offline sign-in when network methods fail.</li>
<li data-principle="understandable">Account selection cards don’t explain differences (local vs. work).</li>
</ul>
</section>
</article>
<article id="settings-breadcrumb-navigation" aria-labelledby="settings-breadcrumb-navigation-h">
<h2 data-principle="pattern" id="settings-breadcrumb-navigation-h">Settings Breadcrumb Navigation</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures settings breadcrumb navigation.</p>
<section id="settings-breadcrumb-navigation-perceivable" aria-labelledby="settings-breadcrumb-navigation-perceivable-h">
<h3 id="settings-breadcrumb-navigation-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Breadcrumb separators are faint and hard to perceive in high DPI.</li>
<li data-principle="perceivable">Ellipsized labels hide critical category names on smaller screens.</li>
<li data-principle="perceivable">Hover affordances don’t render reliably with magnifier docked.</li>
<li data-principle="perceivable">Page headings and trails don’t align, reducing orientation clarity.</li>
<li data-principle="perceivable">Keyboard focus ring is low contrast against breadcrumb background.</li>
</ul>
</section>
<section id="settings-breadcrumb-navigation-operable" aria-labelledby="settings-breadcrumb-navigation-operable-h">
<h3 id="settings-breadcrumb-navigation-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Breadcrumbs are not scrollable via keyboard when overflowed.</li>
<li data-principle="operable">Back/forward shortcuts skip intermediate breadcrumb levels.</li>
<li data-principle="operable">Hit area for tiny breadcrumb nodes is too small for touch.</li>
<li data-principle="operable">Assistive tech announces breadcrumbs inconsistently as links vs. text.</li>
<li data-principle="operable">Deep-linking resets the trail, breaking return navigation paths.</li>
</ul>
</section>
<section id="settings-breadcrumb-navigation-understandable" aria-labelledby="settings-breadcrumb-navigation-understandable-h">
<h3 id="settings-breadcrumb-navigation-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Category names vary between lists and page headers.</li>
<li data-principle="understandable">No explanation of how breadcrumbs map to the Settings hierarchy.</li>
<li data-principle="understandable">Users can’t preview what will be lost when moving up a level.</li>
<li data-principle="understandable">Ambiguous “More” truncation hides sibling categories without hint.</li>
<li data-principle="understandable">No quick path to recent pages or history from the trail.</li>
</ul>
</section>
</article>
<article id="volume-and-media-overlay" aria-labelledby="volume-and-media-overlay-h">
<h2 data-principle="pattern" id="volume-and-media-overlay-h">Volume and Media Overlay</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures volume and media overlay.</p>
<section id="volume-and-media-overlay-perceivable" aria-labelledby="volume-and-media-overlay-perceivable-h">
<h3 id="volume-and-media-overlay-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Overlay covers captions or critical UI in full-screen apps.</li>
<li data-principle="perceivable">Device names truncate, hiding which output is active.</li>
<li data-principle="perceivable">Low-contrast progress bars are hard to read against bright video.</li>
<li data-principle="perceivable">Album art dominates space, reducing legibility of controls.</li>
<li data-principle="perceivable">No visual feedback for hardware mute state in some contexts.</li>
</ul>
</section>
<section id="volume-and-media-overlay-operable" aria-labelledby="volume-and-media-overlay-operable-h">
<h3 id="volume-and-media-overlay-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Keyboard focus doesn’t move to the overlay when it appears.</li>
<li data-principle="operable">Small scrubber handle makes precise adjustments difficult.</li>
<li data-principle="operable">Game controllers inadvertently dismiss the overlay while navigating.</li>
<li data-principle="operable">Voice commands conflict with app-level media shortcuts.</li>
<li data-principle="operable">Switch input cannot reliably select output devices in the menu.</li>