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>
51 lines
1.0 KiB
Markdown
51 lines
1.0 KiB
Markdown
---
|
|
id: 614ccc21ea91ef1736b9b578
|
|
title: Step 1
|
|
challengeType: 0
|
|
dashedName: step-1
|
|
---
|
|
|
|
# --description--
|
|
|
|
Welcome to the first part in the Accessibility Quiz. As you are becoming a seasoned HTML and CSS developer, we have started you off with the basic boilerplate.
|
|
|
|
Start this accessibility journey, by providing a `lang` attribute to your `html` element. This will assist screen readers in identifying the language of the page.
|
|
|
|
# --hints--
|
|
|
|
You should give the `html` element a `lang` attribute. _Hint: You can use the value `en` for English._
|
|
|
|
```js
|
|
assert.match(code, /<html\s+lang=('|")[\w\-]+?\1\s*>/i);
|
|
// TODO: This should/could be fixed in the builder.js
|
|
// assert.notThrow(Intl.getCanonicalLocales(document.querySelector('html').lang));
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
--fcc-editable-region--
|
|
<html>
|
|
<head>
|
|
<link rel="stylesheet" href="styles.css" />
|
|
</head>
|
|
<body>
|
|
|
|
</body>
|
|
</html>
|
|
--fcc-editable-region--
|
|
|
|
```
|
|
|
|
```css
|
|
body {
|
|
background: #f5f6f7;
|
|
color: #1b1b32;
|
|
font-family: Helvetica;
|
|
margin: 0;
|
|
}
|
|
```
|