-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathprojectdocumentation.html
More file actions
574 lines (495 loc) · 22.9 KB
/
Copy pathprojectdocumentation.html
File metadata and controls
574 lines (495 loc) · 22.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
<!DOCTYPE html>
<html lang="en">
<head>
<title> DH150 Web-coding for UX project: Redesign National Mueseum of Funeral History For Better Accessibility
</title>
<meta charset="utf-8">
<meta name="description" content="Web Coding for User Experience in Digital Humanities">
<meta name="keywords" content="HTML, CSS, JavaScript, Accessibility, SEO">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Crimson+Text&display=swap" rel="stylesheet">
</head>
<style>
body {
margin: 0;
font-family: 'Crimson Text', serif;
font-size: 1.2em;
}
header {
text-align: center;
background-color: rgb(108, 39, 39);
color: hsl(240, 0%, 85%);
padding-bottom: 2em;
width: 100vw;
}
main {
margin: 20px;
width: 90vw;
}
section {
border-bottom: 1px dotted gray;
}
button {
background-color: rgb(108, 39, 39);
color: white;
font-size: 0.85em;
line-height: 2em;
border-radius: 10px;
width: 100%;
}
button:hover {
background-color: black;
color: white;
font-size: 0.85em;
line-height: 2em;
border-radius: 10px;
width: 100%;
}
button:focus {
background-color: black;
color: white;
filter: grayscale(50%);
font-size: 0.85em;
line-height: 2em;
border-radius: 10px;
width: 100%;
}
.myButton {
position: absolute;
left: -10000px;
top: auto;
width: 1px;
height: 1px;
overflow: hidden;
background-color: black;
text-decoration: none;
color: rgb(96, 27, 27);
padding: 10px;
margin: 20px;
}
.myButton:focus {
position: static;
width: auto;
height: auto;
background-color: gray;
text-decoration: none;
color: white;
padding: 20px;
margin: 20px;
}
a:any-link {
color: black;
text-decoration: none;
}
a:focus {
text-decoration: underline;
}
a:visited {
color: rgb(165, 71, 37);
text-decoration: none;
}
a:hover {
color: goldenrod;
text-decoration: underline;
}
a:active {
color: yellow;
text-decoration: underline;
}
.imgBox {
width: 15vw;
margin: 1vw;
inline-size: 15vw;
overflow-wrap: break-word;
padding: 1vw;
background-color: lightgray;
}
#M01 {
width: 15vw;
height: 9vw;
background-image: url("./img/M01.jpg");
background-size: cover;
}
#M02 {
width: 15vw;
height: 9vw;
background-image: url("./img/M02.jpg");
background-size: cover;
}
#M03 {
width: 15vw;
height: 9vw;
background-image: url("./img/M03.jpg");
background-size: cover;
}
#M04 {
width: 15vw;
height: 9vw;
background-image: url("./img/M04.jpg");
background-size: cover;
}
#M05 {
width: 15vw;
height: 9vw;
background-image: url("./img/M05.jpg");
background-size: cover;
}
#images {
display: inline-flex;
}
.card {
display: grid;
grid-template-columns: 1fr 2fr;
width: 96vw;
gap: 10px;
}
img {
grid-row: 1;
grid-column: 1;
margin: 1vw;
padding: 1vw;
background-color: lightgray;
height: 200px;
width: 350px;
}
#colors {
grid-row: 1;
grid-column: 1;
margin: 1vw;
padding: 1vw;
height: 200px;
}
.description {
padding: 1vw;
grid-row: 1;
grid-column: 2;
}
.myNav {
list-style-type: none;
margin: 0;
padding: 0;
background-color: rgb(96, 91, 91);
width: 100vw;
height: 3em;
}
li {
display: inline;
float: left;
margin: 1px;
}
li a {
display: block;
color: black;
text-align: center;
padding: 14px 16px;
text-decoration: none;
background-color: lightgray;
}
li a:hover {
background-color: rgb(160, 115, 115);
color: white;
}
.active {
background-color: rgb(186, 155, 155);
color: white;
}
.permaLink {
color: white;
overflow: hidden;
}
.permaLink:hover {
color: black;
}
@media(min-width: 601px) and (max-width: 910px) {
li {
display: block;
margin: 1px;
width: 100vw;
}
h1 {
padding-top: 3em;
}
}
footer {
text-align: center;
background-color: rgb(160, 115, 115);
color: black;
font-size: 0.95em;
line-height: 3em;
height: 3em;
width: 100vw;
}
@media(max-width: 600px) {
img {
display: none;
}
.description {
padding: 1vw;
grid-row: 1;
grid-column: 1/3;
}
li {
display: block;
float: left;
width: 100vw;
margin: 1px;
}
h1 {
padding-top: 3em;
}
footer {
text-align: center;
background-color: rgb(108, 39, 39);
color: white;
font-size: 0.95em;
line-height: 3em;
height: 6em;
margin: 0pt;
}
}
</style>
<body>
<a href="#main" rel="bookmark" title="research main" class="myButton"> skip to contents </a>
<header>
<nav>
<ul class="myNav">
<li> <a href="#M01" rel="bookmark" title="NFMH website analysis" class="active">National Museum of
Funeral History</a>
</li>
<li> <a href="#M01" rel="bookmark" title="NFMH website analysis">Museum of Death</a>
</li>
<li> <a href="#M01" rel="bookmark" title="NFMH website analysis">International Cyptozoology Museum</a>
</li>
<li> <a href="#M01" rel="bookmark" title="NFMH website analysis">Museum of Broken Relationships</a>
</li>
<li> <a href="#M01" rel="bookmark" title="NFMH website analysis">International Banana Museum</a>
</li>
</ul>
</nav>
<!-- img src="https://source.unsplash.com/1600x900/?getty,museum" -->
<br><br>
<h1> Web-accessibility project: <br> National Funeral History Museum Research Process</h1>
<h2> DH150 2021 Summer <br> Project Documentation by Labiba Alam</h2>
<hr>
<h3> About Project </h3>
<p> The following documentation tests and improves web-accessibility of the official National Funeral History
Museum
and as shown in four markup websites.
</p>
</header>
<main id="main">
<section id="research">
<h3> <a class="permaLink" href="#research" rel="bookmark" title="research">Research</a> </h3>
<p> I started research about the museum websites and narrowed down into five museums for accessibility/seo
audit. I used a Chrome Development tool named lighthouse to diagnose the accessibility and SEO score of
those websites.<br></p>
<div id="images">
<article class="imgBox">
<p id="M01"> </p>
<p> 1) <a href="https://www.nmfh.org/" target="_blank" title="go to site"> National Museum of
Funeral
History</a>, <br>
Accessibility (95), SEO (80) </p>
</article>
<article class="imgBox">
<p id="M02"></p>
<p> 2) <a href="http://www.museumofdeath.net/" target="_blank" title="go to site"> Museum of
Death</a>, <br>
Accessibility (93), SEO (80) </p>
</article>
<article class="imgBox">
<p id="M03"> </p>
<p> 3) <a href="https://cryptozoologymuseum.com/" target="_blank" title="go to site">International
Cyptozoology Museum</a>, <br>
Accessibility (100), SEO (100) </p>
</article>
<article class="imgBox">
<p id="M04"> </p>
<p> 4) <a href="https://brokenships.com/" target="_blank" title="go to site">
Museum of Broken Relationships</a>, <br>
Accessibility (68), SEO (70) </p>
</article>
<article class="imgBox">
<p id="M05"> </p>
<p> 5) <a href="http://www.internationalbananamuseum.com/" target="_blank" title="go to site">
International Banana Museum</a>, <br>
Accessibility (93), SEO (80) </p>
</article>
</div>
<p id="analylsis">
While looking through the issues in each of the website's scores, I noticed what each museum needed
improvement on.
International Banana Museum could have improved their score if they added a < meta name="viewport"> tag
which would have optimize their website for mobile screens by announcing a meta description that
might be
included in search results to concisely summarize page content.
Museum of Broken Relationships could have
increased the contrast ratio between the background and foreground colors and addded alternate text
for screen readers.
International Crytozoology Museum Ways could have organized their heading elements in a
sequentially-descending order to make it easier for
screen readers as well as add a [lang] attribute so screen readers understand whether or not the
page is in its
default language.
Museum of Death could add labels to their form elements to ensure that the form controls are
announced properly
by screen readers and also enable zooming for people with visual impairments.
National Funeral Museum could have added descriptive link texts which would help search engines
understand their content as well
as add crawlable links to ensure that the `href` attribute of anchor elements links to an
appropriate destination, so more pages of the site can be discovered.
</p>
</section>
<section id="project">
<h3> <a class="permaLink" href="#project" rel="bookmark" title="Design Process">Project Design Process </a>
</h3>
<p> I chose to improve on the National Museum of Funeral History . One of the reasons why I chose this
particular website
is because I noticed that it was one of museums I had picked with a lower than average accessibility and
SEO scores.
I also noticed that this website had a lot of accessibility issues that I was at the time unfamiliar
with. In order to
familiarize myself with SEO and Accessibility criteria, I chose to challenge myself with this particular
website.
Here are the process as to how I improved the accessibility and SEO scores of each:</p>
<article class="card" id="semanticStructure">
<p class="dummy"> <img src="./img/sem.jpg" alt=""> </p>
<p class="description"> After running lighthouse for the National Museum of Funeral History, I noticed a
score of 74 for accessibility. After delving deeper into what was causing this issue, I noticed the
following issues affected the overall score:
- low color contrast
- nonsequential heading elements
- no [lang] attribute
- images without [alt] attributes
The original accessibility score is 74 and the original SEO score is 73. I noticed the issues were
nonsequential heading elements and the no [lang] attribute. After fixing the semantic style and
adding alt attributes to the scores' images as well as adding sequential heading elements and also
adding more descriptive text to some of the
Museum's Read More/Learn More links, the accessibility score went up to 100, and SEO score went up
to 80.
The SEO score doesn't go up as high as the accessibility score because this is a markup of the site
and
therefore it won't get as much traffic as the original. I revisted this after the graded rubric to
fix errors
I had made in the semantic structure. <br><br>
<button onclick="location.href='https://lisa58.github.io/DH150/Week2/assignment02.html'"
target="_blank">Check the outcome of semantic structure (assignment02)</button>
</p>
</article>
<article class="card" id="colorContrast">
<p class="dummy"> <img src="./img/col.jpg" alt=""> </p>
<p class="description"> For assignment03, I experimented with four different color schemes and
varying animations for this segment of the project. Version 01, the dark mode, was the best version
with a black and lime green color scheme. Initially, I did mess up setting the link colors. I had a
black
background and a black a:anylink color. I have since fixed this issue after revisting the rubric.
The accessibility
score is 96 and SEO score is 80 for this one.
For Version 02, I added an animation that slowly changed the color of the header from blue to red.
The
color used for this one was white, cyan, and a dusty rose red. Version03 had a red and yellow theme
with a
flashing yellow animation for the headers. Version04 had a translucent box that would change colors
and used the colors
red, purple, blue, and black. Versions02-04 all had accessibility scores 0f 90 and SEO scores 0f 80.
A running theme I noticed with the others was
how hard it was to accommodate for all the different colors and their contrast ratios. Whenever, I
would fix
one contrast ratio issue, I noticed that it would create another color contrast ratio issue. I
learned to keep
the color palette simple for the greatest SEO and accessibility scores.
<br><br>
<button onclick="location.href='https://lisa58.github.io/DH150/Week3/assignment03-1.html'"> Check
the outcome of the best color contrast (assignment03-01)</button>
</p>
</article>
<article class="card" id="keyboard">
<p class="dummy"> <img src="./img/key.jpg" alt=""> </p>
<p class="description">I chose to rework the first version of my css altered assignment 3 now with
invisible buttons that appear only appear by tabbing. One of the first things I fixed was the color
scheme. Originally I had shown a link color that had a very low contrast ratio with the background.
This time, I used wave.webaim.org to help me gauge whether or not the contrast ratios were high
enough. This time around, the ratios were high enough. For this assignment, there needs to be at
least 10 interactive items. I only had 8 when I started. I added another invisible bybass block that
skips to this web documentation. Then, I added interactive links to the original navigation bar that
only had text. Afterwards, I added social media icons and added links to those icons as well. Since
there are well over 10 interactive items now, I hid the navigation bar. After these additions, I ran
Lighthouse for the new accessibility and SEO score which were 91 and 70, respectively. For
accessibility, I made the heading sequential and added accessible names to the buttons to bring the
score up to 100. For SEO, I added descriptive links, a < meta name="viewport">, and a meta
description to bring the score up to 100. After bringing the automated testing scores up, I
began the manual testing by tabbing through the crawlable links and making sure the focus tab
did what I specified and made changes accordingly. I ended up adding a grayscale filter to the
links to make it more obvious visually that the tabs were being selected. I didn't make any
revisions to
this version, after revisiting the rubric. <br><br>
<button onclick="location.href='https://lisa58.github.io/DH150/Week4/assignment04.html'"> Check
the
outcome of keyboard accessibility (assignment04)</button>
</p>
</article>
<article class="card" id="ariaLabel">
<p class="dummy"> <img src="./img/aria.jpg" alt=""> </p>
<p class="description">I chose to improve assignment04 by adding a text increasing icon and a text
decreasing icon as well as a toggleable dark mode button. After following the demo and adding aria
labels. I noticed that the Accessibility score went down because of the low contrast between the
white background and the font color, So I changed the font color to a darker shade using
wave.webaim.org to help me pick a color. I also made the navigation bar visible this time. This all
improved the Accessibility Score and brought it back to 100, but SEO went down to 91 from 100
because of a robot.txt error. I didn't entirely understand this error, but after I made sure all the
links had "https://," this error was fixed, bringing the SEO score to 100 again. I did more testing
with ARC Toolkit and found no major errors. Afterwards, I used the Chrome screen reader extension
and tabbed through my website and didn't find any major errors there either since the aria-labels
were called out properly. All of this worked for me in live server.
But when I went to submit it, it stopped working. After looking at the graded rubric, however, I
fixed the buttons.<br><br>
<button onclick="location.href='https://lisa58.github.io/DH150/Week5/assignment05.html'"> Check the
outcome of aria- and screen-reader-manual testing (assignment05)</button>
</p>
</article>
<article id="reflection">
<p> I haven't taken too many Digital Humanities classes, so I only had a vague
understanding of what went into designing websites. Now I have more of an insight
into what goes into curating website usuability tests and audits. The original National
Museum of Funeral History had an accessibility score of 74 and an SEO of 73 with main issues
being not having [alt] text for images, low color contrast ratio, and nonsequential heading
elements.
After learning how many points each issue deducted from <a
href="https://web.dev/accessibility-scoring/">web.dev</a>,
I learned how important it is to have alternate text for images or at learn an empty alt attribute
to show that they are decorative images. Color contrast and nonsequential heading elements only
deduct 3 points each
while not having alt text deducts 10 points. I made sure to keep these aspects in mind while
designing
Assignment05 since points affecting accessibility also affect SEO scoring. Assignment05 and even
this
project documentation both have SEO and accessibility scores of 100. However, having perfect scores
for
automatic tests doesn't mean anything if websites fail manual testing as <a
aria-label='link to perfect accessibility and seo scores for this site' href="https://github.com/lisa58/DH150/blob/main/Week6/img/new.jpg">shown here</a>. I also went through
manual tests for both
the official site and also for this project documentation site to see if there were any major
issues. I didn't find any for either site,
but I found 27 errors for the National Museum of Funeral History, but only one error for this
project documentation on ARC Toolkit. As <a
aria-label='link to ARC Toolkit results, comparing official site with documentation site'
href="https://github.com/lisa58/DH150/blob/main/Week6/img/err.jpg">shown here</a>.
Overall, I learned a lot about website accessibility and just how important it is. I also learned
a lot about my own strengths and weaknesses when it comes to coding. I have a grasp on CSS, however, I
still find JavaScript confusing at times and that is something I need to work on.
</p>
</article>
</section>
</main>
<footer>
<p> Labiba Alam (Contact Info: <a href="mailto:labiba.alam99@gmail.com">labiba.alam99@gmail.com</a>), ©
Copyright 2021 </p>
</footer>
<script>
var myTitle = document.querySelector("title");
myTitle.innerHTML = "DH150 Web-coding for UX project: Redesign NMFH Site for Better Accessibility";
</script>
</body>
</html>