gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Feat: add new Markdown parser (#39800)

Browse Source 
and change all the challenges to new `md` format.
This commit is contained in:
Oliver Eyton-Williams
2020-11-27 19:02:05 +01:00
committed by GitHub
parent a07f84c8ec
commit 0bd52f8bd1
2580 changed files with 113436 additions and 111979 deletions
Download Patch File Download Diff File Expand all files Collapse all files

49
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/add-a-text-alternative-to-images-for-visually-impaired-accessibility.md
View File

@@ -6,53 +6,38 @@ videoUrl: 'https://scrimba.com/c/cPp7VfD'
forumTopicId: 16628
---
## Description
<section id='description'>
It's likely that you've seen an <code>alt</code> attribute on an <code>img</code> tag in other challenges. <code>Alt</code> text describes the content of the image and provides a text-alternative for it. This helps in cases where the image fails to load or can't be seen by a user. It's also used by search engines to understand what an image contains to include it in search results. Here's an example:
<code>&lt;img src=&quot;importantLogo.jpeg&quot; alt=&quot;Company logo&quot;&gt;</code>
People with visual impairments rely on screen readers to convert web content to an audio interface. They won't get information if it's only presented visually. For images, screen readers can access the <code>alt</code> attribute and read its contents to deliver key information.
Good <code>alt</code> text provides the reader a brief description of the image. You should always include an <code>alt</code> attribute on your image. Per HTML5 specification, this is now considered mandatory.
</section>
# --description--
## Instructions
<section id='instructions'>
It's likely that you've seen an `alt` attribute on an `img` tag in other challenges. `Alt` text describes the content of the image and provides a text-alternative for it. This helps in cases where the image fails to load or can't be seen by a user. It's also used by search engines to understand what an image contains to include it in search results. Here's an example:
Camper Cat happens to be both a coding ninja and an actual ninja, who is building a website to share his knowledge. The profile picture he wants to use shows his skills and should be appreciated by all site visitors. Add an <code>alt</code> attribute in the <code>img</code> tag, that explains Camper Cat is doing karate. (The image <code>src</code> doesn't link to an actual file, so you should see the <code>alt</code> text in the display.)
`<img src="importantLogo.jpeg" alt="Company logo">`
</section>
People with visual impairments rely on screen readers to convert web content to an audio interface. They won't get information if it's only presented visually. For images, screen readers can access the `alt` attribute and read its contents to deliver key information.
## Tests
<section id='tests'>
Good `alt` text provides the reader a brief description of the image. You should always include an `alt` attribute on your image. Per HTML5 specification, this is now considered mandatory.
```yml
tests:
- text: Your <code>img</code> tag should have an <code>alt</code> attribute and it should not be empty.
testString: assert($('img').attr('alt'));
# --instructions--
Camper Cat happens to be both a coding ninja and an actual ninja, who is building a website to share his knowledge. The profile picture he wants to use shows his skills and should be appreciated by all site visitors. Add an `alt` attribute in the `img` tag, that explains Camper Cat is doing karate. (The image `src` doesn't link to an actual file, so you should see the `alt` text in the display.)
# --hints--
Your `img` tag should have an `alt` attribute and it should not be empty.
```js
assert($('img').attr('alt'));
```
</section>
# --seed--
## Challenge Seed
<section id='challengeSeed'>
<div id='html-seed'>
## --seed-contents--
```html
<img src="doingKarateWow.jpeg">
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<img src="doingKarateWow.jpeg" alt="Someone doing karate">
```
</section>

70
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/add-an-accessible-date-picker.md
View File

@@ -6,11 +6,14 @@ videoUrl: 'https://scrimba.com/c/cR3bRbCV'
forumTopicId: 301008
---
## Description
<section id='description'>
Forms often include the <code>input</code> field, which can be used to create several different form controls. The <code>type</code> attribute on this element indicates what kind of input will be created.
You may have noticed the <code>text</code> and <code>submit</code> input types in prior challenges, and HTML5 introduced an option to specify a <code>date</code> field. Depending on browser support, a date picker shows up in the <code>input</code> field when it's in focus, which makes filling in a form easier for all users.
For older browsers, the type will default to <code>text</code>, so it helps to show users the expected date format in the label or as placeholder text just in case.
# --description--
Forms often include the `input` field, which can be used to create several different form controls. The `type` attribute on this element indicates what kind of input will be created.
You may have noticed the `text` and `submit` input types in prior challenges, and HTML5 introduced an option to specify a `date` field. Depending on browser support, a date picker shows up in the `input` field when it's in focus, which makes filling in a form easier for all users.
For older browsers, the type will default to `text`, so it helps to show users the expected date format in the label or as placeholder text just in case.
Here's an example:
```html
@@ -18,35 +21,39 @@ Here's an example:
<input type="date" id="input1" name="input1">
```
</section>
# --instructions--
## Instructions
<section id='instructions'>
Camper Cat is setting up a Mortal Kombat tournament and wants to ask his competitors to see what date works best. Add an <code>input</code> tag with a <code>type</code> attribute of "date", an <code>id</code> attribute of "pickdate", and a <code>name</code> attribute of "date".
</section>
Camper Cat is setting up a Mortal Kombat tournament and wants to ask his competitors to see what date works best. Add an `input` tag with a `type` attribute of "date", an `id` attribute of "pickdate", and a `name` attribute of "date".
## Tests
<section id='tests'>
# --hints--
```yml
tests:
- text: Your code should add one <code>input</code> tag for the date selector field.
testString: assert($('input').length == 2);
- text: Your <code>input</code> tag should have a <code>type</code> attribute with a value of date.
testString: assert($('input').attr('type') == 'date');
- text: Your <code>input</code> tag should have an <code>id</code> attribute with a value of pickdate.
testString: assert($('input').attr('id') == 'pickdate');
- text: Your <code>input</code> tag should have a <code>name</code> attribute with a value of date.
testString: assert($('input').attr('name') == 'date');
Your code should add one `input` tag for the date selector field.
```js
assert($('input').length == 2);
```
</section>
Your `input` tag should have a `type` attribute with a value of date.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('input').attr('type') == 'date');
```
<div id='html-seed'>
Your `input` tag should have an `id` attribute with a value of pickdate.
```js
assert($('input').attr('id') == 'pickdate');
```
Your `input` tag should have a `name` attribute with a value of date.
```js
assert($('input').attr('name') == 'date');
```
# --seed--
## --seed-contents--
```html
<body>
@@ -74,14 +81,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -102,5 +102,3 @@ tests:
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>

48
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/avoid-colorblindness-issues-by-carefully-choosing-colors-that-convey-information.md
View File

@@ -1,39 +1,36 @@
---
id: 587d778f367417b2b2512aad
title: Avoid Colorblindness Issues by Carefully Choosing Colors that Convey Information
title: >-
Avoid Colorblindness Issues by Carefully Choosing Colors that Convey
Information
challengeType: 0
videoUrl: 'https://scrimba.com/c/c437as3'
forumTopicId: 301011
---
## Description
<section id='description'>
# --description--
There are various forms of colorblindness. These can range from a reduced sensitivity to a certain wavelength of light to the inability to see color at all. The most common form is a reduced sensitivity to detect greens.
For example, if two similar green colors are the foreground and background color of your content, a colorblind user may not be able to distinguish them. Close colors can be thought of as neighbors on the color wheel, and those combinations should be avoided when conveying important information.
<strong>Note:</strong> Some online color picking tools include visual simulations of how colors appear for different types of colorblindness. These are great resources in addition to online contrast checking calculators.
</section>
## Instructions
<section id='instructions'>
Camper Cat is testing different styles for an important button, but the yellow (<code>#FFFF33</code>) <code>background-color</code> and the green (<code>#33FF33</code>) text <code>color</code> are neighboring hues on the color wheel and virtually indistinguishable for some colorblind users. (Their similar lightness also fails the contrast ratio check). Change the text <code>color</code> to a dark blue (<code>#003366</code>) to solve both problems.
</section>
**Note:** Some online color picking tools include visual simulations of how colors appear for different types of colorblindness. These are great resources in addition to online contrast checking calculators.
## Tests
<section id='tests'>
# --instructions--
```yml
tests:
- text: Your code should change the text <code>color</code> for the <code>button</code> to the dark blue.
testString: assert($('button').css('color') == 'rgb(0, 51, 102)');
Camper Cat is testing different styles for an important button, but the yellow (`#FFFF33`) `background-color` and the green (`#33FF33`) text `color` are neighboring hues on the color wheel and virtually indistinguishable for some colorblind users. (Their similar lightness also fails the contrast ratio check). Change the text `color` to a dark blue (`#003366`) to solve both problems.
# --hints--
Your code should change the text `color` for the `button` to the dark blue.
```js
assert($('button').css('color') == 'rgb(0, 51, 102)');
```
</section>
# --seed--
## Challenge Seed
<section id='challengeSeed'>
<div id='html-seed'>
## --seed-contents--
```html
<head>
@@ -54,14 +51,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<head>
@@ -81,5 +71,3 @@ tests:
<button>Delete Internet</button>
</body>
```
</section>

50
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/avoid-colorblindness-issues-by-using-sufficient-contrast.md
View File

@@ -6,37 +6,37 @@ videoUrl: 'https://scrimba.com/c/cmzMEUw'
forumTopicId: 301012
---
## Description
<section id='description'>
# --description--
Color is a large part of visual design, but its use introduces two accessibility issues. First, color alone should not be used as the only way to convey important information because screen reader users won't see it. Second, foreground and background colors need sufficient contrast so colorblind users can distinguish them.
Previous challenges covered having text alternatives to address the first issue. The last challenge introduced contrast checking tools to help with the second. The WCAG-recommended contrast ratio of 4.5:1 applies for color use as well as gray-scale combinations.
Colorblind users have trouble distinguishing some colors from others - usually in hue but sometimes lightness as well. You may recall the contrast ratio is calculated using the relative luminance (or lightness) values of the foreground and background colors.
In practice, the 4.5:1 contrast ratio can be reached by shading (adding black to) the darker color and tinting (adding white to) the lighter color. Darker shades on the color wheel are considered to be shades of blues, violets, magentas, and reds, whereas lighter tinted colors are oranges, yellows, greens, and blue-greens.
</section>
## Instructions
<section id='instructions'>
Camper Cat is experimenting with using color for his blog text and background, but his current combination of a greenish <code>background-color</code> with maroon text <code>color</code> has a 2.5:1 contrast ratio. You can easily adjust the lightness of the colors since he declared them using the CSS <code>hsl()</code> property (which stands for hue, saturation, lightness) by changing the third argument. Increase the <code>background-color</code> lightness value from 35% to 55%, and decrease the <code>color</code> lightness value from 20% to 15%. This improves the contrast to 5.9:1.
</section>
# --instructions--
## Tests
<section id='tests'>
Camper Cat is experimenting with using color for his blog text and background, but his current combination of a greenish `background-color` with maroon text `color` has a 2.5:1 contrast ratio. You can easily adjust the lightness of the colors since he declared them using the CSS `hsl()` property (which stands for hue, saturation, lightness) by changing the third argument. Increase the `background-color` lightness value from 35% to 55%, and decrease the `color` lightness value from 20% to 15%. This improves the contrast to 5.9:1.
```yml
tests:
- text: Your code should only change the lightness value for the text <code>color</code> property to a value of 15%.
testString: assert(code.match(/color:\s*?hsl\(0,\s*?55%,\s*?15%\)/gi));
- text: Your code should only change the lightness value for the <code>background-color</code> property to a value of 55%.
testString: assert(code.match(/background-color:\s*?hsl\(120,\s*?25%,\s*?55%\)/gi));
# --hints--
Your code should only change the lightness value for the text `color` property to a value of 15%.
```js
assert(code.match(/color:\s*?hsl\(0,\s*?55%,\s*?15%\)/gi));
```
</section>
Your code should only change the lightness value for the `background-color` property to a value of 55%.
## Challenge Seed
<section id='challengeSeed'>
```js
assert(code.match(/background-color:\s*?hsl\(120,\s*?25%,\s*?55%\)/gi));
```
<div id='html-seed'>
# --seed--
## --seed-contents--
```html
<head>
@@ -59,15 +59,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<head>
@@ -89,5 +81,3 @@ tests:
</article>
</body>
```
</section>

64
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/give-links-meaning-by-using-descriptive-link-text.md
View File

@@ -6,37 +6,46 @@ videoUrl: 'https://scrimba.com/c/c437DcV'
forumTopicId: 301013
---
## Description
<section id='description'>
# --description--
Screen reader users have different options for what type of content their device reads. This includes skipping to (or over) landmark elements, jumping to the main content, or getting a page summary from the headings. Another option is to only hear the links available on a page.
Screen readers do this by reading the link text, or what's between the anchor (<code>a</code>) tags. Having a list of "click here" or "read more" links isn't helpful. Instead, you should use brief but descriptive text within the <code>a</code> tags to provide more meaning for these users.
</section>
## Instructions
<section id='instructions'>
The link text that Camper Cat is using is not very descriptive without the surrounding context. Move the anchor (<code>a</code>) tags so they wrap around the text "information about batteries" instead of "Click here".
</section>
Screen readers do this by reading the link text, or what's between the anchor (`a`) tags. Having a list of "click here" or "read more" links isn't helpful. Instead, you should use brief but descriptive text within the `a` tags to provide more meaning for these users.
## Tests
<section id='tests'>
# --instructions--
```yml
tests:
- text: Your code should move the anchor <code>a</code> tags from around the words "Click here" to wrap around the words "information about batteries".
testString: assert($('a').text().match(/^(information about batteries)$/g));
- text: The <code>a</code> element should have an <code>href</code> attribute with a value of an empty string <code>""</code>.
testString: assert($('a').attr('href') === '');
- text: The <code>a</code> element should have a closing tag.
testString: assert(code.match(/<\/a>/g) && code.match(/<\/a>/g).length === code.match(/<a href=(''|"")>/g).length);
The link text that Camper Cat is using is not very descriptive without the surrounding context. Move the anchor (`a`) tags so they wrap around the text "information about batteries" instead of "Click here".
# --hints--
Your code should move the anchor `a` tags from around the words "Click here" to wrap around the words "information about batteries".
```js
assert(
$('a')
.text()
.match(/^(information about batteries)$/g)
);
```
</section>
The `a` element should have an `href` attribute with a value of an empty string `""`.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('a').attr('href') === '');
```
<div id='html-seed'>
The `a` element should have a closing tag.
```js
assert(
code.match(/<\/a>/g) &&
code.match(/<\/a>/g).length === code.match(/<a href=(''|"")>/g).length
);
```
# --seed--
## --seed-contents--
```html
<body>
@@ -50,14 +59,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -70,5 +72,3 @@ tests:
</article>
</body>
```
</section>

103
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.md
View File

@@ -6,10 +6,12 @@ videoUrl: 'https://scrimba.com/c/cVJVkcZ'
forumTopicId: 301014
---
## Description
<section id='description'>
HTML5's <code>audio</code> element gives semantic meaning when it wraps sound or audio stream content in your markup. Audio content also needs a text alternative to be accessible to people who are deaf or hard of hearing. This can be done with nearby text on the page or a link to a transcript.
The <code>audio</code> tag supports the <code>controls</code> attribute. This shows the browser default play, pause, and other controls, and supports keyboard functionality. This is a boolean attribute, meaning it doesn't need a value, its presence on the tag turns the setting on.
# --description--
HTML5's `audio` element gives semantic meaning when it wraps sound or audio stream content in your markup. Audio content also needs a text alternative to be accessible to people who are deaf or hard of hearing. This can be done with nearby text on the page or a link to a transcript.
The `audio` tag supports the `controls` attribute. This shows the browser default play, pause, and other controls, and supports keyboard functionality. This is a boolean attribute, meaning it doesn't need a value, its presence on the tag turns the setting on.
Here's an example:
```html
@@ -19,43 +21,67 @@ Here's an example:
</audio>
```
<strong>Note:</strong> Multimedia content usually has both visual and auditory components. It needs synchronized captions and a transcript so users with visual and/or auditory impairments can access it. Generally, a web developer is not responsible for creating the captions or transcript, but needs to know to include them.
</section>
**Note:** Multimedia content usually has both visual and auditory components. It needs synchronized captions and a transcript so users with visual and/or auditory impairments can access it. Generally, a web developer is not responsible for creating the captions or transcript, but needs to know to include them.
## Instructions
<section id='instructions'>
Time to take a break from Camper Cat and meet fellow camper Zersiax (@zersiax), a champion of accessibility and a screen reader user. To hear a clip of his screen reader in action, add an <code>audio</code> element after the <code>p</code>. Include the <code>controls</code> attribute. Then place a <code>source</code> tag inside the <code>audio</code> tags with the <code>src</code> attribute set to "https://s3.amazonaws.com/freecodecamp/screen-reader.mp3" and <code>type</code> attribute set to "audio/mpeg".
<strong>Note:</strong> The audio clip may sound fast and be difficult to understand, but that is a normal speed for screen reader users.
</section>
# --instructions--
## Tests
<section id='tests'>
Time to take a break from Camper Cat and meet fellow camper Zersiax (@zersiax), a champion of accessibility and a screen reader user. To hear a clip of his screen reader in action, add an `audio` element after the `p`. Include the `controls` attribute. Then place a `source` tag inside the `audio` tags with the `src` attribute set to "`https://s3.amazonaws.com/freecodecamp/screen-reader.mp3`" and `type` attribute set to "audio/mpeg".
```yml
tests:
- text: Your code should have one <code>audio</code> tag.
testString: assert($('audio').length === 1);
- text: Your <code>audio</code> element should have a closing tag.
testString: assert(code.match(/<\/audio>/g).length === 1 && code.match(/<audio.*>[\s\S]*<\/audio>/g));
- text: The <code>audio</code> tag should have the <code>controls</code> attribute.
testString: assert($('audio').attr('controls'));
- text: Your code should have one <code>source</code> tag.
testString: assert($('source').length === 1);
- text: Your <code>source</code> tag should be inside the <code>audio</code> tags.
testString: assert($('audio').children('source').length === 1);
- text: The value for the <code>src</code> attribute on the <code>source</code> tag should match the link in the instructions exactly.
testString: assert($('source').attr('src') === 'https://s3.amazonaws.com/freecodecamp/screen-reader.mp3');
- text: Your code should include a <code>type</code> attribute on the <code>source</code> tag with a value of audio/mpeg.
testString: assert($('source').attr('type') === 'audio/mpeg');
**Note:** The audio clip may sound fast and be difficult to understand, but that is a normal speed for screen reader users.
# --hints--
Your code should have one `audio` tag.
```js
assert($('audio').length === 1);
```
</section>
Your `audio` element should have a closing tag.
## Challenge Seed
<section id='challengeSeed'>
```js
assert(
code.match(/<\/audio>/g).length === 1 &&
code.match(/<audio.*>[\s\S]*<\/audio>/g)
);
```
<div id='html-seed'>
The `audio` tag should have the `controls` attribute.
```js
assert($('audio').attr('controls'));
```
Your code should have one `source` tag.
```js
assert($('source').length === 1);
```
Your `source` tag should be inside the `audio` tags.
```js
assert($('audio').children('source').length === 1);
```
The value for the `src` attribute on the `source` tag should match the link in the instructions exactly.
```js
assert(
$('source').attr('src') ===
'https://s3.amazonaws.com/freecodecamp/screen-reader.mp3'
);
```
Your code should include a `type` attribute on the `source` tag with a value of audio/mpeg.
```js
assert($('source').attr('type') === 'audio/mpeg');
```
# --seed--
## --seed-contents--
```html
<body>
@@ -71,14 +97,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -93,5 +112,3 @@ tests:
</main>
</body>
```
</section>

86
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-chart-accessibility-with-the-figure-element.md
View File

@@ -6,11 +6,13 @@ videoUrl: 'https://scrimba.com/c/cGJMqtE'
forumTopicId: 301015
---
## Description
<section id='description'>
HTML5 introduced the <code>figure</code> element, along with the related <code>figcaption</code>. Used together, these items wrap a visual representation (like an image, diagram, or chart) along with its caption. This gives a two-fold accessibility boost by both semantically grouping related content, and providing a text alternative that explains the <code>figure</code>.
# --description--
HTML5 introduced the `figure` element, along with the related `figcaption`. Used together, these items wrap a visual representation (like an image, diagram, or chart) along with its caption. This gives a two-fold accessibility boost by both semantically grouping related content, and providing a text alternative that explains the `figure`.
For data visualizations like charts, the caption can be used to briefly note the trends or conclusions for users with visual impairments. Another challenge covers how to move a table version of the chart's data off-screen (using CSS) for screen reader users.
Here's an example - note that the <code>figcaption</code> goes inside the <code>figure</code> tags and can be combined with other elements:
Here's an example - note that the `figcaption` goes inside the `figure` tags and can be combined with other elements:
```html
<figure>
@@ -22,39 +24,54 @@ Here's an example - note that the <code>figcaption</code> goes inside the <code>
</figure>
```
</section>
# --instructions--
## Instructions
<section id='instructions'>
Camper Cat is hard at work creating a stacked bar chart showing the amount of time per week to spend training in stealth, combat, and weapons. Help him structure his page better by changing the <code>div</code> tag he used to a <code>figure</code> tag, and the <code>p</code> tag that surrounds the caption to a <code>figcaption</code> tag.
</section>
Camper Cat is hard at work creating a stacked bar chart showing the amount of time per week to spend training in stealth, combat, and weapons. Help him structure his page better by changing the `div` tag he used to a `figure` tag, and the `p` tag that surrounds the caption to a `figcaption` tag.
## Tests
<section id='tests'>
# --hints--
```yml
tests:
- text: Your code should have one <code>figure</code> tag.
testString: assert($('figure').length == 1);
- text: Your code should have one <code>figcaption</code> tag.
testString: assert($('figcaption').length == 1);
- text: Your code should not have any <code>div</code> tags.
testString: assert($('div').length == 0);
- text: Your code should not have any <code>p</code> tags.
testString: assert($('p').length == 0);
- text: The <code>figcaption</code> should be a child of the <code>figure</code> tag.
testString: assert($('figure').children('figcaption').length == 1);
- text: Your <code>figure</code> element should have a closing tag.
testString: assert(code.match(/<\/figure>/g) && code.match(/<\/figure>/g).length === code.match(/<figure>/g).length);
Your code should have one `figure` tag.
```js
assert($('figure').length == 1);
```
</section>
Your code should have one `figcaption` tag.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('figcaption').length == 1);
```
<div id='html-seed'>
Your code should not have any `div` tags.
```js
assert($('div').length == 0);
```
Your code should not have any `p` tags.
```js
assert($('p').length == 0);
```
The `figcaption` should be a child of the `figure` tag.
```js
assert($('figure').children('figcaption').length == 1);
```
Your `figure` element should have a closing tag.
```js
assert(
code.match(/<\/figure>/g) &&
code.match(/<\/figure>/g).length === code.match(/<figure>/g).length
);
```
# --seed--
## --seed-contents--
```html
<body>
@@ -100,14 +117,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -148,5 +158,3 @@ tests:
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>

54
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-form-field-accessibility-with-the-label-element.md
View File

@@ -6,12 +6,15 @@ videoUrl: 'https://scrimba.com/c/cGJMMAN'
forumTopicId: 301016
---
## Description
<section id='description'>
# --description--
Improving accessibility with semantic HTML markup applies to using both appropriate tag names as well as attributes. The next several challenges cover some important scenarios using attributes in forms.
The <code>label</code> tag wraps the text for a specific form control item, usually the name or label for a choice. This ties meaning to the item and makes the form more readable. The <code>for</code> attribute on a <code>label</code> tag explicitly associates that <code>label</code> with the form control and is used by screen readers.
You learned about radio buttons and their labels in a lesson in the Basic HTML section. In that lesson, we wrapped the radio button input element inside a <code>label</code> element along with the label text in order to make the text clickable. Another way to achieve this is by using the <code>for</code> attribute as explained in this lesson.
The value of the <code>for</code> attribute must be the same as the value of the <code>id</code> attribute of the form control. Here's an example:
The `label` tag wraps the text for a specific form control item, usually the name or label for a choice. This ties meaning to the item and makes the form more readable. The `for` attribute on a `label` tag explicitly associates that `label` with the form control and is used by screen readers.
You learned about radio buttons and their labels in a lesson in the Basic HTML section. In that lesson, we wrapped the radio button input element inside a `label` element along with the label text in order to make the text clickable. Another way to achieve this is by using the `for` attribute as explained in this lesson.
The value of the `for` attribute must be the same as the value of the `id` attribute of the form control. Here's an example:
```html
<form>
@@ -20,31 +23,27 @@ The value of the <code>for</code> attribute must be the same as the value of the
</form>
```
</section>
# --instructions--
## Instructions
<section id='instructions'>
Camper Cat expects a lot of interest in his thoughtful blog posts and wants to include an email sign up form. Add a <code>for</code> attribute on the email <code>label</code> that matches the <code>id</code> on its <code>input</code> field.
</section>
Camper Cat expects a lot of interest in his thoughtful blog posts and wants to include an email sign up form. Add a `for` attribute on the email `label` that matches the `id` on its `input` field.
## Tests
<section id='tests'>
# --hints--
```yml
tests:
- text: Your code should have a <code>for</code> attribute on the <code>label</code> tag that is not empty.
testString: assert($('label').attr('for'));
- text: Your <code>for</code> attribute value should match the <code>id</code> value on the email <code>input</code>.
testString: assert($('label').attr('for') == 'email');
Your code should have a `for` attribute on the `label` tag that is not empty.
```js
assert($('label').attr('for'));
```
</section>
Your `for` attribute value should match the `id` value on the email `input`.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('label').attr('for') == 'email');
```
<div id='html-seed'>
# --seed--
## --seed-contents--
```html
<body>
@@ -81,14 +80,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -124,5 +116,3 @@ tests:
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>

47
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-readability-with-high-contrast-text.md
View File

@@ -6,35 +6,33 @@ videoUrl: 'https://scrimba.com/c/cKb3nCq'
forumTopicId: 301017
---
## Description
<section id='description'>
# --description--
Low contrast between the foreground and background colors can make text difficult to read. Sufficient contrast improves the readability of your content, but what exactly does "sufficient" mean?
The Web Content Accessibility Guidelines (WCAG) recommend at least a 4.5 to 1 contrast ratio for normal text. The ratio is calculated by comparing the relative luminance values of two colors. This ranges from 1:1 for the same color, or no contrast, to 21:1 for white against black, the strongest contrast. There are many contrast checking tools available online that calculate this ratio for you.
</section>
## Instructions
<section id='instructions'>
Camper Cat's choice of light gray text on a white background for his recent blog post has a 1.5:1 contrast ratio, making it hard to read. Change the <code>color</code> of the text from the current gray (<code>#D3D3D3</code>) to a darker gray (<code>#636363</code>) to improve the contrast ratio to 6:1.
</section>
# --instructions--
## Tests
<section id='tests'>
Camper Cat's choice of light gray text on a white background for his recent blog post has a 1.5:1 contrast ratio, making it hard to read. Change the `color` of the text from the current gray (`#D3D3D3`) to a darker gray (`#636363`) to improve the contrast ratio to 6:1.
```yml
tests:
- text: Your code should change the text <code>color</code> for the <code>body</code> to the darker gray.
testString: assert($('body').css('color') == 'rgb(99, 99, 99)');
- text: Your code should not change the <code>background-color</code> for the <code>body</code>.
testString: assert($('body').css('background-color') == 'rgb(255, 255, 255)');
# --hints--
Your code should change the text `color` for the `body` to the darker gray.
```js
assert($('body').css('color') == 'rgb(99, 99, 99)');
```
</section>
Your code should not change the `background-color` for the `body`.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('body').css('background-color') == 'rgb(255, 255, 255)');
```
<div id='html-seed'>
# --seed--
## --seed-contents--
```html
<head>
@@ -57,14 +55,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<head>
@@ -86,5 +77,3 @@ tests:
</article>
</body>
```
</section>

57
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/jump-straight-to-the-content-using-the-main-element.md
View File

@@ -6,37 +6,37 @@ videoUrl: 'https://scrimba.com/c/cPp7zuE'
forumTopicId: 301018
---
## Description
<section id='description'>
HTML5 introduced a number of new elements that give developers more options while also incorporating accessibility features. These tags include <code>main</code>, <code>header</code>, <code>footer</code>, <code>nav</code>, <code>article</code>, and <code>section</code>, among others.
By default, a browser renders these elements similarly to the humble <code>div</code>. However, using them where appropriate gives additional meaning in your markup. The tag name alone can indicate the type of information it contains, which adds semantic meaning to that content. Assistive technologies can access this information to provide better page summary or navigation options to their users.
The <code>main</code> element is used to wrap (you guessed it) the main content, and there should be only one per page. It's meant to surround the information that's related to the central topic of your page. It's not meant to include items that repeat across pages, like navigation links or banners.
The <code>main</code> tag also has an embedded landmark feature that assistive technology can use to quickly navigate to the main content. If you've ever seen a "Jump to Main Content" link at the top of a page, using a main tag automatically gives assistive devices that functionality.
</section>
# --description--
## Instructions
<section id='instructions'>
Camper Cat has some big ideas for his ninja weapons page. Help him set up his markup by adding opening and closing <code>main</code> tags between the <code>header</code> and <code>footer</code> (covered in other challenges). Keep the <code>main</code> tags empty for now.
</section>
HTML5 introduced a number of new elements that give developers more options while also incorporating accessibility features. These tags include `main`, `header`, `footer`, `nav`, `article`, and `section`, among others.
## Tests
<section id='tests'>
By default, a browser renders these elements similarly to the humble `div`. However, using them where appropriate gives additional meaning in your markup. The tag name alone can indicate the type of information it contains, which adds semantic meaning to that content. Assistive technologies can access this information to provide better page summary or navigation options to their users.
```yml
tests:
- text: Your code should have one <code>main</code> tag.
testString: assert($('main').length == 1);
- text: The <code>main</code> tags should be between the closing <code>header</code> tag and the opening <code>footer</code> tag.
testString: assert(code.match(/<\/header>\s*?<main>\s*?<\/main>/gi));
The `main` element is used to wrap (you guessed it) the main content, and there should be only one per page. It's meant to surround the information that's related to the central topic of your page. It's not meant to include items that repeat across pages, like navigation links or banners.
The `main` tag also has an embedded landmark feature that assistive technology can use to quickly navigate to the main content. If you've ever seen a "Jump to Main Content" link at the top of a page, using a main tag automatically gives assistive devices that functionality.
# --instructions--
Camper Cat has some big ideas for his ninja weapons page. Help him set up his markup by adding opening and closing `main` tags between the `header` and `footer` (covered in other challenges). Keep the `main` tags empty for now.
# --hints--
Your code should have one `main` tag.
```js
assert($('main').length == 1);
```
</section>
The `main` tags should be between the closing `header` tag and the opening `footer` tag.
## Challenge Seed
<section id='challengeSeed'>
```js
assert(code.match(/<\/header>\s*?<main>\s*?<\/main>/gi));
```
<div id='html-seed'>
# --seed--
## --seed-contents--
```html
<header>
@@ -48,14 +48,7 @@ tests:
<footer></footer>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<header>
@@ -66,5 +59,3 @@ tests:
</main>
<footer></footer>
```
</section>

58
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/know-when-alt-text-should-be-left-blank.md
View File

@@ -6,38 +6,39 @@ videoUrl: 'https://scrimba.com/c/cM9P4t2'
forumTopicId: 301019
---
## Description
<section id='description'>
In the last challenge, you learned that including an <code>alt</code> attribute when using <code>img</code> tags is mandatory. However, sometimes images are grouped with a caption already describing them, or are used for decoration only. In these cases <code>alt</code> text may seem redundant or unnecessary.
In situations when an image is already explained with text content, or does not add meaning to a page, the <code>img</code> still needs an <code>alt</code> attribute, but it can be set to an empty string. Here's an example:
<code>&lt;img src=&quot;visualDecoration.jpeg&quot; alt=&quot;&quot;&gt;</code>
# --description--
In the last challenge, you learned that including an `alt` attribute when using `img` tags is mandatory. However, sometimes images are grouped with a caption already describing them, or are used for decoration only. In these cases `alt` text may seem redundant or unnecessary.
In situations when an image is already explained with text content, or does not add meaning to a page, the `img` still needs an `alt` attribute, but it can be set to an empty string. Here's an example:
`<img src="visualDecoration.jpeg" alt="">`
Background images usually fall under the 'decorative' label as well. However, they are typically applied with CSS rules, and therefore not part of the markup screen readers process.
<strong>Note:</strong> For images with a caption, you may still want to include <code>alt</code> text, since it helps search engines catalog the content of the image.
</section>
## Instructions
<section id='instructions'>
Camper Cat has coded a skeleton page for the blog part of his website. He's planning to add a visual break between his two articles with a decorative image of a samurai sword. Add an <code>alt</code> attribute to the <code>img</code> tag and set it to an empty string. (Note that the image <code>src</code> doesn't link to an actual file - don't worry that there are no swords showing in the display.)
</section>
**Note:** For images with a caption, you may still want to include `alt` text, since it helps search engines catalog the content of the image.
## Tests
<section id='tests'>
# --instructions--
```yml
tests:
- text: Your <code>img</code> tag should have an <code>alt</code> attribute.
testString: assert(!($('img').attr('alt') == undefined));
- text: The <code>alt</code> attribute should be set to an empty string.
testString: assert($('img').attr('alt') == '');
Camper Cat has coded a skeleton page for the blog part of his website. He's planning to add a visual break between his two articles with a decorative image of a samurai sword. Add an `alt` attribute to the `img` tag and set it to an empty string. (Note that the image `src` doesn't link to an actual file - don't worry that there are no swords showing in the display.)
# --hints--
Your `img` tag should have an `alt` attribute.
```js
assert(!($('img').attr('alt') == undefined));
```
</section>
The `alt` attribute should be set to an empty string.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('img').attr('alt') == '');
```
<div id='html-seed'>
# --seed--
## --seed-contents--
```html
<h1>Deep Thoughts with Master Camper Cat</h1>
@@ -54,14 +55,7 @@ tests:
</article>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<h1>Deep Thoughts with Master Camper Cat</h1>
@@ -77,5 +71,3 @@ tests:
<p>To Come...</p>
</article>
```
</section>

67
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-elements-only-visible-to-a-screen-reader-by-using-custom-css.md
View File

@@ -6,10 +6,12 @@ videoUrl: 'https://scrimba.com/c/cJ8QGkhJ'
forumTopicId: 301020
---
## Description
<section id='description'>
# --description--
Have you noticed that all of the applied accessibility challenges so far haven't used any CSS? This is to show the importance of a logical document outline, and using semantically meaningful tags around your content before introducing the visual design aspect.
However, CSS's magic can also improve accessibility on your page when you want to visually hide content meant only for screen readers. This happens when information is in a visual format (like a chart), but screen reader users need an alternative presentation (like a table) to access the data. CSS is used to position the screen reader-only elements off the visual area of the browser window.
Here's an example of the CSS rules that accomplish this:
```css
@@ -23,40 +25,46 @@ Here's an example of the CSS rules that accomplish this:
}
```
<strong>Note:</strong> The following CSS approaches will NOT do the same thing:
**Note:** The following CSS approaches will NOT do the same thing:
<ul>
<li><code>display: none;</code> or <code>visibility: hidden;</code> hides content for everyone, including screen reader users</li>
<li>Zero values for pixel sizes, such as <code>width: 0px; height: 0px;</code> removes that element from the flow of your document, meaning screen readers will ignore it</li>
</ul>
</section>
## Instructions
<section id='instructions'>
Camper Cat created a really cool stacked bar chart for his training page, and put the data into a table for his visually impaired users. The table already has an <code>sr-only</code> class, but the CSS rules aren't filled in yet. Give the <code>position</code> an absolute value, the <code>left</code> a -10000px value, and the <code>width</code> and <code>height</code> both 1px values.
</section>
# --instructions--
## Tests
<section id='tests'>
Camper Cat created a really cool stacked bar chart for his training page, and put the data into a table for his visually impaired users. The table already has an `sr-only` class, but the CSS rules aren't filled in yet. Give the `position` an absolute value, the `left` a -10000px value, and the `width` and `height` both 1px values.
```yml
tests:
- text: Your code should set the <code>position</code> property of the <code>sr-only</code> class to a value of absolute.
testString: assert($('.sr-only').css('position') == 'absolute');
- text: Your code should set the <code>left</code> property of the <code>sr-only</code> class to a value of -10000px.
testString: assert($('.sr-only').css('left') == '-10000px');
- text: Your code should set the <code>width</code> property of the <code>sr-only</code> class to a value of 1 pixel.
testString: assert(code.match(/width:\s*?1px/gi));
- text: Your code should set the <code>height</code> property of the <code>sr-only</code> class to a value of 1 pixel.
testString: assert(code.match(/height:\s*?1px/gi));
# --hints--
Your code should set the `position` property of the `sr-only` class to a value of absolute.
```js
assert($('.sr-only').css('position') == 'absolute');
```
</section>
Your code should set the `left` property of the `sr-only` class to a value of -10000px.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('.sr-only').css('left') == '-10000px');
```
<div id='html-seed'>
Your code should set the `width` property of the `sr-only` class to a value of 1 pixel.
```js
assert(code.match(/width:\s*?1px/gi));
```
Your code should set the `height` property of the `sr-only` class to a value of 1 pixel.
```js
assert(code.match(/height:\s*?1px/gi));
```
# --seed--
## --seed-contents--
```html
<head>
@@ -145,14 +153,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<head>
@@ -240,5 +241,3 @@ tests:
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>

69
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-links-navigable-with-html-access-keys.md
View File

@@ -6,41 +6,49 @@ videoUrl: 'https://scrimba.com/c/cQvmaTp'
forumTopicId: 301021
---
## Description
<section id='description'>
HTML offers the <code>accesskey</code> attribute to specify a shortcut key to activate or bring focus to an element. This can make navigation more efficient for keyboard-only users.
# --description--
HTML offers the `accesskey` attribute to specify a shortcut key to activate or bring focus to an element. This can make navigation more efficient for keyboard-only users.
HTML5 allows this attribute to be used on any element, but it's particularly useful when it's used with interactive ones. This includes links, buttons, and form controls.
Here's an example:
<code>&lt;button accesskey=&quot;b&quot;&gt;Important Button&lt;/button&gt;</code>
</section>
## Instructions
<section id='instructions'>
Camper Cat wants the links around the two blog article titles to have keyboard shortcuts so his site's users can quickly navigate to the full story. Add an <code>accesskey</code> attribute to both links and set the first one to "g" (for Garfield) and the second one to "c" (for Chuck Norris).
</section>
`<button accesskey="b">Important Button</button>`
## Tests
<section id='tests'>
# --instructions--
```yml
tests:
- text: Your code should add an <code>accesskey</code> attribute to the <code>a</code> tag with the <code>id</code> of "first".
testString: assert($('#first').attr('accesskey'));
- text: Your code should add an <code>accesskey</code> attribute to the <code>a</code> tag with the <code>id</code> of "second".
testString: assert($('#second').attr('accesskey'));
- text: Your code should set the <code>accesskey</code> attribute on the <code>a</code> tag with the <code>id</code> of "first" to "g". Note that case matters.
testString: assert($('#first').attr('accesskey') == 'g');
- text: Your code should set the <code>accesskey</code> attribute on the <code>a</code> tag with the <code>id</code> of "second" to "c". Note that case matters.
testString: assert($('#second').attr('accesskey') == 'c');
Camper Cat wants the links around the two blog article titles to have keyboard shortcuts so his site's users can quickly navigate to the full story. Add an `accesskey` attribute to both links and set the first one to "g" (for Garfield) and the second one to "c" (for Chuck Norris).
# --hints--
Your code should add an `accesskey` attribute to the `a` tag with the `id` of "first".
```js
assert($('#first').attr('accesskey'));
```
</section>
Your code should add an `accesskey` attribute to the `a` tag with the `id` of "second".
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('#second').attr('accesskey'));
```
<div id='html-seed'>
Your code should set the `accesskey` attribute on the `a` tag with the `id` of "first" to "g". Note that case matters.
```js
assert($('#first').attr('accesskey') == 'g');
```
Your code should set the `accesskey` attribute on the `a` tag with the `id` of "second" to "c". Note that case matters.
```js
assert($('#second').attr('accesskey') == 'c');
```
# --seed--
## --seed-contents--
```html
<body>
@@ -67,14 +75,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -100,5 +101,3 @@ tests:
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>

56
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-screen-reader-navigation-easier-with-the-footer-landmark.md
View File

@@ -6,36 +6,37 @@ videoUrl: 'https://scrimba.com/c/crVrDh8'
forumTopicId: 301022
---
## Description
<section id='description'>
Similar to <code>header</code> and <code>nav</code>, the <code>footer</code> element has a built-in landmark feature that allows assistive devices to quickly navigate to it. It's primarily used to contain copyright information or links to related documents that usually sit at the bottom of a page.
</section>
# --description--
## Instructions
<section id='instructions'>
Camper Cat's training page is making good progress. Change the <code>div</code> he used to wrap his copyright information at the bottom of the page to a <code>footer</code> element.
</section>
Similar to `header` and `nav`, the `footer` element has a built-in landmark feature that allows assistive devices to quickly navigate to it. It's primarily used to contain copyright information or links to related documents that usually sit at the bottom of a page.
## Tests
<section id='tests'>
# --instructions--
```yml
tests:
- text: Your code should have one <code>footer</code> tag.
testString: assert($('footer').length == 1);
- text: Your code should not have any <code>div</code> tags.
testString: assert($('div').length == 0);
- text: Your code should have an opening and closing <code>footer</code> tag.
testString: assert(code.match(/<footer>\s*&copy; 2018 Camper Cat\s*<\/footer>/g));
Camper Cat's training page is making good progress. Change the `div` he used to wrap his copyright information at the bottom of the page to a `footer` element.
# --hints--
Your code should have one `footer` tag.
```js
assert($('footer').length == 1);
```
</section>
Your code should not have any `div` tags.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('div').length == 0);
```
<div id='html-seed'>
Your code should have an opening and closing `footer` tag.
```js
assert(code.match(/<footer>\s*&copy; 2018 Camper Cat\s*<\/footer>/g));
```
# --seed--
## --seed-contents--
```html
<body>
@@ -74,14 +75,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -119,5 +113,3 @@ tests:
</body>
```
</section>

73
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-screen-reader-navigation-easier-with-the-header-landmark.md
View File

@@ -6,40 +6,50 @@ videoUrl: 'https://scrimba.com/c/cB76vtv'
forumTopicId: 301023
---
## Description
<section id='description'>
The next HTML5 element that adds semantic meaning and improves accessibility is the <code>header</code> tag. It's used to wrap introductory information or navigation links for its parent tag and works well around content that's repeated at the top on multiple pages.
<code>header</code> shares the embedded landmark feature you saw with <code>main</code>, allowing assistive technologies to quickly navigate to that content.
<strong>Note:</strong> The <code>header</code> is meant for use in the <code>body</code> tag of your HTML document. This is different than the <code>head</code> element, which contains the page's title, meta information, etc.
</section>
# --description--
## Instructions
<section id='instructions'>
Camper Cat is writing some great articles about ninja training, and wants to add a page for them to his site. Change the top <code>div</code> that currently contains the <code>h1</code> to a <code>header</code> tag instead.
</section>
The next HTML5 element that adds semantic meaning and improves accessibility is the `header` tag. It's used to wrap introductory information or navigation links for its parent tag and works well around content that's repeated at the top on multiple pages.
## Tests
<section id='tests'>
`header` shares the embedded landmark feature you saw with `main`, allowing assistive technologies to quickly navigate to that content.
```yml
tests:
- text: Your code should have one <code>header</code> tag.
testString: assert($('header').length == 1);
- text: Your <code>header</code> tags should wrap around the <code>h1</code>.
testString: assert($('header').children('h1').length == 1);
- text: Your code should not have any <code>div</code> tags.
testString: assert($('div').length == 0);
- text: Your <code>header</code> element should have a closing tag.
testString: assert(code.match(/<\/header>/g) && code.match(/<\/header>/g).length === code.match(/<header>/g).length);
**Note:** The `header` is meant for use in the `body` tag of your HTML document. This is different than the `head` element, which contains the page's title, meta information, etc.
# --instructions--
Camper Cat is writing some great articles about ninja training, and wants to add a page for them to his site. Change the top `div` that currently contains the `h1` to a `header` tag instead.
# --hints--
Your code should have one `header` tag.
```js
assert($('header').length == 1);
```
</section>
Your `header` tags should wrap around the `h1`.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('header').children('h1').length == 1);
```
<div id='html-seed'>
Your code should not have any `div` tags.
```js
assert($('div').length == 0);
```
Your `header` element should have a closing tag.
```js
assert(
code.match(/<\/header>/g) &&
code.match(/<\/header>/g).length === code.match(/<header>/g).length
);
```
# --seed--
## --seed-contents--
```html
<body>
@@ -69,14 +79,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -105,5 +108,3 @@ tests:
</main>
</body>
```
</section>

70
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-screen-reader-navigation-easier-with-the-nav-landmark.md
View File

@@ -6,39 +6,48 @@ videoUrl: 'https://scrimba.com/c/czVwWSv'
forumTopicId: 301024
---
## Description
<section id='description'>
The <code>nav</code> element is another HTML5 item with the embedded landmark feature for easy screen reader navigation. This tag is meant to wrap around the main navigation links in your page.
If there are repeated site links at the bottom of the page, it isn't necessary to markup those with a <code>nav</code> tag as well. Using a <code>footer</code> (covered in the next challenge) is sufficient.
</section>
# --description--
## Instructions
<section id='instructions'>
Camper Cat included navigation links at the top of his training page, but wrapped them in a <code>div</code>. Change the <code>div</code> to a <code>nav</code> tag to improve the accessibility on his page.
</section>
The `nav` element is another HTML5 item with the embedded landmark feature for easy screen reader navigation. This tag is meant to wrap around the main navigation links in your page.
## Tests
<section id='tests'>
If there are repeated site links at the bottom of the page, it isn't necessary to markup those with a `nav` tag as well. Using a `footer` (covered in the next challenge) is sufficient.
```yml
tests:
- text: Your code should have one <code>nav</code> tag.
testString: assert($('nav').length == 1);
- text: Your <code>nav</code> tags should wrap around the <code>ul</code> and its list items.
testString: assert($('nav').children('ul').length == 1);
- text: Your code should not have any <code>div</code> tags.
testString: assert($('div').length == 0);
- text: Your <code>nav</code> element should have a closing tag.
testString: assert(code.match(/<\/nav>/g) && code.match(/<\/nav>/g).length === code.match(/<nav>/g).length);
# --instructions--
Camper Cat included navigation links at the top of his training page, but wrapped them in a `div`. Change the `div` to a `nav` tag to improve the accessibility on his page.
# --hints--
Your code should have one `nav` tag.
```js
assert($('nav').length == 1);
```
</section>
Your `nav` tags should wrap around the `ul` and its list items.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('nav').children('ul').length == 1);
```
<div id='html-seed'>
Your code should not have any `div` tags.
```js
assert($('div').length == 0);
```
Your `nav` element should have a closing tag.
```js
assert(
code.match(/<\/nav>/g) &&
code.match(/<\/nav>/g).length === code.match(/<nav>/g).length
);
```
# --seed--
## --seed-contents--
```html
<body>
@@ -74,14 +83,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -116,5 +118,3 @@ tests:
</main>
</body>
```
</section>

94
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/standardize-times-with-the-html5-datetime-attribute.md
View File

@@ -6,39 +6,61 @@ videoUrl: 'https://scrimba.com/c/cmzMgtz'
forumTopicId: 301025
---
## Description
<section id='description'>
Continuing with the date theme, HTML5 also introduced the <code>time</code> element along with a <code>datetime</code> attribute to standardize times. This is an inline element that can wrap a date or time on a page. A valid format of that date is held by the <code>datetime</code> attribute. This is the value accessed by assistive devices. It helps avoid confusion by stating a standardized version of a time, even if it's written in an informal or colloquial manner in the text.
# --description--
Continuing with the date theme, HTML5 also introduced the `time` element along with a `datetime` attribute to standardize times. This is an inline element that can wrap a date or time on a page. A valid format of that date is held by the `datetime` attribute. This is the value accessed by assistive devices. It helps avoid confusion by stating a standardized version of a time, even if it's written in an informal or colloquial manner in the text.
Here's an example:
<code>&lt;p&gt;Master Camper Cat officiated the cage match between Goro and Scorpion &lt;time datetime=&quot;2013-02-13&quot;&gt;last Wednesday&lt;/time&gt;, which ended in a draw.&lt;/p&gt;</code>
</section>
## Instructions
<section id='instructions'>
Camper Cat's Mortal Kombat survey results are in! Wrap a <code>time</code> tag around the text "Thursday, September 15&lt;sup&gt;th&lt;/sup&gt;" and add a <code>datetime</code> attribute to it set to "2016-09-15".
</section>
`<p>Master Camper Cat officiated the cage match between Goro and Scorpion <time datetime="2013-02-13">last Wednesday</time>, which ended in a draw.</p>`
## Tests
<section id='tests'>
# --instructions--
```yml
tests:
- text: Your code should have a <code>p</code> element which includes the text <code>Thank you to everyone for responding to Master Camper Cat's survey.</code> and include a <code>time</code> element.
testString: assert(timeElement.length);
- text: Your added <code>time</code> tags should wrap around the text <code>Thursday, September 15&lt;sup&gt;th&lt;/sup&gt;</code>.
testString: assert(timeElement.length && $(timeElement).html().trim() === "Thursday, September 15<sup>th</sup>");
- text: Your added <code>time</code> tag should have a <code>datetime</code> attribute that is not empty.
testString: assert(datetimeAttr && datetimeAttr.length);
- text: Your added <code>datetime</code> attribute should be set to a value of <code>2016-09-15</code>.
testString: assert(datetimeAttr === "2016-09-15");
Camper Cat's Mortal Kombat survey results are in! Wrap a `time` tag around the text "Thursday, September 15&lt;sup>th&lt;/sup>" and add a `datetime` attribute to it set to "2016-09-15".
# --hints--
Your code should have a `p` element which includes the text `Thank you to everyone for responding to Master Camper Cat's survey.` and include a `time` element.
```js
assert(timeElement.length);
```
</section>
Your added `time` tags should wrap around the text `Thursday, September 15<sup>th</sup>`.
## Challenge Seed
<section id='challengeSeed'>
```js
assert(
timeElement.length &&
$(timeElement).html().trim() === 'Thursday, September 15<sup>th</sup>'
);
```
<div id='html-seed'>
Your added `time` tag should have a `datetime` attribute that is not empty.
```js
assert(datetimeAttr && datetimeAttr.length);
```
Your added `datetime` attribute should be set to a value of `2016-09-15`.
```js
assert(datetimeAttr === '2016-09-15');
```
# --seed--
## --after-user-code--
```html
<script>
const pElement = $("article > p")
.filter((_, elem) => $(elem).text().includes("Thank you to everyone for responding to Master Camper Cat's survey."));
const timeElement = pElement[0] ? $(pElement[0]).find("time") : null;
const datetimeAttr = $(timeElement).attr("datetime");
</script>
```
## --seed-contents--
```html
<body>
@@ -74,25 +96,7 @@ tests:
</body>
```
</div>
<div id='html-teardown'>
```html
<script>
const pElement = $("article > p")
.filter((_, elem) => $(elem).text().includes("Thank you to everyone for responding to Master Camper Cat's survey."));
const timeElement = pElement[0] ? $(pElement[0]).find("time") : null;
const datetimeAttr = $(timeElement).attr("datetime");
</script>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -123,5 +127,3 @@ const datetimeAttr = $(timeElement).attr("datetime");
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>

76
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/use-headings-to-show-hierarchical-relationships-of-content.md
View File

@@ -6,42 +6,53 @@ videoUrl: 'https://scrimba.com/c/cqVEktm'
forumTopicId: 301026
---
## Description
<section id='description'>
Headings (<code>h1</code> through <code>h6</code> elements) are workhorse tags that help provide structure and labeling to your content. Screen readers can be set to read only the headings on a page so the user gets a summary. This means it is important for the heading tags in your markup to have semantic meaning and relate to each other, not be picked merely for their size values.
<em>Semantic meaning</em> means that the tag you use around content indicates the type of information it contains.
# --description--
Headings (`h1` through `h6` elements) are workhorse tags that help provide structure and labeling to your content. Screen readers can be set to read only the headings on a page so the user gets a summary. This means it is important for the heading tags in your markup to have semantic meaning and relate to each other, not be picked merely for their size values.
*Semantic meaning* means that the tag you use around content indicates the type of information it contains.
If you were writing a paper with an introduction, a body, and a conclusion, it wouldn't make much sense to put the conclusion as a subsection of the body in your outline. It should be its own section. Similarly, the heading tags in a webpage need to go in order and indicate the hierarchical relationships of your content.
Headings with equal (or higher) rank start new implied sections, headings with lower rank start subsections of the previous one.
As an example, a page with an <code>h2</code> element followed by several subsections labeled with <code>h4</code> tags would confuse a screen reader user. With six choices, it's tempting to use a tag because it looks better in a browser, but you can use CSS to edit the relative sizing.
One final point, each page should always have one (and only one) <code>h1</code> element, which is the main subject of your content. This and the other headings are used in part by search engines to understand the topic of the page.
</section>
## Instructions
<section id='instructions'>
Camper Cat wants a page on his site dedicated to becoming a ninja. Help him fix the headings so his markup gives semantic meaning to the content, and shows the proper parent-child relationships of his sections. Change all the <code>h5</code> tags to the proper heading level to indicate they are subsections of the <code>h2</code> ones. Use <code>h3</code> tags for the purpose.
</section>
As an example, a page with an `h2` element followed by several subsections labeled with `h4` tags would confuse a screen reader user. With six choices, it's tempting to use a tag because it looks better in a browser, but you can use CSS to edit the relative sizing.
## Tests
<section id='tests'>
One final point, each page should always have one (and only one) `h1` element, which is the main subject of your content. This and the other headings are used in part by search engines to understand the topic of the page.
```yml
tests:
- text: Your code should have 6 <code>h3</code> tags.
testString: assert($("h3").length === 6);
- text: Your code should have 6 <code>h3</code> closing tags.
testString: assert((code.match(/\/h3/g) || []).length===6);
- text: Your code should not have any <code>h5</code> tags.
testString: assert($("h5").length === 0);
- text: Your code should not have any <code>h5</code> closing tags.
testString: assert(/\/h5/.test(code)===false);
# --instructions--
Camper Cat wants a page on his site dedicated to becoming a ninja. Help him fix the headings so his markup gives semantic meaning to the content, and shows the proper parent-child relationships of his sections. Change all the `h5` tags to the proper heading level to indicate they are subsections of the `h2` ones. Use `h3` tags for the purpose.
# --hints--
Your code should have 6 `h3` tags.
```js
assert($('h3').length === 6);
```
</section>
Your code should have 6 `h3` closing tags.
## Challenge Seed
<section id='challengeSeed'>
```js
assert((code.match(/\/h3/g) || []).length === 6);
```
<div id='html-seed'>
Your code should not have any `h5` tags.
```js
assert($('h5').length === 0);
```
Your code should not have any `h5` closing tags.
```js
assert(/\/h5/.test(code) === false);
```
# --seed--
## --seed-contents--
```html
<h1>How to Become a Ninja</h1>
@@ -60,14 +71,7 @@ tests:
</main>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<h1>How to Become a Ninja</h1>
@@ -85,5 +89,3 @@ tests:
<h3>How to Simplify your Life</h3>
</main>
```
</section>

57
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/use-tabindex-to-add-keyboard-focus-to-an-element.md
View File

@@ -6,37 +6,37 @@ videoUrl: 'https://scrimba.com/c/cmzMDHW'
forumTopicId: 301027
---
## Description
<section id='description'>
The HTML <code>tabindex</code> attribute has three distinct functions relating to an element's keyboard focus. When it's on a tag, it indicates that element can be focused on. The value (an integer that's positive, negative, or zero) determines the behavior.
Certain elements, such as links and form controls, automatically receive keyboard focus when a user tabs through a page. It's in the same order as the elements come in the HTML source markup. This same functionality can be given to other elements, such as <code>div</code>, <code>span</code>, and <code>p</code>, by placing a <code>tabindex="0"</code> attribute on them. Here's an example:
<code>&lt;div tabindex=&quot;0&quot;&gt;I need keyboard focus!&lt;/div&gt;</code>
<strong>Note:</strong> A negative <code>tabindex</code> value (typically -1) indicates that an element is focusable, but is not reachable by the keyboard. This method is generally used to bring focus to content programmatically (like when a <code>div</code> used for a pop-up window is activated), and is beyond the scope of these challenges.
</section>
# --description--
## Instructions
<section id='instructions'>
Camper Cat created a new survey to collect information about his users. He knows input fields automatically get keyboard focus, but he wants to make sure his keyboard users pause at the instructions while tabbing through the items. Add a <code>tabindex</code> attribute to the <code>p</code> tag and set its value to <code>"0"</code>. Bonus - using <code>tabindex</code> also enables the CSS pseudo-class <code>:focus</code> to work on the <code>p</code> tag.
</section>
The HTML `tabindex` attribute has three distinct functions relating to an element's keyboard focus. When it's on a tag, it indicates that element can be focused on. The value (an integer that's positive, negative, or zero) determines the behavior.
## Tests
<section id='tests'>
Certain elements, such as links and form controls, automatically receive keyboard focus when a user tabs through a page. It's in the same order as the elements come in the HTML source markup. This same functionality can be given to other elements, such as `div`, `span`, and `p`, by placing a `tabindex="0"` attribute on them. Here's an example:
```yml
tests:
- text: Your code should add a <code>tabindex</code> attribute to the <code>p</code> tag that holds the form instructions.
testString: assert($('p').attr('tabindex'));
- text: Your code should set the <code>tabindex</code> attribute on the <code>p</code> tag to a value of 0.
testString: assert($('p').attr('tabindex') == '0');
`<div tabindex="0">I need keyboard focus!</div>`
**Note:** A negative `tabindex` value (typically -1) indicates that an element is focusable, but is not reachable by the keyboard. This method is generally used to bring focus to content programmatically (like when a `div` used for a pop-up window is activated), and is beyond the scope of these challenges.
# --instructions--
Camper Cat created a new survey to collect information about his users. He knows input fields automatically get keyboard focus, but he wants to make sure his keyboard users pause at the instructions while tabbing through the items. Add a `tabindex` attribute to the `p` tag and set its value to `"0"`. Bonus - using `tabindex` also enables the CSS pseudo-class `:focus` to work on the `p` tag.
# --hints--
Your code should add a `tabindex` attribute to the `p` tag that holds the form instructions.
```js
assert($('p').attr('tabindex'));
```
</section>
Your code should set the `tabindex` attribute on the `p` tag to a value of 0.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('p').attr('tabindex') == '0');
```
<div id='html-seed'>
# --seed--
## --seed-contents--
```html
<head>
@@ -88,14 +88,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<head>
@@ -146,5 +139,3 @@ tests:
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>

75
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/use-tabindex-to-specify-the-order-of-keyboard-focus-for-several-elements.md
View File

@@ -6,43 +6,53 @@ videoUrl: 'https://scrimba.com/c/cmzRRcb'
forumTopicId: 301028
---
## Description
<section id='description'>
The <code>tabindex</code> attribute also specifies the exact tab order of elements. This is achieved when the value of the attribute is set to a positive number of 1 or higher.
Setting a <code>tabindex="1"</code> will bring keyboard focus to that element first. Then it cycles through the sequence of specified <code>tabindex</code> values (2, 3, etc.), before moving to default and <code>tabindex="0"</code> items.
# --description--
The `tabindex` attribute also specifies the exact tab order of elements. This is achieved when the value of the attribute is set to a positive number of 1 or higher.
Setting a `tabindex="1"` will bring keyboard focus to that element first. Then it cycles through the sequence of specified `tabindex` values (2, 3, etc.), before moving to default and `tabindex="0"` items.
It's important to note that when the tab order is set this way, it overrides the default order (which uses the HTML source). This may confuse users who are expecting to start navigation from the top of the page. This technique may be necessary in some circumstances, but in terms of accessibility, take care before applying it.
Here's an example:
<code>&lt;div tabindex=&quot;1&quot;&gt;I get keyboard focus, and I get it first!&lt;/div&gt;</code>
<code>&lt;div tabindex=&quot;2&quot;&gt;I get keyboard focus, and I get it second!&lt;/div&gt;</code>
</section>
## Instructions
<section id='instructions'>
Camper Cat has a search field on his Inspirational Quotes page that he plans to position in the upper right corner with CSS. He wants the search <code>input</code> and submit <code>input</code> form controls to be the first two items in the tab order. Add a <code>tabindex</code> attribute set to <code>"1"</code> to the search <code>input</code>, and a <code>tabindex</code> attribute set to <code>"2"</code> to the submit <code>input</code>.
</section>
`<div tabindex="1">I get keyboard focus, and I get it first!</div>`
## Tests
<section id='tests'>
`<div tabindex="2">I get keyboard focus, and I get it second!</div>`
```yml
tests:
- text: Your code should add a <code>tabindex</code> attribute to the search <code>input</code> tag.
testString: assert($('#search').attr('tabindex'));
- text: Your code should add a <code>tabindex</code> attribute to the submit <code>input</code> tag.
testString: assert($('#submit').attr('tabindex'));
- text: Your code should set the <code>tabindex</code> attribute on the search <code>input</code> tag to a value of 1.
testString: assert($('#search').attr('tabindex') == '1');
- text: Your code should set the <code>tabindex</code> attribute on the submit <code>input</code> tag to a value of 2.
testString: assert($('#submit').attr('tabindex') == '2');
# --instructions--
Camper Cat has a search field on his Inspirational Quotes page that he plans to position in the upper right corner with CSS. He wants the search `input` and submit `input` form controls to be the first two items in the tab order. Add a `tabindex` attribute set to `"1"` to the search `input`, and a `tabindex` attribute set to `"2"` to the submit `input`.
# --hints--
Your code should add a `tabindex` attribute to the search `input` tag.
```js
assert($('#search').attr('tabindex'));
```
</section>
Your code should add a `tabindex` attribute to the submit `input` tag.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('#submit').attr('tabindex'));
```
<div id='html-seed'>
Your code should set the `tabindex` attribute on the search `input` tag to a value of 1.
```js
assert($('#search').attr('tabindex') == '1');
```
Your code should set the `tabindex` attribute on the submit `input` tag to a value of 2.
```js
assert($('#submit').attr('tabindex') == '2');
```
# --seed--
## --seed-contents--
```html
<body>
@@ -78,14 +88,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -120,5 +123,3 @@ tests:
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>

53
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/wrap-content-in-the-article-element.md
View File

@@ -6,12 +6,16 @@ videoUrl: 'https://scrimba.com/c/cPp79S3'
forumTopicId: 301029
---
## Description
<section id='description'>
<code>article</code> is another one of the new HTML5 elements that adds semantic meaning to your markup. <code>article</code> is a sectioning element, and is used to wrap independent, self-contained content. The tag works well with blog entries, forum posts, or news articles.
# --description--
`article` is another one of the new HTML5 elements that adds semantic meaning to your markup. `article` is a sectioning element, and is used to wrap independent, self-contained content. The tag works well with blog entries, forum posts, or news articles.
Determining whether content can stand alone is usually a judgement call, but there are a couple simple tests you can use. Ask yourself if you removed all surrounding context, would that content still make sense? Similarly for text, would the content hold up if it were in an RSS feed?
Remember that folks using assistive technologies rely on organized, semantically meaningful markup to better understand your work.
<strong>Note about <code>section</code> and <code>div</code></strong><br>The <code>section</code> element is also new with HTML5, and has a slightly different semantic meaning than <code>article</code>. An <code>article</code> is for standalone content, and a <code>section</code> is for grouping thematically related content. They can be used within each other, as needed. For example, if a book is the <code>article</code>, then each chapter is a <code>section</code>. When there's no relationship between groups of content, then use a <code>div</code>.
**Note about `section` and `div`**
The `section` element is also new with HTML5, and has a slightly different semantic meaning than `article`. An `article` is for standalone content, and a `section` is for grouping thematically related content. They can be used within each other, as needed. For example, if a book is the `article`, then each chapter is a `section`. When there's no relationship between groups of content, then use a `div`.
```html
<div> - groups content
@@ -19,31 +23,27 @@ Remember that folks using assistive technologies rely on organized, semantically
<article> - groups independent, self-contained content
```
</section>
# --instructions--
## Instructions
<section id='instructions'>
Camper Cat used <code>article</code> tags to wrap the posts on his blog page, but he forgot to use them around the top one. Change the <code>div</code> tag to use an <code>article</code> tag instead.
</section>
Camper Cat used `article` tags to wrap the posts on his blog page, but he forgot to use them around the top one. Change the `div` tag to use an `article` tag instead.
## Tests
<section id='tests'>
# --hints--
```yml
tests:
- text: Your code should have three <code>article</code> tags.
testString: assert($('article').length == 3);
- text: Your code should not have any <code>div</code> tags.
testString: assert($('div').length == 0);
Your code should have three `article` tags.
```js
assert($('article').length == 3);
```
</section>
Your code should not have any `div` tags.
## Challenge Seed
<section id='challengeSeed'>
```js
assert($('div').length == 0);
```
<div id='html-seed'>
# --seed--
## --seed-contents--
```html
<h1>Deep Thoughts with Master Camper Cat</h1>
@@ -69,14 +69,7 @@ tests:
</main>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<h1>Deep Thoughts with Master Camper Cat</h1>
@@ -101,5 +94,3 @@ tests:
</article>
</main>
```
</section>

81
curriculum/challenges/english/01-responsive-web-design/applied-accessibility/wrap-radio-buttons-in-a-fieldset-element-for-better-accessibility.md
View File

@@ -6,11 +6,14 @@ videoUrl: 'https://scrimba.com/c/cVJVefw'
forumTopicId: 301030
---
## Description
<section id='description'>
The next form topic covers accessibility of radio buttons. Each choice is given a <code>label</code> with a <code>for</code> attribute tying to the <code>id</code> of the corresponding item as covered in the last challenge. Since radio buttons often come in a group where the user must choose one, there's a way to semantically show the choices are part of a set.
The <code>fieldset</code> tag surrounds the entire grouping of radio buttons to achieve this. It often uses a <code>legend</code> tag to provide a description for the grouping, which is read by screen readers for each choice in the <code>fieldset</code> element.
The <code>fieldset</code> wrapper and <code>legend</code> tag are not necessary when the choices are self-explanatory, like a gender selection. Using a <code>label</code> with the <code>for</code> attribute for each radio button is sufficient.
# --description--
The next form topic covers accessibility of radio buttons. Each choice is given a `label` with a `for` attribute tying to the `id` of the corresponding item as covered in the last challenge. Since radio buttons often come in a group where the user must choose one, there's a way to semantically show the choices are part of a set.
The `fieldset` tag surrounds the entire grouping of radio buttons to achieve this. It often uses a `legend` tag to provide a description for the grouping, which is read by screen readers for each choice in the `fieldset` element.
The `fieldset` wrapper and `legend` tag are not necessary when the choices are self-explanatory, like a gender selection. Using a `label` with the `for` attribute for each radio button is sufficient.
Here's an example:
```html
@@ -27,37 +30,48 @@ Here's an example:
</form>
```
</section>
# --instructions--
## Instructions
<section id='instructions'>
Camper Cat wants information about the ninja level of his users when they sign up for his email list. He's added a set of radio buttons and learned from our last lesson to use label tags with <code>for</code> attributes for each choice. Go Camper Cat! However, his code still needs some help. Change the <code>div</code> tag surrounding the radio buttons to a <code>fieldset</code> tag, and change the <code>p</code> tag inside it to a <code>legend</code>.
</section>
Camper Cat wants information about the ninja level of his users when they sign up for his email list. He's added a set of radio buttons and learned from our last lesson to use label tags with `for` attributes for each choice. Go Camper Cat! However, his code still needs some help. Change the `div` tag surrounding the radio buttons to a `fieldset` tag, and change the `p` tag inside it to a `legend`.
## Tests
<section id='tests'>
# --hints--
```yml
tests:
- text: Your code should have a <code>fieldset</code> tag around the radio button set.
testString: assert($('fieldset').length == 1);
- text: The <code>fieldset</code> element should have a closing tag.
testString: assert(code.match(/<\/fieldset>/g) && code.match(/<\/fieldset>/g).length === code.match(/<fieldset>/g).length);
- text: Your code should have a <code>legend</code> tag around the text asking what level ninja a user is.
testString: assert($('legend').length == 1);
- text: Your code should not have any <code>div</code> tags.
testString: assert($('div').length == 0);
- text: Your code should no longer have a <code>p</code> tag around the text asking what level ninja a user is.
testString: assert($('p').length == 4);
Your code should have a `fieldset` tag around the radio button set.
```js
assert($('fieldset').length == 1);
```
</section>
The `fieldset` element should have a closing tag.
## Challenge Seed
<section id='challengeSeed'>
```js
assert(
code.match(/<\/fieldset>/g) &&
code.match(/<\/fieldset>/g).length === code.match(/<fieldset>/g).length
);
```
<div id='html-seed'>
Your code should have a `legend` tag around the text asking what level ninja a user is.
```js
assert($('legend').length == 1);
```
Your code should not have any `div` tags.
```js
assert($('div').length == 0);
```
Your code should no longer have a `p` tag around the text asking what level ninja a user is.
```js
assert($('p').length == 4);
```
# --seed--
## --seed-contents--
```html
<body>
@@ -105,14 +119,7 @@ tests:
</body>
```
</div>
</section>
## Solution
<section id='solution'>
# --solutions--
```html
<body>
@@ -155,5 +162,3 @@ tests:
<footer>&copy; 2018 Camper Cat</footer>
</body>
```
</section>