From df8659ab8ca7a38ac3f977188d6e76f838350a12 Mon Sep 17 00:00:00 2001 From: Randell Dawson <5313213+RandellDawson@users.noreply.github.com> Date: Tue, 14 May 2019 01:11:58 -0700 Subject: [PATCH] fix(curriculum): Convert blockquote elements to triple backtick syntax for Responsive Web Design (#35993) * fix: converted blockquotes to code fences --- .../add-an-accessible-date-picker.english.md | 7 ++++++- ...-content-with-the-audio-element.english.md | 9 ++++++++- ...ibility-with-the-figure-element.english.md | 12 +++++++++++- ...sibility-with-the-label-element.english.md | 9 ++++++++- ...reen-reader-by-using-custom-css.english.md | 13 ++++++++++++- ...-content-in-the-article-element.english.md | 8 +++++++- ...lement-for-better-accessibility.english.md | 16 +++++++++++++++- ...x-shadow-to-a-card-like-element.english.md | 6 +++++- ...ement-using-the-height-property.english.md | 8 +++++++- ...he-hover-state-of-an-anchor-tag.english.md | 8 +++++++- ...lement-using-the-width-property.english.md | 8 +++++++- ...e-an-elements-relative-position.english.md | 9 ++++++++- ...omplex-shape-using-css-and-html.english.md | 15 ++++++++++++++- ...te-movement-using-css-animation.english.md | 19 ++++++++++++++++++- ...s-and-animation-properties-work.english.md | 18 +++++++++++++++++- ...nge-the-hover-state-of-a-button.english.md | 19 ++++++++++++++++++- ...kew-an-element-along-the-x-axis.english.md | 8 +++++++- ...o-change-the-size-of-an-element.english.md | 8 +++++++- ...ty-to-scale-an-element-on-hover.english.md | 8 +++++++- ...dd-borders-around-your-elements.english.md | 12 +++++++++++- ...allback-value-to-a-css-variable.english.md | 6 +++++- ...nge-the-font-size-of-an-element.english.md | 8 +++++++- .../create-a-custom-css-variable.english.md | 6 +++++- ...ckground-color-to-a-div-element.english.md | 8 +++++++- ...ations-by-styling-id-attributes.english.md | 8 +++++++- ...t-the-font-family-of-an-element.english.md | 8 +++++++- .../basic-css/size-your-images.english.md | 10 +++++++++- ...pecify-how-fonts-should-degrade.english.md | 8 +++++++- .../style-the-html-body-element.english.md | 8 +++++++- ...a-css-class-to-style-an-element.english.md | 10 +++++++++- .../use-a-custom-css-variable.english.md | 6 +++++- ...d-attribute-to-style-an-element.english.md | 8 +++++++- ...ute-selectors-to-style-elements.english.md | 8 +++++++- ...css-selectors-to-style-elements.english.md | 17 +++++++++++++++-- ...se-hex-code-for-specific-colors.english.md | 8 +++++++- ...se-rgb-values-to-color-elements.english.md | 8 +++++++- ...reate-a-bulleted-unordered-list.english.md | 9 ++++++++- .../create-a-set-of-radio-buttons.english.md | 16 ++++++++++++++-- .../create-an-ordered-list.english.md | 9 ++++++++- ...the-doctype-of-an-html-document.english.md | 9 ++++++++- ...ad-and-body-of-an-html-document.english.md | 14 +++++++++++++- .../introduction-to-html5-elements.english.md | 9 ++++++++- ...-of-a-page-with-anchor-elements.english.md | 8 +++++++- ...chor-element-within-a-paragraph.english.md | 8 +++++++- ...th-radio-buttons-and-checkboxes.english.md | 14 ++++++++++---- ...umns-with-grid-template-columns.english.md | 9 ++++++++- ...olumn-gap-using-grid-column-gap.english.md | 6 +++++- ...lexible-layouts-using-auto-fill.english.md | 6 +++++- ...-the-grid-into-an-area-template.english.md | 9 ++++++++- ...-size-using-the-minmax-function.english.md | 6 +++++- ...as-using-the-grid-area-property.english.md | 8 +++++++- ...ition-using-the-repeat-function.english.md | 18 +++++++++++++++--- ...ge-the-size-of-columns-and-rows.english.md | 6 +++++- ...hout-creating-an-areas-template.english.md | 12 ++++++++++-- ...-grid-column-to-control-spacing.english.md | 6 +++++- .../make-an-image-responsive.english.md | 10 +++++++++- ...-for-higher-resolution-displays.english.md | 9 ++++++++- 57 files changed, 491 insertions(+), 65 deletions(-) diff --git a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/add-an-accessible-date-picker.english.md b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/add-an-accessible-date-picker.english.md index 88734f6cc1..3b93dc1bc1 100644 --- a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/add-an-accessible-date-picker.english.md +++ b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/add-an-accessible-date-picker.english.md @@ -11,7 +11,12 @@ Forms often include the input field, which can be used to create se 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: -
<label for="input1">Enter a date:</label>
<input type="date" id="input1" name="input1">
+ +```html + + +``` + ## Instructions diff --git a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.english.md b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.english.md index 35d0138a3b..4e8d0d54da 100644 --- a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.english.md +++ b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.english.md @@ -10,7 +10,14 @@ videoUrl: 'https://scrimba.com/c/cVJVkcZ' 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: -
<audio id="meowClip" controls>
  <source src="audio/meow.mp3" type="audio/mpeg" />
  <source src="audio/meow.ogg" type="audio/ogg" />
</audio>
+ +```html + +``` + 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. diff --git a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-chart-accessibility-with-the-figure-element.english.md b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-chart-accessibility-with-the-figure-element.english.md index cf2cd9ecc3..8145651d41 100644 --- a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-chart-accessibility-with-the-figure-element.english.md +++ b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-chart-accessibility-with-the-figure-element.english.md @@ -10,7 +10,17 @@ videoUrl: 'https://scrimba.com/c/cGJMqtE' 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 figcaption goes inside the figure tags and can be combined with other elements: -
<figure>
  <img src="roundhouseDestruction.jpeg" alt="Photo of Camper Cat executing a roundhouse kick">
  <br>
  <figcaption>
    Master Camper Cat demonstrates proper form of a roundhouse kick.
  </figcaption>
</figure>
+ +```html +
+ Photo of Camper Cat executing a roundhouse kick +
+
+ Master Camper Cat demonstrates proper form of a roundhouse kick. +
+
+``` + ## Instructions diff --git a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-form-field-accessibility-with-the-label-element.english.md b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-form-field-accessibility-with-the-label-element.english.md index 174653c408..72e8222f4a 100644 --- a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-form-field-accessibility-with-the-label-element.english.md +++ b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/improve-form-field-accessibility-with-the-label-element.english.md @@ -11,7 +11,14 @@ Improving accessibility with semantic HTML markup applies to using both appropri 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: -
<form>
  <label for="name">Name:</label>
  <input type="text" id="name" name="name">
</form>
+ +```html +
+ + +
+``` + ## Instructions diff --git a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-elements-only-visible-to-a-screen-reader-by-using-custom-css.english.md b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-elements-only-visible-to-a-screen-reader-by-using-custom-css.english.md index d255b3fc40..fa30e3d906 100644 --- a/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-elements-only-visible-to-a-screen-reader-by-using-custom-css.english.md +++ b/curriculum/challenges/english/01-responsive-web-design/applied-accessibility/make-elements-only-visible-to-a-screen-reader-by-using-custom-css.english.md @@ -10,7 +10,18 @@ videoUrl: 'https://scrimba.com/c/cJ8QGkhJ' 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: -
.sr-only {
  position: absolute;
  left: -10000px;
  width: 1px;
  height: 1px;
  top: auto;
  overflow: hidden;
}
+ +```css +.sr-only { + position: absolute; + left: -10000px; + width: 1px; + height: 1px; + top: auto; + overflow: hidden; +} +``` + Note: The following CSS approaches will NOT do the same thing: