web/ITL_AI-Inclusive-Design-Sprints_Windows_exclusions.html at master · InclusiveTechLab/web · GitHub

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-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>
</ul>
</section>
<section id="volume-and-media-overlay-understandable" aria-labelledby="volume-and-media-overlay-understandable-h">
<h3 id="volume-and-media-overlay-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Terminology like “spatial” or “exclusive mode” isn’t explained.</li>
<li data-principle="understandable">No guidance when app volume is limited by system communications mode.</li>
<li data-principle="understandable">Output vs. input device controls appear together without distinction.</li>
<li data-principle="understandable">Lack of confirmation when switching outputs mid-call.</li>
<li data-principle="understandable">Errors like “device not available” don’t suggest alternatives.</li>
</ul>
</section>
</article>

<article id="clipboard-history-win-v" aria-labelledby="clipboard-history-win-v-h">
<h2 data-principle="pattern" id="clipboard-history-win-v-h">Clipboard History (Win + V)</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures clipboard history (win + v).</p>
<section id="clipboard-history-win-v-perceivable" aria-labelledby="clipboard-history-win-v-perceivable-h">
<h3 id="clipboard-history-win-v-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Small thumbnails for images and emoji are hard to distinguish.</li>
<li data-principle="perceivable">Item borders are faint, blending adjacent entries.</li>
<li data-principle="perceivable">Synced items lack a clear visual badge to show their source.</li>
<li data-principle="perceivable">Animated GIF previews cause distraction and motion sensitivity.</li>
<li data-principle="perceivable">Low-contrast “Clear all” link is easily overlooked.</li>
</ul>
</section>
<section id="clipboard-history-win-v-operable" aria-labelledby="clipboard-history-win-v-operable-h">
<h3 id="clipboard-history-win-v-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Keyboard navigation doesn’t preserve position after paste.</li>
<li data-principle="operable">Pin/unpin icons have small hit areas for touch users.</li>
<li data-principle="operable">Search within clipboard items isn’t available via keyboard-only.</li>
<li data-principle="operable">Voice users can’t easily reference item numbers for selection.</li>
<li data-principle="operable">Focus jumps when cloud-sync repopulates the list mid-selection.</li>
</ul>
</section>
<section id="clipboard-history-win-v-understandable" aria-labelledby="clipboard-history-win-v-understandable-h">
<h3 id="clipboard-history-win-v-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Sync privacy details aren’t explained where the feature is used.</li>
<li data-principle="understandable">No preview hints for large text entries or code blocks.</li>
<li data-principle="understandable">Pasting rich content vs. plain text isn’t clearly indicated.</li>
<li data-principle="understandable">Error states for unavailable items provide no retry path.</li>
<li data-principle="understandable">Users aren’t informed when pinned items persist across reboots.</li>
</ul>
</section>
</article>

<article id="system-tray-icons" aria-labelledby="system-tray-icons-h">
<h2 data-principle="pattern" id="system-tray-icons-h">System Tray Icons</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures system tray icons.</p>
<section id="system-tray-icons-perceivable" aria-labelledby="system-tray-icons-perceivable-h">
<h3 id="system-tray-icons-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Status badges are small and unreadable at common scaling.</li>
<li data-principle="perceivable">Hidden overflow chevron lacks clear label when read by screen readers.</li>
<li data-principle="perceivable">Tooltips disappear behind other overlays or at screen edges.</li>
<li data-principle="perceivable">Animated syncing icons cause distraction and visual fatigue.</li>
<li data-principle="perceivable">Low-contrast icons in custom themes reduce recognizability.</li>
</ul>
</section>
<section id="system-tray-icons-operable" aria-labelledby="system-tray-icons-operable-h">
<h3 id="system-tray-icons-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Right-click menus open off-screen in multi-monitor setups.</li>
<li data-principle="operable">Keyboard navigation into the overflow tray is inconsistent.</li>
<li data-principle="operable">Drag-to-reorder is difficult with small hit targets.</li>
<li data-principle="operable">Hover-dependent states don’t translate to touch input.</li>
<li data-principle="operable">Switch control users can’t access nested context submenus easily.</li>
</ul>
</section>
<section id="system-tray-icons-understandable" aria-labelledby="system-tray-icons-understandable-h">
<h3 id="system-tray-icons-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Icons lack consistent naming between tooltip and app settings.</li>
<li data-principle="understandable">Users aren’t told which icons reflect system vs. third-party status.</li>
<li data-principle="understandable">No explanation of how “Show hidden icons” persistence works.</li>
<li data-principle="understandable">Similar cloud sync providers use indistinguishable glyphs.</li>
<li data-principle="understandable">Notification badges don’t link to relevant settings or history.</li>
</ul>
</section>
</article>

<article id="focus-sessions-in-clock" aria-labelledby="focus-sessions-in-clock-h">
<h2 data-principle="pattern" id="focus-sessions-in-clock-h">Focus Sessions in Clock</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures focus sessions in clock.</p>
<section id="focus-sessions-in-clock-perceivable" aria-labelledby="focus-sessions-in-clock-perceivable-h">
<h3 id="focus-sessions-in-clock-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Timer progress color isn’t distinguishable from the background theme.</li>
<li data-principle="perceivable">Break notifications are quiet and lack a strong visual cue.</li>
<li data-principle="perceivable">Goal streak indicators rely on color-only differentiation.</li>
<li data-principle="perceivable">Embedded task list text truncates without accessible expansion.</li>
<li data-principle="perceivable">Music integration overlays obscure timer details on small screens.</li>
</ul>
</section>
<section id="focus-sessions-in-clock-operable" aria-labelledby="focus-sessions-in-clock-operable-h">
<h3 id="focus-sessions-in-clock-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Start/pause controls are small and near non-interactive text.</li>
<li data-principle="operable">Keyboard users can’t adjust session length while the timer runs.</li>
<li data-principle="operable">Switch input cannot quickly skip a break or add 5 minutes.</li>
<li data-principle="operable">Notifications steal focus from other full-screen activities.</li>
<li data-principle="operable">Integration sign-ins time out before assistive flows complete.</li>
</ul>
</section>
<section id="focus-sessions-in-clock-understandable" aria-labelledby="focus-sessions-in-clock-understandable-h">
<h3 id="focus-sessions-in-clock-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Terminology like “streaks” and “daily goal” lacks onboarding.</li>
<li data-principle="understandable">No summary shows how focus filters interact with notifications.</li>
<li data-principle="understandable">End-of-session dialogs don’t explain what was silenced.</li>
<li data-principle="understandable">Analytics cards omit units and time zones for session totals.</li>
<li data-principle="understandable">Break customization options are buried and labeled inconsistently.</li>
</ul>
</section>
</article>

<article id="virtual-desktops-and-task-view" aria-labelledby="virtual-desktops-and-task-view-h">
<h2 data-principle="pattern" id="virtual-desktops-and-task-view-h">Virtual Desktops & Task View</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures virtual desktops & task view.</p>
<section id="virtual-desktops-and-task-view-perceivable" aria-labelledby="virtual-desktops-and-task-view-perceivable-h">
<h3 id="virtual-desktops-and-task-view-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Window thumbnails are small; titles truncate and look identical.</li>
<li data-principle="perceivable">Wallpaper tint effects reduce contrast of desktop labels.</li>
<li data-principle="perceivable">Motion-heavy transitions cause discomfort for some users.</li>
<li data-principle="perceivable">App badges don’t clearly indicate which desktop holds the focus.</li>
<li data-principle="perceivable">High-contrast themes apply inconsistently to Task View controls.</li>
</ul>
</section>
<section id="virtual-desktops-and-task-view-operable" aria-labelledby="virtual-desktops-and-task-view-operable-h">
<h3 id="virtual-desktops-and-task-view-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Drag-to-move windows between desktops is difficult with magnification.</li>
<li data-principle="operable">Keyboard shortcuts differ between pinned and unpinned taskbars.</li>
<li data-principle="operable">Switch access users can’t quickly reorder desktops.</li>
<li data-principle="operable">Focus jumps when apps spawn new windows across desktops.</li>
<li data-principle="operable">Touch gestures to create desktops conflict with trackpad gestures.</li>
</ul>
</section>
<section id="virtual-desktops-and-task-view-understandable" aria-labelledby="virtual-desktops-and-task-view-understandable-h">
<h3 id="virtual-desktops-and-task-view-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">No clear explanation of which items persist across desktops.</li>
<li data-principle="understandable">Naming desktops isn’t discoverable; labels look non-editable.</li>
<li data-principle="understandable">Unclear mapping between Task View thumbnails and live windows.</li>
<li data-principle="understandable">No onboarding for “show windows from all desktops” behavior.</li>
<li data-principle="understandable">Closing a desktop doesn’t preview where its windows will go.</li>
</ul>
</section>
</article>


<article id="snap-layout-flyout" aria-labelledby="snap-layout-flyout-h">
<h2 data-principle="pattern" id="snap-layout-flyout-h">Snap Layout Flyout</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures snap layout flyout.</p>
<section id="snap-layout-flyout-perceivable" aria-labelledby="snap-layout-flyout-perceivable-h">
<h3 id="snap-layout-flyout-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Key status or feedback in Snap Layout Flyout is visually subtle; users may miss state changes.</li>
<li data-principle="perceivable">Small text or icons in Snap Layout Flyout reduce readability at common scaling levels.</li>
<li data-principle="perceivable">Transient visuals in Snap Layout Flyout dismiss quickly, limiting time to notice content.</li>
<li data-principle="perceivable">Color-only cues in Snap Layout Flyout lower distinguishability for color-vision differences.</li>
<li data-principle="perceivable">Motion, blur, or translucency in Snap Layout Flyout can obscure information during interaction.</li>
</ul>
</section>
<section id="snap-layout-flyout-operable" aria-labelledby="snap-layout-flyout-operable-h">
<h3 id="snap-layout-flyout-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Activation targets in Snap Layout Flyout are compact, requiring fine pointer control.</li>
<li data-principle="operable">Keyboard routes for key actions in Snap Layout Flyout are non-obvious or inconsistent.</li>
<li data-principle="operable">Gesture or hover dependency in Snap Layout Flyout reduces operability for alternate inputs.</li>
<li data-principle="operable">Sequential steps in Snap Layout Flyout are time-sensitive, causing failures at slower input speeds.</li>
<li data-principle="operable">Focus or caret movement in Snap Layout Flyout changes unexpectedly, interrupting workflows.</li>
</ul>
</section>
<section id="snap-layout-flyout-understandable" aria-labelledby="snap-layout-flyout-understandable-h">
<h3 id="snap-layout-flyout-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels and copy in Snap Layout Flyout use vague terminology that obscures outcomes.</li>
<li data-principle="understandable">Settings related to Snap Layout Flyout are split across surfaces; the mental model is unclear.</li>
<li data-principle="understandable">System messages in Snap Layout Flyout lack effort/time estimates, making planning difficult.</li>
<li data-principle="understandable">Icons and metaphors in Snap Layout Flyout are not self-evident without examples or hints.</li>
<li data-principle="understandable">State transitions in Snap Layout Flyout aren’t explained, reducing user confidence and trust.</li>
</ul>
</section>
</article>

<article id="touch-keyboard-invocation" aria-labelledby="touch-keyboard-invocation-h">
<h2 data-principle="pattern" id="touch-keyboard-invocation-h">Touch Keyboard Invocation</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures touch keyboard invocation.</p>
<section id="touch-keyboard-invocation-perceivable" aria-labelledby="touch-keyboard-invocation-perceivable-h">
<h3 id="touch-keyboard-invocation-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Dock/undock state icon is subtle; users can’t tell if the keyboard will cover input fields.</li>
<li data-principle="perceivable">Key legends shrink on small screens, reducing legibility for low-vision users.</li>
<li data-principle="perceivable">Haptic and click sounds lack visual equivalents when device is muted.</li>
<li data-principle="perceivable">Suggestion strip truncates alternatives with ellipses without accessible names.</li>
<li data-principle="perceivable">Launch animation obscures the target input momentarily, hiding caret placement.</li>
</ul>
</section>
<section id="touch-keyboard-invocation-operable" aria-labelledby="touch-keyboard-invocation-operable-h">
<h3 id="touch-keyboard-invocation-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Swipe-to-dismiss conflicts with app-level gestures near screen edges.</li>
<li data-principle="operable">Small invocation button on taskbar is hard to target with assistive pointers.</li>
<li data-principle="operable">External keyboard presence disables touch keyboard without an override control.</li>
<li data-principle="operable">Voice typing toggle requires long-press; no simple keyboard shortcut alternative.</li>
<li data-principle="operable">Floating keyboard drags require precise grip; it snaps unpredictably on rotation.</li>
</ul>
</section>
<section id="touch-keyboard-invocation-understandable" aria-labelledby="touch-keyboard-invocation-understandable-h">
<h3 id="touch-keyboard-invocation-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Settings don’t clarify when the keyboard auto-opens vs. requires manual launch.</li>
<li data-principle="understandable">Predictive text and autocorrect differences aren’t explained with examples.</li>
<li data-principle="understandable">Privacy notice for voice typing permissions is buried and jargon-heavy.</li>
<li data-principle="understandable">Layout choices (split, one-handed) lack previews before applying.</li>
<li data-principle="understandable">Users aren’t warned that clipboard history can surface in suggestion bar.</li>
</ul>
</section>
</article>

<article id="context-menu-modernization" aria-labelledby="context-menu-modernization-h">
<h2 data-principle="pattern" id="context-menu-modernization-h">Context Menu Modernization</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures context menu modernization.</p>
<section id="context-menu-modernization-perceivable" aria-labelledby="context-menu-modernization-perceivable-h">
<h3 id="context-menu-modernization-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Compact spacing and thin dividers make groups of actions hard to distinguish.</li>
<li data-principle="perceivable">Icon-only top row (copy, paste, rename) lacks accompanying labels at small sizes.</li>
<li data-principle="perceivable">Submenu chevrons are faint; nesting depth isn’t obvious.</li>
<li data-principle="perceivable">Reduced opacity on disabled items is insufficient for some color-vision profiles.</li>
<li data-principle="perceivable">Elevation prompts momentarily hide the menu without an auditory cue.</li>
</ul>
</section>
<section id="context-menu-modernization-operable" aria-labelledby="context-menu-modernization-operable-h">
<h3 id="context-menu-modernization-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Long-press duration for touch varies; users overshoot and trigger drag instead.</li>
<li data-principle="operable">Keyboard users can’t jump to commands by first letter when icons precede labels.</li>
<li data-principle="operable">Scroll areas in tall menus are narrow and difficult for switch control.</li>
<li data-principle="operable">Third-party extensions appear in inconsistent order across surfaces.</li>
<li data-principle="operable">Menu can close on pointer slip, losing position within nested submenus.</li>
</ul>
</section>
<section id="context-menu-modernization-understandable" aria-labelledby="context-menu-modernization-understandable-h">
<h3 id="context-menu-modernization-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">“Show more options” doesn’t explain legacy vs. modern actions.</li>
<li data-principle="understandable">Verb phrasing differs between surfaces (“Share” vs. “Send”), causing confusion.</li>
<li data-principle="understandable">Hidden keyboard shortcuts aren’t surfaced in tooltips or hints.</li>
<li data-principle="understandable">Action scope (file vs. selection vs. folder) isn’t clarified in copy.</li>
<li data-principle="understandable">No inline guidance for customizing which actions are pinned to the top row.</li>
</ul>
</section>
</article>

<article id="bluetooth-device-pairing-flow" aria-labelledby="bluetooth-device-pairing-flow-h">
<h2 data-principle="pattern" id="bluetooth-device-pairing-flow-h">Bluetooth Device Pairing Flow</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures bluetooth device pairing flow.</p>
<section id="bluetooth-device-pairing-flow-perceivable" aria-labelledby="bluetooth-device-pairing-flow-perceivable-h">
<h3 id="bluetooth-device-pairing-flow-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Discovered device rows truncate names; model and type are indistinguishable.</li>
<li data-principle="perceivable">Pairing codes flash briefly and aren’t repeated with text-to-speech.</li>
<li data-principle="perceivable">Battery level for connected devices is hidden or low contrast.</li>
<li data-principle="perceivable">Security/LE audio badges rely on color alone to convey support.</li>
<li data-principle="perceivable">Error toasts overlap the list and block the selected device.</li>
</ul>
</section>
<section id="bluetooth-device-pairing-flow-operable" aria-labelledby="bluetooth-device-pairing-flow-operable-h">
<h3 id="bluetooth-device-pairing-flow-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Scan refresh area is a small icon; keyboard access requires tabbing through the whole list.</li>
<li data-principle="operable">Confirmation dialogs lose focus when devices re-order during scanning.</li>
<li data-principle="operable">Removing a device requires multiple nested actions with tiny targets.</li>
<li data-principle="operable">PIN entry fields don’t auto-advance, slowing switch and eye-tracking users.</li>
<li data-principle="operable">Pairing attempts time out quickly with no “retry” control in focus.</li>
</ul>
</section>
<section id="bluetooth-device-pairing-flow-understandable" aria-labelledby="bluetooth-device-pairing-flow-understandable-h">
<h3 id="bluetooth-device-pairing-flow-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Difference between “Connect,” “Pair,” and “Set as default” isn’t described.</li>
<li data-principle="understandable">Instructions don’t mention device-specific pairing modes or long-press patterns.</li>
<li data-principle="understandable">Audio profile acronyms (HFP, A2DP, BLE) appear without explanations.</li>
<li data-principle="understandable">Users aren’t told that turning off power saving may improve connection stability.</li>
<li data-principle="understandable">No plain-language steps for resolving “driver required” states.</li>
</ul>
</section>
</article>

<article id="power-and-battery-flyout" aria-labelledby="power-and-battery-flyout-h">
<h2 data-principle="pattern" id="power-and-battery-flyout-h">Power & Battery Flyout</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures power & battery flyout.</p>
<section id="power-and-battery-flyout-perceivable" aria-labelledby="power-and-battery-flyout-perceivable-h">
<h3 id="power-and-battery-flyout-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Remaining time estimate is low contrast and updates without announcement.</li>
<li data-principle="perceivable">Charging vs. trickle-charging iconography is too similar to distinguish quickly.</li>
<li data-principle="perceivable">Performance mode badges collide with text at 125–150% scaling.</li>
<li data-principle="perceivable">Battery saver toast overlays flyout content during critical states.</li>
<li data-principle="perceivable">Graphs use thin lines and rely on color alone to show trends.</li>
</ul>
</section>
<section id="power-and-battery-flyout-operable" aria-labelledby="power-and-battery-flyout-operable-h">
<h3 id="power-and-battery-flyout-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Slider handle is small; step changes are inconsistent via keyboard.</li>
<li data-principle="operable">Flyout closes when focus moves to secondary settings, interrupting tasks.</li>
<li data-principle="operable">Touch gestures to change modes conflict with notification panel swipes.</li>
<li data-principle="operable">External battery info isn’t accessible without drilling into deep menus.</li>
<li data-principle="operable">Low-battery dialogs steal focus from fullscreen accessibility tools.</li>
</ul>
</section>
<section id="power-and-battery-flyout-understandable" aria-labelledby="power-and-battery-flyout-understandable-h">
<h3 id="power-and-battery-flyout-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Terms like “balanced,” “best performance,” and “efficiency” lack concrete effects.</li>
<li data-principle="understandable">Copy doesn’t clarify how screen brightness interacts with battery life estimates.</li>
<li data-principle="understandable">No indication that background indexing can affect drain after updates.</li>
<li data-principle="understandable">Battery health vs. capacity isn’t differentiated in plain language.</li>
<li data-principle="understandable">Charging behavior on USB-C hubs isn’t explained or linked to guidance.</li>
</ul>
</section>
</article>

<article id="accessibility-quick-access-win-u" aria-labelledby="accessibility-quick-access-win-u-h">
<h2 data-principle="pattern" id="accessibility-quick-access-win-u-h">Accessibility Quick Access (Win + U)</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures accessibility quick access (win + u).</p>
<section id="accessibility-quick-access-win-u-perceivable" aria-labelledby="accessibility-quick-access-win-u-perceivable-h">
<h3 id="accessibility-quick-access-win-u-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Tile states for Narrator, Magnifier, and Contrast look alike in some themes.</li>
<li data-principle="perceivable">Status text wraps and is cut off at smaller window widths.</li>
<li data-principle="perceivable">Focus outline is thin; active control isn’t obvious for low-vision users.</li>
<li data-principle="perceivable">Audio feedback cues aren’t mirrored with captions or visuals.</li>
<li data-principle="perceivable">Transient banners about required restart disappear too quickly.</li>
</ul>
</section>
<section id="accessibility-quick-access-win-u-operable" aria-labelledby="accessibility-quick-access-win-u-operable-h">
<h3 id="accessibility-quick-access-win-u-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Keyboard navigation cycles through off-screen elements before visible ones.</li>
<li data-principle="operable">Small toggles hinder touch and switch control accuracy.</li>
<li data-principle="operable">Voice commands don’t disambiguate between similar toggles (e.g., captions vs. live captions).</li>
<li data-principle="operable">Launching sub-settings replaces context without a clear “back” route.</li>
<li data-principle="operable">Magnifier shortcuts conflict with app-level zoom bindings.</li>
</ul>
</section>
<section id="accessibility-quick-access-win-u-understandable" aria-labelledby="accessibility-quick-access-win-u-understandable-h">
<h3 id="accessibility-quick-access-win-u-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Descriptions don’t state what each toggle changes system-wide vs. per-app.</li>
<li data-principle="understandable">Narrator learning materials aren’t linked from the quick panel.</li>
<li data-principle="understandable">No guidance on profiles or saving preferred accessibility combinations.</li>
<li data-principle="understandable">Terminology like “filter keys” and “sticky keys” lacks quick hints.</li>
<li data-principle="understandable">Warnings about performance impact of high-contrast or captions are missing.</li>
</ul>
</section>
</article>

<article id="desktop-context-menu-alignment" aria-labelledby="desktop-context-menu-alignment-h">
<h2 data-principle="pattern" id="desktop-context-menu-alignment-h">Desktop Context Menu Alignment</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures desktop context menu alignment.</p>
<section id="desktop-context-menu-alignment-perceivable" aria-labelledby="desktop-context-menu-alignment-perceivable-h">
<h3 id="desktop-context-menu-alignment-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Menu spawns partially off-screen on ultra-wide or portrait layouts.</li>
<li data-principle="perceivable">Drop shadows blend into dark wallpapers, hiding edges.</li>
<li data-principle="perceivable">Selection highlight is subtle and hard to track when scrolling.</li>
<li data-principle="perceivable">Hover states rely on color alone; no shape or underline change.</li>
<li data-principle="perceivable">Context help icons are too small at 200% scaling.</li>
</ul>
</section>
<section id="desktop-context-menu-alignment-operable" aria-labelledby="desktop-context-menu-alignment-operable-h">
<h3 id="desktop-context-menu-alignment-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Right/left alignment flips unpredictably based on cursor position.</li>
<li data-principle="operable">Keyboard focus can escape to the desktop and close the menu unexpectedly.</li>
<li data-principle="operable">Touch opening requires long-press timing that conflicts with drag-to-select.</li>
<li data-principle="operable">Nested submenus open under the pointer, blocking target items.</li>
<li data-principle="operable">Screen edges capture pointer and prevent reaching far submenu items.</li>
</ul>
</section>
<section id="desktop-context-menu-alignment-understandable" aria-labelledby="desktop-context-menu-alignment-understandable-h">
<h3 id="desktop-context-menu-alignment-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">No setting explains how alignment is calculated or how to lock it.</li>
<li data-principle="understandable">Copy doesn’t clarify differences between “View,” “Sort by,” and “Group by.”</li>
<li data-principle="understandable">Legacy items appear without labels indicating their origin.</li>
<li data-principle="understandable">Menu density options (compact/cozy) aren’t previewed.</li>
<li data-principle="understandable">Users aren’t told how alignment impacts multi-monitor edges or taskbar overlap.</li>
</ul>
</section>
</article>

<article id="alt-tab-window-switcher" aria-labelledby="alt-tab-window-switcher-h">
<h2 data-principle="pattern" id="alt-tab-window-switcher-h">Alt+Tab Window Switcher</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures alt+tab window switcher.</p>
<section id="alt-tab-window-switcher-perceivable" aria-labelledby="alt-tab-window-switcher-perceivable-h">
<h3 id="alt-tab-window-switcher-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Preview thumbnails are low-detail; foreground vs. background isn’t obvious.</li>
<li data-principle="perceivable">App labels truncate and omit workspace/desktop context.</li>
<li data-principle="perceivable">Focus ring blends into dark wallpaper; active tile is unclear.</li>
<li data-principle="perceivable">Animation blur hides small text in previews.</li>
<li data-principle="perceivable">Screen readers don’t announce tab order or window counts consistently.</li>
</ul>
</section>
<section id="alt-tab-window-switcher-operable" aria-labelledby="alt-tab-window-switcher-operable-h">
<h3 id="alt-tab-window-switcher-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Holding modifier keys is strenuous; no sticky alternative for mobility impairments.</li>
<li data-principle="operable">Mouse selection inside the switcher conflicts with pointer capture of apps.</li>
<li data-principle="operable">Switch order reflows when apps open/close mid-selection.</li>
<li data-principle="operable">Touch users can’t scrub reliably across many thumbnails.</li>
<li data-principle="operable">Game mode can suppress or delay the switcher without clear notice.</li>
</ul>
</section>
<section id="alt-tab-window-switcher-understandable" aria-labelledby="alt-tab-window-switcher-understandable-h">
<h3 id="alt-tab-window-switcher-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">“Most recent” vs. “In launch order” behavior isn’t documented.</li>
<li data-principle="understandable">Options to show tabs from browsers aren’t explained with examples.</li>
<li data-principle="understandable">No tips indicate per-desktop switching or filtering.</li>
<li data-principle="understandable">Copy doesn’t explain how the switcher interacts with focus assist.</li>
<li data-principle="understandable">Error states when an app stops responding aren’t described.</li>
</ul>
</section>
</article>

<article id="windows-search-flyout" aria-labelledby="windows-search-flyout-h">
<h2 data-principle="pattern" id="windows-search-flyout-h">Windows Search Flyout</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures windows search flyout.</p>
<section id="windows-search-flyout-perceivable" aria-labelledby="windows-search-flyout-perceivable-h">
<h3 id="windows-search-flyout-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Category chips (Apps, Docs, Web) have low contrast and similar shapes.</li>
<li data-principle="perceivable">Spell-correction banners fade quickly without screen reader output.</li>
<li data-principle="perceivable">Result snippets use small, gray text that fails readability at 125% scaling.</li>
<li data-principle="perceivable">Loading indicators appear far from the query field, disconnecting context.</li>
<li data-principle="perceivable">Pinned searches look identical to suggestions, reducing scannability.</li>
</ul>
</section>
<section id="windows-search-flyout-operable" aria-labelledby="windows-search-flyout-operable-h">
<h3 id="windows-search-flyout-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Arrow key navigation skips certain result groups unpredictably.</li>
<li data-principle="operable">Keyboard focus moves when results re-rank, causing accidental launches.</li>
<li data-principle="operable">Touch scrolling inside the flyout conflicts with page scroll underneath.</li>
<li data-principle="operable">Voice search button is small and lacks a keyboard alternative.</li>
<li data-principle="operable">Filters reset after closing the flyout, forcing repeated interaction.</li>
</ul>
</section>
<section id="windows-search-flyout-understandable" aria-labelledby="windows-search-flyout-understandable-h">
<h3 id="windows-search-flyout-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Ranking signals (recent, local, cloud) aren’t explained to users.</li>
<li data-principle="understandable">Search scope (device vs. web) isn’t clearly indicated in results.</li>
<li data-principle="understandable">Query history retention and privacy aren’t summarized inline.</li>
<li data-principle="understandable">Advanced query syntax tips are missing from the UI.</li>
<li data-principle="understandable">Why certain apps show “Open as admin” isn’t clarified.</li>
</ul>
</section>
</article>

<article id="system-notifications-summary-action-center-history" aria-labelledby="system-notifications-summary-action-center-history-h">
<h2 data-principle="pattern" id="system-notifications-summary-action-center-history-h">System Notifications Summary (Action Center History)</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures system notifications summary (action center history).</p>
<section id="system-notifications-summary-action-center-history-perceivable" aria-labelledby="system-notifications-summary-action-center-history-perceivable-h">
<h3 id="system-notifications-summary-action-center-history-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Collapsed groups hide unread counts; users miss important items.</li>
<li data-principle="perceivable">Time stamps are small and low-contrast, hard to parse quickly.</li>
<li data-principle="perceivable">App icons dominate space; message text is truncated excessively.</li>
<li data-principle="perceivable">Media preview cards lack text alternatives for screen readers.</li>
<li data-principle="perceivable">Section headers blend into content when using custom themes.</li>
</ul>
</section>
<section id="system-notifications-summary-action-center-history-operable" aria-labelledby="system-notifications-summary-action-center-history-operable-h">
<h3 id="system-notifications-summary-action-center-history-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Clear buttons are small; bulk actions are close to individual dismiss.</li>
<li data-principle="operable">Tab order enters background elements before active notifications.</li>
<li data-principle="operable">Swipe gestures vary by device and occasionally trigger app open.</li>
<li data-principle="operable">History pagination resets focus to the top after each page load.</li>
<li data-principle="operable">Keyboard shortcuts for expand/collapse aren’t documented.</li>
</ul>
</section>
<section id="system-notifications-summary-action-center-history-understandable" aria-labelledby="system-notifications-summary-action-center-history-understandable-h">
<h3 id="system-notifications-summary-action-center-history-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">“Suggestions” vs. “alerts” aren’t differentiated with plain-language labels.</li>
<li data-principle="understandable">No explanation of retention duration or what “clear” actually deletes.</li>
<li data-principle="understandable">Snooze durations aren’t shown before confirming an action.</li>
<li data-principle="understandable">App categories aren’t explained, making filters opaque.</li>
<li data-principle="understandable">No summary of changes when Focus modes alter notification behavior.</li>
</ul>
</section>
</article>

<article id="display-scaling-and-text-size-controls" aria-labelledby="display-scaling-and-text-size-controls-h">
<h2 data-principle="pattern" id="display-scaling-and-text-size-controls-h">Display Scaling and Text Size Controls</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures display scaling and text size controls.</p>
<section id="display-scaling-and-text-size-controls-perceivable" aria-labelledby="display-scaling-and-text-size-controls-perceivable-h">
<h3 id="display-scaling-and-text-size-controls-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Preview text doesn’t reflect mixed-language or script-specific rendering.</li>
<li data-principle="perceivable">Scaling options are clipped on small displays; important values are hidden.</li>
<li data-principle="perceivable">Contrast on sample UI elements is insufficient to judge readability.</li>
<li data-principle="perceivable">High DPI icons appear blurry during transitions without notice.</li>
<li data-principle="perceivable">Assistive tech status is not announced after applying new scaling.</li>
</ul>
</section>
<section id="display-scaling-and-text-size-controls-operable" aria-labelledby="display-scaling-and-text-size-controls-operable-h">
<h3 id="display-scaling-and-text-size-controls-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Slider and dropdown controls are small; keyboard increments skip key values.</li>
<li data-principle="operable">Apply changes triggers brief black screen without preserving focus.</li>
<li data-principle="operable">Per-monitor scaling requires deep navigation; no quick toggle is available.</li>
<li data-principle="operable">Touch users struggle to drag the fine-grained text size slider.</li>
<li data-principle="operable">Log out requirement isn’t queued; unsaved work can be lost.</li>
</ul>
</section>
<section id="display-scaling-and-text-size-controls-understandable" aria-labelledby="display-scaling-and-text-size-controls-understandable-h">
<h3 id="display-scaling-and-text-size-controls-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">“Recommended” scale doesn’t explain trade-offs with app sharpness.</li>
<li data-principle="understandable">No guidance on accessibility best practices for text size vs. zoom.</li>
<li data-principle="understandable">Mixed-DPI multi-monitor behavior isn’t described with diagrams.</li>
<li data-principle="understandable">Advanced overrides (custom scaling) lack warnings about UI clipping.</li>
<li data-principle="understandable">Users aren’t told how ClearType or font smoothing interacts with scaling.</li>
</ul>
</section>
</article>


<article id="taskbar-pinning-and-unpinning" aria-labelledby="taskbar-pinning-and-unpinning-h">
<h2 data-principle="pattern" id="taskbar-pinning-and-unpinning-h">Taskbar Pinning and Unpinning</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures taskbar pinning and unpinning.</p>
<section id="taskbar-pinning-and-unpinning-perceivable" aria-labelledby="taskbar-pinning-and-unpinning-perceivable-h">
<h3 id="taskbar-pinning-and-unpinning-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Pin/unpin confirmation uses subtle micro-animations that are easy to miss at a glance.</li>
<li data-principle="perceivable">Pinned state is indicated only by a faint underline that fails low-contrast themes.</li>
<li data-principle="perceivable">Tooltip text truncates long app names, making it hard to identify similar apps.</li>
<li data-principle="perceivable">Context menu labels are small on high DPI, reducing legibility for low vision users.</li>
<li data-principle="perceivable">Icon changes during install/update aren’t announced, confusing recognition by sight.</li>
</ul>
</section>
<section id="taskbar-pinning-and-unpinning-operable" aria-labelledby="taskbar-pinning-and-unpinning-operable-h">
<h3 id="taskbar-pinning-and-unpinning-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Right-click targets are tight; misclicks open the app instead of the context menu.</li>
<li data-principle="operable">Keyboard users must navigate nested menus; “Pin to taskbar” isn’t first in focus order.</li>
<li data-principle="operable">Drag-to-pin requires precise pointer control and fails near screen edges.</li>
<li data-principle="operable">Touch-and-hold gesture to open the menu times out inconsistently.</li>
<li data-principle="operable">Pinned items can jump position when new apps launch, disrupting target predictability.</li>
</ul>
</section>
<section id="taskbar-pinning-and-unpinning-understandable" aria-labelledby="taskbar-pinning-and-unpinning-understandable-h">
<h3 id="taskbar-pinning-and-unpinning-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">“Pin to taskbar” vs. “Pin to Start” phrasing is similar and easy to confuse.</li>
<li data-principle="understandable">No explanation that unpinning doesn’t uninstall the app, leading to anxiety.</li>
<li data-principle="understandable">The overflow chevron doesn’t clarify that pinned items might be hidden off-bar.</li>
<li data-principle="understandable">No preview of where a new pin will land relative to existing icons.</li>
<li data-principle="understandable">Status messages don’t confirm success audibly or via ARIA live regions.</li>
</ul>
</section>
</article>

<article id="window-snap-assist-suggestions" aria-labelledby="window-snap-assist-suggestions-h">
<h2 data-principle="pattern" id="window-snap-assist-suggestions-h">Window Snap Assist Suggestions</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures window snap assist suggestions.</p>
<section id="window-snap-assist-suggestions-perceivable" aria-labelledby="window-snap-assist-suggestions-perceivable-h">
<h3 id="window-snap-assist-suggestions-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Snap zone outlines are faint and blend into busy wallpapers.</li>
<li data-principle="perceivable">Suggested app thumbnails are small and omit app names at smaller sizes.</li>
<li data-principle="perceivable">Highlighting of the active zone relies on color only, not shape or pattern.</li>
<li data-principle="perceivable">Transition blur during snapping obscures content verification.</li>
<li data-principle="perceivable">Screen reader cues don’t announce layout options as they appear.</li>
</ul>
</section>
<section id="window-snap-assist-suggestions-operable" aria-labelledby="window-snap-assist-suggestions-operable-h">
<h3 id="window-snap-assist-suggestions-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Precise edge targeting is required; touch users overshoot snap areas.</li>
<li data-principle="operable">Keyboard shortcuts to cycle layouts differ by device and aren’t discoverable in UI.</li>
<li data-principle="operable">Snap preview can steal focus from the app being positioned.</li>
<li data-principle="operable">Switch access hits multiple suggestions before the desired one due to ordering.</li>
<li data-principle="operable">Window resizing after snap resets layout unexpectedly.</li>
</ul>
</section>
<section id="window-snap-assist-suggestions-understandable" aria-labelledby="window-snap-assist-suggestions-understandable-h">
<h3 id="window-snap-assist-suggestions-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Labels like “Focus” and “Columns” don’t map to on-screen geometry for novices.</li>
<li data-principle="understandable">No guidance about how snapped sets behave across virtual desktops.</li>
<li data-principle="understandable">Suggestions don’t explain why certain apps are prioritized.</li>
<li data-principle="understandable">Undo/redo of a snap configuration isn’t surfaced in plain language.</li>
<li data-principle="understandable">Tooltips omit time-saving shortcuts, increasing cognitive load.</li>
</ul>
</section>
</article>

<article id="window-corner-radius-and-shadows" aria-labelledby="window-corner-radius-and-shadows-h">
<h2 data-principle="pattern" id="window-corner-radius-and-shadows-h">Window Corner Radius and Shadows</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures window corner radius and shadows.</p>
<section id="window-corner-radius-and-shadows-perceivable" aria-labelledby="window-corner-radius-and-shadows-perceivable-h">
<h3 id="window-corner-radius-and-shadows-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Rounded corners reduce the visible drag area for resizing in dark mode.</li>
<li data-principle="perceivable">Shadow depth is subtle; foreground window isn’t clearly distinguished.</li>
<li data-principle="perceivable">High-transparency backgrounds make edges indistinct on HDR displays.</li>
<li data-principle="perceivable">Corner anti-aliasing creates halos on certain scaling factors.</li>
<li data-principle="perceivable">Focus rings conflict visually with shadow edges, lowering discoverability.</li>
</ul>
</section>
<section id="window-corner-radius-and-shadows-operable" aria-labelledby="window-corner-radius-and-shadows-operable-h">
<h3 id="window-corner-radius-and-shadows-operable-h">Operable</h3>
<ul>
<li data-principle="operable">Small corner radii reduce effective hit zones for resize handles.</li>
<li data-principle="operable">Shadows overlap adjacent windows, causing accidental window selection.</li>
<li data-principle="operable">Keyboard resizing doesn’t align with the visible corner geometry.</li>
<li data-principle="operable">Touch users misinterpret shadow as draggable area.</li>
<li data-principle="operable">Accessibility cursor highlight can be obscured by heavy drop shadows.</li>
</ul>
</section>
<section id="window-corner-radius-and-shadows-understandable" aria-labelledby="window-corner-radius-and-shadows-understandable-h">
<h3 id="window-corner-radius-and-shadows-understandable-h">Understandable</h3>
<ul>
<li data-principle="understandable">Settings don’t describe tradeoffs between aesthetics and operability.</li>
<li data-principle="understandable">Users aren’t told how these visuals affect battery/performance on low-end GPUs.</li>
<li data-principle="understandable">No preview shows before/after differences for corner radii.</li>
<li data-principle="understandable">Terminology like “elevation” and “depth” isn’t explained.</li>
<li data-principle="understandable">It’s unclear which apps can override system corner styling.</li>
</ul>
</section>
</article>

<article id="night-light-and-hdr-brightness-adjustments" aria-labelledby="night-light-and-hdr-brightness-adjustments-h">
<h2 data-principle="pattern" id="night-light-and-hdr-brightness-adjustments-h">Night Light and HDR Brightness Adjustments</h2>
<p class="user-action" data-principle="user-action">User interacts with or configures night light and hdr brightness adjustments.</p>
<section id="night-light-and-hdr-brightness-adjustments-perceivable" aria-labelledby="night-light-and-hdr-brightness-adjustments-perceivable-h">
<h3 id="night-light-and-hdr-brightness-adjustments-perceivable-h">Perceivable</h3>
<ul>
<li data-principle="perceivable">Temperature slider uses color-only feedback; numeric values are hidden by default.</li>
<li data-principle="perceivable">HDR toggle state is ambiguous when the app forces SDR fallback.</li>
<li data-principle="perceivable">Schedule activation toast fades quickly; users miss state changes.</li>