-
Notifications
You must be signed in to change notification settings - Fork 12
/
index.html
2208 lines (2157 loc) · 149 KB
/
index.html
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 content="text/html; charset=utf-8" http-equiv="Content-Type">
<meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
<title>UI Events KeyboardEvent code Values</title>
<meta content="WD" name="w3c-status">
<link href="https://www.w3.org/StyleSheets/TR/2021/W3C-WD" rel="stylesheet">
<link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
<meta content="Bikeshed version 3383f409d, updated Fri Apr 28 15:49:22 2023 -0700" name="generator">
<link href="http://www.w3.org/TR/uievents-code/" rel="canonical">
<meta content="1370f517480c0167d9978a4433d0f9cc46f568a1" name="document-revision">
<style>
/* Used when spelling out words or symbols phonetically. */
span.phonetic {
font-style: italic;
}
/* KEY
* Denotes a key value (the value of the KeyboardEvent.key property).
*/
code.key {
color: #191970;
background-color: #b0e0e6;
padding: 0 2px;
border: 1px solid #b0d0d6;
border-radius: 3px;
}
code.key a:link, code.key a:visited {
color: #191970;
text-decoration: none;
}
code.key:hover, code.key a:hover {
color: #000000;
background-color: #b0d0d6;
}
/* CODE
* Denotes a code value that indicates the physical location of the key on
* the keyboard). This is the value of the KeyboardEvent.code property.
*/
code.code {
color: #191970;
background-color: #ffc4ff;
padding: 0 2px;
border: 1px solid #f0a4f0;
border-radius: 3px;
}
code.code a:link, code.code a:visited {
color: #191970;
text-decoration: none;
}
code.code:hover, code.code a:hover {
color: #000000;
background-color: #f0a4f0;
}
/* Denotes a string displayed on the keycap. */
code.keycap {
padding: 0 2px;
border: 1px solid black;
border-radius: 3px;
}
/* Denotes a Unicode code-point for the character. */
code.unicode {
color: #191970;
background-color: #98fb98;
}
/* Denotes an example glyph for the character. */
code.glyph {
color: #191970;
background-color: #ffe4b5;
}
/* Formatting for data tables (including the keyboard codes) */
.data-table {
border-collapse:collapse;
text-align:left;
width: 100%;
}
.data-table th {
background:none repeat scroll 0 0 #B9C9FE;
border-bottom:1px solid #FFFFFF;
border-top:4px solid #AABCFE;
color:#003399;
font-weight:normal;
padding: 0.4em 1em;
}
.data-table td {
background:none repeat scroll 0 0 #E8EDFF;
border-bottom:1px solid #FFFFFF;
border-top:1px solid transparent;
color:#666699;
padding: 0.4em 1em;
}
.data-table tr:hover td {
background:none repeat scroll 0 0 #D0DAFD;
color:#333399;
}
/* The cell in a code table that contains the code value. */
.code-table-code {
}
.code-table-required {
text-align: center;
}
.code-impl-data {
text-align: center;
}
.code-impl-data-dark {
background:none repeat scroll 0 0 #d8dDeF !important;
text-align: center;
}
.code-impl-yes {
color: #0a0;
font-weight: bold;
}
.code-impl-no {
color: #f00;
font-weight: bold;
}
</style>
<style>/* style-autolinks */
.css.css, .property.property, .descriptor.descriptor {
color: var(--a-normal-text);
font-size: inherit;
font-family: inherit;
}
.css::before, .property::before, .descriptor::before {
content: "‘";
}
.css::after, .property::after, .descriptor::after {
content: "’";
}
.property, .descriptor {
/* Don't wrap property and descriptor names */
white-space: nowrap;
}
.type { /* CSS value <type> */
font-style: italic;
}
pre .property::before, pre .property::after {
content: "";
}
[data-link-type="property"]::before,
[data-link-type="propdesc"]::before,
[data-link-type="descriptor"]::before,
[data-link-type="value"]::before,
[data-link-type="function"]::before,
[data-link-type="at-rule"]::before,
[data-link-type="selector"]::before,
[data-link-type="maybe"]::before {
content: "‘";
}
[data-link-type="property"]::after,
[data-link-type="propdesc"]::after,
[data-link-type="descriptor"]::after,
[data-link-type="value"]::after,
[data-link-type="function"]::after,
[data-link-type="at-rule"]::after,
[data-link-type="selector"]::after,
[data-link-type="maybe"]::after {
content: "’";
}
[data-link-type].production::before,
[data-link-type].production::after,
.prod [data-link-type]::before,
.prod [data-link-type]::after {
content: "";
}
[data-link-type=element],
[data-link-type=element-attr] {
font-family: Menlo, Consolas, "DejaVu Sans Mono", monospace;
font-size: .9em;
}
[data-link-type=element]::before { content: "<" }
[data-link-type=element]::after { content: ">" }
[data-link-type=biblio] {
white-space: pre;
}
</style>
<style>/* style-counters */
body {
counter-reset: example figure issue;
}
.issue {
counter-increment: issue;
}
.issue:not(.no-marker)::before {
content: "Issue " counter(issue);
}
.example {
counter-increment: example;
}
.example:not(.no-marker)::before {
content: "Example " counter(example);
}
.invalid.example:not(.no-marker)::before,
.illegal.example:not(.no-marker)::before {
content: "Invalid Example" counter(example);
}
figcaption {
counter-increment: figure;
}
figcaption:not(.no-marker)::before {
content: "Figure " counter(figure) " ";
}
</style>
<style>/* style-dfn-panel */
:root {
--dfnpanel-bg: #ddd;
--dfnpanel-text: var(--text);
}
.dfn-panel {
position: absolute;
z-index: 35;
width: 20em;
width: 300px;
height: auto;
max-height: 500px;
overflow: auto;
padding: 0.5em 0.75em;
font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
background: var(--dfnpanel-bg);
color: var(--dfnpanel-text);
border: outset 0.2em;
white-space: normal; /* in case it's moved into a pre */
}
.dfn-panel:not(.on) { display: none; }
.dfn-panel * { margin: 0; padding: 0; text-indent: 0; }
.dfn-panel > b { display: block; }
.dfn-panel a { color: var(--dfnpanel-text); }
.dfn-panel a:not(:hover) { text-decoration: none !important; border-bottom: none !important; }
.dfn-panel > b + b { margin-top: 0.25em; }
.dfn-panel ul { padding: 0 0 0 1em; list-style: none; }
.dfn-panel li a {
white-space: pre;
display: inline-block;
max-width: calc(300px - 1.5em - 1em);
overflow: hidden;
text-overflow: ellipsis;
}
.dfn-panel.activated {
display: inline-block;
position: fixed;
left: .5em;
bottom: 2em;
margin: 0 auto;
max-width: calc(100vw - 1.5em - .4em - .5em);
max-height: 30vh;
}
.dfn-paneled[role="button"] { cursor: pointer; }
</style>
<style>/* style-issues */
a[href].issue-return {
float: right;
float: inline-end;
color: var(--issueheading-text);
font-weight: bold;
text-decoration: none;
}
</style>
<style>/* style-md-lists */
/* This is a weird hack for me not yet following the commonmark spec
regarding paragraph and lists. */
[data-md] > :first-child {
margin-top: 0;
}
[data-md] > :last-child {
margin-bottom: 0;
}
</style>
<style>/* style-selflinks */
:root {
--selflink-text: white;
--selflink-bg: gray;
--selflink-hover-text: black;
}
.heading, .issue, .note, .example, li, dt {
position: relative;
}
a.self-link {
position: absolute;
top: 0;
left: calc(-1 * (3.5rem - 26px));
width: calc(3.5rem - 26px);
height: 2em;
text-align: center;
border: none;
transition: opacity .2s;
opacity: .5;
}
a.self-link:hover {
opacity: 1;
}
.heading > a.self-link {
font-size: 83%;
}
.example > a.self-link,
.note > a.self-link,
.issue > a.self-link {
/* These blocks are overflow:auto, so positioning outside
doesn't work. */
left: auto;
right: 0;
}
li > a.self-link {
left: calc(-1 * (3.5rem - 26px) - 2em);
}
dfn > a.self-link {
top: auto;
left: auto;
opacity: 0;
width: 1.5em;
height: 1.5em;
background: var(--selflink-bg);
color: var(--selflink-text);
font-style: normal;
transition: opacity .2s, background-color .2s, color .2s;
}
dfn:hover > a.self-link {
opacity: 1;
}
dfn > a.self-link:hover {
color: var(--selflink-hover-text);
}
a.self-link::before { content: "¶"; }
.heading > a.self-link::before { content: "§"; }
dfn > a.self-link::before { content: "#"; }
</style>
<body class="h-entry">
<div class="head">
<p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
<h1>UI Events KeyboardEvent code Values</h1>
<p id="w3c-state"><a href="https://www.w3.org/standards/types#WD">W3C Working Draft</a>, <time class="dt-updated" datetime="2023-05-09">9 May 2023</time></p>
<details open>
<summary>More details about this document</summary>
<div data-fill-with="spec-metadata">
<dl>
<dt>This version:
<dd><a class="u-url" href="https://www.w3.org/TR/2023/WD-uievents-code-20230509/">https://www.w3.org/TR/2023/WD-uievents-code-20230509/</a>
<dt>Latest published version:
<dd><a href="http://www.w3.org/TR/uievents-code/">http://www.w3.org/TR/uievents-code/</a>
<dt>Editor's Draft:
<dd><a href="https://w3c.github.io/uievents-code/">https://w3c.github.io/uievents-code/</a>
<dt>Previous Versions:
<dd><a href rel="prev"></a>
<dd><a href="http://www.w3.org/TR/2015/WD-uievents-code-20151215/" rel="prev">http://www.w3.org/TR/2015/WD-uievents-code-20151215/</a>
<dt>History:
<dd><a class="u-url" href="https://www.w3.org/standards/history/uievents-code">https://www.w3.org/standards/history/uievents-code</a>
<dt>Feedback:
<dd><a href="https://github.com/w3c/uievents-code/issues/">GitHub</a>
<dt class="editor">Editors:
<dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:garykac@google.com">Gary Kacmarcik</a> (<span class="p-org org">Google</span>)
<dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:travisleithead@hotmail.com">Travis Leithead</a> (<span class="p-org org">Invited Expert</span>)
<dt>Implementation Report:
<dd><a href="https://w3c.github.io/uievents-code/impl-report.html">https://w3c.github.io/uievents-code/impl-report.html</a>
</dl>
</div>
</details>
<div data-fill-with="warning"></div>
<p class="copyright" data-fill-with="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2023 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document" rel="license">permissive document license</a> rules apply. </p>
<hr title="Separator for header">
</div>
<div class="p-summary" data-fill-with="abstract">
<h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></h2>
<p>This specification defines the values for the KeyboardEvent.code attribute,
which is defined as part of the UI Events Specification <a data-link-type="biblio" href="#biblio-uievents" title="UI Events">[UIEvents]</a>.
The code value contains information about the key event that can be used to
identify the physical key being pressed by the user.</p>
</div>
<h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content">Status of this document</span></h2>
<div data-fill-with="status">
<p> <em>This section describes the status of this document at the time of its publication. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision of this technical report can be found in the <a href="https://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at https://www.w3.org/TR/.</em> </p>
<p> This document was published by the <a href="https://www.w3.org/groups/wg/webapps">Web Applications Working Group</a> as a Working Draft. This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. </p>
<p></p>
<p> This document was published by the <a href="https://www.w3.org/groups/wg/webapps">Web Applications Working Group</a> as a Working Draft using the <a href="https://www.w3.org/2021/Process-20211102/#recs-and-notes">Recommendation
track</a>.
Feedback and comments on this specification are welcome. Please use <a href="https://github.com/w3c/uievents-code/issues">GitHub issues</a> Historical discussions can be found in the <a href="https://lists.w3.org/Archives/Public/public-webapps/">public-webapps@w3.org archives</a>. </p>
<p> Publication as a Working Draft does not imply endorsement by <abbr title="World Wide Web Consortium">W3C</abbr> and its Members. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. </p>
<p> This document was produced by a group operating under the <a href="https://www.w3.org/Consortium/Patent-Policy-20200915/"><abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>. <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="https://www.w3.org/2004/01/pp-impl/114929/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="https://www.w3.org/Consortium/Patent-Policy-20200915/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="https://www.w3.org/Consortium/Patent-Policy-20200915/#sec-Disclosure">section 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>. </p>
<p>This document is governed by the <a href="https://www.w3.org/2021/Process-20211102/" id="w3c_process_revision">2 November 2021 W3C Process Document</a>. </p>
</div>
<div data-fill-with="at-risk"></div>
<nav data-fill-with="table-of-contents" id="toc">
<h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
<ol class="toc" role="directory">
<li>
<a href="#introduction"><span class="secno">1</span> <span class="content">Introduction</span></a>
<ol class="toc">
<li><a href="#style-conventions"><span class="secno">1.1</span> <span class="content">Stylistic Conventions</span></a>
</ol>
<li>
<a href="#keyboard-layout"><span class="secno">2</span> <span class="content">Keyboard Layout</span></a>
<ol class="toc">
<li>
<a href="#keyboard-common-layouts"><span class="secno">2.1</span> <span class="content">Standard Keyboard Layouts</span></a>
<ol class="toc">
<li><a href="#keyboard-sections"><span class="secno">2.1.1</span> <span class="content">Keyboard Sections</span></a>
<li><a href="#keyboard-101"><span class="secno">2.1.2</span> <span class="content">Standard "101" Keyboard Layout</span></a>
<li><a href="#keyboard-101alt"><span class="secno">2.1.3</span> <span class="content">Alternate "101" Keyboard Layout</span></a>
<li><a href="#keyboard-102"><span class="secno">2.1.4</span> <span class="content">Standard "102" Keyboard Layout</span></a>
<li><a href="#keyboard-103"><span class="secno">2.1.5</span> <span class="content">Korean "103" Keyboard Layout</span></a>
<li><a href="#keyboard-104"><span class="secno">2.1.6</span> <span class="content">Brazilian "104" Keyboard Layout</span></a>
<li><a href="#keyboard-106"><span class="secno">2.1.7</span> <span class="content">Japanese "106" Keyboard Layout</span></a>
<li><a href="#keyboard-mac"><span class="secno">2.1.8</span> <span class="content">Apple Keyboard Layout</span></a>
<li><a href="#keyboard-laptops"><span class="secno">2.1.9</span> <span class="content">Laptop Keyboard Layouts</span></a>
<li><a href="#other-locales"><span class="secno">2.1.10</span> <span class="content">Keyboard Layouts For Other Locales</span></a>
</ol>
<li><a href="#keyboard-mobile"><span class="secno">2.2</span> <span class="content">Mobile Keypads</span></a>
<li><a href="#remote-control"><span class="secno">2.3</span> <span class="content">Media Remote Controls</span></a>
<li><a href="#keyboard-chording-virtual"><span class="secno">2.4</span> <span class="content">Virtual Keyboards and Chording Keyboards</span></a>
</ol>
<li>
<a href="#code-value-tables"><span class="secno">3</span> <span class="content">Keyboard Event <code class="idl"><span>code</span></code> Value Tables</span></a>
<ol class="toc">
<li>
<a href="#key-alphanumeric-section"><span class="secno">3.1</span> <span class="content">Alphanumeric Section</span></a>
<ol class="toc">
<li><a href="#key-alphanumeric-writing-system"><span class="secno">3.1.1</span> <span class="content">Writing System Keys</span></a>
<li><a href="#key-alphanumeric-functional"><span class="secno">3.1.2</span> <span class="content">Functional Keys</span></a>
</ol>
<li><a href="#key-controlpad-section"><span class="secno">3.2</span> <span class="content">Control Pad Section</span></a>
<li><a href="#key-arrowpad-section"><span class="secno">3.3</span> <span class="content">Arrow Pad Section</span></a>
<li><a href="#key-numpad-section"><span class="secno">3.4</span> <span class="content">Numpad Section</span></a>
<li><a href="#key-function-section"><span class="secno">3.5</span> <span class="content">Function Section</span></a>
<li><a href="#key-media"><span class="secno">3.6</span> <span class="content">Media Keys</span></a>
<li><a href="#key-legacy"><span class="secno">3.7</span> <span class="content">Legacy, Non-Standard and Special Keys</span></a>
</ol>
<li><a href="#accessibility"><span class="secno">4</span> <span class="content">Accessibility</span></a>
<li><a href="#i18n"><span class="secno">5</span> <span class="content">I18n</span></a>
<li><a href="#security"><span class="secno">6</span> <span class="content">Security Considerations</span></a>
<li><a href="#privacy"><span class="secno">7</span> <span class="content">Privacy Considerations</span></a>
<li><a href="#acknowledgements-contributors"><span class="secno">8</span> <span class="content">Acknowledgements</span></a>
<li>
<a href="#w3c-conformance"><span class="secno"></span> <span class="content">Conformance</span></a>
<ol class="toc">
<li><a href="#w3c-conventions"><span class="secno"></span> <span class="content">Document conventions</span></a>
<li><a href="#w3c-conformant-algorithms"><span class="secno"></span> <span class="content">Conformant Algorithms</span></a>
</ol>
<li>
<a href="#index"><span class="secno"></span> <span class="content">Index</span></a>
<ol class="toc">
<li><a href="#index-defined-here"><span class="secno"></span> <span class="content">Terms defined by this specification</span></a>
<li><a href="#index-defined-elsewhere"><span class="secno"></span> <span class="content">Terms defined by reference</span></a>
</ol>
<li>
<a href="#references"><span class="secno"></span> <span class="content">References</span></a>
<ol class="toc">
<li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
<li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
</ol>
</ol>
</nav>
<main>
<h2 class="heading settled" data-level="1" id="introduction"><span class="secno">1. </span><span class="content">Introduction</span><a class="self-link" href="#introduction"></a></h2>
<p>This document provides an overview of the various keyboard layouts and
specifies the <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code">code</a></code> values that should be
used for each of the keys. Unlike the <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-key" id="ref-for-dom-keyboardevent-key">key</a></code> values described
in <a data-link-type="biblio" href="#biblio-uievents-key" title="UI Events KeyboardEvent key Values">[UIEvents-key]</a>, the <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code①">code</a></code> values are based only on the
key’s physical location on the keyboard and do not vary based on the user’s
current locale.</p>
<p>This specification was formerly titled <em>DOM Level 3 KeyboardEvent <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code②">code</a></code> Values</em>.</p>
<h3 class="heading settled" data-level="1.1" id="style-conventions"><span class="secno">1.1. </span><span class="content">Stylistic Conventions</span><a class="self-link" href="#style-conventions"></a></h3>
<p>This specification uses the following conventions:</p>
<ul>
<li data-md>
<p>The <em><a data-link-type="dfn" href="https://www.w3.org/TR/uievents/#key-legends" id="ref-for-key-legends">key cap</a></em> or label printed on a key is shown as <code class="keycap">↓</code>, <code class="keycap">=</code> or <code class="keycap">Q</code>. This is used to refer to a
key from the user’s perspective without regard for the <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-key" id="ref-for-dom-keyboardevent-key①">key</a></code> and <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code③">code</a></code> values in the
generated <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#interface-keyboardevent" id="ref-for-interface-keyboardevent">KeyboardEvent</a></code>.</p>
<li data-md>
<p>Glyphs representing character are shown as: <code class="glyph">"𣧂"</code>.</p>
<li data-md>
<p>Unicode <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#code-point" id="ref-for-code-point">code points</a> are shown as: <code class="unicode">U+003D</code>.</p>
<li data-md>
<p>Valid <a data-link-type="dfn" href="https://www.w3.org/TR/uievents-key/#key-attr-values" id="ref-for-key-attr-values">key attribute values</a> (i.e., the value of
a <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-key" id="ref-for-dom-keyboardevent-key②">key</a></code> attribute) are shown as: <code class="key">"<a href="http://www.w3.org/TR/uievents-key/#key-ArrowDown">ArrowDown</a>"</code>, <code class="key">"="</code>, <code class="key">"q"</code> or <code class="key">"Q"</code>.</p>
<li data-md>
<p>Valid <a data-link-type="dfn" href="#key-code-attribute-value" id="ref-for-key-code-attribute-value">key code attribute values</a> (i.e., the
value of a <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code④">code</a></code> attribute) are shown as: <code class="code">"<a href="#code-ArrowDown">ArrowDown</a>"</code>, <code class="code">"<a href="#code-Equal">Equal</a>"</code> or <code class="code">"<a href="#code-KeyQ">KeyQ</a>"</code>.</p>
</ul>
<h2 class="heading settled" data-level="2" id="keyboard-layout"><span class="secno">2. </span><span class="content">Keyboard Layout</span><a class="self-link" href="#keyboard-layout"></a></h2>
<p><em>This section is non-normative.</em></p>
<p>Alphanumeric keyboards are the most common way for users to generate
keyboard events. This section provides an overview of standard keyboards and
their physical layouts.</p>
<h3 class="heading settled" data-level="2.1" id="keyboard-common-layouts"><span class="secno">2.1. </span><span class="content">Standard Keyboard Layouts</span><a class="self-link" href="#keyboard-common-layouts"></a></h3>
<p>This section describes the physical layouts found on commonly available
keyboards.</p>
<h4 class="heading settled" data-level="2.1.1" id="keyboard-sections"><span class="secno">2.1.1. </span><span class="content">Keyboard Sections</span><a class="self-link" href="#keyboard-sections"></a></h4>
<p>When discussing keyboard layouts, it is convenient to divide the
standard keyboard into distinct sections and to label each row.</p>
<figure id="figure-keyboard-sections">
<img alt="The five general sections of a standard keyboard" height="225" src="images/keyboard-sections.svg" width="684">
<figcaption>The five general sections of a standard keyboard</figcaption>
</figure>
<p>These keyboard sections are:</p>
<ul>
<li data-md>
<p>The <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section">alphanumeric section</a> is the main part of the
keyboard and is where most of the keyboard variation occurs.
When a user selects a keyboard layout, it is the keys in this
sections that are most affected.</p>
<li data-md>
<p>The <a data-link-type="dfn" href="#control-pad" id="ref-for-control-pad">control pad</a> and <a data-link-type="dfn" href="#arrow-pad" id="ref-for-arrow-pad">arrow pad</a> sections contain the arrow keys and other editing keys.</p>
<li data-md>
<p>The <a data-link-type="dfn" href="#numpad" id="ref-for-numpad">numpad</a> (also known as the "numeric <a data-link-type="dfn" href="#keypad" id="ref-for-keypad">keypad</a>"
or "number pad") contains number and math keys to make it easier
to enter numeric data.</p>
<li data-md>
<p>And finally, the <a data-link-type="dfn" href="#function-section" id="ref-for-function-section">function section</a> contains
miscellaneous <a data-link-type="dfn" href="#function-key" id="ref-for-function-key">function keys</a> and special keys like <code class="keycap">Escape</code>.</p>
</ul>
<p>To make it easier to identify keys, the rows on the keyboard are
named starting with "A" for the bottom row up to "E" for the top
row. The row of keys in the <a data-link-type="dfn" href="#function-section" id="ref-for-function-section①">function section</a> are considered to be in
row "K". These row names are consistent with those given in <a data-link-type="biblio" href="#biblio-iso9995-1" title="ISO/IEC 9995-1:2009 Information technology -- Keyboard layouts for text and office systems -- Part 1: General principles governing keyboard layouts">[ISO9995-1]</a>.</p>
<p>Note that many keyboards (both modern and legacy) have extra keys
that do not fit neatly into the above sections. Some of these keys
are covered in <a href="#key-media">§ 3.6 Media Keys</a>.</p>
<h4 class="heading settled" data-level="2.1.2" id="keyboard-101"><span class="secno">2.1.2. </span><span class="content">Standard "101" Keyboard Layout</span><a class="self-link" href="#keyboard-101"></a></h4>
<p>The standard "101" keyboard (commonly referred to as the "US
layout") is the only layout that has a <code class="code">"<a href="#code-Backslash">Backslash</a>"</code> key (labeled <code class="keycap">\|</code>) above a single-row <code class="keycap">Enter</code> key. All the other
layouts omit this key and expand the <code class="keycap">Enter</code> key to
occupy two-rows.</p>
<figure id="figure-keyboard-101-us">
<img alt="Standard '101' keyboard layout" height="225" src="images/keyboard-101-us.svg" width="684">
<figcaption>Standard "101" keyboard layout showing unmodified US key values</figcaption>
</figure>
<p>Modern standard "101"-layout keyboards actually contain 104 keys: 61
keys in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section①">alphanumeric section</a> and 43 keys in the <a data-link-type="dfn" href="#numpad" id="ref-for-numpad①">numpad</a>, <a data-link-type="dfn" href="#control-pad" id="ref-for-control-pad①">control pad</a>, <a data-link-type="dfn" href="#arrow-pad" id="ref-for-arrow-pad①">arrow pad</a> and <a data-link-type="dfn" href="#function-section" id="ref-for-function-section②">function sections</a>.
The "101" name for this keyboard layout dates to the
time when this standard keyboard did in fact contain 101 keys. The
two <code class="keycap">Meta</code> keys (commonly given an OS-specific label), and the <code class="keycap">Menu</code> key were added later to bring the total to 104 keys.</p>
<h4 class="heading settled" data-level="2.1.3" id="keyboard-101alt"><span class="secno">2.1.3. </span><span class="content">Alternate "101" Keyboard Layout</span><a class="self-link" href="#keyboard-101alt"></a></h4>
<p>The alternate "101" keyboard has a large <code class="keycap">Enter</code> key and
shrinks the <code class="keycap">Backspace</code> key to make room for the <code class="code">"<a href="#code-IntlYen">IntlYen</a>"</code> key (which replaces the <code class="code">"<a href="#code-Backslash">Backslash</a>"</code> key found in the standard
101 layout). The <code class="code">"<a href="#code-IntlYen">IntlYen</a>"</code> name comes from the Japanese layout
where this is the <code class="keycap">¥</code> (<span class="unicode">yen</span>) key — in the Russian
layout shown below this key maps to a <code class="keycap">\/</code>.</p>
<figure id="figure-keyboard-101-russian">
<img alt="Alternate '101' keyboard layout" height="225" src="images/keyboard-101-russian.svg" width="684">
<figcaption>Alternate "101" keyboard layout showing unmodified Russian key values</figcaption>
</figure>
<p>Modern alternate "101"-layout keyboards contain 104 keys: 61 keys in
the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section②">alphanumeric section</a> and 43 keys in the <a data-link-type="dfn" href="#numpad" id="ref-for-numpad②">numpad</a>, <a data-link-type="dfn" href="#control-pad" id="ref-for-control-pad②">control pad</a>, <a data-link-type="dfn" href="#arrow-pad" id="ref-for-arrow-pad②">arrow pad</a> and <a data-link-type="dfn" href="#function-section" id="ref-for-function-section③">function sections</a>.</p>
<h4 class="heading settled" data-level="2.1.4" id="keyboard-102"><span class="secno">2.1.4. </span><span class="content">Standard "102" Keyboard Layout</span><a class="self-link" href="#keyboard-102"></a></h4>
<p>The standard "102" keyboard is common throughout Europe and adds a
key that doesn’t exist on the "101" layouts: The <code class="code">"<a href="#code-IntlBackslash">IntlBackslash</a>"</code> key (labelled <code class="keycap">\|</code> on a UK keyboard) next to the left shift
key.</p>
<p>A second key is also added (labelled <code class="keycap">#~</code> on a UK
keyboard) which is partially tucked under the <code class="keycap">Enter</code> key.
This key is encoded as <code class="code">"<a href="#code-Backslash">Backslash</a>"</code>, using the same code as the <code class="keycap">\|</code> key found on the "101" keyboard layout.
According to <a data-link-type="biblio" href="#biblio-usb-hid" title="USB HID Usage Tables 1.12">[USB-HID]</a>, the US <code class="keycap">\|</code> and UK <code class="keycap">#~</code> are
actually two separate keys (named "Keyboard \ and |" and "Keyboard
Non-US # and ~"), but since these two keys never co-occur on the
same keyboard most platforms use the same scancode for both keys,
making them difficult to distinguish. It is for this reason that the
code <code class="code">"<a href="#code-Backslash">Backslash</a>"</code> is used for both of these keys.</p>
<figure id="figure-keyboard-102-uk">
<img alt="Standard '102' keyboard layout" height="225" src="images/keyboard-102-uk.svg" width="684">
<figcaption>Standard "102" keyboard layout showing unmodified UK key values</figcaption>
</figure>
<p>Modern "102"-layout keyboards contain 105 keys: 62 keys in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section③">alphanumeric section</a> and 43 keys in the <a data-link-type="dfn" href="#numpad" id="ref-for-numpad③">numpad</a>, <a data-link-type="dfn" href="#control-pad" id="ref-for-control-pad③">control pad</a>, <a data-link-type="dfn" href="#arrow-pad" id="ref-for-arrow-pad③">arrow pad</a> and <a data-link-type="dfn" href="#function-section" id="ref-for-function-section④">function sections</a>.</p>
<h4 class="heading settled" data-level="2.1.5" id="keyboard-103"><span class="secno">2.1.5. </span><span class="content">Korean "103" Keyboard Layout</span><a class="self-link" href="#keyboard-103"></a></h4>
<p>The Korean "103" keyboard is based on the alternate 101 layout and
adds two additional keys (one on each side of the spacebar) to
handle Korean-specific input modes. These keys are <code class="code">"<a href="#code-Lang2">Lang2</a>"</code> ("Hanja", labelled <code class="keycap">한자</code> <span class="unicode">hanja</span>)
and <code class="code">"<a href="#code-Lang1">Lang1</a>"</code> ("HangulMode", labelled <code class="keycap">한/영</code> <span class="unicode">han/yeong</span>).</p>
<figure id="figure-keyboard-103-korean">
<img alt="Korean '103' keyboard layout" height="225" src="images/keyboard-103-korean.svg" width="684">
<figcaption>Korean "103" keyboard layout showing unmodified Korean key values</figcaption>
</figure>
<p>Modern "103"-layout keyboards contain 106 keys: 63 keys in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section④">alphanumeric section</a> and 43 keys in the <a data-link-type="dfn" href="#numpad" id="ref-for-numpad④">numpad</a>, <a data-link-type="dfn" href="#control-pad" id="ref-for-control-pad④">control pad</a>, <a data-link-type="dfn" href="#arrow-pad" id="ref-for-arrow-pad④">arrow pad</a> and <a data-link-type="dfn" href="#function-section" id="ref-for-function-section⑤">function sections</a>.</p>
<h4 class="heading settled" data-level="2.1.6" id="keyboard-104"><span class="secno">2.1.6. </span><span class="content">Brazilian "104" Keyboard Layout</span><a class="self-link" href="#keyboard-104"></a></h4>
<p>The "104" layout used in Brazil adds 4 new keys: two keys
from the "102" layout (<code class="code">"<a href="#code-Backslash">Backslash</a>"</code> and <code class="code">"<a href="#code-IntlBackslash">IntlBackslash</a>"</code>) plus
the <code class="code">"<a href="#code-IntlRo">IntlRo</a>"</code> key (next to the right shift key) and an extra key
on the <a data-link-type="dfn" href="#numpad" id="ref-for-numpad⑤">numpad</a>. This new <a data-link-type="dfn" href="#numpad" id="ref-for-numpad⑥">numpad</a> key is called <code class="code">"<a href="#code-NumpadComma">NumpadComma</a>"</code> because it represents the thousands separator. On
the Brazilian key layout, this key is labelled <code class="keycap">.</code> and the <code class="code">"<a href="#code-NumpadDecimal">NumpadDecimal</a>"</code> key is labelled <code class="keycap">,</code>.</p>
<figure id="figure-keyboard-104-brazilian">
<img alt="Standard '104' keyboard layout" height="225" src="images/keyboard-104-brazilian.svg" width="684">
<figcaption>Standard "104" keyboard layout showing unmodified Brazilian key values</figcaption>
</figure>
<p>Modern "104"-layout keyboards contain 107 keys: 63 keys in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section⑤">alphanumeric section</a> and 44 keys in the <a data-link-type="dfn" href="#numpad" id="ref-for-numpad⑦">numpad</a>, <a data-link-type="dfn" href="#control-pad" id="ref-for-control-pad⑤">control pad</a>, <a data-link-type="dfn" href="#arrow-pad" id="ref-for-arrow-pad⑤">arrow pad</a> and <a data-link-type="dfn" href="#function-section" id="ref-for-function-section⑥">function sections</a>.
Some Brazilian keyboards lack the extra <a data-link-type="dfn" href="#numpad" id="ref-for-numpad⑧">numpad</a> key and have
only 106 keys.</p>
<h4 class="heading settled" data-level="2.1.7" id="keyboard-106"><span class="secno">2.1.7. </span><span class="content">Japanese "106" Keyboard Layout</span><a class="self-link" href="#keyboard-106"></a></h4>
<p>The Japanese "106" keyboard layout adds 3 new keys: <code class="code">"<a href="#code-IntlYen">IntlYen</a>"</code> (labelled <code class="keycap">¥_</code>), <code class="code">"<a href="#code-Backslash">Backslash</a>"</code> (labelled <code class="keycap">]む</code>)
and <code class="code">"<a href="#code-IntlRo">IntlRo</a>"</code> (labelled <code class="keycap">\ろ</code>).
It also shrinks the spacebar to make room for 3 input mode keys: <code class="code">"<a href="#code-NonConvert">NonConvert</a>"</code> (labelled <code class="keycap">無変換</code> <span class="unicode">muhenkan</span>), <code class="code">"<a href="#code-Convert">Convert</a>"</code> (labelled <code class="keycap">変換</code> <span class="unicode">henkan</span>)
and <code class="code">"<a href="#code-KanaMode">KanaMode</a>"</code> (labelled <code class="keycap">カタカナ/ひらがな/ローマ字</code> <span class="unicode">katakana/hiragana/romaji</span>).</p>
<figure id="figure-keyboard-106-japanese">
<img alt="Standard '106' keyboard layout" height="225" src="images/keyboard-106-japanese.svg" width="684">
<figcaption>Standard "106" keyboard layout showing unmodified Japanese key values</figcaption>
</figure>
<p>Modern "106"-layout keyboards contain 109 keys: 66 keys in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section⑥">alphanumeric section</a> and 43 keys in the <a data-link-type="dfn" href="#numpad" id="ref-for-numpad⑨">numpad</a>, <a data-link-type="dfn" href="#control-pad" id="ref-for-control-pad⑥">control pad</a>, <a data-link-type="dfn" href="#arrow-pad" id="ref-for-arrow-pad⑥">arrow pad</a> and <a data-link-type="dfn" href="#function-section" id="ref-for-function-section⑦">function sections</a>.</p>
<h4 class="heading settled" data-level="2.1.8" id="keyboard-mac"><span class="secno">2.1.8. </span><span class="content">Apple Keyboard Layout</span><a class="self-link" href="#keyboard-mac"></a></h4>
<p>In general, Apple keyboards follow the same layout as PC keyboards,
but there are some differences as noted in the following figure.</p>
<figure id="figure-keyboard-mac">
<img alt="Apple extended keyboard layout" height="225" src="images/keyboard-mac.svg" width="684">
<figcaption>Apple extended keyboard layout showing unmodified English key values</figcaption>
</figure>
<p>In this figure, the green keys are those that have been moved to a
new location while the blue keys indicate keys that have been added.</p>
<h4 class="heading settled" data-level="2.1.9" id="keyboard-laptops"><span class="secno">2.1.9. </span><span class="content">Laptop Keyboard Layouts</span><a class="self-link" href="#keyboard-laptops"></a></h4>
<p>The limited space available on laptop keyboards often means that the
physical key layout needs to be adjusted to fit all the required
keys. The <a data-link-type="dfn" href="#writing-system-keys" id="ref-for-writing-system-keys">writing system keys</a> in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section⑦">alphanumeric
section</a> tend to remain intact, but the other keyboard sections
are usually combined with other keys or removed altogether.</p>
<figure id="figure-keyboard-laptop-mac">
<img alt="Apple laptop keyboard layout" height="180" src="images/keyboard-laptop-mac.svg" width="420">
<figcaption>Apple laptop keyboard layout</figcaption>
</figure>
<p>In this Apple laptop keyboard, the right control key has been
removed to make room for half-height arrow keys and a <code class="keycap">Fn</code> key
is added on the left.</p>
<figure id="figure-keyboard-laptop">
<img alt="Sample PC laptop keyboard layout" height="180" src="images/keyboard-laptop.svg" width="460">
<figcaption>Sample PC laptop keyboard layout</figcaption>
</figure>
<p>PC laptop keyboards vary considerably, but this sample keyboard
demonstrates some commonly found aspects. The <a data-link-type="dfn" href="#control-pad" id="ref-for-control-pad⑦">control pad</a> keys are added along the right-hand side with the <a data-link-type="dfn" href="#arrow-pad" id="ref-for-arrow-pad⑦">arrow pad</a> keys tucked in along the bottom. The right <code class="keycap">Shift</code> key is
often shrunk to make room for the up arrow key and the right <code class="keycap">Meta</code> key is typically removed altogether.</p>
<h4 class="heading settled" data-level="2.1.10" id="other-locales"><span class="secno">2.1.10. </span><span class="content">Keyboard Layouts For Other Locales</span><a class="self-link" href="#other-locales"></a></h4>
<p>Other locales are not explicitly described in this specification because they
start with one of the existing layouts and adapt it by changing the keycaps
and the key mappings.</p>
<p>Because these keyboards do not introduce new physical keys, they do not
require explicit documentation.</p>
<p>These keyboards are typically based on the "101" (standard or alternate)
or "102" layouts.
For example, the common Arabic, Cyrillic, Greek, Hindi, Khmer and Thai
keyboards are all based on either the "101" or "102" keyboard layouts.</p>
<h3 class="heading settled" data-level="2.2" id="keyboard-mobile"><span class="secno">2.2. </span><span class="content">Mobile Keypads</span><a class="self-link" href="#keyboard-mobile"></a></h3>
<p>In the case where a content author wishes to rely on the mechanical
layout of a mobile keypad, this specification suggests the keyboard
configuration specified in <a data-link-type="biblio" href="#biblio-iso9995-8" title="ISO/IEC 9995-8:2009 Information technology -- Keyboard layouts for text and office systems -- Part 8: Allocation of letters to the keys of a numeric keypad">[ISO9995-8]</a>, which defines a numeric keypad
layout and secondary assignment of Unicode characters in the range <code class="unicode">U+0061</code> ... <code class="unicode">U+007A</code> (<code class="glyph">"a"</code> - <code class="glyph">"z"</code>) to the number keys <code class="keycap">2</code> through <code class="keycap">9</code>, as a common layout appropriate to some
international uses.</p>
<p class="note" role="note"> This keypad layout, and in particular the distribution of letters is for
English devices, and will not match the keypads or configurations of
many users. Content authors cannot rely upon any particular
configuration, and are expected to create content in an
internationalized and localizable manner. </p>
<figure id="figure-numeric-keypad">
<img alt="Mobile keypad layout" height="305" src="images/mobile-keypad.svg" width="140">
<figcaption>A graphical depiction of a generic mobile keypad.</figcaption>
</figure>
<h3 class="heading settled" data-level="2.3" id="remote-control"><span class="secno">2.3. </span><span class="content">Media Remote Controls</span><a class="self-link" href="#remote-control"></a></h3>
<p>Many keyboards contain special keys to control media functions.
Increasingly, many media devices, especially televisions, are
Web-enabled. Hybrid keyboard/remote-control devices are becoming more
common. To meet the needs of these hybrid Web/media devices, this
specification defines keys that are common as remote control buttons, in
addition to traditional keyboard keys.</p>
<p>Because of the smaller form factor, keys (or buttons) on a remote
control will often be modal, with one key performing different functions
based on the context of the on-screen content. Additionally, many keys
serve as toggles, to change back and forth between two or more states
(see toggling keys). These remote control buttons typically do not have
modifier states so each button is assigned a single function (like <code class="keycap">Play</code>, <code class="keycap">Pause</code>, <code class="keycap">Up</code>, <code class="keycap">Menu</code> or <code class="keycap">Exit</code>).</p>
<figure id="figure-media-remote-control">
<img alt="A sample media remote control" height="422" src="images/remote-control.svg" width="102">
<figcaption>A graphical depiction of a media remote control.</figcaption>
</figure>
<h3 class="heading settled" data-level="2.4" id="keyboard-chording-virtual"><span class="secno">2.4. </span><span class="content">Virtual Keyboards and Chording Keyboards</span><a class="self-link" href="#keyboard-chording-virtual"></a></h3>
<p>Virtual keyboards are software-based sets of keys, in a variety of
different arrangements, commonly found on touch-screen devices. They are
often modal, with the ability to switch between different dynamic sets
of keys, such as alphabetic, numeric, or symbolic keys. Because of the
lack of physical constraints, these keyboards MAY present the widest
range of characters, including emoticons and other symbols. Wherever possible,
however, virtual keyboards SHOULD produce the normal range of keyboard events
and values, for ease of authoring and compatibility with existing content.</p>
<p>Chording keyboards, also known as chorded keysets or chord keyboards, are
key input devices which produce values by pressing several keys in
combination or sequence, normally to simulate a full range of characters
or commands on a reduced set of keys, often for single-handed use. A
chording keyboard MAY have additional mode keys to switch between key
values, and the number and type of keys pressed to produce a key value
will vary, but the final key values produced by such keyboards SHOULD
match the range of key values described in this specification.</p>
<p>For these and other alternative modal keyboards, the <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-key" id="ref-for-dom-keyboardevent-key③">key</a></code> values <code class="key">"<a href="http://www.w3.org/TR/uievents-key/#key-Alphanumeric">Alphanumeric</a>"</code>, <code class="key">"<a href="http://www.w3.org/TR/uievents-key/#key-CapsLock">CapsLock</a>"</code>, <code class="key">"<a href="http://www.w3.org/TR/uievents-key/#key-NumLock">NumLock</a>"</code>,
and <code class="key">"<a href="http://www.w3.org/TR/uievents-key/#key-SymbolLock">SymbolLock</a>"</code> are RECOMMENDED for the keys which switch between different modes.</p>
<h2 class="heading settled" data-level="3" id="code-value-tables"><span class="secno">3. </span><span class="content">Keyboard Event <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code⑤">code</a></code> Value Tables</span><a class="self-link" href="#code-value-tables"></a></h2>
<p>This section defines a list of values which are appropriate for use as <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code⑥">code</a></code> values.</p>
<p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="key-code-attribute-value">key code attribute value</dfn> is any of the values given in the
"<code>KeyboardEvent.code</code>" column of any of the tables in this section of the
specification.</p>
<p>Each table in this section has a "Required" column which indicates whether or not the
value is required for a conforming implementation. Entries where the "Required" column
is "No" are optional and may be used by implementations to support special keyboards
(such as multimedia or legacy keyboards).</p>
<p class="note" role="note"> Note: Some values listed in this specification as "Required" may not be available on
all platforms or devices. For example, Mac keyboards do not have an <code class="keycap">Insert</code> key
whereas standard PC keyboards do not have a <code class="keycap">Help</code> key. </p>
<p>For every key listed as "Required" in this specification, a conforming implementation
of the <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#interface-keyboardevent" id="ref-for-interface-keyboardevent①">KeyboardEvent</a></code> interface MUST return the correct value as long as that key
is available on that platform.</p>
<p class="note" role="note"> Note: While every attempt has been made to make this list of values as complete as possible,
new values will periodically need to be defined as new input devices are introduced.
Rather than allowing user agents to define their own <a data-link-type="dfn" href="#key-code-attribute-value" id="ref-for-key-code-attribute-value①">key code attribute values</a> (which are unlikely to be consistent across multiple user agents), bugs SHOULD be
filed so that this specification can be updated. </p>
<h3 class="heading settled" data-level="3.1" id="key-alphanumeric-section"><span class="secno">3.1. </span><span class="content">Alphanumeric Section</span><a class="self-link" href="#key-alphanumeric-section"></a></h3>
<p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="alphanumeric-section">alphanumeric section</dfn> is the main section of the keyboard. It
contains keys that fall into two general
categories: <a data-link-type="dfn" href="#writing-system-keys" id="ref-for-writing-system-keys①">writing system keys</a> whose meaning
changes based on the current keyboard layout, and <a data-link-type="dfn" href="#functional-keys" id="ref-for-functional-keys">functional keys</a> which are (mostly) the same for all
layouts.</p>
<h4 class="heading settled" data-level="3.1.1" id="key-alphanumeric-writing-system"><span class="secno">3.1.1. </span><span class="content">Writing System Keys</span><a class="self-link" href="#key-alphanumeric-writing-system"></a></h4>
<p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="writing-system-keys">writing system keys</dfn> are those that change
meaning (i.e., they produce different <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-key" id="ref-for-dom-keyboardevent-key④">key</a></code> values) based on the current locale and keyboard layout.</p>
<figure id="figure-keyboard-codes-alphanum1">
<img alt="The writing system keys" height="225" src="images/keyboard-codes-alphanum1.svg" width="653">
<figcaption>The <a data-link-type="dfn" href="#writing-system-keys" id="ref-for-writing-system-keys②">writing system keys</a> in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section⑧">alphanumeric section</a></figcaption>
</figure>
<p>This figure shows a hypothetical keyboard that combines all the <a data-link-type="dfn" href="#writing-system-keys" id="ref-for-writing-system-keys③">writing system keys</a> (shown in blue and green) found on the
various keyboards. Blue keys are present on all standard
keyboards while green keys are only available on some keyboards.</p>
<div class="example" id="example-9b83bb2c"><a class="self-link" href="#example-9b83bb2c"></a> The <code class="code">"<a href="#code-Digit2">Digit2</a>"</code> and <code class="code">"<a href="#code-KeyQ">KeyQ</a>"</code> keys are <a data-link-type="dfn" href="#writing-system-keys" id="ref-for-writing-system-keys④">writing system keys</a> that
generate <code class="key">"2"</code> and <code class="key">"q"</code> when the US locale is
active and <code class="key">"é"</code> and <code class="key">"a"</code> when the French locale is active. </div>
<p>The name shown on each key is the <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code⑦">code</a></code> assigned to that key. Wherever possible, the <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code⑧">code</a></code> names are based on the name for the US
key in that position (i.e., they are based on the US keyboard
layout), which follows the naming convention found in <a data-link-type="biblio" href="#biblio-usb-hid" title="USB HID Usage Tables 1.12">[USB-HID]</a>.
For keys that don’t exist on the US keyboard, names from the UK or Japanese
layouts are used instead.</p>
<p>Note that there are two <code class="code">"<a href="#code-Backslash">Backslash</a>"</code> keys in this figure: a
large one at the end of Row D on the 101-key layout, and a
smaller one between <code class="code">"<a href="#code-Quote">Quote</a>"</code> and <code class="code">"<a href="#code-Enter">Enter</a>"</code> on Row C of the
102-, 104- and 106-key layouts. Only one <code class="code">"<a href="#code-Backslash">Backslash</a>"</code> key
may be present on a keyboard layout.</p>
<table class="data-table full-width" id="table-key-code-alphanumeric-writing-system">
<caption>List of code values for writing system keys in the Alphanumeric section.</caption>
<thead>
<tr>
<th style="width:20%"><code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#interface-keyboardevent" id="ref-for-interface-keyboardevent②">KeyboardEvent</a></code> <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code⑨">code</a></code>
<th style="width:10%">Required
<th style="width:70%">Notes (Non-normative)
<tbody>
<tr>
<td class="code-table-code"><code class="code" id="code-Backquote">"Backquote"</code>
<td class="code-table-required">Yes
<td><code class="keycap">`~</code> on a US keyboard. This is the <code class="keycap">半角/全角/漢字</code> (<span class="unicode">hankaku/zenkaku/kanji</span>) key on Japanese keyboards
<tr>
<td class="code-table-code"><code class="code" id="code-Backslash">"Backslash"</code>
<td class="code-table-required">Yes
<td>Used for both the US <code class="keycap">\|</code> (on the 101-key layout) and also for the key located between the <code class="keycap">"</code> and <code class="keycap">Enter</code> keys on row C of the 102-,
104- and 106-key layouts.
Labelled <code class="keycap">#~</code> on a UK (102) keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-BracketLeft">"BracketLeft"</code>
<td class="code-table-required">Yes
<td><code class="keycap">[{</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-BracketRight">"BracketRight"</code>
<td class="code-table-required">Yes
<td><code class="keycap">]}</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Comma">"Comma"</code>
<td class="code-table-required">Yes
<td><code class="keycap">,<</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit0">"Digit0"</code>
<td class="code-table-required">Yes
<td><code class="keycap">0)</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit1">"Digit1"</code>
<td class="code-table-required">Yes
<td><code class="keycap">1!</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit2">"Digit2"</code>
<td class="code-table-required">Yes
<td><code class="keycap">2@</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit3">"Digit3"</code>
<td class="code-table-required">Yes
<td><code class="keycap">3#</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit4">"Digit4"</code>
<td class="code-table-required">Yes
<td><code class="keycap">4$</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit5">"Digit5"</code>
<td class="code-table-required">Yes
<td><code class="keycap">5%</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit6">"Digit6"</code>
<td class="code-table-required">Yes
<td><code class="keycap">6^</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit7">"Digit7"</code>
<td class="code-table-required">Yes
<td><code class="keycap">7&</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit8">"Digit8"</code>
<td class="code-table-required">Yes
<td><code class="keycap">8*</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Digit9">"Digit9"</code>
<td class="code-table-required">Yes
<td><code class="keycap">9(</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Equal">"Equal"</code>
<td class="code-table-required">Yes
<td><code class="keycap">=+</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-IntlBackslash">"IntlBackslash"</code>
<td class="code-table-required">Yes
<td>Located between the left <code class="keycap">Shift</code> and <code class="keycap">Z</code> keys. Labelled <code class="keycap">\|</code> on a UK keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-IntlRo">"IntlRo"</code>
<td class="code-table-required">Yes
<td>Located between the <code class="keycap">/</code> and right <code class="keycap">Shift</code> keys. Labelled <code class="keycap">\ろ</code> (<span class="unicode">ro</span>) on a Japanese keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-IntlYen">"IntlYen"</code>
<td class="code-table-required">Yes
<td>Located between the <code class="keycap">=</code> and <code class="keycap">Backspace</code> keys. Labelled <code class="keycap">¥</code> (<span class="unicode">yen</span>) on a Japanese keyboard. <code class="keycap">\/</code> on a
Russian keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyA">"KeyA"</code>
<td class="code-table-required">Yes
<td><code class="keycap">a</code> on a US keyboard. Labelled <code class="keycap">q</code> on an AZERTY (e.g., French) keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyB">"KeyB"</code>
<td class="code-table-required">Yes
<td><code class="keycap">b</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyC">"KeyC"</code>
<td class="code-table-required">Yes
<td><code class="keycap">c</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyD">"KeyD"</code>
<td class="code-table-required">Yes
<td><code class="keycap">d</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyE">"KeyE"</code>
<td class="code-table-required">Yes
<td><code class="keycap">e</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyF">"KeyF"</code>
<td class="code-table-required">Yes
<td><code class="keycap">f</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyG">"KeyG"</code>
<td class="code-table-required">Yes
<td><code class="keycap">g</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyH">"KeyH"</code>
<td class="code-table-required">Yes
<td><code class="keycap">h</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyI">"KeyI"</code>
<td class="code-table-required">Yes
<td><code class="keycap">i</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyJ">"KeyJ"</code>
<td class="code-table-required">Yes
<td><code class="keycap">j</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyK">"KeyK"</code>
<td class="code-table-required">Yes
<td><code class="keycap">k</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyL">"KeyL"</code>
<td class="code-table-required">Yes
<td><code class="keycap">l</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyM">"KeyM"</code>
<td class="code-table-required">Yes
<td><code class="keycap">m</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyN">"KeyN"</code>
<td class="code-table-required">Yes
<td><code class="keycap">n</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyO">"KeyO"</code>
<td class="code-table-required">Yes
<td><code class="keycap">o</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyP">"KeyP"</code>
<td class="code-table-required">Yes
<td><code class="keycap">p</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyQ">"KeyQ"</code>
<td class="code-table-required">Yes
<td><code class="keycap">q</code> on a US keyboard. Labelled <code class="keycap">a</code> on an AZERTY (e.g., French) keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyR">"KeyR"</code>
<td class="code-table-required">Yes
<td><code class="keycap">r</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyS">"KeyS"</code>
<td class="code-table-required">Yes
<td><code class="keycap">s</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyT">"KeyT"</code>
<td class="code-table-required">Yes
<td><code class="keycap">t</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyU">"KeyU"</code>
<td class="code-table-required">Yes
<td><code class="keycap">u</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyV">"KeyV"</code>
<td class="code-table-required">Yes
<td><code class="keycap">v</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyW">"KeyW"</code>
<td class="code-table-required">Yes
<td><code class="keycap">w</code> on a US keyboard. Labelled <code class="keycap">z</code> on an AZERTY (e.g., French) keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyX">"KeyX"</code>
<td class="code-table-required">Yes
<td><code class="keycap">x</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyY">"KeyY"</code>
<td class="code-table-required">Yes
<td><code class="keycap">y</code> on a US keyboard. Labelled <code class="keycap">z</code> on a QWERTZ (e.g., German) keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-KeyZ">"KeyZ"</code>
<td class="code-table-required">Yes
<td><code class="keycap">z</code> on a US keyboard. Labelled <code class="keycap">w</code> on an AZERTY (e.g., French) keyboard, and <code class="keycap">y</code> on a
QWERTZ (e.g., German) keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Minus">"Minus"</code>
<td class="code-table-required">Yes
<td><code class="keycap">-_</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Period">"Period"</code>
<td class="code-table-required">Yes
<td><code class="keycap">.></code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Quote">"Quote"</code>
<td class="code-table-required">Yes
<td><code class="keycap">'"</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Semicolon">"Semicolon"</code>
<td class="code-table-required">Yes
<td><code class="keycap">;:</code> on a US keyboard.
<tr>
<td class="code-table-code"><code class="code" id="code-Slash">"Slash"</code>
<td class="code-table-required">Yes
<td><code class="keycap">/?</code> on a US keyboard.
</table>
<h4 class="heading settled" data-level="3.1.2" id="key-alphanumeric-functional"><span class="secno">3.1.2. </span><span class="content">Functional Keys</span><a class="self-link" href="#key-alphanumeric-functional"></a></h4>
<p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="functional-keys">functional keys</dfn> (<em>not to be confused with the <a data-link-type="dfn" href="#function-key" id="ref-for-function-key①">function keys</a> described later</em>) are those keys in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section⑨">alphanumeric section</a> that provide general editing
functions that are common to all locales (like <code class="keycap">Shift</code>, <code class="keycap">Tab</code>, <code class="keycap">Enter</code> and <code class="keycap">Backspace</code>). With a few
exceptions, these keys do not change meaning based on the
current keyboard layout.</p>
<figure id="figure-keyboard-codes-alphanum2">
<img alt="The standard set of functional keys" height="225" src="images/keyboard-codes-alphanum2.svg" width="653">
<figcaption>The standard set of <a data-link-type="dfn" href="#functional-keys" id="ref-for-functional-keys①">functional keys</a> in the <a data-link-type="dfn" href="#alphanumeric-section" id="ref-for-alphanumeric-section①⓪">alphanumeric section</a></figcaption>
</figure>
<p>The <code class="code">"<a href="#code-AltRight">AltRight</a>"</code> key (highlighted in green) is the only <a data-link-type="dfn" href="#functional-keys" id="ref-for-functional-keys②">functional key</a> that does not generate the same <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-key" id="ref-for-dom-keyboardevent-key⑤">key</a></code> value for every locale. In some locales it
produces <code class="key">"<a href="http://www.w3.org/TR/uievents-key/#key-Alt">Alt</a>"</code> while in others it produces <code class="key">"<a href="http://www.w3.org/TR/uievents-key/#key-AltGraph">AltGraph</a>"</code>.</p>
<table class="data-table full-width" id="table-key-code-alphanumeric-functional-1">
<caption>List of code values for functional keys in the Alphanumeric section.</caption>
<thead>
<tr>
<th style="width:20%"><code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#interface-keyboardevent" id="ref-for-interface-keyboardevent③">KeyboardEvent</a></code> <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/uievents/#dom-keyboardevent-code" id="ref-for-dom-keyboardevent-code①⓪">code</a></code>
<th style="width:10%">Required
<th style="width:70%">Notes (Non-normative)
<tbody>
<tr>
<td class="code-table-code"><code class="code" id="code-AltLeft">"AltLeft"</code>
<td class="code-table-required">Yes
<td><code class="keycap">Alt</code>, <code class="keycap">Option</code> or <code class="keycap">⌥</code>.
<tr>
<td class="code-table-code"><code class="code" id="code-AltRight">"AltRight"</code>
<td class="code-table-required">Yes
<td><code class="keycap">Alt</code>, <code class="keycap">Option</code> or <code class="keycap">⌥</code>. This is labelled <code class="keycap">AltGr</code> key on many keyboard layouts.
<tr>
<td class="code-table-code"><code class="code" id="code-Backspace">"Backspace"</code>