-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathindex.html
More file actions
539 lines (498 loc) · 23.1 KB
/
index.html
File metadata and controls
539 lines (498 loc) · 23.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Stacked Disclosure Pattern</title>
<link rel="stylesheet" href="css/normalize.css">
<link rel="stylesheet" href="css/local.css">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/prism/1.23.0/themes/prism.min.css" integrity="sha512-tN7Ec6zAFaVSG3TpNAKtk4DOHNpSwKHxxrsiw4GHKESGPs5njn/0sMCUMl2svV4wo4BK/rCP7juYz+zx+l6oeQ==" crossorigin="anonymous" />
<link rel="stylesheet" href="css/prism-visual-studio.css">
<script src="https://cdnjs.cloudflare.com/ajax/libs/prism/1.23.0/prism.min.js" integrity="sha512-YBk7HhgDZvBxmtOfUdvX0z8IH2d10Hp3aEygaMNhtF8fSOvBZ16D/1bXZTJV6ndk/L/DlXxYStP8jrF77v2MIg==" crossorigin="anonymous">
</script>
<link rel="stylesheet" href="dist/stacked-disclosure.css">
<script src="dist/stacked-disclosure.js"></script>
<script src="https://metageeky.github.io/screen-reader-messaging/dist/sr-messaging.js"></script>
<link rel="stylesheet" href="css/demo.css">
</head>
<body>
<div id="hiddenStuff" aria-hidden="true" hidden>
<svg aria-hidden="true" focusable="false" id="icons" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<symbol id="icon-plus" viewBox="0 0 90 90">
<g>
<line stroke-width="20" stroke="currentColor" fill="none" y2="85" y1="5" x2="45" x1="45"/>
<line stroke-width="20" stroke="currentColor" fill="none" y2="45" y1="45" x2="85" x1="5"/>
</g>
</symbol>
<symbol id="icon-minus" viewBox="0 0 90 90">
<g>
<line stroke-width="20" stroke="currentColor" fill="none" y2="45" y1="45" x2="85" x1="5"/>
</g>
</symbol>
<symbol id="icon-close-all" viewBox="0 0 200 200">
<path stroke-width="10" stroke="currentColor" fill="transparent" style="fill: var(--top-fill-color, transparent); stroke: var(--top-stroke-color, currentColor)" d="M15 15h130v130H15z"/>
<path fill="none" stroke="currentColor" stroke-width="20" style="stroke: var(--icon-color, currentColor)" d="M40 80h80"/>
<path fill="none" stroke="currentColor" stroke-width="10" style="stroke: var(--stroke-color, currentColor)" d="M50 185h140M165 30v140"/>
<path fill="none" stroke="currentColor" stroke-width="10" style="stroke: var(--stroke-color, currentColor)" d="M30 165h140M185 50v135"/>
<g fill="none" stroke="transparent" style="stroke: var(--highlight-color, transparent)" stroke-width="10" >
<path d="M40 175h140M155 20v140M20 155h140M175 40v140"/>
</g>
</symbol>
<symbol id="icon-open-all" viewBox="0 0 200 200">
<path stroke-width="10" stroke="currentColor" fill="transparent" style="fill: var(--top-fill-color, transparent); stroke: var(--top-stroke-color, currentColor)" d="M15 15h130v130H15z"/>
<path fill="none" stroke="currentColor" stroke-width="20" style="stroke: var(--icon-color, currentColor)" d="M80 40v80M40 80h80"/>
<path fill="none" stroke="currentColor" stroke-width="10" style="stroke: var(--stroke-color, currentColor)" d="M50 185h140M165 30v140"/>
<path fill="none" stroke="currentColor" stroke-width="10" style="stroke: var(--stroke-color, currentColor)" d="M30 165h140M185 50v135"/>
<g fill="none" stroke="transparent" style="stroke: var(--highlight-color, transparent)" stroke-width="10" >
<path d="M40 175h140M155 20v140M20 155h140M175 40v140"/>
</g>
</symbol>
<symbol id="icon-link" viewBox="0 0 32 32" xml:space="preserve">
<title>Pelase don't see this</title>
<g stroke="currentColor" fill="currentColor" >
<path d="M11 5v6H5v2h6v6H5v2h6v6h2v-6h6v6h2v-6h6v-2h-6v-6h6v-2h-6V5h-2v6h-6V5zm2 8h6v6h-6z"/>
</g>
</symbol>
<symbol id="icon-github" viewBox="0 0 16 16">
<path fill-rule="evenodd" d="M8 0C3.58 0 0 3.58 0 8c0 3.54 2.29 6.53 5.47 7.59.4.07.55-.17.55-.38 0-.19-.01-.82-.01-1.49-2.01.37-2.53-.49-2.69-.94-.09-.23-.48-.94-.82-1.13-.28-.15-.68-.52-.01-.53.63-.01 1.08.58 1.23.82.72 1.21 1.87.87 2.33.66.07-.52.28-.87.51-1.07-1.78-.2-3.64-.89-3.64-3.95 0-.87.31-1.59.82-2.15-.08-.2-.36-1.02.08-2.12 0 0 .67-.21 2.2.82.64-.18 1.32-.27 2-.27.68 0 1.36.09 2 .27 1.53-1.04 2.2-.82 2.2-.82.44 1.1.16 1.92.08 2.12.51.56.82 1.27.82 2.15 0 3.07-1.87 3.75-3.65 3.95.29.25.54.73.54 1.48 0 1.07-.01 1.93-.01 2.2 0 .21.15.46.55.38A8.013 8.013 0 0016 8c0-4.42-3.58-8-8-8z"></path>
</symbol>
<symbol id="icon-twitter" viewBox="0 0 48 48">
<circle cx="24" cy="24" fill="#fff" r="24"/>
<path d="M36.8 15.4c-.9.5-2 .8-3 .9 1.1-.7 1.9-1.8 2.3-3.1-1 .6-2.1 1.1-3.4 1.4-1-1.1-2.3-1.8-3.8-1.8-2.9 0-5.3 2.5-5.3 5.7 0 .4 0 .9.1 1.3-4.4-.2-8.3-2.5-10.9-5.9-.5.8-.7 1.8-.7 2.9 0 2 .9 3.7 2.3 4.7-.9 0-1.7-.3-2.4-.7v.1c0 2.7 1.8 5 4.2 5.6-.4.1-.9.2-1.4.2-.3 0-.7 0-1-.1.7 2.3 2.6 3.9 4.9 3.9-1.8 1.5-4.1 2.4-6.5 2.4-.4 0-.8 0-1.3-.1 2.3 1.6 5.1 2.6 8.1 2.6 9.7 0 15-8.6 15-16.1v-.7c1.2-1 2.1-2 2.8-3.2z" fill="#000"/>
</symbol>
</svg>
</div>
<header aria-labelledby="h1">
<a class="skipnavlink offscreen" href="#main">
Skip to main content
</a>
<h1 id="h1" class="page-centered-content">
Stacked Disclosure Pattern:
<span>An Accordion Variant</span>
</h1>
</header>
<main id="main" class="page-centered-content">
<nav id="toc" aria-labelledby="toc-h2">
<h2 id="toc-h2">
Table of Contents
</h2>
<ul>
<li>
<a href="Introduction">Introduction</a>
</li>
<li>
<a href="#Example">Example Stacked Disclosure </a>
<ul>
<li>
<a href="ExampleStack">Cat Coat Patterns (example)</a>
</li>
<li>
<a href="#HTML">HTML Structure</a>
</li>
<li>
<a href="#Configuration">Configuration Options</a>
</li>
</ul>
</li>
<li>
<a href="#Design">Design Aspects</a>
<ul>
<li>
<a href="#Specifications">Design Specifications</a>
</li>
<li>
<a href="#Accessibility">Accessibility Features</a>
</li>
</ul>
</li>
</ul>
</nav>
<section aria-labelledby="Introduction">
<h2 class="offscreen" id="Introduction">
Introduction
</h2>
<p>
The <a href="https://www.w3.org/TR/wai-aria-practices-1.1/#accordion">accordion
widget pattern</a> consists of a set of associated disclosure panels. Each panel
can be opened or closed individually with the purpose of reducing the need to
scroll through multiple sections on a page. Commonly, the accordion will
typically limit it to only ONE panel open at a time. If a panel is open and
the user opens another, the formerly open one closes. This comes off as a potential
antipattern in that the accordion can prevent the user from comparing the content
in different panels. The approach to accordions works if the panel contents are truly
independent of each other. That is rarely the case.
</p>
<p>
While some <a href="https://www.w3.org/TR/wai-aria-practices-1.1/examples/accordion/accordion.html">
accordion code examples</a> include configuration to control how many panels can be
open at a time, the accordion variation presented here is explicitly restricted.
The <strong>stacked disclosure pattern</strong> explicitly prevents this antipattern by
allowing any number of panels to be open (or closed at a time). Additionally, to support
managing the panels, the stacked disclosure requires buttons to open or close all the
panels at once.
</p>
<p>
This JavaScript library and supporting information are an
<a href="https://github.com/metageeky/stacked-disclosures">open
source project</a> on GitHub released under the
<a href="https://www.mozilla.org/en-US/MPL/2.0/">Mozilla Public License
Version 2.0</a>.
</p>
</section>
<section aria-labelledby="Example">
<div class="header-anchor">
<h2 id="Example">
Example Stacked Disclosure
</h2>
<a href="#Example">
<svg><use xlink:href="#icon-link"></use></svg>
<span>Example Stacked Disclosure Link</span>
</a>
</div>
<p>
The example below, <a href="#ExampleStack">Cat Coat Patterns</a>,
showcases the basic features of the stacked disclosure in
action. At the top of the widget is an <code><H3></code>
that names the entire widget. To the right of this heading
are the Open All and Close All button that show a tooltip
on <i>hover</i> and <i>focus</i>. The three disclosure panels
are controlled by three toggles which are buttons embedded
inside <code><H4></code> headings that also label the
toggled panels.
</p>
<div class="stacked-disclosure tooltip" id="ExampleStack" aria-labelledby="ExampleStack-heading" role="region">
<div class="stack-top">
<h3 class="stack-name" id="ExampleStack-heading">
Cat Coat Patterns
</h3>
<button class="open-all">
<span>Open All</span>
<svg focusable="false"><use xlink:href="#icon-open-all"></use></svg>
</button>
<button class="close-all">
<span>Close All</span>
<svg focusable="false"><use xlink:href="#icon-close-all"></use></svg>
</button>
</div>
<h4 class="panel-toggle" data-disclosure-expanded="true">
<button class="toggle" aria-expanded="true">
<svg focusable="false" class="plus"><use xlink:href="#icon-plus"></use></svg>
<svg focusable="false" class="minus"><use xlink:href="#icon-minus"></use></svg>
<span class="toggle-text">
Tuxedo Cats
</span>
</button>
</h4>
<div class="panel">
<p>
Tuxedo cats refer to cats whose coats are a mix of only white and black,
although there are dilute tuxedos who are gray and white. However, not
all cats with black and white coats are "proper" tuxedos. A "true" tuxedo
looks like they are in formal wear. They usually have a white belly that
extends up to the next or face while the rest is black, just like a tuxedo
shirt and coat. Quite often, they they will have more white on their face
(including mustaches) as well as the very popular white socks at the end of
their legs.
</p>
</div>
<h4 class="panel-toggle" data-disclosure-expanded="true">
<button class="toggle" aria-expanded="true">
<svg focusable="false" class="plus"><use xlink:href="#icon-plus"></use></svg>
<svg focusable="false" class="minus"><use xlink:href="#icon-minus"></use></svg>
<span class="toggle-text">
Calico Cats
</span>
</button>
</h4>
<div class="panel">
<p>
The calico cat is an amazing genetic circumstance that produces at tricolor
cat of white, orange, and either gray or black. Because some coat colorings
are sex-linked traits, it is extremely rare for a calico cat to be a male.
In such cases, a male calico usually has some genetic anomalies such as being
intersexed or having a chromosome duplication. The consequences are generally
sterility but a beautiful coat.
</p>
</div>
<h4 class="panel-toggle" data-disclosure-expanded="true">
<button class="toggle" aria-expanded="true">
<svg focusable="false" class="plus"><use xlink:href="#icon-plus"></use></svg>
<svg focusable="false" class="minus"><use xlink:href="#icon-minus"></use></svg>
<span class="toggle-text">
White Cats
</span>
</button>
</h4>
<div class="panel">
<p>
A white cat is not necessarily albino, but there is a decent chance that
the cat may have some degree of deafness. The degree of deafness is linked
to eyecolor. White cats with blue eyes have a very high chance of being deaf,
while other eye colors still have a higher chance of hearing issues compared
to other cat coat patterns and colors.
</p>
</div>
</div>
<div class="header-anchor">
<h3 id="HTML">
HTML Structure
</h3>
<a href="#HTML">
<svg><use xlink:href="#icon-link"></use></svg>
<span>HTML Structure Link</span>
</a>
</div>
<p>
The general HTML structure of any stacked disclosure follows a fixed pattern
that begins with the top matter followed by toggles and panels:
</p>
<details>
<summary>
Stacked Disclosure HTML
</summary>
<pre><code class="language-html"><div role="region" class="stacked-disclosure" aria-labelledby="ID-STACK-NAME">
<div class="stack-top">
<h3 class="stack-name" id="ID-STACK-NAME"> ... </h3>
<button class="open-all">
<span>Open All</span>
<svg focusable="false"><use xlink:href="#icon-open-all"></use></svg>
</button>
<button class="close-all">
<span>Close All</span>
<svg focusable="false"><use xlink:href="#icon-close-all"></use></svg>
</button>
</div> <!-- end stack top -->
<h4 class="panel-toggle" data-disclosure-expanded="true / false">
<button class="toggle" aria-expanded="true / false">
<svg focusable="false" class="plus"><use xlink:href="#icon-plus"></use></svg>
<svg focusable="false" class="minus"><use xlink:href="#icon-minus"></use></svg>
<div class="toggle-text"> ... </div>
</button>
</h4> <!-- end panel toggle -->
<div class="panel">
...
</div> <!-- end panel -->
<!-- repeat panel-toggle and panel -->
<div> <!-- end stacked disclosure -->
</code></pre>
</details>
<p>
Note that headings should be used in the stacked disclosure
for the <code class="language-html">.stack-name</code> and
the <code class="language-html">.panel-toggle</code> elements.
This benefits any users of assistive technologies. Note that
the headings should be properly nested. For example, if an
<code class="language-html"><h4></code> is used for
the stack's name, the panel toggles need to be
<code class="language-html"><h5></code> elements.
</p>
<p>
If you wish to use the open all, close all, plus, or minus SVG icons used
in this demo, include the following SVG code on your page. Note that this
code intentionally hides the SVG from screen readers, meaning that any use
of the icons should provide proper accessible naming of where it is used.
</p>
<details>
<summary>
SVG Icon HTML
</summary>
<pre><code class="language-html"><svg hidden aria-hidden="true" focusable="false" id="icons" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<symbol id="icon-plus" viewBox="0 0 90 90">
<g>
<line stroke-width="20" stroke="currentColor" fill="none" y2="85" y1="5" x2="45" x1="45"/>
<line stroke-width="20" stroke="currentColor" fill="none" y2="45" y1="45" x2="85" x1="5"/>
</g>
</symbol>
<symbol id="icon-minus" viewBox="0 0 90 90">
<g>
<line stroke-width="20" stroke="currentColor" fill="none" y2="45" y1="45" x2="85" x1="5"/>
</g>
</symbol>
<symbol id="icon-close-all" viewBox="0 0 200 200">
<path stroke-width="10" stroke="currentColor" fill="transparent" style="fill: var(--top-fill-color, transparent); stroke: var(--top-stroke-color, currentColor)" d="M15 15h130v130H15z"/>
<path fill="none" stroke="currentColor" stroke-width="20" style="stroke: var(--icon-color, currentColor)" d="M40 80h80"/>
<path fill="none" stroke="currentColor" stroke-width="10" style="stroke: var(--stroke-color, currentColor)" d="M50 185h140M165 30v140"/>
<path fill="none" stroke="currentColor" stroke-width="10" style="stroke: var(--stroke-color, currentColor)" d="M30 165h140M185 50v135"/>
<g fill="none" stroke="transparent" style="stroke: var(--highlight-color, transparent)" stroke-width="10" >
<path d="M40 175h140M155 20v140M20 155h140M175 40v140"/>
</g>
</symbol>
<symbol id="icon-open-all" viewBox="0 0 200 200">
<path stroke-width="10" stroke="currentColor" fill="transparent" style="fill: var(--top-fill-color, transparent); stroke: var(--top-stroke-color, currentColor)" d="M15 15h130v130H15z"/>
<path fill="none" stroke="currentColor" stroke-width="20" style="stroke: var(--icon-color, currentColor)" d="M80 40v80M40 80h80"/>
<path fill="none" stroke="currentColor" stroke-width="10" style="stroke: var(--stroke-color, currentColor)" d="M50 185h140M165 30v140"/>
<path fill="none" stroke="currentColor" stroke-width="10" style="stroke: var(--stroke-color, currentColor)" d="M30 165h140M185 50v135"/>
<g fill="none" stroke="transparent" style="stroke: var(--highlight-color, transparent)" stroke-width="10" >
<path d="M40 175h140M155 20v140M20 155h140M175 40v140"/>
</g>
</symbol>
</svg>
</code></pre>
</details>
<div class="header-anchor">
<h3 id="Configuration">
Configuration Options
</h3>
<a href="#Configuration">
<svg><use xlink:href="#icon-link"></use></svg>
<span>Configuration Options Link</span>
</a>
</div>
<p>
Two configuration options are included with the stacked disclosures. The
first is the optional display of tooltips on the open all and close all
buttons. One can turn on the tooltips by including the <code>tooltip</code>
class on the stacked disclosure outer element:
</p>
<pre><code class="language-html"><div role="region" class="stacked-disclosure tooltip" aria-labelledby="ID-STACK-NAME">
</code></pre>
<p>
The other option involves including the
<a href="https://metageeky.github.io/screen-reader-messaging/">Screen
Reader Messaging JavaScript library</a> on your page. If this library
is optionally loaded, the open all and close all buttons will inform
screen readers that the panels were successful all opened or closed.
This is arguably an accessibility improvement as these buttons
otherwise give no indication if any panels are open or closed.
</p>
</section>
<section aria-labelledby="Design">
<div class="header-anchor">
<h2 id="Design">
Design Aspects
</h2>
<a href="#Design">
<svg><use xlink:href="#icon-link"></use></svg>
<span>Design Aspects Accordion Link</span>
</a>
</div>
<div class="header-anchor">
<h3 id="Specifications">
Design Specifications
</h3>
<a href="#Specifications">
<svg><use xlink:href="#icon-link"></use></svg>
<span>Design Specifications Link</span>
</a>
</div>
<p>
The Stacked Disclosure pattern was created to meet the specific needs
of a client to ensure that all accordions performed consistently on
a site. The design request specified:
</p>
<ul>
<li>
Each accordion can have any number of panels opened or closed
at any time independent of each other.
</li>
<li>
The accordion has options to open or close all the panels at
once.
</li>
<li>
The overall accordion conforms and possibly exceeds accessibility
standards.
</li>
</ul>
<div class="header-anchor">
<h3 id="Accessibility">
Accessibility Features
</h3>
<a href="#Accessibility">
<svg><use xlink:href="#icon-link"></use></svg>
<span>Accessibility Features Link</span>
</a>
</div>
<p>
As accessibility was a key goal of the stacked disclosure pattern,
multiple design decisions were made to ensure accessibility. These
decisions were informed by the
<a href="https://www.w3.org/TR/wai-aria-practices-1.1/examples/accordion/accordion.html">
WAI-ARIA accordion example</a> but modified to meet the design
specifications and current browser capabilities.
</p>
<ul>
<li>
<p>
The entire HTML intentionally uses semantic HTML properly.
All interactive elements are
<code class="language-html"><button></code> and thus
come with the appropriate and expected built-in keyboard
functionality.
</p>
<p>
One exception to using semantic HTML was the decision to not
use the native disclosure elements
<a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details">
<code class="language-html"><details></code> and
<code class="language-html"><summary></code></a>. The
<code class="language-html"><summary></code> element cannot
contain headings despite those being a recommended practice as that leads to the
<a href="https://daverupert.com/2019/12/why-details-is-not-an-accordion/">heading
not being exposed</a> to screen readers. This is a known <a href="https://github.com/FreedomScientific/VFO-standards-support/issues/105">ongoing
access issue</a>. As accordion toggles are recommended to be headings, this is
the major reason why accordions should not rely on the
<code class="language-html"><details></code> element currently.
</p>
</li>
<li>The toggle buttons for the panels utilize
<code class="language-html">aria-expanded="true / false"</code>
to indicate to screen readers the state of each panel.
</li>
<li>
The stacked disclosure is expected to use properly nested heading
elements for the <code class="language-html">.stack-name</code> and
the <code class="language-html">.panel-toggle</code> elements
to make clear the overall structure of the disclosures.
</li>
<li>
<p>
The overall stacked disclosure is marked as being a
<code class="language-html">role="region"</code> landmark. It
is also named via <code class="language-html">aria-labelledby</code>
assigned to the <code class="language-html">.stack-name</code>.
</p>
<p>
Marking individual panels as regions was also considered but
decided against for the same reason articulated in the
<a href="https://www.w3.org/TR/wai-aria-practices-1.1/#wai-aria-roles-states-and-properties">WAI-ARIA
accordion pattern</a>: overuse of landmark regions can lead to
confusingly complex structures reported by screen readers.
</p>
</li>
<li>
The Open All and Close All buttons have appropriate accessible
names despite being represented only by icons. These names can
optionally also be provided as tooltips if so desired. Usage of
either button can also optionally provide feedback to screen
readers via an ARIA live region if an additional library is
loaded.
</li>
<li>
For progressive enhancement purposes, the disclosure panels are
set to open by default. If JavaScript is available, the panels
are closed on page load. If mutation observers are available, the
panels are closed as they are added to the DOM to prevent
page flashing.
</li>
</ul>
</section>
</main>
<footer aria-label="Additional Information">
<div class="page-centered-content">
<img id="avatar" src="https://metageeky.github.io/resources/avatar-bg.png" alt="Cartoon avatar of a bespectacled brunette geek girl in a green hoodie in front of a bookcase" />
<div>
a metageeky production
</div>
<div class="spacer"></div>
<a class="social-media" href="https://twitter.com/metageeky">
<svg><use xlink:href="#icon-twitter"></use></svg>
<span>twitter</span>
</a>
<a class="social-media" href="https://github.com/metageeky">
<svg><use xlink:href="#icon-github"></use></svg>
<span>github</span>
</a>
</div>
</footer>
</body>
</html>