8614db7a32
* feat: use legacy flag chore: reorder challenges fix: linter revert: server change feat: unblock new editor fix: proper order fix: 0-based order fix: broke the order feat: move tribute certification to its own block feat: split the old projects block into 4 fix: put all blocks in order chore: add intro text refactor: use block, not blockName in query fix: project progress indicator * fix: reorder new challenges/certs * fix: reorder legacy challenges * fix: reintroduce legacy certs * feat: add showNewCurriculum flag to env * chore: forgot sample.env * feat: use feature flag for display * fix: rename meta + dirs to match new blocks * fix: add new blocks to help-category-map * fix: update completion-modal for new GQL schema * test: duplicate title/id errors -> warnings * fix: update completion-modal to new GQL schema Mk2 * chore: re-order metas (again) * fix: revert super-block-intro changes The intro needs to show both legacy and new content. We need to decide which pages are created, rather than than what a page shows when rendered. * feat: move upcoming curriculum into own superblock * fix: handle one certification with two superBlocks * fix: remove duplicated intros * fix: remove duplicate projects from /settings * fix: drop 'two' from Responsive Web Design Two * chore: rename slug suffix from two to v2 * feat: control display of new curriculum * feat: control project paths shown on /settings * fix: use new project order for /settings This does mean that /settings will change before the release, but I don't think it's serious. All the projects are there, just not in the legacy order. * fix: claim/show cert button * chore: remove isLegacy Since we have legacy superblocks, we don't currently need individual blocks to be legacy * test: fix utils.test * fix: verifyCanClaim needs certification If Shaun removes the cert claim cards, maybe we can remove this entirely * fix: add hasEditableBoundaries flags where needed * chore: remove isUpcomingChange * chore: v2 -> 22 Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
128 lines
3.0 KiB
Markdown
128 lines
3.0 KiB
Markdown
---
|
|
id: 6143920c8eafb00b735746ce
|
|
title: Step 22
|
|
challengeType: 0
|
|
dashedName: step-22
|
|
---
|
|
|
|
# --description--
|
|
|
|
Even though you added a `placeholder` to the first `input` element in the previous lesson, this is actually not a best-practice for accessibility; too often, users confuse the placeholder text with an actual input value - they think there is already a value in the input.
|
|
|
|
Remove the placeholder text from the first `input` element, relying on the `label` being the best-practice.
|
|
|
|
# --hints--
|
|
|
|
You should remove the `placeholder` attribute from the first `input` element.
|
|
|
|
```js
|
|
assert.isEmpty(document.querySelectorAll('input')?.[0]?.placeholder);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
<meta name="description" content="freeCodeCamp Accessibility Quiz practice project" />
|
|
<title>freeCodeCamp: Accessibility Quiz</title>
|
|
<link rel="stylesheet" href="styles.css" />
|
|
</head>
|
|
<body>
|
|
<header>
|
|
<img id="logo" src="https://cdn.freecodecamp.org/platform/universal/fcc_primary.svg">
|
|
<h1>HTML/CSS Quiz</h1>
|
|
<nav>
|
|
<ul>
|
|
<li><a href="#student-info">INFO</a></li>
|
|
<li><a href="#html-questions">HTML</a></li>
|
|
<li><a href="#css-questions">CSS</a></li>
|
|
</ul>
|
|
</nav>
|
|
</header>
|
|
<main>
|
|
<form method="post" action="https://freecodecamp.org/practice-project/accessibility-quiz">
|
|
<section role="region" aria-labelledby="student-info">
|
|
<h2 id="student-info">Student Info</h2>
|
|
--fcc-editable-region--
|
|
<div class="info">
|
|
<label for="student-name">Name:</label>
|
|
<input type="text" name="student-name" id="student-name" placeholder="e.g. Quincy Larson" />
|
|
</div>
|
|
--fcc-editable-region--
|
|
<div class="info">
|
|
<label for="student-email">Email:</label>
|
|
<input type="email" name="student-email" id="student-email" />
|
|
</div>
|
|
<div class="info">
|
|
<label for="birth-date">D.O.B.:</label>
|
|
<input type="date" name="birth-date" id="birth-date" />
|
|
</div>
|
|
</section>
|
|
<section role="region" aria-labelledby="html-questions">
|
|
<h2 id="html-questions">HTML</h2>
|
|
</section>
|
|
<section role="region" aria-labelledby="css-questions">
|
|
<h2 id="css-questions">CSS</h2>
|
|
</section>
|
|
</form>
|
|
</main>
|
|
</body>
|
|
</html>
|
|
|
|
```
|
|
|
|
```css
|
|
body {
|
|
background: #f5f6f7;
|
|
color: #1b1b32;
|
|
font-family: Helvetica;
|
|
margin: 0;
|
|
}
|
|
|
|
header {
|
|
width: 100%;
|
|
height: 50px;
|
|
background-color: #1b1b32;
|
|
display: flex;
|
|
}
|
|
|
|
#logo {
|
|
width: max(100px, 18vw);
|
|
background-color: #0a0a23;
|
|
aspect-ratio: 35 / 4;
|
|
padding: 0.4rem;
|
|
}
|
|
|
|
h1 {
|
|
color: #f1be32;
|
|
font-size: min(5vw, 1.2em);
|
|
}
|
|
|
|
nav {
|
|
width: 50%;
|
|
max-width: 300px;
|
|
height: 50px;
|
|
}
|
|
|
|
nav > ul {
|
|
display: flex;
|
|
justify-content: space-evenly;
|
|
}
|
|
|
|
h1,
|
|
h2 {
|
|
font-family: Verdana, Tahoma;
|
|
}
|
|
|
|
h2 {
|
|
border-bottom: 4px solid #dfdfe2;
|
|
}
|
|
|
|
```
|