+
diff --git a/src/pages/components/accordion/accessibility.mdx b/src/pages/components/accordion/accessibility.mdx
index 165201c7c90..94846b22c6c 100755
--- a/src/pages/components/accordion/accessibility.mdx
+++ b/src/pages/components/accordion/accessibility.mdx
@@ -7,423 +7,117 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import {
- StructuredListWrapper,
- StructuredListHead,
- StructuredListBody,
- StructuredListRow,
- StructuredListInput,
- StructuredListCell,
- OrderedList,
- ListItem,
-} from '@carbon/react';
+
+
+Design annotations are needed for specific instances shown below, but for the
+standard accordion component, Carbon already incorporates accessibility.
+
+
- How it works
- Accessibility considerations
- Resources
- Accessibility testing
+ What Carbon provides
+ Design recommendations
+ Development considerations
-## How it works
-
-The accordion Carbon component provides a vertically stacked layout for web
-content, commonly used to reduce scrolling. The accordion header is a button
-that is used to expand and collapse each accordion panel. Buttons are used so
-that the accordions are tab-able by keyboard users and accessible to screen
-readers. `Tab` and `Shift-Tab` are used to navigate through each accordion
-header and all focusable elements in the accordion should be included in the
-page `Tab` sequence. `Enter` or `Space` expand and collapse each accordion
-panel.
-
-When an accordion panel is collapsed the content is hidden, therefore the ARIA
-state `aria-expanded="false"` advises users of assistive technologies that the
-accordion panel is not visible. When the accordion header is expanded the ARIA
-state changes to `aria-expanded="true"` and the accordion panel content is
-displayed. Each accordion header contains an ARIA label, and the header buttons
-have an ARIA-control property set that points to the unique id of the panel it
-controls. When focus is on the accordion header there is a prominent style
-change to the border as well as background of the accordion header.
-
-## Accessibility considerations
-
-This component has been validated to meet the
-[WCAG 2.0 AA](https://www.w3.org/TR/WCAG20/) and
-[Section 508](http://www.section508.gov/) accessibility guidelines, however
-changes made by the content owner can affect accessibility compliance. Be sure
-to review and follow the guidance in this section when updating or adding new
-content to this component.
-
-1. Each accordion header must have a unique title (implemented via the label for
- the button) that clearly describes the accordion panel content. This is
- particularly helpful for users of assistive technologies so they have the
- necessary information to efficiently navigate the content without having to
- expand every section.
-1. Carbon components should be used to create the content that displays within
- each accordion panel.
-1. Avoid keyboard traps when adding components to the accordion panel. For
- example, the user expands an accordion, but is unable to tab to the next
- focusable element.
-1. Although the accordion component passes accessibility testing, content
- authors need to ensure the content that is added to the accordion is
- accessible. For example, if you add an image to the accordion header or panel
- you need to include alternative text to pass accessibility testing.
-
-## Resources
-
-- [W3C WAI-ARIA Authoring Practices Accordion Design Pattern](https://www.w3.org/TR/wai-aria-practices/#accordion)
- covers the usage of ARIA names, state and roles, as well as the expected
- keyboard interactions.
-- [IBM Accessibility Requirements:](https://www.ibm.com/able/requirements/requirements/)
- - [1.3.1 Info and Relationships](https://www.ibm.com/able/requirements/requirements/#1_3_1)
- (WCAG Success Criteria
- [1.3.1](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships))
- - [1.3.2 Meaningful Sequence](https://www.ibm.com/able/requirements/requirements/#1_3_2)
- (WCAG Success Criteria
- [1.3.2](https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence))
- - [2.1.1 Keyboard](https://www.ibm.com/able/requirements/requirements/#2_1_1)
- (WCAG Success Criteria
- [2.1.1](https://www.w3.org/WAI/WCAG21/Understanding/keyboard))
- - [2.1.2 No Keyboard Trap](https://www.ibm.com/able/requirements/requirements/#2_1_2)
- (WCAG Success Criteria
- [2.1.2](https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap))
- - [2.4.3 Focus Order](https://www.ibm.com/able/requirements/requirements/#2_4_3)
- (WCAG Success Criteria
- [2.4.3](https://www.w3.org/WAI/WCAG21/Understanding/focus-order))
- - [2.4.6 Headings and Labels](https://www.ibm.com/able/requirements/requirements/#2_4_6)
- (WCAG Success Criteria
- [2.4.6](https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels))
- - [2.4.7 Focus Visible](https://www.ibm.com/able/requirements/requirements/#2_4_7)
- (WCAG Success Criteria
- [2.4.7](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible))
- - [4.1.2 Name, Role, Value](https://www.ibm.com/able/requirements/requirements/#4_1_2)
- (WCAG Success Criteria
- [4.1.2](https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html))
-
-## Accessibility testing
-
-Accessibility issues are tracked in the
-[Carbon Component GitHub repository](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+label%3A%22type%3A+a11y+%E2%99%BF%22+label%3A%22component%3A+accordion%22+).
-
-### Automated test
+## What Carbon provides
-
-
-
-
-
-
- Automated test environment
-
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.2 with VoiceOver
-
- - Chrome version 77.0.3865.90
-
- - Dynamic Assessment Plugin (DAP) version 1.8.0.0 - IBM
- Accessibility WCAG 2.1 Sept. 2019 Ruleset
- - Carbon React version 7.7.1
-
-
- DAP test:
- - Violations
-
-
-
-
-
-
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
+
+### Keyboard interactions
-### macOS screen reader tests
+Each accordion is a tab stop. `Space` or `Enter` keys expand or collapse
+accordions, which are collapsed by default. Interactive elements within expanded
+accordions integrate into the tab order automatically.
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome version 77.0.3865.90
- - Carbon React version 7.7.1
-
-
- VoiceOver(VO) Test:
-
-
- The Tab key and Shift-Tab navigate between accordion headers. VO
- announces, expand/collapse, title, collapsed, button, the
- button's state (expanded or collapsed), list, 1 item. You are
- currently on a button...
-
-
- Press Control-Option-Space (or Space) to expand or collapse the
- accordion panel. VO announces expand/collapse title, the
- button's state (expanded or collapsed).
-
-
- With the second or third accordion header expanded, Press
- Control-Option-Right Arrow. VO announces, the accordion panel
- content and the line number in the list.
-
-
- Press Control-Option-Left Arrow - VO announces reads the
- accordion header again.
-
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Safari version 13.0.2
- - Carbon React version 7.7.1
-
-
- VoiceOver(VO) test:
-
-
- The Tab key and Shift-Tab navigate between accordion headers. VO
- announces, expand/collapse, title, collapsed, button, the
- button's state (expanded or collapsed), group.
-
-
- Press Control-Option-Space (or Space) to expand or collapse the
- accordion panel. VO announces expand/collapse title, the
- button's state (expanded or collapsed).
-
-
- With the second or third accordion header expanded, Press
- Control-Option-Right Arrow. VO announces, the accordion panel
- content and the line number in the list. Your are currently on a
- text area.
-
-
- Press Control-Option-Left Arrow - VO announces reads the
- accordion header again.
-
-
-
-
-
-
-
+
+
+![example of accordion keyboard interaction](images/accordion-accessibility-1.png)
+
+
+ Accordions and interactive elements in the expanded content are in the tab
+ order and keyboard operable.
+
+
+
-### Windows screen reader tests
+### Labeling and states
+
+The collapsed or expanded state of the accordions is
+[programmatically set](https://www.ibm.com/able/requirements/requirements/#4_1_2)
+by default, eliminating the need for designers to provide
+[text equivalents](https://www.ibm.com/able/toolkit/design/content/text-equivalents/)
+for the chevron icons.
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - Microsoft Windows 10
-
- - JAWS 19.1903.47
-
- - Firefox version 67
- - Carbon React version 7.7.1
-
-
- JAWS test:
-
-
- The Tab key and Shift-Tab navigate between accordion headers.
- JAWS announces, title, and expand/collapse status.
-
-
- Press the Enter or Space key on the title. JAWS announces expand
- or collapsed.
-
-
- Navigate the text using the Up and Down Arrow keys, when JAWS
- read the headers and associated text if expanded in a linear
- order.
-
-
- Please note that sometimes it takes a second for the text to
- update after a title is expanded. When pressing the down arrow
- key immediately after JAWS announces "expanded", JAWS jumps past
- the text and reads the next title.
-
-
-
-
-
-
- - Microsoft Windows 10
-
- - JAWS 19.1903.47
-
- - Chrome version 71.0.3578.98 (Official Build) (64-bit)
- - Carbon React version 7.7.1
-
-
- JAWS test:
-
-
- The Tab key and Shift-Tab navigate between accordion headers.
- JAWS announces, title, and expand/collapse status.
-
-
- Press the Enter or Space key on the title. JAWS announces expand
- or collapsed.
-
-
- Navigate the text using the Up and Down Arrow keys, when JAWS
- read the headers and associated text if expanded in a linear
- order.
-
-
- Please note that sometimes it takes a second for the text to
- update after a title is expanded. When pressing the down arrow
- key immediately after JAWS announces "expanded", JAWS jumps past
- the text and reads the next title.
-
-
-
-
-
-
- - Microsoft Windows 10
-
- - NVDA version 2018.4.1
-
- - Chrome version 72.0.3626.96 (Official Build) (64-bit)
- - Carbon React version 7.7.1
-
-
- NVDA test:
-
-
- The Tab key and Shift-Tab navigate between accordion headers.
- NVDA announces, title, and expand/collapse status.
-
-
- Press the Enter or Space key on the title. NVDA announces expand
- or collapsed.
-
-
- Navigate the text using the Up and Down Arrow keys, when JAWS
- read the headers and associated text if expanded in a linear
- order.
-
-
-
-
-
-
-
+
+
+![expanded and collapsed accordions](images/accordion-accessibility-2.png)
+
+Carbon handles the accessibility of the chevron indicators.
+
+
-### iOS screen reader tests
+## Design recommendations
+
+Design annotations are needed for the following instances.
+
+### Headings
+
+Carbon accordions are not set as headings by default. For improved
+accessibility, annotate accordions as headings on the first occurrence in a
+product. Annotate the heading level of accordions as needed. See
+[Indicate heading levels](https://www.ibm.com/able/toolkit/design/content/text-meaning/#heading-levels).
-
-
-
- Environment
- Results
-
-
-
-
- - iOS version 13.1.3 with VoiceOver
-
- - Safari version 13.1.3
- - Carbon React version 7.7.1
-
-
- VoiceOver test:
-
-
- To navigate the accordion, swipe left or right, or use the Left
- or Right Arrow keys when quick nav mode is on. On each header,
- VoiceOver announces the header, and expanded/collapsed status.
-
-
- To expand or collapse the accordion, doubletap on the header, or
- press Control+Option+Space. VoiceOver announces, expanded or
- collapses.
-
-
- In some cases, VoiceOver also reads out the entire header, it
- seems to happen randomly, possibly have to do with the speed of
- the phone.
-
-
- Navigate the text by swiping left or right, or by pressing the
- Left or Right Arrow keys when quick navigation mode is on. After
- each title, when moving to the left or right, VoiceOver will
- read the text if it is expanded.
-
-
-
-
-
-
-
+
+
+![H1 and H2 annotations for headings, plus direction to ‘include accordion titles as headings'](images/accordion-accessibility-3.png)
+
+
+ If accordion titles act as headings, annotate for development.
+
+
+
-### Android screen reader tests
+### Alignment
+
+Carbon chevrons are right-aligned by default, but left-aligned chevrons are more
+accessible for users with low vision, as the expanded/collapsed indicator is
+closer to the accordion title.
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - Android version 9 with Talkback
-
- - Chrome version 72.0.3626.96 (Official Build) (64-bit)
- - Carbon React version 7.7.1
-
-
- Talkback test:
-
-
- To navigate the accordion, swipe left or right, or use the
- Alt+Left or Right Arrow keys. On each header, TalkBack announces
- the header, and expanded/collapsed status.
-
-
- To expand or collapse the accordion, doubletap on the header, or
- press Alt+Enter. Talkback announces expanded or collapses.
-
-
- Navigate the text by swiping left or right, or by pressing the
- Left or Right Arrow keys. After each title, when moving to the
- left or right, Talkback will read the text if it is expanded.
-
-
-
-
-
-
-
+
+
+![annotation stating ‘position chevrons on the left of accordion titles'](images/accordion-accessibility-4.png)
+
+Annotate if the accordion chevrons should be left-aligned.
+
+
+
+## Development considerations
+
+Keep these considerations in mind if you are modifying Carbon or creating a
+custom component:
+
+- The accordion header has a role of `
`, with an `aria-expanded`
+ attribute set to `"true"` or `"false"`.
+- The button has an `aria-controls` property set to the unique id of the panel
+ it controls.
+- Since accordions are typically grouped together, Carbon puts each button
+ inside a list item in an unordered list, which provides additional context to
+ screen reader users; where only one accordion is used, it should not be put in
+ a list.
+- When accordion titles are used as headings, the buttons are also wrapped in an
+ element with an appropriate heading level; ARIA can be used to set both the
+ heading role and the level (via `aria-level`).
+- See the
+ [ARIA authoring practices](https://www.w3.org/TR/wai-aria-practices-1.2/#accordion)
+ for more guidance.
diff --git a/src/pages/components/accordion/images/accordion-accessibility-1.png b/src/pages/components/accordion/images/accordion-accessibility-1.png
new file mode 100644
index 00000000000..ae2a6506a69
Binary files /dev/null and b/src/pages/components/accordion/images/accordion-accessibility-1.png differ
diff --git a/src/pages/components/accordion/images/accordion-accessibility-2.png b/src/pages/components/accordion/images/accordion-accessibility-2.png
new file mode 100644
index 00000000000..5db30f6bd9b
Binary files /dev/null and b/src/pages/components/accordion/images/accordion-accessibility-2.png differ
diff --git a/src/pages/components/accordion/images/accordion-accessibility-3.png b/src/pages/components/accordion/images/accordion-accessibility-3.png
new file mode 100644
index 00000000000..f143fae7e1e
Binary files /dev/null and b/src/pages/components/accordion/images/accordion-accessibility-3.png differ
diff --git a/src/pages/components/accordion/images/accordion-accessibility-4.png b/src/pages/components/accordion/images/accordion-accessibility-4.png
new file mode 100644
index 00000000000..87b06deae57
Binary files /dev/null and b/src/pages/components/accordion/images/accordion-accessibility-4.png differ
diff --git a/src/pages/components/breadcrumb/accessibility.mdx b/src/pages/components/breadcrumb/accessibility.mdx
index 8e83f13a857..0b9cc249ac8 100644
--- a/src/pages/components/breadcrumb/accessibility.mdx
+++ b/src/pages/components/breadcrumb/accessibility.mdx
@@ -6,335 +6,73 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import {
- StructuredListWrapper,
- StructuredListHead,
- StructuredListBody,
- StructuredListRow,
- StructuredListInput,
- StructuredListCell,
- OrderedList,
- ListItem,
-} from '@carbon/react';
+
+
+No accessibility annotations are needed for breadcrumbs, but keep these
+considerations in mind if you are modifying Carbon or creating a custom
+component.
+
+
- How it works
- Accessibility considerations
- Resources
- Accessibility testing
+ What Carbon provides
+ Development considerations
-## How it works
+## What Carbon provides
-The `Breadcrumb` component implements the
-[Breadcrumb design pattern from WAI ARIA](https://www.w3.org/TR/wai-aria-practices-1.1/#breadcrumb)
-for Carbon. It establishes a landmark on the page which assists the user in
-understanding where they currently are and which pages exist in the current
-page's hierarchical order.
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
-The landmark is provided through the `` element which contains a list of
-links. The `` element is labeled by the `aria-label`attribute, providing a
-chance to describe to the user the type of navigation provided by the list of
-links. The current page is identified with the `aria-current="page"` attribute
-on the appropriate link.
+### Keyboard interactions
-## Accessibility considerations
+Each page link in the breadcrumb is reached by `Tab` and activated by `Enter`.
+The current page, if listed in the breadcrumb, is not a link. If the breadcrumb
+is truncated, the ellipsis button for the overflow menu is in the tab order. See
+[overflow menu](https://carbondesignsystem.com/components/overflow-menu/usage/)
+for details on its keyboard operation.
-This component has been validated to meet the
-[WCAG 2.0 AA](https://www.w3.org/TR/WCAG20/) and
-[Section 508](http://www.section508.gov/) accessibility guidelines, however
-changes made by the content owner can affect accessibility compliance. Be sure
-to review and follow the guidance in this section when updating or adding new
-content to this component.
-
-1. The breadcrumb should remain in the same relative order and location on each
- web page.
-1. The link text should be clear, reflect the breadcrumb location accurately and
- easy to understand for all users.
-1. The link to the current page element in the breadcrumb has the
- `aria-current="page"` attribute.
+
+
-## Resources
+![example of breadcrumb keyboard interaction](images/breadcrumb-accessibility-1.png)
-- [W3C WAI-ARIA Authoring Practices Breadcrumb Design Pattern](https://www.w3.org/TR/wai-aria-practices/#breadcrumb)
- covers the usage of ARIA names, state and roles.
-- [IBM Accessibility Requirements:](https://www.ibm.com/able/requirements/requirements/)
- - [2.4.4 Link Purpose (In Context)](https://www.ibm.com/able/requirements/requirements/#2_4_4)
- (WCAG Success Criteria
- [2.4.4](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html))
- - [3.2.3 Consistent Navigation](https://www.ibm.com/able/requirements/requirements/#3_2_3)
- (WCAG Success
- Criteria[3.2.3](https://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-consistent-locations.html))
+
+ The breadcrumb's links are reached by Tab and activated by Enter.
+
-## Accessibility testing
+
+
-Accessibility issues are tracked in the
-[Carbon Design System GitHub repository](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+label%3A%22type%3A+a11y+%E2%99%BF%22+label%3A%22component%3A+breadcrumb%22+).
+### Labeling and regions
-### Automated test
+Carbon implements each page link as a list item inside a navigation region named
+“breadcrumb.” The ellipsis symbol is a button called “more breadcrumbs” which
+opens the
+[overflow menu](https://carbondesignsystem.com/components/overflow-menu/usage/).
-
-
-
-
-
- Automated test Environment
-
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome version 77.0.3865.90
-
- - Dynamic Assessment Plugin version 1.8.0.0 - IBM Accessibility WCAG
- 2.1 Sept. 2019 Ruleset
- - Carbon React version 7.7.1
-
-
- DAP test:
- - No violations
-
-
-
-
-
-
+
-### macOS screen reader tests
+![aria-label designates the navigation region 'breadcrumb' and the ellipsis button 'more breadcrumbs’](images/breadcrumb-accessibility-2.png)
-
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome version 77.0.3865.90
- - Carbon React version 7.7.1
-
-
- VoiceOver(VO) Test:
-
-
- Tab to the breadcrumb and VO announces, "Breadcrumb 1,
- breadcrumb navigation".
-
-
- The Tab key and shift-tab navigate between the links in the
- breadcrumb. VO announces, "Link Breadcrumb #. You are currently
- on a link to click this link press Control-Option-Space."
-
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Safari version 12.14.6
- - Carbon React Version 7.7.1
-
-
- VoiceOver(VO) Test:
-
-
- Tab to the breadcrumb and VO announces, "Breadcrumb 1,
- breadcrumb navigation".
-
-
- The Tab key and shift-tab navigate between the links in the
- breadcrumb. VO announces, "Link Breadcrumb #. You are currently
- on a link to click this link press Control-Option-Space."
-
-
- Note: In Safari > Preferences > Advanced > ensure "Press Tab to
- highlight each item on a webpage" option is checked.
-
-
-
-
-
-
-
-
+
+ Carbon provides the accessibility information about the breadcrumb's
+ structure.
+
-### Windows screen reader tests
-
-
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - Microsoft Windows 10
-
- - Chrome: 71.0.3578.98 (Official Build) (64-bit)
-
- - JAWS 19.1810.64
- - Carbon React version 7.7.1
-
-
- JAWS Test:
-
-
- Navigate the list with the Up and Down Arrow keys.
-
-
- JAWS announces the beginning of the list, number of items in the
- list, nesting level, content of the list item and end of the
- list.
-
-
- Information and the list item content are announced on two
- separate lines on the virtual viewer.
-
-
- Bullets and item numbers are also placed on a separate line.
-
-
-
-
-
-
- - Microsoft Windows 10
-
- - Chrome: 71.0.3578.98 (Official Build) (64-bit)
-
- - NVDA 2018.4.1
- - Carbon React version 7.7.1
-
-
- NVDA test:
-
-
- Navigate the list with the Up and Down Arrow keys.
-
-
- NVDA announces the beginning of the list, number of items in the
- list, nesting level, content of the list item.
-
-
- End of list, when exiting the list from the top or bottom.
-
-
- List item parameters are announced together with the list item
- content.
-
-
-
-
-
-
-
+
-### Android screen reader tests
+## Development considerations
-
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - Android version 9 with Talkback
-
- - Chrome: 71.0.3578.98 (Official Build) (64-bit)
- - Carbon React version 7.7.1
-
-
- Talkback Test:
-
-
- Navigate the list by swiping left or right or pressing the Alt
- key with the Left or Right Arrow key.
-
-
- Talkback announces, "in list" when entering the list and "out of
- list" when exiting the list.
-
-
- Talkback also announces entering and exiting the nested lists,
- the number of list items, nesting level, and content of the list
- item.
-
-
- Bullets and numbers are announced separately from the list item
- content.
-
-
-
-
-
-
-
-
+Keep these considerations in mind if you are modifying Carbon or creating a
+custom component:
-### iOS screen reader tests
-
-
-
-
-
- Environment
- Results
-
-
-
-
- - iOS version 13.1.3 with VoiceOver
-
- - Safari version 13.1.3
- - Carbon React version 7.7.1
-
-
- VoiceOver test:
-
-
- Navigate list items by swiping left or right, or using the Left
- and Right Arrow keys on the keyboard when the quick navigation
- is turned on.
-
-
- VoiceOver announces the beginning of the list, nesting level,
- content of the list item, the end of the list.
-
-
- VoiceOver announces the beginning of the list, nesting level,
- content of the list item, the end of the list.
-
-
- Information about the list, bullets and numbers and list item
- contents are pronounced separately, we have to navigate through
- these one by one.
-
-
-
-
-
-
-
-
+- The Carbon implementation uses an html5 `` element; this could also be
+ achieved with a “navigation” landmark on a ``.
+- Each link in the breadcrumb is implemented as an unordered list item so that
+ screen readers provide more context.
+- The visual / separators do not need to be text (Carbon uses CSS) and are not
+ intended to be navigable.
diff --git a/src/pages/components/breadcrumb/images/breadcrumb-accessibility-1.png b/src/pages/components/breadcrumb/images/breadcrumb-accessibility-1.png
new file mode 100644
index 00000000000..9921fc84c1c
Binary files /dev/null and b/src/pages/components/breadcrumb/images/breadcrumb-accessibility-1.png differ
diff --git a/src/pages/components/breadcrumb/images/breadcrumb-accessibility-2.png b/src/pages/components/breadcrumb/images/breadcrumb-accessibility-2.png
new file mode 100644
index 00000000000..1d43e8ff504
Binary files /dev/null and b/src/pages/components/breadcrumb/images/breadcrumb-accessibility-2.png differ
diff --git a/src/pages/components/button/accessibility.mdx b/src/pages/components/button/accessibility.mdx
index 2bd1247a66b..6b174241643 100644
--- a/src/pages/components/button/accessibility.mdx
+++ b/src/pages/components/button/accessibility.mdx
@@ -6,314 +6,100 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import {
- StructuredListWrapper,
- StructuredListHead,
- StructuredListBody,
- StructuredListRow,
- StructuredListInput,
- StructuredListCell,
- OrderedList,
- ListItem,
-} from '@carbon/react';
+
+
+Design annotations are needed for specific instances shown below, but for the
+standard button component, Carbon already incorporates accessibility.
+
+
- How it works
- Accessibility considerations
- Resources
- Accessibility testing
+ What Carbon provides
+ Design recommendations
+ Development considerations
-## How it works
-
-The `Button` component is used to trigger an action or event, such as submitting
-a form, opening a modal, canceling an action, or performing an add or delete
-operation. Almost all interactions in the Carbon Design System are implemented
-using the native `
` element.
-
-By default, interactive elements like `` are included in the tab order
-of the document. When a button has focus, both the `Space` and `Enter` keys will
-activate the button. If the button is disabled, then the `disabled` attribute is
-provided.
-
-The label for a button can be computed by the contents of the underlying
-``, or provided by the `aria-label` or `aria-labelledby` attributes.
-Additional information about the button may be supplied by the
-`aria-describedby` attribute.
-
-## Accessibility considerations
-
-This component has been validated to meet the
-[WCAG 2.1 AA](https://www.w3.org/TR/WCAG21/) and
-[Section 508](http://www.section508.gov/) accessibility guidelines, however
-changes made by the content owner can affect accessibility compliance. Be sure
-to review and follow the guidance in this section when updating or adding new
-content to this component.
-
-1. The button can be activated using both the `Space` or `Enter` key.
-1. The button should have text or label that accurately describes the action of
- the button.
-1. If a description of the button's function is present, the button element
- should have an `aria-describedby` set to the ID of the element containing the
- description.
-1. After the button is activated ensure the focus is set correctly based on the
- type of action the button performs. See
- [W3C WAI-ARIA Authoring Practices Button Design Pattern](https://www.w3.org/TR/wai-aria-practices-1.1/#button)
- for a list of examples.
-
-## Resources
-
-- [W3C WAI-ARIA Authoring Practices Button Design Pattern](https://www.w3.org/TR/wai-aria-practices-1.1/#button)
- covers the usage of ARIA names, state and roles, as well as the expected
- keyboard interactions.
-- [IBM Accessibility Requirements:](https://www.ibm.com/able/requirements/requirements/)
- - [2.4.7 Focus Visible](https://www.ibm.com/able/requirements/requirements/#2_4_7)
- (WCAG Success Criteria
- [2.4.7](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible))
- - [3.2.2 On Input](https://www.ibm.com/able/requirements/requirements/#3_2_2)
- (WCAG Success Criteria
- [3.2.2](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/consistent-behavior-unpredictable-change.html))
-
-## Accessibility testing
-
-Accessibility issues are tracked in the
-[Carbon Design System GitHub repository](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+label%3A%22type%3A+a11y+%E2%99%BF%22+label%3A%22component%3A+button%22+).
-
-### Automated test
+## What Carbon provides
-
-
-
-
-
-
- Automated test environment
-
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome version 77.0.3865.90
-
- - Dynamic Assessment Plugin (DAP) version 1.8.0.0 - IBM
- Accessibility WCAG 2.1 Sept. 2019 Ruleset
- - Carbon React version 7.7.1
-
-
- DAP test:
- - No violations
-
-
-
-
-
-
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
+
+### Keyboard interactions
-### macOS screen reader tests
+Buttons can be reached by `Tab` and selected with `Space` or `Enter`.
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome version 77.0.3865.90
- - Carbon React version 7.7.1
-
-
- VoiceOver(VO) test:
-
-
- Tab to the first button, VO announces, "The button label".
-
-
- Clicking the Enter or Space key activates the button.
-
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Safari version 13.0.2
- - Carbon React version 7.7.1
-
-
- VoiceOver(VO) test:
-
-
- Tab to the first button, VO announces, "The button label".
-
-
- Clicking the Enter or Space key activates the button.
-
-
-
-
-
-
-
+
+
+![example of button keyboard interaction](images/button-accessibility-1.png)
+
+Carbon buttons retain expected interactions.
+
+
-### Windows screen reader tests
+### Behavior
+
+Icon-only butttons, which do not persistently display a text label, expose their
+label on hover and focus. When icon-only buttons are used to open menus, they
+are treated as separate components in Carbon. See
+[Dropdown](https://carbondesignsystem.com/components/dropdown/usage/) and
+[Overflow menu](https://carbondesignsystem.com/components/overflow-menu/usage/).
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - Microsoft Windows 10
-
- - Firefox version 67
-
- - JAWS 19.1810.64
- - Carbon React version 7.7.1
-
-
- JAWS test:
-
-
- Tab to the first button, JAWS announces, "The button label".
-
-
- Clicking the Enter or Space key activates the button.
-
-
-
-
-
-
- - Microsoft Windows 10
-
- - Chrome Version 73.0.3683.68 (Official Build) (64-bit)
-
- - JAWS Version 19.1810.64
- - Carbon React version 7.7.1
-
-
- JAWS test:
-
-
- Tab to the first button, JAWS announces, "The button label".
-
-
- Clicking the Enter or Space key activates the button.
-
-
-
-
-
-
- - Microsoft Windows 10
-
- - Chrome Version 73.0.3683.68 (Official Build) (64-bit)
-
- - NVDA Version 2018.4.1
- - Carbon React version 7.7.1
-
-
- NVDA test:
-
-
- Tab to the first button, NVDA announces, "The button label".
-
-
- Clicking the Enter or Space key activates the button.
-
-
-
-
-
-
-
-
+
+
+![a pointer hovering over an icon-only button shows the name ‘Close’](images/button-accessibility-2.png)
+
+
+ Icon-only buttons have their labels exposed automatically on hover and focus.
+
-### iOS screen reader tests
+
+
-
-
-
- Environment
- Results
-
-
-
-
- - iOS version 13.1.3 with VoiceOver
-
- - Safari version 13.1.3
- - Carbon React version 7.7.1
-
-
- VoiceOver test:
-
-
- Tab to the first button, VO announces, "The button label".
-
-
- Clicking the Enter or Space key activates the button.
-
-
-
-
-
-
-
+
+
+![an activated button reveals 3 options in a menu](images/button-accessibility-3.png)
+
+Buttons that open menus are separate components in Carbon.
+
-### Android screen reader tests
+## Design recommendations
+
+Design annotations are needed for the following instances.
+
+### Labeling
+
+When buttons do not have a persistently displayed label, they must be annotated
+with a label that will be exposed on hover or focus.
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - Android version 9 with Talkback
-
- - Chrome version 72.0.3683.68 (Official Build) (64-bit)
- - Carbon React version 7.7.1
-
-
- Talkback test:
-
-
- Tab to the first button, Talkback announces, "The button label".
-
-
- Clicking the Enter or Space key activates the button.
-
-
-
-
-
-
-
+
+
+![a button with a pencil icon has an annotation ‘label=Rename’](images/button-accessibility-4.png)
+
+
+ Annotate the label for icon-only buttons so the proper tooltip appears.
+
+
+
+
+## Development considerations
+
+Keep these considerations in mind if you are modifying Carbon or creating a
+custom component:
+
+- Where links have been ‘repurposed’ as a button, they need to be coded so the
+ `Space` key can also activate (since links are only activated by default by
+ `Enter`).
+- Toggle buttons can be accessibility supported by changing the value of
+ `aria-pressed` between `"true"` and `"false"` or with a change of name that
+ reflects a change in the icon shape (for example: "play" / "pause" )
+- See the
+ [ARIA authoring practices](https://www.w3.org/TR/wai-aria-practices-1.2/#button)
+ for more considerations.
diff --git a/src/pages/components/button/images/button-accessibility-1.png b/src/pages/components/button/images/button-accessibility-1.png
new file mode 100644
index 00000000000..674ddbcc06b
Binary files /dev/null and b/src/pages/components/button/images/button-accessibility-1.png differ
diff --git a/src/pages/components/button/images/button-accessibility-2.png b/src/pages/components/button/images/button-accessibility-2.png
new file mode 100644
index 00000000000..9df8c76301a
Binary files /dev/null and b/src/pages/components/button/images/button-accessibility-2.png differ
diff --git a/src/pages/components/button/images/button-accessibility-3.png b/src/pages/components/button/images/button-accessibility-3.png
new file mode 100644
index 00000000000..2cda88800d5
Binary files /dev/null and b/src/pages/components/button/images/button-accessibility-3.png differ
diff --git a/src/pages/components/button/images/button-accessibility-4.png b/src/pages/components/button/images/button-accessibility-4.png
new file mode 100644
index 00000000000..371f48883dd
Binary files /dev/null and b/src/pages/components/button/images/button-accessibility-4.png differ
diff --git a/src/pages/components/button/usage.mdx b/src/pages/components/button/usage.mdx
index 462e1b841b9..6bd64604fd8 100755
--- a/src/pages/components/button/usage.mdx
+++ b/src/pages/components/button/usage.mdx
@@ -46,8 +46,8 @@ interacts with it.
#### When to use
Use buttons to communicate actions users can take and to allow users to interact
-with the page. Each page should have one primary button, and any remaining calls
-to action should be represented as lower emphasis buttons.
+with the page. Each page should have only one primary button, and any remaining
+calls to action should be represented as lower emphasis buttons.
#### When not to use
@@ -595,18 +595,8 @@ Users can trigger a button by clicking anywhere within the button container.
#### Keyboard
Users can trigger a button by pressing `Enter` or `Space` while the button has
-focus. For additional keyboard interactions, see the accessibility tab.
-
-#### Screen readers
-
-VoiceOver: Users can trigger a button by pressing `Enter` or `Space` while the
-button has focus.
-
-JAWS: Users can trigger a button by pressing `Enter` or `Space` while the button
-has focus.
-
-NVDA: Users can trigger a button by pressing `Enter` or `Space` while the button
-has focus.
+focus. For additional keyboard interactions, see the
+[accessibility tab](/components/button/accessibility).
## Modifiers
diff --git a/src/pages/components/checkbox/accessibility.mdx b/src/pages/components/checkbox/accessibility.mdx
index 3c8796f0200..e03544f336e 100644
--- a/src/pages/components/checkbox/accessibility.mdx
+++ b/src/pages/components/checkbox/accessibility.mdx
@@ -6,417 +6,88 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import {
- StructuredListWrapper,
- StructuredListHead,
- StructuredListBody,
- StructuredListRow,
- StructuredListInput,
- StructuredListCell,
- OrderedList,
- ListItem,
-} from '@carbon/react';
+
+
+Design annotations are needed for specific instances shown below, but for the
+standard checkbox component, Carbon already incorporates accessibility.
+
+
- How it works
- Accessibility considerations
- Resources
- Accessibility testing
+ What Carbon provides
+ Design recommendations
+ Development considerations
-## How it works
+## What Carbon provides
-The Checkbox component is used to provide a list of options where the user can
-select multiple options, including all or none. A checkbox control has three
-possible states indicated by the value of its `aria-checked` attribute, “true”
-when selected, “false” when unselected and “mixed” when in the indeterminate
-state. The indeterminate state comes into play when the checkbox contains a
-sublist of selections, some of which are selected, and some unselected.
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
-The `Tab` key is used to move focus to each checkbox. Checkboxes identified as
-disabled are ignored in the tab order. The `Space` key is used to select and
-deselect each checkbox when the checkbox has focus. When the checkbox is
-selected the ARIA state is set to `aria-checked="true"` and when it is
-deselected `aria-checked="false"`. An indeterminable checkbox has an ARIA state
-that is set to `aria-checked="mixed"` until it is selected or deselected by the
-user. Fieldset and Legend elements are used for labeling the checkbox group.
+### Keyboard interactions
-## Accessibility considerations
+Each checkbox can be reached by `Tab` and selected with `Space` independently.
+This matches the established HTML interaction pattern.
+
+
+
-This component has been validated to meet the
-[WCAG 2.0 AA](https://www.w3.org/TR/WCAG20/) and
-[Section 508](http://www.section508.gov/) accessibility guidelines, however
-changes made by the content owner can affect accessibility compliance. Be sure
-to review and follow the guidance in this section when updating or adding new
-content to this component.
+![example of checkbox keyboard interaction](images/checkbox-accessibility-1.png)
-1. Checkboxes must have a clear and concise label.
-2. Users should be warned if selecting a checkbox will cause a change in
- context.
-3. If the checkbox is a required field include the
- [aria-required property](https://www.w3.org/TR/WCAG20-TECHS/ARIA2.html) and
- indicate that it is a required field and use the validation message for input
- errors.
+Carbon checkboxes retain expected interactions.
-## Resources
+
+
-#### Helpful resources for creating customized accessible implementations
+### Grouping
-- [W3C WAI-ARIA Authoring Practices Checkbox Design Pattern](https://www.w3.org/TR/wai-aria-practices/examples/checkbox/checkbox-1/checkbox-1.html)
- covers the usage of ARIA names, state and roles, as well as the expected
- keyboard interactions.
-- [IBM Accessibility Requirements:](https://www.ibm.com/able/requirements/requirements/)
- - [1.3.1 Information and Relationships](https://www.ibm.com/able/requirements/requirements/#1_3_1)
- (WCAG Success Criteria
- [1.3.1](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/content-structure-separation-programmatic.html))
- - [3.3.2 Labels or Instructions](https://www.ibm.com/able/requirements/requirements/#3_3_2)
- (WCAG Success Criteria
- [3.3.2](https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html))
- - [4.1.2 Name, Role, Value](https://www.ibm.com/able/requirements/requirements/#4_1_2)
- (WCAG Success Criteria
- [4.2.1](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value))
+For groups of checkboxes, Carbon already provides the code for screen readers to
+properly detect the set of checkboxes and announce the group label.
-## Accessibility testing
+
+
-Accessibility issues are tracked in the
-[Carbon Component GitHub repository](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+label%3A%22type%3A+a11y+%E2%99%BF%22+label%3A%22component%3A+checkbox%22+).
+![checkbox items with group label](images/checkbox-accessibility-2.png)
-### Automated test
+Carbon handles the accessibility of grouped checkboxes.
-
-
-
-
-
-
- Automated test environment
-
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome Version 77.0.3865.90
-
- - Dynamic Assessment Plugin Version 1.8.0.0 - IBM Accessibility WCAG
- 2.1 Sept. 2019 Ruleset
- - Carbon React Version 7.7.1
-
-
- DAP Test
- - Violations
-
-
-
-
-
+
-### macOS Screen reader tests
+## Design recommendations
-
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome Version 77.0.3865.90
- - Carbon React Version 7.7.1
-
-
- VoiceOver(VO) Test:
-
-
- Press the Tab key to navigate to the first checkbox. VO
- announces the label, the state as checked, that it is a checkbox
- input and the label group.
-
-
- Press the Space key to select or deselect the checkbox.
-
-
- Press the Tab key to navigate to the indeterminable checkbox. VO
- announces the label, and the state as mixed.
-
-
- Press the Space key to select or deselect the checkbox.
-
-
- Press the Tab key and the disabled checkbox is skipped.
-
-
- Control-Option-Left Arrow key to read the disabled field. VO
- announces, "Disabled checkbox, dimmed unchecked checkbox".
-
-
- Tab to the next group of checkboxes with the same results.
-
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Safari Version 13.0.2
- - Carbon React Version 7.7.1
-
-
- VoiceOver(VO) Test:
-
-
- Press the Tab key to navigate to the first checkbox. VO
- announces the label, the state as checked, the checkbox legend
- and the group.
-
-
- Press the Space key to select or deselect the checkbox.
-
-
- Press the Tab key to navigate to the indeterminable checkbox. VO
- announces the label, and the state as unchecked (Note: The mixed
- state is not announced).
-
-
- Press the Space key to select or deselect the checkbox.
-
-
- Press the Tab key and the disabled checkbox is skipped.
-
-
- Control-Option-Left Arrow key to read the disabled field. VO
- announces, "Off off dimmed unchecked checkbox".
-
-
- Tab to the next group of checkboxes with the same results.
-
-
-
-
-
-
-
-
+Design annotations are needed for the following instances.
+
+### Meaningful order
-### Windows screen reader tests
+Checkboxes can appear in multiple columns. If there is a meaningful order to the
+items (such as days of the week), annotate whether the tab order is by row or by
+column. See
+[Specify the tab order](https://www.ibm.com/able/toolkit/design/ux/navigation/#tab-order).
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - Microsoft Windows 10
-
- - Firefox Version 67
-
- - JAWS 19.1810.64
- - Carbon React Version 7.7.1
-
-
- JAWS test:
-
-
- Navigate among check boxes by pressing the Tab and Shift-Tab
- keys, or X and Shift+X keys to jump to next or previous
- checkboxes.
-
-
- When navigating to a checkbox, JAWS announces the label,
- checkbox, and the status of the checkbox.
-
-
- Disabled checkboxes can only be found by using the Up and Down
- Arrow keys, when JAWS.
-
-
- Press the Space key to select or deselect the checkbox. JAWS
- announces the status of checked or unchecked.
-
-
-
-
-
-
- - Microsoft Windows 10
-
- - Chrome Version 73.0.3683.103 (Official Build) (64-bit)
-
- - JAWS Version 19.1810.64
- - Carbon React Version 7.7.1
-
-
- JAWS test:
-
-
- Navigate among check boxes by pressing the Tab and Shift-Tab
- keys, or X and Shift+X keys to jump to next or previous
- checkboxes.
-
-
- When navigating to a checkbox, JAWS announces the label,
- checkbox, and the status of the checkbox.
-
-
- Disabled checkboxes can only be found by using the Up and Down
- Arrow keys, when JAWS announces "disabled checkbox checkbox
- unchecked unavailable".
-
-
- Press the Space key to select or deselect the checkbox. JAWS
- announces the status of checked or unchecked.
-
-
-
-
-
-
- - Microsoft Windows 10
-
- - Chrome Version 73.0.3683.103 (Official Build) (64-bit)
-
- - NVDA Version 2018.4.1
- - Carbon React Version 7.7.1
-
-
- NVDA test:
-
-
- Navigate among check boxes by pressing the Tab and Shift-Tab
- keys, or X and Shift+X keys to jump to next or previous
- checkboxes.
-
-
- When navigating to a checkbox, NVDA announces the label,
- checkbox, and the status of the checkbox, but repeats the
- information twice.
-
-
- When navigating to an indeterminable checkbox NVDA announces,
- "indeterminate checkbox indeterminate checkbox checkbox half
- checked".
-
-
- Disabled checkboxes can only be found by using the Up and Down
- Arrow keys, or the the X and Shift+X keys. NVDA announces
- "checkbox unavailable not checked disabled checkbox".
-
-
- Press the Space or Enter key to select or deselect the checkbox.
- NVDA announces the status of checked or unchecked.
-
-
-
-
-
-
-
-
+
-### Android screen reader tests
+![checkboxes with instruction to ‘navigate in columns'](images/checkbox-accessibility-3.png)
-
-
-
-
-
- Environment
- Results
-
-
-
-
-
- - Android Version 9 with Talkback
-
- - Chrome Version 73.0.3683.103 (Official Build) (64-bit)
- - Carbon React Version 7.7.1
-
-
- Talkback Test:
-
-
- Navigate to the checkbox by swiping left or right, or press the
- Left or Right Arrow keys. Talkback announces,the label, field
- type, and the status of the checkbox.
-
-
- The status of indeterminate checkboxes is not announced
- properly, Talkback only announces checked or unchecked.
-
-
- When tapping on a checkbox, or pressing the Alt-Enter keys,
- Talkback announces the new status of the checkbox as checked or
- not checked.
-
-
-
-
-
-
-
+
+ Annotate if there is meaningful navigation order in rows of checkboxes.
+
+
+
-### iOS screen reader tests
+## Development considerations
-
-
-
-
- Environment
- Results
-
-
-
-
- - iOS Version 13.1.3 with VoiceOver
-
- - Safari Version 13.1.3
- - Carbon React Version 7.7.1
-
-
- VoiceOver Test:
-
-
- Navigate to the checkbox by swiping left or right, or press the
- Left-Arrow or Right-Arrow keys when quick navigation is turned
- on. VO announces,the label, field type, and the status of the
- checkbox.
-
-
- The status of indeterminate checkboxes is not announced
- properly, VoiceOver only announces checked or unchecked.
-
-
- VoiceOver announces the beginning of the list, nesting level,
- content of the list item, the end of the list.
-
-
- When tapping on a checkbox, or pressing VO+Space, VoiceOver
- announces the new status of the checkbox as checked or
- unchecked.
-
-
-
-
-
-
-
-
+Keep these considerations in mind if you are modifying Carbon or creating a
+custom component:
+
+- Checkboxes are grouped using `` and ``.
+- A tri-state checkbox that is partially checked (indeterminate) has
+ `aria-checked` set to `"mixed"`. See
+ [Behaviors](https://carbondesignsystem.com/components/checkbox/usage/#behaviors)
+ on the Usage tab for details.
+- See the
+ [ARIA authoring practices](https://www.w3.org/TR/wai-aria-practices-1.2/#checkbox)
+ for more considerations.
diff --git a/src/pages/components/checkbox/images/checkbox-accessibility-1.png b/src/pages/components/checkbox/images/checkbox-accessibility-1.png
new file mode 100644
index 00000000000..23bab2cb2de
Binary files /dev/null and b/src/pages/components/checkbox/images/checkbox-accessibility-1.png differ
diff --git a/src/pages/components/checkbox/images/checkbox-accessibility-2.png b/src/pages/components/checkbox/images/checkbox-accessibility-2.png
new file mode 100644
index 00000000000..d253dc7f2fc
Binary files /dev/null and b/src/pages/components/checkbox/images/checkbox-accessibility-2.png differ
diff --git a/src/pages/components/checkbox/images/checkbox-accessibility-3.png b/src/pages/components/checkbox/images/checkbox-accessibility-3.png
new file mode 100644
index 00000000000..124cf438a78
Binary files /dev/null and b/src/pages/components/checkbox/images/checkbox-accessibility-3.png differ
diff --git a/src/pages/components/code-snippet/accessibility.mdx b/src/pages/components/code-snippet/accessibility.mdx
index 733cf13a51b..2e5961cf2b3 100644
--- a/src/pages/components/code-snippet/accessibility.mdx
+++ b/src/pages/components/code-snippet/accessibility.mdx
@@ -19,79 +19,89 @@ import {
-The code snippet React Carbon component has been tested against the latest
-[W3C Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA success criteria](https://www.w3.org/TR/WCAG21/)
-and violations have been identified as high priority issues. This document will
-be updated when these accessibility issues are resolved.
+No accessibility annotations are needed for code snippets, but keep these
+considerations in mind if you’re modifying Carbon or creating a custom
+component.
- How it works
- Accessibility considerations
- Resources
- Accessibility testing
+ What Carbon provides
+ Development considerations
-## Accessibility considerations
+## What Carbon provides
-1. The code snippet copy button can be activated using both the `Space` or
- `Enter` key.
-2. The code snippet copy button label accurately describes what the button does.
-3. After the button is activated the focus remains on the button since there is
- no change in context.
+Carbon bakes keyboard operation into its components, as well as many other
+accessibility considerations.
-## Resources
+### Keyboard interaction
-- [W3C WAI-ARIA Authoring Practices Button Design Pattern](https://www.w3.org/TR/wai-aria-practices-1.1/#buttonn)
- covers the usage of ARIA names, state and roles, as well as the expected
- keyboard interactions.
-- [IBM Accessibility Requirements:](https://www.ibm.com/able/requirements/requirements/)
- - [2.4.7 Focus Visible](https://www.ibm.com/able/requirements/requirements/#2_4_7)
- (WCAG Success Criteria
- [2.4.7](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible))
- - [3.2.2 On Input](https://www.ibm.com/able/requirements/requirements/#3_2_2)
- (WCAG Success Criteria
- [3.2.2](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/consistent-behavior-unpredictable-change.html))
+For all three variants, the code snippet can be copied with `Space` or `Enter`.
+Arrow keys can operate scroll bars.
-## Accessibility testing
+
+
+
+![inline code snippet keyboard interaction](images/code-snippet-accessibility-1.png)
-Automated, manual and screen reader accessibility verification test has been
-performed on the code snippet React Carbon component.
-[WCAG 2.1 Level A and AA success criteria](https://www.w3.org/TR/WCAG21/) issues
-have been identified and the list of open accessibility violations is available
-in the Carbon Component GitHub repository.
+
+
-### Automated test
+By default, each inline code snippet is reachable by `Tab` and copied with
+`Space` or `Enter`.
-
-
-
-
-
- Automated test environment
-
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome version 77.0.3865.90
-
- - Dynamic Assessment Plugin (DAP) version 1.8.0.0 - IBM
- Accessibility WCAG 2.1 Sept. 2019 Ruleset
- - Carbon React version 7.7.1
-
-
- DAP test:
- - Violations
-
-
-
-
-
+
+
+![single line code snippet interaction, with 2 tab stops](images/code-snippet-accessibility-2.png)
+
+
+
+The single line code snippet tabstop supports left and right arrow key
+scrolling.
+
+
+
+
+![multi-line code snippet keyboard interaction](images/code-snippet-accessibility-3.png)
+
+
+
+
+The multi-line’s buttons are reachable by `Tab` and activated with `Space` or
+`Enter`.
+
+### Labeling and updates
+
+Carbon provides the copy button's default label and tooltip behavior. Carbon
+handles notices about the success of the copy function, as well as updates to
+the Show more mechanism.
+
+
+
+
+![hovering on the button exposes ‘copy to clipboard’ tooltip](images/code-snippet-accessibility-4.png)
+
+
+
+
+The code snippet’s buttons expose their labels on hover or focus.
+
+
+
+
+![the activated button shows a ‘copied!’ message](images/code-snippet-accessibility-5.png)
+
+
+
+
+The results of activating buttons are provided in text.
+
+## Development considerations
+
+Keep this in mind if you’re modifying Carbon or creating a custom component:
+
+- the inline code text is implemented as a button so its text can be copied
+- single line snippets take an additional tabstop to support arrow key scrolling
diff --git a/src/pages/components/code-snippet/images/code-snippet-accessibility-1.png b/src/pages/components/code-snippet/images/code-snippet-accessibility-1.png
new file mode 100644
index 00000000000..c7eb680567b
Binary files /dev/null and b/src/pages/components/code-snippet/images/code-snippet-accessibility-1.png differ
diff --git a/src/pages/components/code-snippet/images/code-snippet-accessibility-2.png b/src/pages/components/code-snippet/images/code-snippet-accessibility-2.png
new file mode 100644
index 00000000000..fa7fb046914
Binary files /dev/null and b/src/pages/components/code-snippet/images/code-snippet-accessibility-2.png differ
diff --git a/src/pages/components/code-snippet/images/code-snippet-accessibility-3.png b/src/pages/components/code-snippet/images/code-snippet-accessibility-3.png
new file mode 100644
index 00000000000..a0e55b9d195
Binary files /dev/null and b/src/pages/components/code-snippet/images/code-snippet-accessibility-3.png differ
diff --git a/src/pages/components/code-snippet/images/code-snippet-accessibility-4.png b/src/pages/components/code-snippet/images/code-snippet-accessibility-4.png
new file mode 100644
index 00000000000..6e32284e62e
Binary files /dev/null and b/src/pages/components/code-snippet/images/code-snippet-accessibility-4.png differ
diff --git a/src/pages/components/code-snippet/images/code-snippet-accessibility-5.png b/src/pages/components/code-snippet/images/code-snippet-accessibility-5.png
new file mode 100644
index 00000000000..7b4805c96aa
Binary files /dev/null and b/src/pages/components/code-snippet/images/code-snippet-accessibility-5.png differ
diff --git a/src/pages/components/code-snippet/usage.mdx b/src/pages/components/code-snippet/usage.mdx
index 122f02f7632..8e24c7161db 100644
--- a/src/pages/components/code-snippet/usage.mdx
+++ b/src/pages/components/code-snippet/usage.mdx
@@ -263,14 +263,8 @@ manually highlighting the text and right clicking "copy".
- Show more or less code by pressing `Space` or `Enter` while the ghost button
is in focus.
-#### Screen readers
-
-- VoiceOver: Users can copy code by pressing `Space` while the copy button has
- screen reader focus.
-- JAWS: Users can copy code by pressing `Space` while the copy button has screen
- reader focus.
-- NVDA: Users can copy code by pressing `Space` while the copy button has screen
- reader focus.
+For additional keyboard interactions, see the
+[accessibility tab](/components/code-snippet/accessibility#keyboard-interaction).
## Inline
@@ -329,8 +323,8 @@ Use multi-line code snippets for displaying multiple lines of code.
#### Show more button
-A ghost button can be added to a multi-line code snippet to show more or fewer
-lines of code. Use this functionality if your layout is tight on space.
+A Show more ghost button can be added to a multi-line code snippet to show more
+or fewer lines of code. Use this functionality if your layout is tight on space.
diff --git a/src/pages/components/data-table/accessibility.mdx b/src/pages/components/data-table/accessibility.mdx
index 26422c99642..2e28a2d8a77 100644
--- a/src/pages/components/data-table/accessibility.mdx
+++ b/src/pages/components/data-table/accessibility.mdx
@@ -6,109 +6,98 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import {
- StructuredListWrapper,
- StructuredListHead,
- StructuredListBody,
- StructuredListRow,
- StructuredListInput,
- StructuredListCell,
- OrderedList,
- ListItem,
-} from '@carbon/react';
-
-The data table React Carbon component has been tested against the latest
-[W3C Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA success criteria](https://www.w3.org/TR/WCAG21/)
-and violations have been identified as high priority issues. This document will
-be updated when these accessibility issues are resolved.
+Design annotations are needed for specific instances shown below, but for the
+standard data table component, Carbon already incorporates accessibility.
- Accessibility considerations
- Resources
- Accessibility testing
+ What Carbon provides
+ Design recommendations
+ Development considerations
-## Accessibility considerations
-
-1. The data table headers accurately describe the data contained in the rows and
- columns.
-2. If the data table has a labels it should be clear and concise.
-3. If the data table has a caption or description, `aria-describedby` should be
- set on the table element with a value referring to the element containing the
- description.
-
-## Resources
-
-- [W3C WAI-ARIA Authoring Practices Table Design Pattern](https://www.w3.org/TR/wai-aria-practices-1.1/#table)
- covers the usage of ARIA names, state and roles, as well as the expected
- keyboard interactions.
-- [W3C Tutorial - Table Concepts](https://www.w3.org/WAI/tutorials/tables/)
- covers the usage of various tables, headers, and captions.
-- [IBM Accessibility Requirements](https://www.ibm.com/able/requirements/requirements/):
- - [1.3.1 Info and Relationships](https://www.ibm.com/able/requirements/requirements/#1_3_1)
- (WCAG Success Criteria
- [1.3.1](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships))
- - [1.3.2 Meaningful Sequence](https://www.ibm.com/able/requirements/requirements/#1_3_2)
- (WCAG Success Criteria
- [1.3.2](https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence))
- - [2.1.1 Keyboard](https://www.ibm.com/able/requirements/requirements/#2_1_1)
- (WCAG Success Criteria
- [2.1.1](https://www.w3.org/WAI/WCAG21/Understanding/keyboard))
- - [2.4.3 Focus Order](https://www.ibm.com/able/requirements/requirements/#2_4_3)
- (WCAG Success Criteria
- [2.4.3](https://www.w3.org/WAI/WCAG21/Understanding/focus-order))
- - [2.4.6 Headings and Labels](https://www.ibm.com/able/requirements/requirements/#2_4_6)
- (WCAG Success Criteria
- [2.4.6](https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels))
- - [2.4.7 Focus Visible](https://www.ibm.com/able/requirements/requirements/#2_4_7)
- (WCAG Success Criteria
- [2.4.7](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible))
- - [4.1.2 Name, Role, Value](https://www.ibm.com/able/requirements/requirements/#4_1_2)
- (WCAG Success Criteria
- [4.1.2](https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html))
-
-## Accessibility testing
-
-Automated, manual and screen reader accessibility verification test has been
-performed on the data table React Carbon component.
-[WCAG 2.1 Level A and AA success criteria](https://www.w3.org/TR/WCAG21/) issues
-have been identified and the list of open accessibility violations is available
-in the Carbon Component GitHub repository.
-
-### Automated test
+## What Carbon provides
+
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
+
+### Keyboard interaction
+
+There are three data table variants with different interactions. Optional
+features like column sorting can appear in any of the variants. Table
+[pagination](https://www.carbondesignsystem.com/components/pagination/usage/) is
+treated as a separate component.
+
+
+
+
+![sortable table keyboard interaction](images/datatable-accessibility-1.png)
+
+
+
+
+For sortable tables, the column headers are reachable by `Tab` and sortable with
+`Space` or `Enter`.
+
+### Controls inside tables
+
+Any interactive controls in data cells are in the tab order and maintain normal
+keyboard operation. This also applies to expandable table rows, which operate in
+the same manner as
+[accordions](https://www.carbondesignsystem.com/components/accordions/usage/)
+
+
+
+
+![tab order proceeds sequentially through the table row expansion icons then to a link inside an expanded row](images/datatable-accessibility-2.png)
+
+
+
+
+Links, inputs, and other interactive controls inside tables operate by keyboard
+as normal.
+
+### Labeling and updates
+
+If columns are sortable, the sort symbols appear on hover or focus. A sorted
+column retains an indicator until it is no longer sorted.
-
-
-
-
-
- Automated test environment
-
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.2 with VoiceOver
-
- - Chrome version 77.0.3865.90
-
- - Dynamic Assessment Plugin (DAP) version 1.8.0.0 - IBM
- Accessibility WCAG 2.1 Sept. 2019 Ruleset
- - Carbon React version 7.7.1
-
-
- DAP test:
- - Violations
-
-
-
-
-
+
+
+![The Rule column header has focus and shows a sortable icon, and the Status column header has a 'sorted ascending' icon](images/datatable-accessibility-3.png)
+
+
+
+Sort indicators appear on hover and focus. A sorted column is indicated
+visually.
+
+## Design recommendations
+
+Since there is no persistent visual indicator that a table is sortable,
+designers need to annotate if a table should be implemented with sortable column
+headers.
+
+
+
+
+![the header row is annotated 'sortable headers'](images/datatable-accessibility-4.png)
+
+
+
+
+Annotate if a table is sortable.
+
+## Development considerations
+
+Keep this in mind if you’re modifying Carbon or creating a custom component:
+
+- Column sorting indicators are matched programmatically using `aria-sort`
+- See the
+ [ARIA authoring practices](https://www.w3.org/TR/wai-aria-practices-1.2/#table)
+ for more considerations
diff --git a/src/pages/components/data-table/code.mdx b/src/pages/components/data-table/code.mdx
index 5e193b810d7..9f4c9583ab9 100644
--- a/src/pages/components/data-table/code.mdx
+++ b/src/pages/components/data-table/code.mdx
@@ -7,11 +7,7 @@ tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
import { rowData, headerData } from '../../../data/components/data-table.js';
-import {
- Delete16 as Delete,
- Save16 as Save,
- Download16 as Download,
-} from '@carbon/icons-react';
+import { TrashCan, Save, Download } from '@carbon/icons-react';
@@ -26,7 +22,7 @@ usage documentation, see the Storybooks for each framework below.
@@ -86,7 +82,7 @@ usage documentation, see the Storybooks for each framework below.
label: 'With batch actions',
},
]}
- scope={{ rowData, headerData, React, Delete, Save, Download }}
+ scope={{ rowData, headerData, React, TrashCan, Save, Download }}
>
console.log('clicked')}
>
Delete
diff --git a/src/pages/components/data-table/images/datatable-accessibility-1.png b/src/pages/components/data-table/images/datatable-accessibility-1.png
new file mode 100644
index 00000000000..d4780ed7706
Binary files /dev/null and b/src/pages/components/data-table/images/datatable-accessibility-1.png differ
diff --git a/src/pages/components/data-table/images/datatable-accessibility-2.png b/src/pages/components/data-table/images/datatable-accessibility-2.png
new file mode 100644
index 00000000000..7ece2742247
Binary files /dev/null and b/src/pages/components/data-table/images/datatable-accessibility-2.png differ
diff --git a/src/pages/components/data-table/images/datatable-accessibility-3.png b/src/pages/components/data-table/images/datatable-accessibility-3.png
new file mode 100644
index 00000000000..13b3bf6f9ec
Binary files /dev/null and b/src/pages/components/data-table/images/datatable-accessibility-3.png differ
diff --git a/src/pages/components/data-table/images/datatable-accessibility-4.png b/src/pages/components/data-table/images/datatable-accessibility-4.png
new file mode 100644
index 00000000000..445f7cfb1dc
Binary files /dev/null and b/src/pages/components/data-table/images/datatable-accessibility-4.png differ
diff --git a/src/pages/components/data-table/usage.mdx b/src/pages/components/data-table/usage.mdx
index ed2924d3090..e788a738191 100755
--- a/src/pages/components/data-table/usage.mdx
+++ b/src/pages/components/data-table/usage.mdx
@@ -59,11 +59,7 @@ table display settings, and other utilities.
## Live demo
import { rowData, headerData } from '../../../data/components/data-table.js';
-import {
- Delete16 as Delete,
- Save16 as Save,
- Download16 as Download,
-} from '@carbon/icons-react';
+import { TrashCan, Save, Download } from '@carbon/icons-react';
console.log('clicked')}
>
Delete
diff --git a/src/pages/components/notification/images/notification-style-1.png b/src/pages/components/notification/images/notification-style-1.png
new file mode 100644
index 00000000000..41517b0f9ed
Binary files /dev/null and b/src/pages/components/notification/images/notification-style-1.png differ
diff --git a/src/pages/components/notification/images/notification-style-2.png b/src/pages/components/notification/images/notification-style-2.png
new file mode 100644
index 00000000000..135b5ec6351
Binary files /dev/null and b/src/pages/components/notification/images/notification-style-2.png differ
diff --git a/src/pages/components/notification/images/notification-style-3.png b/src/pages/components/notification/images/notification-style-3.png
new file mode 100644
index 00000000000..074126d6c7f
Binary files /dev/null and b/src/pages/components/notification/images/notification-style-3.png differ
diff --git a/src/pages/components/notification/images/notification-style-4.png b/src/pages/components/notification/images/notification-style-4.png
new file mode 100644
index 00000000000..efe49b42b37
Binary files /dev/null and b/src/pages/components/notification/images/notification-style-4.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-style-1.png b/src/pages/components/progress-bar/images/progress-bar-style-1.png
new file mode 100644
index 00000000000..d22d6bc45c3
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-style-1.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-style-2.png b/src/pages/components/progress-bar/images/progress-bar-style-2.png
new file mode 100644
index 00000000000..c2457f8653f
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-style-2.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-style-3.png b/src/pages/components/progress-bar/images/progress-bar-style-3.png
new file mode 100644
index 00000000000..ea254969b65
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-style-3.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-style-4.png b/src/pages/components/progress-bar/images/progress-bar-style-4.png
new file mode 100644
index 00000000000..3fb5f477b2b
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-style-4.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-style-5.png b/src/pages/components/progress-bar/images/progress-bar-style-5.png
new file mode 100644
index 00000000000..50d2723f864
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-style-5.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-style-6.png b/src/pages/components/progress-bar/images/progress-bar-style-6.png
new file mode 100644
index 00000000000..302fa8cb167
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-style-6.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-1.png b/src/pages/components/progress-bar/images/progress-bar-usage-1.png
new file mode 100755
index 00000000000..84870e58c1a
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-1.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-10.png b/src/pages/components/progress-bar/images/progress-bar-usage-10.png
new file mode 100644
index 00000000000..7a42a69220e
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-10.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-11.gif b/src/pages/components/progress-bar/images/progress-bar-usage-11.gif
new file mode 100755
index 00000000000..298f6c87cf9
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-11.gif differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-11.png b/src/pages/components/progress-bar/images/progress-bar-usage-11.png
new file mode 100644
index 00000000000..52afbef1beb
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-11.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-12.png b/src/pages/components/progress-bar/images/progress-bar-usage-12.png
new file mode 100644
index 00000000000..f63733e8593
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-12.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-13.png b/src/pages/components/progress-bar/images/progress-bar-usage-13.png
new file mode 100644
index 00000000000..4ce9253d2a2
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-13.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-14.png b/src/pages/components/progress-bar/images/progress-bar-usage-14.png
new file mode 100755
index 00000000000..85614734d52
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-14.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-15.png b/src/pages/components/progress-bar/images/progress-bar-usage-15.png
new file mode 100755
index 00000000000..d4a6e3d496e
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-15.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-16.png b/src/pages/components/progress-bar/images/progress-bar-usage-16.png
new file mode 100644
index 00000000000..d22d6bc45c3
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-16.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-17.gif b/src/pages/components/progress-bar/images/progress-bar-usage-17.gif
new file mode 100644
index 00000000000..625fbbdea66
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-17.gif differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-17.png b/src/pages/components/progress-bar/images/progress-bar-usage-17.png
new file mode 100644
index 00000000000..41a796098d2
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-17.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-18.gif b/src/pages/components/progress-bar/images/progress-bar-usage-18.gif
new file mode 100755
index 00000000000..7920f6bfd77
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-18.gif differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-18.png b/src/pages/components/progress-bar/images/progress-bar-usage-18.png
new file mode 100644
index 00000000000..17015ee28ff
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-18.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-19.png b/src/pages/components/progress-bar/images/progress-bar-usage-19.png
new file mode 100644
index 00000000000..2d68e350a58
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-19.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-2.gif b/src/pages/components/progress-bar/images/progress-bar-usage-2.gif
new file mode 100755
index 00000000000..7ee1487704b
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-2.gif differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-20.png b/src/pages/components/progress-bar/images/progress-bar-usage-20.png
new file mode 100644
index 00000000000..73bbb6956b3
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-20.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-21.gif b/src/pages/components/progress-bar/images/progress-bar-usage-21.gif
new file mode 100644
index 00000000000..69ce7c07089
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-21.gif differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-21.png b/src/pages/components/progress-bar/images/progress-bar-usage-21.png
new file mode 100644
index 00000000000..f9cc483291b
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-21.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-22.png b/src/pages/components/progress-bar/images/progress-bar-usage-22.png
new file mode 100644
index 00000000000..69229aaa3a6
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-22.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-3.gif b/src/pages/components/progress-bar/images/progress-bar-usage-3.gif
new file mode 100755
index 00000000000..6bba97a8f60
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-3.gif differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-4.gif b/src/pages/components/progress-bar/images/progress-bar-usage-4.gif
new file mode 100755
index 00000000000..3dba814db44
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-4.gif differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-4.png b/src/pages/components/progress-bar/images/progress-bar-usage-4.png
new file mode 100644
index 00000000000..cc644b754f7
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-4.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-5.gif b/src/pages/components/progress-bar/images/progress-bar-usage-5.gif
new file mode 100755
index 00000000000..764d2679cfc
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-5.gif differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-5.png b/src/pages/components/progress-bar/images/progress-bar-usage-5.png
new file mode 100644
index 00000000000..6a41cc4e6be
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-5.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-6.png b/src/pages/components/progress-bar/images/progress-bar-usage-6.png
new file mode 100644
index 00000000000..09f3a6606e3
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-6.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-7.png b/src/pages/components/progress-bar/images/progress-bar-usage-7.png
new file mode 100644
index 00000000000..d02a784744f
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-7.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-8.png b/src/pages/components/progress-bar/images/progress-bar-usage-8.png
new file mode 100644
index 00000000000..3652b2897e7
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-8.png differ
diff --git a/src/pages/components/progress-bar/images/progress-bar-usage-9.png b/src/pages/components/progress-bar/images/progress-bar-usage-9.png
new file mode 100644
index 00000000000..9d44bf5f3fd
Binary files /dev/null and b/src/pages/components/progress-bar/images/progress-bar-usage-9.png differ
diff --git a/src/pages/components/progress-bar/style.mdx b/src/pages/components/progress-bar/style.mdx
new file mode 100644
index 00000000000..a02829be271
--- /dev/null
+++ b/src/pages/components/progress-bar/style.mdx
@@ -0,0 +1,105 @@
+---
+title: Progress bar
+description:
+ A progress bar provides feedback about the duration and progression of a
+ process.
+tabs: ['Usage', 'Style']
+---
+
+## Color
+
+| Element | Property | Color token |
+| ------------- | ---------- | --------------------- |
+| Label | text color | `$text-primary` |
+| Helper text | text color | `$text-helper` |
+| Track | background | `$border-subtle` |
+| Bar: active | background | `$border-interactive` |
+| Bar: success | background | `$support-success` |
+| Icon: success | fill | `$support-success` |
+| Bar: error | background | `$support-error` |
+| Icon: error | fill | `$support-error` |
+
+
+
+
+![Progress bar status colors](images/progress-bar-style-1.png)
+
+Status colors
+
+
+
+
+
+
+
+![Progress bar status colors](images/progress-bar-style-2.png)
+
+Progress bar colors for light themes
+
+
+
+
+
+
+
+![Progress bar status colors](images/progress-bar-style-3.png)
+
+Progress bar colors for dark themes
+
+
+
+
+## Typography
+
+| Element | Font-size (px/rem) | Font-weight | Type token |
+| ----------- | ------------------ | ------------- | ----------------- |
+| Label | 14px / 0.875rem | Regular / 400 | `$label-01` |
+| Helper text | 12px / 0.75rem | Regular / 400 | `$helper-text-01` |
+
+## Structure
+
+Depending on the use case, progress bar can have three ways for text alignment:
+default, inline, and indented. The width of a progress bar can be customized
+appropriately for its context. The minimum width of a progress bar is 48px and
+keep its width to a maximum of six columns when possible.
+
+| Element | Property | px / rem | Spacing token |
+| -------------------- | -------------- | -------- | ------------- |
+| Label (top aligned) | padding-bottom | 8 / 0.5 | `$spacing-03` |
+| Helper text | padding-top | 8 / 0.5 | `$spacing-03` |
+| Label (left aligned) | padding-right | 16 / 1 | `$spacing-05` |
+
+
+
+![Structure and spacing measurements for the progress bar.](images/progress-bar-style-4.png)
+
+
+
+
+ Structure and spacing measurements the progress bar | px / rem
+
+
+
+
+![Structure and spacing measurements for the progress bar with an icon.](images/progress-bar-style-5.png)
+
+
+
+
+ Structure and spacing measurements the progress bar with an icon | px / rem
+
+
+## Sizes
+
+There are two sizes for the progress bar height, big and small.
+
+| Size | Height px / rem |
+| ----- | --------------- |
+| Big | 8 / 0.5 |
+| Small | 4 / 0.25 |
+
+
+
+![Progress bar sizes](images/progress-bar-style-6.png)
+
+
diff --git a/src/pages/components/progress-bar/usage.mdx b/src/pages/components/progress-bar/usage.mdx
new file mode 100644
index 00000000000..c475a6f49c0
--- /dev/null
+++ b/src/pages/components/progress-bar/usage.mdx
@@ -0,0 +1,500 @@
+---
+title: Progress bar
+description:
+ A progress bar provides feedback about the duration and progression of a
+ process.
+tabs: ['Usage', 'Style']
+---
+
+import localVideo from './videos/progress-bar-usage-4.mp4';
+import localPoster from './images/progress-bar-usage-4.png';
+
+import localVideo1 from './videos/progress-bar-usage-5.mp4';
+import localPoster1 from './images/progress-bar-usage-5.png';
+
+import localVideo2 from './videos/progress-bar-usage-11.mp4';
+import localPoster2 from './images/progress-bar-usage-11.png';
+
+import localVideo3 from './videos/progress-bar-usage-17.mp4';
+import localPoster3 from './images/progress-bar-usage-17.png';
+
+import localVideo4 from './videos/progress-bar-usage-18.mp4';
+import localPoster4 from './images/progress-bar-usage-18.png';
+
+import localVideo5 from './videos/progress-bar-usage-21.mp4';
+import localPoster5 from './images/progress-bar-usage-21.png';
+
+
+
+A progress bar provides feedback about the duration and progression of a
+process, such as a download, file transfer, or installation, to indicate how
+long a user will be waiting.
+
+
+
+
+
+Overview
+Live demo
+Variants
+Formatting
+Content
+Universal behaviors
+Modifiers
+Accessibility
+Related
+References
+Feedback
+
+
+
+## Overview
+
+A progress bar indicates that the user's request has been received and the
+application is making progress toward completing the requested action. Progress
+bars inform users about the status of ongoing processes, the estimated time of
+how long a process will take, or if a request is being executed.
+
+
+
+
+![Progress bar hero image](images/progress-bar-usage-1.png)
+
+
+
+
+#### When to use
+
+- For a long operation or a process that can take a considerable or unknown
+ amount of time
+- When the process can be described with quantitative information, such as a
+ percentage
+- To visually show the progression of a system operation such as downloading,
+ uploading, loading data, submitting a form, or saving updates
+- To convey that data is being requested, transferred, or processed
+
+#### When not to use
+
+- When the load time is expected to display expanded information, use skeleton
+ states instead
+- When manual user actions are required to progress, use a
+ [progress indicator](/components/progress-indicator/usage) instead
+- When the progress is determined by user actions such as tutorials completed,
+ or storage space, rather than system actions
+- If the process takes less than 5 seconds to load, use
+ [loading spinners](/components/loading/usage) instead
+
+## Live demo
+
+## Variants
+
+A progress bar can either be determinate or indeterminate. The determinate
+variant is visualized as a track on which a bar fills up from left to right
+representing the progress. The indeterminate variant is visualized as a track on
+which a bar is moving along in constant speed, repeating over time.
+
+| Variant | Purpose |
+| -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- |
+| [Determinate](Determinate) | Use determinate progress bars for a specified amount of time for clear information about the progression — they convey exact and qualitative information about the progression. | |
+| [Indeterminate](/components/progress-bar/usage#indeterminate-progress-bar) | Use indeterminate progress bars for an unspecified completion of time or unclear information about the progression — they convey that users’ request, action, or data is being processed at the moment without indicating how long the activity will take. |
+
+
+
+
+![Determinate progress bars fill from 0 to 100%.](images/progress-bar-usage-2.gif)
+
+
+ Determinate progress bars fill from 0 to 100%.
+
+
+
+
+
+![Indeterminate progress bars move along a fixed track continually until the process is complete.](images/progress-bar-usage-3.gif)
+
+
+ Indeterminate progress bars move along a fixed track continually until the process is complete.
+
+
+
+
+## Determinate progress bar
+
+Determinate progress bars are used when the loading progress can be tracked and
+translated into a percentage indicator which fills from 0% to 100% and never
+decreases in value. The entire animation moves from the left to the right — with
+no back and forth motion.
+
+Use a determinate progress bar when the progress can be calculated against a
+specific goal. For example, when downloading a file of a known size.
+
+## Indeterminate progress bar
+
+Indeterminate progress bars are used when the loading progress is unknown or the
+amount of wait time can't be calculated.
+
+Once triggered, the loading bar will begin by moving along in constant speed,
+repeating over time while data is being gathered during the first stages of the
+load. This bar then changes to a determinate indicator (finishing from left to
+right) when enough information is gathered to end the load animation. The final
+determinate stage of the load is used to visually indicate the completion of the
+task to the user. In this scenario, a percentage indicator would not be present.
+
+
+
+
+
+
+
+### Progress status
+
+It's best to give the user transparency about the process which usually leads to
+increased trust in the software or platform. However, it may not be possible to
+provide progress estimation in certain cases. If progress data is not available,
+an indeterminate progress bar can be used.
+
+As a more concrete set of examples, there are generally three different major
+progressions of a system operation: downloading, uploading, and local
+processing.
+
+#### Downloading
+
+For downloading actions, it's usually possible to get a value of progress and
+update it in real time for a determinate progress bar. Depending on the
+information reported from a data source, time remaining could be estimated based
+on how much has been downloaded so far over a time period.
+
+#### Uploading
+
+Upload actions may be unable to report real time progress status depending on
+the data source and API configuration. However, always strive to provide users
+the determinate value whenever it's possible to inform them about the process.
+
+#### Data processing
+
+Data processing refers to manipulations of data to produce meaningful
+information. This can include currency exchange, file generation, data
+reformatting, or similar operations. Depending on the operation, time estimated
+or cycles to complete processing could be used to populate a determinate
+progress bar.
+
+## Formatting
+
+### Anatomy
+
+
+
+
+![Progress bar anatomy](images/progress-bar-usage-6.png)
+
+
+
+
+1. **Label:** The text describes the process that the progress bar refers to.
+ The label can be visually hidden, but must be defined in order to be
+ accessible.
+2. **Track:** The static area that the bar indicator moves on top of and acts as
+ a fixed visual reference of what the total length and duration of the process
+ could be.
+3. **Bar indicator:** Indicates how much the process has progressed.
+4. **Helper text (optional):** Assistive text to show additional information
+ about the process taking place. For determinate, the information is usually
+ values of number or percentage. Sometimes, a fraction or ratio may be shown.
+ These values are not applicable when a progress bar is indeterminate.
+
+### Sizing
+
+#### Height
+
+The progress bar is offered in two different sizes—big (8px) and small (4px).
+The big progress bar height is typically used when there is large amounts of
+space on a page. The small progress bar height is commonly used when space is
+restricted and can be placed within cards, data tables, or side panels.
+
+
+
+
+![Progress bar sizes](images/progress-bar-usage-7.png)
+
+
+
+
+#### Width
+
+The width of a progress bar can vary based on the content. The minimum width of
+a progress bar is 48px and keep its width to a maximum of six columns when
+possible. If the progress bar width is too long, it can reduce readability.
+Don't increase the progress bar length to fill the entire width of a window or
+application.
+
+
+
+
+
+![Do keep a width within six columns.](images/progress-bar-usage-8.png)
+
+
+
+
+![Do not exceed a width of six columns.](images/progress-bar-usage-9.png)
+
+
+
+
+### Alignment
+
+Text alignment depends on the context and area given. Progress bar can have
+three ways for text alignment: default, inline, and indent. Indent alignment
+should only be used inside containers, tiles, or side panels which the progress
+bar will extend to the edges.
+
+
+
+
+![Progress bar alignments](images/progress-bar-usage-10.png)
+
+A few common examples of text alignment for progress bars
+
+
+
+
+
+
+
+![Progress bar alignments](images/progress-bar-usage-22.png)
+
+
+
+
+| Text alignment | Use case |
+| -------------- | ----------------------------------------- |
+| Default | Full page, cards, dialogs |
+| Inline | Data table |
+| Indent | Side panels, cards (usually on dashboard) |
+
+#### Text placement
+
+Labels or helper text should always be placed above, below, or beside the
+progress bar for readability. Avoid placing text inside or centering text with
+the progress bar. This visual could cause clutter and inconsistency in text
+alignment. Meanwhile, placing the text far away from the progress bar could
+cause confusion in the context.
+
+
+
+
+![Do place text inline with the progress bar.](images/progress-bar-usage-12.png)
+
+
+
+
+![Do not place the label far away from the progress bar](images/progress-bar-usage-13.png)
+
+
+
+
+
+
+
+![Do place the label close to the progress bar](images/progress-bar-usage-14.png)
+
+
+
+
+![Do not place the label far away from the progress bar](images/progress-bar-usage-15.png)
+
+
+
+
+#### Internationalization (RTL)
+
+For RTL (right-to-left) languages, the layout of the progress bar is mirrored
+for both determinate and indeterminate options. The label is right-aligned, the
+value is left-aligned, and the fill progresses from right to left. Keep in mind
+that the placement of the percent sign differs depending on the locale.
+
+
+
+
+
+
+
+## Content
+
+Determinate and indeterminate progress bars both have a label and an optional
+helper text. However, the indeterminate can’t provide the exact, quantitative
+information about the progression in the optional helper text.
+
+#### Labels
+
+- Labels inform users what information the progress bar is processing.
+- Keep the label short and concise by limiting it to a single line of text.
+- Labels should never change as the progress bar is loading.
+
+#### Helper text
+
+- Helper text is used to show additional information about the process taking
+ place.
+- Common use cases of helper text for a progress bar can either be a generic
+ phrase, for example “Fetching assets…”, or it can indicate an exact amount of
+ something to be completed, for example "42/256 items".
+- When indicating a loading percentage, the percentage number should count up as
+ the bar progresses.
+
+### Further guidance
+
+For further content guidance, see Carbon's
+[content guidelines]([https://www.carbondesignsystem.com/guidelines/content/overview/]).
+
+## Universal behaviors
+
+### States
+
+There are three states for the progress bar: active, success, and error. These
+states also apply on both indeterminate and determinate progress bars. After the
+process completes successfully or unsuccesfully, a progress bar can either
+remain persistent as confirmation or validation, or it can be automatically
+dismissed depending on what is most suitable for the use case.
+
+
+
+
+![Progress bar states](images/progress-bar-usage-16.png)
+
+
+
+
+#### Active
+
+The active loading state indicates that the action is still in progress.
+
+#### Success
+
+The success loading state indicates that the action completed successfully.
+
+#### Error
+
+The error loading state indicates that the action did not successfully complete.
+If an error occurs, an inline notification or error handling within the form
+should appear. As soon as a process fails, the current visual progress remains
+visible but the indicator bar's progress stops in place and spans full width.
+
+
+
+
+
+
+
+ The example shows the progress bar with error remains persistent as
+ confirmation inside the image tile.
+
+
+
+
+
+
+
+
+
+
+
+ The example shows the progress bar is automatically dismissed once it’s done
+ uploading.
+
+
+
+
+
+### Interactions
+
+#### Part of a page
+
+While the progress bar is processing information on part of a page, you can
+still interact with other elements on the page. When the progress bar finishes
+processing it can either remain persistant on the page for confirmation or
+automatically dismiss itself depending on the use case.
+
+
+
+
+![Progress bar as a part of a page](images/progress-bar-usage-19.png)
+
+
+
+
+#### Inside a container
+
+While the progress bar is processing information that could affect multiple
+pieces of content within a container, such as a card, depending on the use case,
+the whole container should become inactive until processing has been completed
+or the specific section within the container being processed should become
+inactive until processing has been completed. The user should be able to
+interact with the rest of the container or page that is unaffected by the
+progress bar.
+
+
+
+
+![Progress bar inside a container](images/progress-bar-usage-20.png)
+
+
+
+
+## Modifiers
+
+#### Transitions
+
+An indeterminate bar can change to a determinate indicator (finishing from left
+to right) when enough information is gathered to end the load animation.
+
+
+
+
+
+
+
+## Accessibility
+
+- The loading component is implemented using the ARIA 1.1 progressbar pattern.
+ It outputs an ARIA `role="progressbar"` and uses `aria-valuemin`,
+ `aria-valuemax`, and `aria-valuenow` to convey the loaded percentage to screen
+ reader users.
+
+- If the progress bar shows the loading of a specific part or region of the
+ application, set `aria-busy="true"` and `aria-describedby="[progressbar-id]"`
+ on the related element to ensure assistive technologies can correctly convey
+ this relation to the user.
+
+- Only hide the label when it is absolute clear to the user which process the
+ progress bar represents. Note that you are still required to pass an
+ appropriate label which will be read by screen readers.
+
+## Related
+
+#### Components
+
+- [Loading spinners](/components/loading/usage)
+- [Inline loading](/components/inline-loading/usage)
+- [Progress indicator](/components/progress-indicator/usage)
+
+#### Components
+
+- [Loading: skeleton states](/patterns/loading/skeleton-states)
+
+## References
+
+- Accessible Rich Internet Applications Working Group,
+ [“progressbar” role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_progressbar_role),
+ (W3C, 2017)
+- Katie Sherwin,
+ [Progress Indicators Make a Slow System Less Insufferable](https://www.nngroup.com/articles/progress-indicators/)
+ (Nielsen Norman Group, 2001)
+- Jakob Nielsen,
+ [Response Times: The 3 Important Limits (Nielsen Norman Group](https://www.nngroup.com/articles/response-times-3-important-limits/),
+ (Nielsen Norman Group,1993)
+
+## Feedback
+
+Help us improve this component by providing feedback, asking questions, and
+leaving any other comments on
+[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
diff --git a/src/pages/components/progress-bar/videos/progress-bar-usage-11.mp4 b/src/pages/components/progress-bar/videos/progress-bar-usage-11.mp4
new file mode 100644
index 00000000000..6d9b1274a08
Binary files /dev/null and b/src/pages/components/progress-bar/videos/progress-bar-usage-11.mp4 differ
diff --git a/src/pages/components/progress-bar/videos/progress-bar-usage-17.mp4 b/src/pages/components/progress-bar/videos/progress-bar-usage-17.mp4
new file mode 100644
index 00000000000..246161c6a7b
Binary files /dev/null and b/src/pages/components/progress-bar/videos/progress-bar-usage-17.mp4 differ
diff --git a/src/pages/components/progress-bar/videos/progress-bar-usage-18.mp4 b/src/pages/components/progress-bar/videos/progress-bar-usage-18.mp4
new file mode 100644
index 00000000000..fe97f1668c6
Binary files /dev/null and b/src/pages/components/progress-bar/videos/progress-bar-usage-18.mp4 differ
diff --git a/src/pages/components/progress-bar/videos/progress-bar-usage-21.mp4 b/src/pages/components/progress-bar/videos/progress-bar-usage-21.mp4
new file mode 100644
index 00000000000..bd2b40032e4
Binary files /dev/null and b/src/pages/components/progress-bar/videos/progress-bar-usage-21.mp4 differ
diff --git a/src/pages/components/progress-bar/videos/progress-bar-usage-4.mp4 b/src/pages/components/progress-bar/videos/progress-bar-usage-4.mp4
new file mode 100644
index 00000000000..30f95699b71
Binary files /dev/null and b/src/pages/components/progress-bar/videos/progress-bar-usage-4.mp4 differ
diff --git a/src/pages/components/progress-bar/videos/progress-bar-usage-5.mp4 b/src/pages/components/progress-bar/videos/progress-bar-usage-5.mp4
new file mode 100644
index 00000000000..d68db926dbc
Binary files /dev/null and b/src/pages/components/progress-bar/videos/progress-bar-usage-5.mp4 differ
diff --git a/src/pages/components/slider/accessibility.mdx b/src/pages/components/slider/accessibility.mdx
index b1c88c45258..7441b54a2c5 100644
--- a/src/pages/components/slider/accessibility.mdx
+++ b/src/pages/components/slider/accessibility.mdx
@@ -6,99 +6,88 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import {
- StructuredListWrapper,
- StructuredListHead,
- StructuredListBody,
- StructuredListRow,
- StructuredListInput,
- StructuredListCell,
- OrderedList,
- ListItem,
-} from '@carbon/react';
+import localVideo from './videos/slider.mp4';
+import localPoster from './images/slider-accessibility-3.png';
-The slider React Carbon component has been tested against the latest
-[W3C Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA success criteria](https://www.w3.org/TR/WCAG21/)
-and violations have been identified as high priority issues. This document will
-be updated when these accessibility issues are resolved.
+No accessibility annotations are needed for sliders, but keep these
+considerations in mind if you are modifying Carbon or creating a custom
+component.
- Accessibility considerations
- Resources
- Accessibility testing
+ What Carbon provides
+ Development considerations
-## Accessibility considerations
-
-1. Labels should be clear and concise.
-
-## Resources
-
-- [W3C WAI-ARIA Authoring Practices Slider Design Pattern](https://www.w3.org/TR/wai-aria-practices/#slider)
- covers the usage of ARIA names, state and roles, as well as the expected
- keyboard interactions.
-- [IBM Accessibility Requirements](https://www.ibm.com/able/requirements/requirements/):
- - [1.3.1 Info and Relationships](https://www.ibm.com/able/requirements/requirements/#1_3_1)
- (WCAG Success Criteria
- [1.3.1](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships))
- - [1.3.2 Meaningful Sequence](https://www.ibm.com/able/requirements/requirements/#1_3_2)
- (WCAG Success Criteria
- [1.3.2](https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence))
- - [2.1.1 Keyboard](https://www.ibm.com/able/requirements/requirements/#2_1_1)
- (WCAG Success Criteria
- [2.1.1](https://www.w3.org/WAI/WCAG21/Understanding/keyboard))
- - [2.4.3 Focus Order](https://www.ibm.com/able/requirements/requirements/#2_4_3)
- (WCAG Success Criteria
- [2.4.3](https://www.w3.org/WAI/WCAG21/Understanding/focus-order))
- - [2.4.6 Headings and Labels](https://www.ibm.com/able/requirements/requirements/#2_4_6)
- (WCAG Success Criteria
- [2.4.6](https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels))
- - [2.4.7 Focus Visible](https://www.ibm.com/able/requirements/requirements/#2_4_7)
- (WCAG Success Criteria
- [2.4.7](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible))
- - [4.1.2 Name, Role, Value](https://www.ibm.com/able/requirements/requirements/#4_1_2)
- (WCAG Success Criteria
- [4.1.2](https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html))
-
-## Accessibility testing
-
-Accessibility issues are tracked in the
-[Carbon Component GitHub repository](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+label%3A%22type%3A+a11y+%E2%99%BF%22+label%3A%22component%3A+slider%22+).
-
-### Automated test
+## What Carbon provides
+
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
+
+### Keyboard interactions
+
+Tab order goes from slider to text input. Arrow keys are used to change the
+slider value. `Shift`+arrow changes the slider value by a larger increment (such
+as by 10 instead of 1). Users can also directly enter a value in the input.
+
+
+
+
+![example of slider keyboard interaction](images/slider-accessibility-1.png)
+
+
+ Both the slider and input are in the tab order and keyboard operable.
+
+
+
+
+
+### Labeling and updates
+
+
+
+
+![slider label is connected to slider control and text input](images/slider-accessibility-2.png)
+
+
+ The slider label is programmatically associated with both the slider and
+ input.
+
+
+
+
-
-
-
-
-
- Automated test environment
-
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome version 77.0.3865.90
-
- - Dynamic Assessment Plugin (DAP) version 1.8.0.0 - IBM
- Accessibility WCAG 2.1 Sept. 2019 Ruleset
- - Carbon React version 7.7.1
-
-
- DAP test:
- - No violations
-
-
-
-
-
+
+
+
+
+
+ The input value and slider position are in sync. An update to either causes
+ the other to update.
+
+
+
+
+## Development considerations
+
+Keep these considerations in mind if you are modifying Carbon or creating a
+custom component:
+
+- The `step` value determines the change increment when moving the slider,
+ either by pointer or keyboard. A value of `"1"` is recommended.
+- The `stepMultiplier` determines the value change when the keyboard is used to
+ alter the slider by pressing `Shift`+ Arrow key. A tenth of the total range is
+ recommended as a value, such as `"10"` in a 0-100 slider.
+- See the
+ [ARIA authoring practices](https://www.w3.org/TR/wai-aria-practices-1.2/#slider)
+ for more considerations.
diff --git a/src/pages/components/slider/images/slider-accessibility-1.png b/src/pages/components/slider/images/slider-accessibility-1.png
new file mode 100644
index 00000000000..9c15183bf8a
Binary files /dev/null and b/src/pages/components/slider/images/slider-accessibility-1.png differ
diff --git a/src/pages/components/slider/images/slider-accessibility-2.png b/src/pages/components/slider/images/slider-accessibility-2.png
new file mode 100644
index 00000000000..7600cc19184
Binary files /dev/null and b/src/pages/components/slider/images/slider-accessibility-2.png differ
diff --git a/src/pages/components/slider/images/slider-accessibility-3-video.png b/src/pages/components/slider/images/slider-accessibility-3-video.png
new file mode 100644
index 00000000000..47e65cf486b
Binary files /dev/null and b/src/pages/components/slider/images/slider-accessibility-3-video.png differ
diff --git a/src/pages/components/slider/images/slider-accessibility-3.png b/src/pages/components/slider/images/slider-accessibility-3.png
new file mode 100644
index 00000000000..a4b59c0d8a4
Binary files /dev/null and b/src/pages/components/slider/images/slider-accessibility-3.png differ
diff --git a/src/pages/components/slider/videos/slider.mp4 b/src/pages/components/slider/videos/slider.mp4
new file mode 100644
index 00000000000..322ae80da76
Binary files /dev/null and b/src/pages/components/slider/videos/slider.mp4 differ
diff --git a/src/pages/components/structured-list/code.mdx b/src/pages/components/structured-list/code.mdx
index cf5ac08a2b5..802d41f9612 100755
--- a/src/pages/components/structured-list/code.mdx
+++ b/src/pages/components/structured-list/code.mdx
@@ -6,7 +6,7 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import { CheckmarkFilled16 } from '@carbon/icons-react';
+import { CheckmarkFilled } from '@carbon/icons-react';
diff --git a/src/pages/components/structured-list/images/structured-list-style-1.png b/src/pages/components/structured-list/images/structured-list-style-1.png
index ef598405456..55cd8ab3bca 100644
Binary files a/src/pages/components/structured-list/images/structured-list-style-1.png and b/src/pages/components/structured-list/images/structured-list-style-1.png differ
diff --git a/src/pages/components/structured-list/images/structured-list-style-2.png b/src/pages/components/structured-list/images/structured-list-style-2.png
index 3e8b768af3f..8590f1071c3 100644
Binary files a/src/pages/components/structured-list/images/structured-list-style-2.png and b/src/pages/components/structured-list/images/structured-list-style-2.png differ
diff --git a/src/pages/components/structured-list/images/structured-list-style-3.png b/src/pages/components/structured-list/images/structured-list-style-3.png
new file mode 100644
index 00000000000..0d8c97c2303
Binary files /dev/null and b/src/pages/components/structured-list/images/structured-list-style-3.png differ
diff --git a/src/pages/components/structured-list/images/structured-list-usage-1.png b/src/pages/components/structured-list/images/structured-list-usage-1.png
new file mode 100644
index 00000000000..67fc9bf24f0
Binary files /dev/null and b/src/pages/components/structured-list/images/structured-list-usage-1.png differ
diff --git a/src/pages/components/structured-list/images/structured-list-usage-2.png b/src/pages/components/structured-list/images/structured-list-usage-2.png
index c0a3a384d9f..9307dca8080 100644
Binary files a/src/pages/components/structured-list/images/structured-list-usage-2.png and b/src/pages/components/structured-list/images/structured-list-usage-2.png differ
diff --git a/src/pages/components/structured-list/images/structured-list-usage-3.png b/src/pages/components/structured-list/images/structured-list-usage-3.png
new file mode 100644
index 00000000000..5c25fab2d37
Binary files /dev/null and b/src/pages/components/structured-list/images/structured-list-usage-3.png differ
diff --git a/src/pages/components/structured-list/style.mdx b/src/pages/components/structured-list/style.mdx
index 00703b66433..fee711f08d5 100644
--- a/src/pages/components/structured-list/style.mdx
+++ b/src/pages/components/structured-list/style.mdx
@@ -58,7 +58,9 @@ set in sentence case. All typography is left aligned.
-Spacing and measurements for structured list | px / rem
+
+ The width of structured list varies based on content and layout.
+
@@ -67,5 +69,17 @@ set in sentence case. All typography is left aligned.
- Spacing and measurements for structured list with selection | px / rem
+ Spacing and measurements for default spacing with hang alignment and flush
+ alignment| px / rem
+
+
+
+
+![Spacing and measurements for structured list with selection](images/structured-list-style-3.png)
+
+
+
+
+ Spacing and measurements for condensed spacing with hang alignment and flush
+ alignment | px / rem
diff --git a/src/pages/components/structured-list/usage.mdx b/src/pages/components/structured-list/usage.mdx
index f34e4147430..df76267755b 100755
--- a/src/pages/components/structured-list/usage.mdx
+++ b/src/pages/components/structured-list/usage.mdx
@@ -15,13 +15,47 @@ definitions.
+Overview
+Live demo
+Formatting
Content
-Interactions
+Related
Feedback
-import { CheckmarkFilled16 } from '@carbon/icons-react';
+## Overview
+
+Structured list displays a simple list with a considerable amount of items of
+read-only values. It helps organize and present grouped information into logical
+and scannable patterns. The content within a list can be stacked to create
+hierarchy within the data.
+
+#### When to use
+
+- To browse information or select certain information within the group in the
+ simplest form
+- To view description and detailed information, present features, or compare
+ pricing plans
+
+#### When not to use
+
+Nesting items is not recommended, as structured lists are used to present simple
+data. If you have more than 25 items or additional content that needs to be
+shown, consider using a
+[data table](https://www.carbondesignsystem.com/components/data-table/usage/),
+which supports nesting items and presents a larger set of content.
+
+### Variants
+
+| Variant | Purpose |
+| ------------ | ----------------------------------------------------------------------------- |
+| _Default_ | Allows the user to quickly browse and view information within a group of data |
+| _Selectable_ | Allows the user to mark or select a desired option within a group of data |
+
+## Live demo
+
+import { CheckmarkFilled } from '@carbon/icons-react';
-## Content
+## Formatting
+
+### Anatomy
+
+Structured list is composed of two sections—column header and data row.
+
+
+
+
+![Structured list anatomy](images/structured-list-usage-1.png)
+
+
+
+
+1. **Column header**: Shows titles for the row header description.
+2. **Data row**: Shows different types of data. Rows can be selectable and
+ modified to show alternating zebra stripe background colors
-- Row height varies based on content and can expand to fit multiple lines.
-- In a single list, all rows do not have to be the same height.
-- Column widths can either be equally proportional or proportioned based on
- content.
-- If a list extends past 25 items, consider using a
- [data table](/components/data-table/usage) to present this larger set of
- content.
-- A maximum of one paragraph of text is recommended per row.
-- Nesting items is not recommended, as structured lists are used to present
- simple data. If you have additional content that needs to be shown, consider
- using a [data table](/components/data-table/usage), which supports nesting
- items.
+### Sizing
+
+The structured list is available in two different sizes in height: default and
+condensed. The structure list's width varies based on content and layout.
-![Structured list to present definitions.](images/structured-list-usage-2.png)
+![data table anatomy](images/structured-list-usage-2.png)
-## Interactions
+### Alignment
+
+The structured list is available in two alignment styles: hang and flush
+alignment.
+
+
+
-Structured lists can be single-select if a user is choosing between a set of
-options.
+![data table anatomy](images/structured-list-usage-3.png)
-#### Guidelines:
+
+
+
+## Content
+
+- A maximum of three paragraphs of text is recommended per row.
+- A structured list’s title and row information should use sentence-case
+ capitalization.
+
+#### Column header titles
+
+- Column header titles should be short and clear, sticking to one or two words
+ that describe the data in that column.
+- In cases where a column header title is too long, wrap the text to two lines
+ and then truncate the rest of the text. The full text should be shown in a
+ tooltip on hover.
+- Column header titles should use sentence-case capitalization.
+
+## Interactions
+
+#### Selectable structured list
- Only one item can be selected from the list.
- By default, one option should be selected.
@@ -239,6 +306,14 @@ options.
- When the user selects an item from the list, the selected row will appear with
the `checkmark--filled` icon.
+## Related
+
+These following components are additional ways to organize a group of data.
+
+- [Accordion](https://www.carbondesignsystem.com/components/accordion/usage/)
+- [Data table](https://www.carbondesignsystem.com/components/data-table/usage/)
+- [List](https://www.carbondesignsystem.com/components/list/usage/)
+
## Feedback
Help us improve this component by providing feedback, asking questions, and
diff --git a/src/pages/components/tooltip/code.mdx b/src/pages/components/tooltip/code.mdx
index 522a0638b41..7ffa3c9857e 100755
--- a/src/pages/components/tooltip/code.mdx
+++ b/src/pages/components/tooltip/code.mdx
@@ -6,7 +6,7 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import { Filter16 } from '@carbon/icons-react';
+import { Filter } from '@carbon/icons-react';
diff --git a/src/pages/components/tooltip/usage.mdx b/src/pages/components/tooltip/usage.mdx
index 80c00175652..5c481ca2592 100755
--- a/src/pages/components/tooltip/usage.mdx
+++ b/src/pages/components/tooltip/usage.mdx
@@ -155,7 +155,7 @@ The exception here is that definition tooltip can be invoked on `hover` or
## Live demo
-import { Filter16 } from '@carbon/icons-react';
+import { Filter } from '@carbon/icons-react';
+ scope={{ Filter16 }}
+>
{`
+ }}
+ >{`
{`
+ }}
+ >{`
@@ -236,7 +239,8 @@ import { Filter16 } from '@carbon/icons-react';
Vanilla: 'https://the-carbon-components.netlify.com/?nav=tooltip',
'Web Components':
'https://web-components.carbondesignsystem.com/?path=/story/components-tooltip--definition',
- }}>{`
+ }}
+ >{`
diff --git a/src/pages/contributing/add-ons.mdx b/src/pages/contributing/add-ons.mdx
index 3cbd01edea4..493e6347aca 100644
--- a/src/pages/contributing/add-ons.mdx
+++ b/src/pages/contributing/add-ons.mdx
@@ -5,7 +5,7 @@ description:
a specific product or experience.
---
-import { CheckmarkFilled16 } from '@carbon/icons-react';
+import { CheckmarkFilled } from '@carbon/icons-react';
diff --git a/src/pages/contributing/component/index.mdx b/src/pages/contributing/component/index.mdx
index 152d0a9819e..733a4eaf482 100644
--- a/src/pages/contributing/component/index.mdx
+++ b/src/pages/contributing/component/index.mdx
@@ -691,7 +691,7 @@ specific repo you intend to contribute to.
diff --git a/src/pages/contributing/contribute-icons.mdx b/src/pages/contributing/contribute-icons.mdx
index 1bf7cff64ff..d2fc9a3a601 100644
--- a/src/pages/contributing/contribute-icons.mdx
+++ b/src/pages/contributing/contribute-icons.mdx
@@ -52,7 +52,7 @@ guidelines to ensure visual consistency and proper formatting.
- Make sure to properly name layers and artboards _(these names will also be
exported into the code)_.
- Review the
- [icon master file](https://github.com/carbon-design-system/carbon/tree/main/packages/icons/master)
+ [icon master file](https://github.com/carbon-design-system/carbon/tree/v10/packages/icons/master)
to see these guidelines in practice.
### Production-ready
@@ -124,7 +124,7 @@ for approval.
Before submitting artwork, first review our
[icons library](https://www.carbondesignsystem.com/guidelines/icons/library/) or
download the
-[Carbon icon master .ai file](https://github.com/carbon-design-system/carbon/tree/main/packages/icons/master)
+[Carbon icon master .ai file](https://github.com/carbon-design-system/carbon/tree/v10/packages/icons/master)
to check your design for duplication against existing icons.
### Approval process
diff --git a/src/pages/designing/design-resources/index.mdx b/src/pages/designing/design-resources/index.mdx
index 9f446daf391..ae13251e308 100755
--- a/src/pages/designing/design-resources/index.mdx
+++ b/src/pages/designing/design-resources/index.mdx
@@ -59,7 +59,7 @@ You'll find even more guidance and assets in this file than on the site.
![](/images/ase.png)
@@ -189,8 +189,8 @@ to help designers with every aspect of image creation and component specs.
+ href="https://www.sketch.com/s/240226b0-f455-484d-b412-cfd13fb1bb39"
+ actionIcon="launch">
diff --git a/src/pages/designing/tutorials.mdx b/src/pages/designing/tutorials.mdx
index 6e065830b50..f4b788efb91 100644
--- a/src/pages/designing/tutorials.mdx
+++ b/src/pages/designing/tutorials.mdx
@@ -6,7 +6,7 @@ description:
---
import { Button } from '@carbon/react';
-import { ArrowRight16 } from '@carbon/icons-react';
+import { ArrowRight } from '@carbon/icons-react';
diff --git a/src/pages/developing/dev-resources/index.mdx b/src/pages/developing/dev-resources/index.mdx
index 05a0fb8bf8f..beb1179bbe4 100644
--- a/src/pages/developing/dev-resources/index.mdx
+++ b/src/pages/developing/dev-resources/index.mdx
@@ -37,7 +37,7 @@ your framework of choice.
diff --git a/src/pages/developing/frameworks/react.mdx b/src/pages/developing/frameworks/react.mdx
index 8faee2d5e75..a91aab4e135 100755
--- a/src/pages/developing/frameworks/react.mdx
+++ b/src/pages/developing/frameworks/react.mdx
@@ -76,7 +76,7 @@ yarn add @carbon/react
1. These components require the use of
[webpack](https://webpack.js.org/guides/getting-started/) in your project.
See our
- [webpack.config.js](https://github.com/carbon-design-system/carbon/blob/main/packages/react/.storybook/webpack.config.js)
+ [webpack.config.js](https://github.com/carbon-design-system/carbon/blob/v10/packages/react/.storybook/webpack.config.js)
for an example configuration.
2. Components do not import any of the styles themselves, use the SCSS or CSS
@@ -92,7 +92,7 @@ yarn add @carbon/react
## Development
Please refer to the
-[Contribution Guidelines](https://github.com/carbon-design-system/carbon/blob/main/.github/CONTRIBUTING.md)
+[Contribution Guidelines](https://github.com/carbon-design-system/carbon/blob/v10/.github/CONTRIBUTING.md)
before starting any work.
### Using the server
@@ -124,7 +124,7 @@ top right corner of the selected component.
If you experience any issues while getting set up with Carbon Components React,
please head over to the
-[GitHub repo](https://github.com/carbon-design-system/carbon/tree/main/packages/react)
+[GitHub repo](https://github.com/carbon-design-system/carbon/tree/v10/packages/react)
for more guidelines and support. Please
[create an issue](https://github.com/carbon-design-system/carbon/issues) if your
issue does not already exist.
diff --git a/src/pages/developing/frameworks/vanilla.mdx b/src/pages/developing/frameworks/vanilla.mdx
index 9d9128fcb9c..552748a86b0 100755
--- a/src/pages/developing/frameworks/vanilla.mdx
+++ b/src/pages/developing/frameworks/vanilla.mdx
@@ -123,7 +123,7 @@ prefixes are automatically added to your output CSS.
#### Default body styles
CSS is automatically applied to `` element, which comes from
-[\_css--body.scss](https://github.com/carbon-design-system/carbon/blob/main/packages/components/src/globals/scss/_css--body.scss).
+[\_css--body.scss](https://github.com/carbon-design-system/carbon/blob/v10/packages/components/src/globals/scss/_css--body.scss).
These styles are meant to cascade down to everything in `` to set common
styles shared across all components.
@@ -153,7 +153,7 @@ to `true` by default.
For example:
- When you set `$css--reset: true`, then the contents of
- [\_css--reset.scss](https://github.com/carbon-design-system/carbon/blob/main/packages/components/src/globals/scss/_css--reset.scss)
+ [\_css--reset.scss](https://github.com/carbon-design-system/carbon/blob/v10/packages/components/src/globals/scss/_css--reset.scss)
will be part of your output CSS.
- When you set `$css--reset: false`, then nothing gets included from that SCSS
file.
@@ -336,7 +336,7 @@ customElements.define('bx-loading', BXLoading);
carbon-components requires some polyfills for older browsers, in addition to
carbon-components.js (or carbon-components.min.js). The latest list of polyfills
is maintained in
-[carbon-components/blob/main/packages/components/demo/polyfills/index.js](https://github.com/carbon-design-system/carbon/blob/main/packages/components/demo/polyfills/index.js).
+[carbon-components/blob/main/packages/components/demo/polyfills/index.js](https://github.com/carbon-design-system/carbon/blob/v10/packages/components/demo/polyfills/index.js).
You can easily find the polyfills in NPM, etc. The current list is below:
- [Array.from()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/from)
diff --git a/src/pages/developing/react-tutorial/step-1.mdx b/src/pages/developing/react-tutorial/step-1.mdx
index 50d9c7a4c01..041cee622ca 100644
--- a/src/pages/developing/react-tutorial/step-1.mdx
+++ b/src/pages/developing/react-tutorial/step-1.mdx
@@ -331,7 +331,7 @@ export default TutorialHeader;
**Note:** you can find a description of the different components used UI Shell
in our
-[carbon-components-react](https://github.com/carbon-design-system/carbon/tree/main/packages/react/src/components/UIShell)
+[carbon-components-react](https://github.com/carbon-design-system/carbon/tree/v10/packages/react/src/components/UIShell)
package.
diff --git a/src/pages/developing/react-tutorial/step-2.mdx b/src/pages/developing/react-tutorial/step-2.mdx
index e14ec5e2bb0..b700dc66af6 100644
--- a/src/pages/developing/react-tutorial/step-2.mdx
+++ b/src/pages/developing/react-tutorial/step-2.mdx
@@ -102,7 +102,7 @@ You should see something similar to where the
Before we get started with this step, we'll be adding some components that
require IE11 polyfills. As shown in the
-[Carbon React documentation](https://github.com/carbon-design-system/carbon/blob/main/packages/react/.storybook/polyfills.js),
+[Carbon React documentation](https://github.com/carbon-design-system/carbon/blob/v10/packages/react/.storybook/polyfills.js),
go ahead and add these imports to the top of the root `index.js`. They aren't
all needed, but we'll add them all to play it safe for the duration of the
tutorial.
diff --git a/src/pages/developing/react-tutorial/step-4.mdx b/src/pages/developing/react-tutorial/step-4.mdx
index 51a06a9970c..8e09c11328c 100644
--- a/src/pages/developing/react-tutorial/step-4.mdx
+++ b/src/pages/developing/react-tutorial/step-4.mdx
@@ -253,7 +253,7 @@ While we're at the top of `LandingPage.js`, import the icons that we'll need as
well.
```javascript path=src/content/LandingPage/LandingPage.js
-import { Application32, Globe32, PersonFavorite32 } from '@carbon/icons-react';
+import { Application, Globe, PersonFavorite } from '@carbon/icons-react';
```
@@ -422,26 +422,70 @@ styles and to bottom-align the icons.
## Check accessibility
We've added new markup and styles, so it's a good practice to check
-[DAP](https://www.ibm.com/able/dynamic-assessment-plug-in.html) and make sure
+[Equal Access Checker](https://www.ibm.com/able/toolkit/tools/) and make sure
our rendered markup is on the right track for accessibility.
With the browser extension installed, Chrome in this example, open Dev Tools and
-run DAP.
+run Accessibility Assessment.
-![DAP violations](../shared/step-4/images/DAP-violations.png)
+![Equal Access Checker violations](../shared/step-4/images/EqualAccessChecker-violations.png)
-DAP violations
+Equal Access Checker violations
-That first violation is for the off-screen "skip to content" link. This link
-isn't shown and is used to assist screen reading, so the color contrast
-violation can be ignored.
+All these violations came from the `` element used in `LandingPage`.
+`` element expects a unique value for the ARIA properties `aria-controls`
+and `aria-labelledby`. Setting a unique `id` attribute for all the three tabs
+will solve the problem.
-But, those three other violations came from the `` element used in new
-`InfoCard`. Since the `` element requires a label, it seems like we may
-be using the wrong semantic element. A humble `` will suffice.
+In `LandingPage.js`, replace the `
` element with:
-In `Info.js`, replace the `` opening and closing tags with ``
-tags.
+```javascript path=src/content/LandingPage/LandingPage.js
+
+
+
+
+
+
What is Carbon?
+
+ Carbon is IBM’s open-source design system for digital products and
+ experiences. With the IBM Design Language as its foundation, the
+ system consists of working code, design tools and resources, human
+ interface guidelines, and a vibrant community of contributors.
+
+
Learn more
+
+
+
+
+
+
+
+
+
+
+
+ Rapidly build beautiful and accessible experiences. The Carbon kit
+ contains all resources you need to get started.
+
+
+
+
+
+
+
+
+ Carbon provides styles and components in Vanilla, React, Angular, and
+ Vue for anyone building on the web.
+
+
+
+
+
+```
## Submit pull request
diff --git a/src/pages/developing/shared/step-4/images/DAP-violations.png b/src/pages/developing/shared/step-4/images/DAP-violations.png
deleted file mode 100644
index a0a90d1b3cc..00000000000
Binary files a/src/pages/developing/shared/step-4/images/DAP-violations.png and /dev/null differ
diff --git a/src/pages/developing/shared/step-4/images/EqualAccessChecker-violations.png b/src/pages/developing/shared/step-4/images/EqualAccessChecker-violations.png
new file mode 100644
index 00000000000..d6fe7e70a8c
Binary files /dev/null and b/src/pages/developing/shared/step-4/images/EqualAccessChecker-violations.png differ
diff --git a/src/pages/guidelines/2x-grid/implementation.mdx b/src/pages/guidelines/2x-grid/implementation.mdx
index 5c007e414e4..52f9cf45eba 100644
--- a/src/pages/guidelines/2x-grid/implementation.mdx
+++ b/src/pages/guidelines/2x-grid/implementation.mdx
@@ -1369,7 +1369,7 @@ Image size can change ratios when the breakpoint changes.
diff --git a/src/pages/guidelines/2x-grid/overview.mdx b/src/pages/guidelines/2x-grid/overview.mdx
index 6034a786e66..8766fb17c69 100644
--- a/src/pages/guidelines/2x-grid/overview.mdx
+++ b/src/pages/guidelines/2x-grid/overview.mdx
@@ -41,7 +41,7 @@ creative decision-making.
@@ -108,16 +108,16 @@ fluid grid, or by tiling fixed boxes in multiples.
#### Fluid grid
-A [fluid grid](#fluid-grid) divides space by twos. This division is immediately
-evident in the 2x column structure. Within a breakpoint, the column count is
-constant, and unit size scales with screen size. Choose a column count by
-starting with one, then divide by two as needed.
+A fluid grid divides space by twos. This division is immediately evident in the
+2x column structure. Within a breakpoint, the column count is constant, and unit
+size scales with screen size. Choose a column count by starting with one, then
+divide by two as needed.
#### Fixed grid
-A [fixed grid](#fixed-grid) starts with a fixed unit size from the sizing scale,
-then tiles and wraps as needed, like text. To employ the 2x concept, multiply
-box sizes by two and mix them together.
+A fixed grid starts with a fixed unit size from the sizing scale, then tiles and
+wraps as needed, like text. To employ the 2x concept, multiply box sizes by two
+and mix them together.
When tiling fixed boxes, the column count is not known in advance, but a grid
emerges visually due to the use of a consistent sizing scale. On breakpoint
@@ -181,7 +181,7 @@ breakpoints.
Create custom breakpoints to accommodate special needs, by writing your own
media queries and CSS rules. Refer to the
-[grid code package](https://github.com/carbon-design-system/carbon/tree/main/packages/grid)
+[grid code package](https://github.com/carbon-design-system/carbon/tree/v10/packages/grid)
for more information.
| Breakpoint | Value (px/rem) | Columns | Size (%) | Size | Padding | Margin |
diff --git a/src/pages/guidelines/color/code.mdx b/src/pages/guidelines/color/code.mdx
index e963b319aa1..f8dff8e2621 100644
--- a/src/pages/guidelines/color/code.mdx
+++ b/src/pages/guidelines/color/code.mdx
@@ -126,7 +126,7 @@ warmGray100; // Using the `warmGray100` variable.
diff --git a/src/pages/guidelines/color/overview.mdx b/src/pages/guidelines/color/overview.mdx
index cec196c86b7..b868988247f 100755
--- a/src/pages/guidelines/color/overview.mdx
+++ b/src/pages/guidelines/color/overview.mdx
@@ -641,7 +641,7 @@ to achieve commonly used contrast ratios between any two colors.
@@ -651,7 +651,7 @@ to achieve commonly used contrast ratios between any two colors.
diff --git a/src/pages/guidelines/icons/code.mdx b/src/pages/guidelines/icons/code.mdx
index e7afeabca41..1d7273f2968 100644
--- a/src/pages/guidelines/icons/code.mdx
+++ b/src/pages/guidelines/icons/code.mdx
@@ -163,7 +163,7 @@ browsers like Internet Explorer 11 by setting `focusable` to `true`.
@@ -173,7 +173,7 @@ browsers like Internet Explorer 11 by setting `focusable` to `true`.
diff --git a/src/pages/guidelines/icons/contribute.mdx b/src/pages/guidelines/icons/contribute.mdx
index fd7793e2ece..f1019718a48 100644
--- a/src/pages/guidelines/icons/contribute.mdx
+++ b/src/pages/guidelines/icons/contribute.mdx
@@ -53,7 +53,7 @@ guidelines to ensure visual consistency and proper formatting.
- Make sure to properly name layers and artboards _(these names will also be
exported into the code)_.
- Review the
- [icon master file](https://github.com/carbon-design-system/carbon/tree/main/packages/icons/master)
+ [icon master file](https://github.com/carbon-design-system/carbon/tree/v10/packages/icons/master)
to see these guidelines in practice.
### Production-ready
@@ -100,7 +100,7 @@ for approval.
Before submitting artwork, first review our
[icons library](https://www.carbondesignsystem.com/guidelines/icons/library/) or
download the
-[Carbon icon master .ai file](https://github.com/carbon-design-system/carbon/tree/main/packages/icons/master)
+[Carbon icon master .ai file](https://github.com/carbon-design-system/carbon/tree/v10/packages/icons/master)
to check your design for duplication against existing icons.
### Approval process
diff --git a/src/pages/guidelines/icons/usage.mdx b/src/pages/guidelines/icons/usage.mdx
index 9fdc716cbd1..d1001d49e75 100644
--- a/src/pages/guidelines/icons/usage.mdx
+++ b/src/pages/guidelines/icons/usage.mdx
@@ -25,7 +25,7 @@ important information.
@@ -35,7 +35,7 @@ important information.
diff --git a/src/pages/guidelines/motion/overview.mdx b/src/pages/guidelines/motion/overview.mdx
index 9448c1cd2d7..95163300ae3 100644
--- a/src/pages/guidelines/motion/overview.mdx
+++ b/src/pages/guidelines/motion/overview.mdx
@@ -227,7 +227,7 @@ that it would come to rest just outside the view, and ready to be recalled.
### Summary on easing
The
-[IBM motion package](https://github.com/carbon-design-system/carbon/tree/main/packages/motion)
+[IBM motion package](https://github.com/carbon-design-system/carbon/tree/v10/packages/motion)
has the easing curves stored for fast access. This is the recommended method to
call an easing curve and stay connected to receive any future updates.
@@ -363,7 +363,7 @@ statically.
diff --git a/src/pages/guidelines/pictograms/code.mdx b/src/pages/guidelines/pictograms/code.mdx
index 84e7930420c..0e422e37281 100644
--- a/src/pages/guidelines/pictograms/code.mdx
+++ b/src/pages/guidelines/pictograms/code.mdx
@@ -128,7 +128,7 @@ browsers like Internet Explorer 11 by setting `focusable` to `true`.
diff --git a/src/pages/guidelines/pictograms/usage.mdx b/src/pages/guidelines/pictograms/usage.mdx
index 16ef73c4462..f8dcc20233b 100644
--- a/src/pages/guidelines/pictograms/usage.mdx
+++ b/src/pages/guidelines/pictograms/usage.mdx
@@ -6,7 +6,7 @@ description:
tabs: ['Library', 'Usage', 'Code', 'Contribute']
---
-import { Bee32 } from '@carbon/icons-react';
+import { Bee } from '@carbon/icons-react';
@@ -44,7 +44,7 @@ become an elegant addition to the IBM experience.
![Github Icon](../../../images/resource-cards/github.png)
@@ -55,7 +55,7 @@ become an elegant addition to the IBM experience.
@@ -67,7 +67,7 @@ become an elegant addition to the IBM experience.
diff --git a/src/pages/guidelines/spacing/code.mdx b/src/pages/guidelines/spacing/code.mdx
index ec6b0a312ab..e23dbc98b50 100644
--- a/src/pages/guidelines/spacing/code.mdx
+++ b/src/pages/guidelines/spacing/code.mdx
@@ -68,8 +68,7 @@ the following:
#### API
-
-| Export | Description | !default | | :------------------ | :---------- | :-------
+ | Export | Description | !default | | :------------------ | :---------- | :-------
| | `$spacing-01` | | ✅ | | `$spacing-02` | | ✅ | | `$spacing-03` | | ✅ | | `$spacing-04`
| | ✅ | | `$spacing-05` | | ✅ | | `$spacing-06` | | ✅ | | `$spacing-07` | | ✅
| | `$spacing-08` | | ✅ | | `$spacing-09` | | ✅ | | `$spacing-10` | | ✅ | | `$spacing-11`
@@ -94,7 +93,7 @@ following:
diff --git a/src/pages/guidelines/themes/code.mdx b/src/pages/guidelines/themes/code.mdx
index eb49902c1a6..5aada190809 100644
--- a/src/pages/guidelines/themes/code.mdx
+++ b/src/pages/guidelines/themes/code.mdx
@@ -143,7 +143,7 @@ import {
diff --git a/src/pages/guidelines/themes/overview.mdx b/src/pages/guidelines/themes/overview.mdx
index ccd91f67b42..8e176a205f6 100755
--- a/src/pages/guidelines/themes/overview.mdx
+++ b/src/pages/guidelines/themes/overview.mdx
@@ -867,7 +867,7 @@ changing for each individual theme.
diff --git a/src/pages/guidelines/typography/code.mdx b/src/pages/guidelines/typography/code.mdx
index 2702b52942e..07583ca8f03 100644
--- a/src/pages/guidelines/typography/code.mdx
+++ b/src/pages/guidelines/typography/code.mdx
@@ -267,7 +267,7 @@ There is also a `type-scale` mixin that will set `font-size` for your directly:
diff --git a/src/pages/guidelines/typography/overview.mdx b/src/pages/guidelines/typography/overview.mdx
index 3764fe8655d..767a6057d92 100644
--- a/src/pages/guidelines/typography/overview.mdx
+++ b/src/pages/guidelines/typography/overview.mdx
@@ -221,7 +221,7 @@ for primary actions.
@@ -231,7 +231,7 @@ for primary actions.
diff --git a/src/pages/help/migration-guide/design.mdx b/src/pages/help/migration-guide/design.mdx
new file mode 100644
index 00000000000..97097adf512
--- /dev/null
+++ b/src/pages/help/migration-guide/design.mdx
@@ -0,0 +1,188 @@
+---
+title: Migration guide
+description:
+ This guide includes everything you need to migrate your offering from an
+ earlier version of Carbon to v10.
+tabs: ['Overview', 'Design', 'Develop']
+---
+
+
+
+The transition from v9 to v10 is primarily visual. The IBM color palette was
+updated between versions and a 16-column grid was introduced.
+
+
+
+
+
+IBM Design Language
+Design kit
+Elements
+Design migration strategy
+
+
+
+## IBM Design Language
+
+Carbon v10 delivers the
+[IBM Design Language](https://www.ibm.com/design/language/) to product teams. It
+represents a complete visual refresh of the system, delivering the ethos of IBM
+Design. Carbon v10 is a modern, open-source framework for building digital
+products and experiences, with tooling and guidance on color, layout,
+typography, iconography, motion, patterns, and content.
+
+## Design kit
+
+All components, colors, icons, typography, motion, and grid elements in the kit
+align with the IBM Design Language.
+
+### What changed
+
+- Sketch kit delivered with Sketch Cloud
+- New color tokens
+- Updated text styles
+- Updated spacing
+- Icon updates
+- Updated layer styles
+
+#### Sketch libraries
+
+Designers can subscribe to the design kit library via Sketch Cloud, and updates
+to the contents of the kit will be pushed to subscribers as they become
+available.
+
+#### Icons, pictograms, and the full IBM color palette
+
+To access the IBM Design Language icons, pictograms, and colors, subscribe to
+the
+[IBM Design Language libraries](/designing/design-resources#color-grid-and-icons).
+
+#### Migrating to v10
+
+Upgrading to the v10 kit will not automatically change any files created in
+previous versions of the kit. Swapping v9 symbols for v10 symbols is a manual
+process.
+
+Although libraries from multiple versions of Carbon can exist in Sketch at the
+same time, you should avoid using v10 symbols in an app designed with v9.
+
+### Setting up the kit
+
+Head over to [Design kits](/designing/kits/sketch) to set up the new Sketch
+libraries.
+
+## Elements
+
+### Themes and color
+
+Carbon offers four color themes. See the
+[theming guidelines](/guidelines/color/overview#themes) to learn how to use the
+themes, and visit the color migration guide to learn more about color tokens
+added in v10.
+
+
+
+
+
+
+
+
+
+
+
+### Icons
+
+The [icon library](/guidelines/icons/library) was updated and expanded with v10.
+The full library of icons and pictograms is available via the IBM Design
+Language icon [Sketch library](/guidelines/icons/usage#resources).
+
+Any v9 icons should be reviewed against the new icons before publishing.
+Wherever possible, replace old icons with an updated version.
+
+
+
+
+
+
+
+
+
+
+
+### Typography
+
+The typeface for Carbon remains
+[IBM Plex](/guidelines/typography/overview/#typeface:-ibm-plex). The
+[type token](/guidelines/typography/overview#type-tokens-and-sets) architecture
+was redesigned for better clarity and flexibility, moving from a basic type
+scale model to a more robust token-based architecture. Work with your
+development team to discuss how this new architecture might affect your team's
+workflow.
+
+
+
+
+
+
+
+
+
+
+
+### Motion
+
+Carbon v10 adheres to IBM Design Language
+[motion standards](/guidelines/motion/overview), designed to bring unity and
+cohesion to all motion in a user interface. All interactions that include motion
+should abide by these standards.
+
+### Layout, grid, and spacing
+
+Carbon v10 uses the 16-column [2x Grid](/guidelines/2x-grid/overview). Carbon
+v10 will default to the 12-column grid with an option to switch to the 16-column
+grid. Designers starting on new layouts using v10 should use the 16-column grid.
+
+Layout and spacing token names were updated in v10 but the values remain the
+same.
+
+
+
+
+
+
+
+
+
+
+
+## Design migration strategy
+
+The fastest approach to v10 migration starts with the front-end developer.
+Developers should update the product's front end code to v10 and conduct a
+visual review with team designers. The transition should not cause any major
+breaks in the UI but there will likely be layout and color issues. Product teams
+using v9 components in their code should see a mostly seamless code transition.
+
+Throughout visual review and iteration process, ask:
+
+- Are you using type tokens?
+- Are you using the color tokens correctly?
+- Is the spacing between components correct?
+- Do animations in the UI match the new motion standards?
+- Does the general layout still work, and does it express the IBM Design
+ Language accurately and effectively?
+
+Following this review, work any development and design issues into your team's
+planning workflow.
diff --git a/src/pages/help/migration-guide/develop.mdx b/src/pages/help/migration-guide/develop.mdx
new file mode 100644
index 00000000000..ee208b6356d
--- /dev/null
+++ b/src/pages/help/migration-guide/develop.mdx
@@ -0,0 +1,286 @@
+---
+title: Migration guide
+description:
+ This guide includes everything you need to migrate your offering from an older
+ version of Carbon to v10.
+tabs: ['Overview', 'Design', 'Develop']
+---
+
+
+
+The repository structure was overhauled during the transition from v9 to v10.
+Carbon code now lives in a monorepo.
+
+
+
+
+
+Repo architecture
+Carbon components
+Carbon elements
+
+
+
+## Repo architecture
+
+[Carbon-themes](https://github.com/carbon-design-system/carbon-themes) was
+deprecated in v10, and the themes package
+[@carbon/themes](https://github.com/carbon-design-system/carbon/tree/v10/packages/themes)
+now lives in the [Carbon](https://github.com/carbon-design-system/carbon)
+monorepo.
+
+
+
+
+
+
+
+
+
+
+
+## Carbon components
+
+Carbon components were reskinned in v10. The redesign was conducted with maximum
+backwards compatibility in mind. Users of v9 should be able to upgrade to v10
+automatically with minimal breakage.
+
+Detailed technical migration docs for Carbon components are available in the
+[carbon-components repo](https://github.com/carbon-design-system/carbon/blob/v10/packages/components/docs/migration/migrate-to-10.x.md).
+Here you will find links to component-level migration information, as well as a
+list of those components that have been removed or are under development.
+
+There is also a dedicated
+[Sass migration guide](https://github.com/carbon-design-system/carbon/blob/v10/packages/components/src/globals/scss/migrate-to-10.x.md)
+that covers changes to global styling.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Carbon elements
+
+All technical migration docs for Carbon elements are available in the `carbon`
+monorepo
+[docs folder](https://github.com/carbon-design-system/carbon/tree/v10/docs/migration).
+
+
+
+
+
+
+
+
+
+
+
+### Icons
+
+The `@carbon/icons` package can be now be found in the
+[Carbon monorepo](https://github.com/carbon-design-system/carbon/tree/v10/packages/icons).
+
+The
+[Carbon icons demo](https://carbon-elements.netlify.com/icons/examples/preview/)
+contains a master table for all Carbon icons, including name, size, preview,
+download links, quick links for filing issues, module name, and relative path.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Color
+
+The v10 color token architecture is based on the v9 architecture, with some
+minor changes to align with the design language. Carbon v9 product teams will
+see automatic, non-breaking color updates when they upgrade to v10.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Type
+
+The type token architecture was redesigned for better clarity and flexibility.
+V10 moves from a basic type scale model to a more robust token-based
+architecture.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Layout, grid, and spacing
+
+Token names changed in v10 but spacing values did not.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Motion
+
+Carbon adheres to IBM Design Language motion standards. Motion updates should be
+coordinated with your product's design team.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/src/pages/index.mdx b/src/pages/index.mdx
index 9b59c527954..86d055e6d21 100755
--- a/src/pages/index.mdx
+++ b/src/pages/index.mdx
@@ -67,7 +67,7 @@ building websites and user interfaces.
@@ -87,7 +87,7 @@ building websites and user interfaces.
diff --git a/src/pages/migrating/guide/images/carbon_2021-beta-1.png b/src/pages/migrating/guide/images/carbon_2021-beta-1.png
new file mode 100644
index 00000000000..4b24ea10f3a
Binary files /dev/null and b/src/pages/migrating/guide/images/carbon_2021-beta-1.png differ
diff --git a/src/pages/migrating/guide/images/carbon_2021-beta-2.png b/src/pages/migrating/guide/images/carbon_2021-beta-2.png
new file mode 100644
index 00000000000..08107b0d023
Binary files /dev/null and b/src/pages/migrating/guide/images/carbon_2021-beta-2.png differ
diff --git a/src/pages/migrating/guide/images/carbon_2021-beta-3.png b/src/pages/migrating/guide/images/carbon_2021-beta-3.png
new file mode 100644
index 00000000000..39346635faa
Binary files /dev/null and b/src/pages/migrating/guide/images/carbon_2021-beta-3.png differ
diff --git a/src/pages/whats-happening/meetups/index.mdx b/src/pages/whats-happening/meetups/index.mdx
index a2a0a9afa54..46fd971e9fe 100644
--- a/src/pages/whats-happening/meetups/index.mdx
+++ b/src/pages/whats-happening/meetups/index.mdx
@@ -7,7 +7,7 @@ description:
---
import { Button } from '@carbon/react';
-import { ArrowRight16 } from '@carbon/icons-react';
+import { ArrowRight } from '@carbon/icons-react';
diff --git a/src/styles/_grid-demo.scss b/src/styles/_grid-demo.scss
index ce34452035a..c98fe38e61f 100644
--- a/src/styles/_grid-demo.scss
+++ b/src/styles/_grid-demo.scss
@@ -1,4 +1,4 @@
-@use '@carbon/grid/scss/modules/flex-grid' as *;
+@use '@carbon/grid/scss/flex-grid' as *;
@use '@carbon/react/scss/breakpoint' as *;
@use '@carbon/react/scss/compat/theme' as *;
@use '@carbon/react/scss/colors' as *;
@@ -106,7 +106,7 @@
}
.grid-demo [class*='col'] {
- @include type-style('caption-01');
+ @include type-style('label-01');
padding-top: $spacing-05;
min-height: 4rem;
background-color: $blue-10;
diff --git a/src/styles/_homepage.scss b/src/styles/_homepage.scss
index bc6e256dc2c..437cded4e45 100644
--- a/src/styles/_homepage.scss
+++ b/src/styles/_homepage.scss
@@ -18,14 +18,14 @@
}
.homepage--header {
- height: 0;
+ height: 500px;
overflow: hidden;
- padding-top: 100%;
+ padding-top: 0;
position: relative;
- @include breakpoint('md') {
- padding-top: 50%;
- }
+ // @include breakpoint('lg') {
+ // padding-top: 50%;
+ // }
// Match max height at lg breakpoint
@include breakpoint('lg') {
@@ -34,6 +34,19 @@
}
}
+.homepage--header .cds--grid {
+ background-size: cover;
+ background-position: center;
+ height: 50vh;
+ max-height: 560px;
+ width: 100%;
+ max-width: 100%;
+
+ @include breakpoint('lg') {
+ background-position: 100px center;
+ }
+}
+
.homepage--header .cds--grid,
.homepage--header .cds--row {
height: 100%;
diff --git a/yarn.lock b/yarn.lock
index 6cdf8d518f1..751500d2401 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -1140,47 +1140,45 @@
resolved "https://registry.yarnpkg.com/@carbon/colors/-/colors-10.29.0.tgz#92b1f8822a0ca07d23daba12d360f90debcc3d26"
integrity sha512-Ga20vVFGrhEgALIVZoWbcooWOVnx7Ox8GbRWlZDEAe6JUbz6ynDKiq3td7GtFVk0ELRCIV8gVu3F/PfssyhwQA==
-"@carbon/colors@^10.37.0":
- version "10.37.1"
- resolved "https://registry.yarnpkg.com/@carbon/colors/-/colors-10.37.1.tgz#6e5a62fedb256bab56873f7b42985b515521b856"
- integrity sha512-Bst1o2RGB0Fpdd2p9y+2fl2oxtXuI0RiVhxKBChKOPZkeBJZTWj1jNgQuNK1ZALHWGX9rL75i7tJmhlXbukfmA==
-
-"@carbon/elements@^10.55.0":
- version "10.55.0"
- resolved "https://registry.yarnpkg.com/@carbon/elements/-/elements-10.55.0.tgz#98363ef44ddfe19171e0f6d77ac0fb3d02417908"
- integrity sha512-R6oXQtEwm6r+v64MsE6/vFCwVqijBg6rvzxq70KTYmLVpbn01TH9+oZg+BQ/dkUkWoURPmubMLocPYMOMqUxoQ==
- dependencies:
- "@carbon/colors" "^10.37.0"
- "@carbon/grid" "^10.43.0"
- "@carbon/icons" "^10.48.0"
- "@carbon/import-once" "^10.7.0"
- "@carbon/layout" "^10.37.0"
- "@carbon/motion" "^10.29.0"
- "@carbon/themes" "^10.54.0"
- "@carbon/type" "^10.44.0"
+"@carbon/colors@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/colors/-/colors-11.0.0.tgz#01e7bb7ca7d71deea5c6f20e2d6bf99e7f47b618"
+ integrity sha512-12zcB3Hf6kgxzvrhMEnGEMs4m8ferwEOqkcmeKYmCTr7G3uTozcCdwYGc7vEFIjKPbmKNpQ3BJ+19k/+kMViDg==
+
+"@carbon/elements@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/elements/-/elements-11.0.0.tgz#fd25b02d70667f1c4a7bde8ea779e32444cd4f13"
+ integrity sha512-V0sV1hbI1Yc8K8dVh88SpB5YMoERfs+QwIDmNbf3nCpi7MBVijXmX2nprZL27MaEDlIuKOtO1Da7mCKUBfkDmQ==
+ dependencies:
+ "@carbon/colors" "^11.0.0"
+ "@carbon/grid" "^11.0.0"
+ "@carbon/icons" "^11.0.0"
+ "@carbon/layout" "^11.0.0"
+ "@carbon/motion" "^11.0.0"
+ "@carbon/themes" "^11.0.0"
+ "@carbon/type" "^11.0.0"
"@carbon/feature-flags@^0.7.0":
version "0.7.0"
resolved "https://registry.yarnpkg.com/@carbon/feature-flags/-/feature-flags-0.7.0.tgz#fe8068b482439ae7af519ccdbf627f31373bb646"
integrity sha512-nxVvnSMC6Ia/xn0j02FHPATfB/Iv6nnkZAQ6GrEdPLivSF1T2oaTvgawUsXBO8RBX7wQBq5l7uW8qH/0WfjIFw==
-"@carbon/grid@^10.43.0", "@carbon/grid@^10.43.1":
- version "10.43.1"
- resolved "https://registry.yarnpkg.com/@carbon/grid/-/grid-10.43.1.tgz#6332a9ab3a0730c7077e3b57fe88e140e13c1182"
- integrity sha512-gBfAEIfso5GjYPB1+BHjpNIfzDzBHb8xz9GRBhdrTlDVw9RJ4KH4MfYDeObiFQ/I7/6YCOE+LjjLv/BTm9iWBQ==
+"@carbon/grid@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/grid/-/grid-11.0.0.tgz#b3ead27a87883a78b6fca597306c1b0e13fce863"
+ integrity sha512-GFP5M4nH8tDEkOMgfKCV9ZA7I9SnDVgmg+L7vwlDHW6Kq1TS2jBoiLC7BBdeNE8RJZPk/lgDXn/56RV8hjrWVw==
dependencies:
- "@carbon/import-once" "^10.7.0"
- "@carbon/layout" "^10.37.1"
+ "@carbon/layout" "^11.0.0"
"@carbon/icon-helpers@^10.25.0":
version "10.25.0"
resolved "https://registry.yarnpkg.com/@carbon/icon-helpers/-/icon-helpers-10.25.0.tgz#bfe2465e165bb78477c77494610552064fcab09f"
integrity sha512-jvDUKz3NLopiDf7BROLDAT4NoswMpeXg4+ulbkLlFHdgY3v7gaxT/MJ7f9DZeEIiYUBhQSjTmcB3agIIO1jOdw==
-"@carbon/icon-helpers@^10.28.0":
- version "10.28.0"
- resolved "https://registry.yarnpkg.com/@carbon/icon-helpers/-/icon-helpers-10.28.0.tgz#702f1bb055c6c2bc203cdd44582ebd3d2801eaaf"
- integrity sha512-hf4fjouzr3jCvh5lTWJt87ABWmoq+3ck0/OOLpxUZLfhumTLRW+8H1Ctz0ldQh5mhmFaPNQUifll6tGI5bkmTw==
+"@carbon/icon-helpers@^10.29.0":
+ version "10.29.0"
+ resolved "https://registry.yarnpkg.com/@carbon/icon-helpers/-/icon-helpers-10.29.0.tgz#686bc5a337bec6d8fb482655f4564f3376452a35"
+ integrity sha512-QlYdeL97klhqahsayK6uEDPtr7imU4bdaudWPVZojg+7Uio3WNzb5iUNLkWA5zRLvP4xgcjSpbdDX2sT3CgL2A==
"@carbon/icons-react@^10.32.0":
version "10.42.0"
@@ -1191,74 +1189,83 @@
"@carbon/telemetry" "0.0.0-alpha.6"
prop-types "^15.7.2"
-"@carbon/icons-react@^10.49.0":
- version "10.49.0"
- resolved "https://registry.yarnpkg.com/@carbon/icons-react/-/icons-react-10.49.0.tgz#178f62fe2f5b343fa2d2034fb14203b01d44b894"
- integrity sha512-Lzz0A/DfR0fBye0pyxA/7+EPr1e0GeA5qYlxoOwOVJrp/L2vFuKPOe7QLBHkNgKly/BAdqN9Uo1IHKbp6Zljeg==
+"@carbon/icons-react@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/icons-react/-/icons-react-11.0.0.tgz#23651a3f9abacb7994eb5cad9017aba4e72272b1"
+ integrity sha512-ZAbBzRD/gs+NOv5fsTMvNPyYook64plDA8qFb59ANDxQg4EA717RjuVMlHK8uOkj5+fK0OjJ/5bLmfKLaXogsQ==
dependencies:
- "@carbon/icon-helpers" "^10.28.0"
+ "@carbon/icon-helpers" "^10.29.0"
"@carbon/telemetry" "0.1.0"
prop-types "^15.7.2"
-"@carbon/icons@^10.48.0":
- version "10.48.0"
- resolved "https://registry.yarnpkg.com/@carbon/icons/-/icons-10.48.0.tgz#a517812f42fc816ef9735409383111d8f23e7bff"
- integrity sha512-wLvTfQy4k/vF8oVH2T/esISogdyjWJ34KdlfD//A0bKa6YViJStnvyoJA8Pmi7XolVyKm5Cw1ho7CjV1TFBJSg==
-
-"@carbon/import-once@^10.7.0":
- version "10.7.0"
- resolved "https://registry.yarnpkg.com/@carbon/import-once/-/import-once-10.7.0.tgz#3e66e1308cad78272e2d9d9ea3741dd073860263"
- integrity sha512-KoqbfzGKjO89iUPabN6zNpXpcjxgQYgpHmesZ/DXc/zeV0PyHrnAOC8Q3J0cRPf1zYpGRHN2Tbw1ttTjonzbjg==
+"@carbon/icons@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/icons/-/icons-11.0.0.tgz#58ca9255579fbe8d4377ead3bf9c7ca045ee58d6"
+ integrity sha512-3kmWrXEcGaj2kqcWVYHFPwMSs6L/07C3irQZPgSXI9wioZxft/saifO/s6Grs2JhmVfW/60GZsVohKIH68qyeQ==
-"@carbon/layout@^10.37.0", "@carbon/layout@^10.37.1":
- version "10.37.1"
- resolved "https://registry.yarnpkg.com/@carbon/layout/-/layout-10.37.1.tgz#697ac4ba0500f55163cd84e0dc200d637fd41beb"
- integrity sha512-iX8rWc2CkFB7W7wi5NLa3pVRVb/jRI2KrVDna3FO3X3DgNz3zoRCgN+r2c+8FEhpJWeUwds5aDzTWUuTtlOT3w==
+"@carbon/layout@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/layout/-/layout-11.0.0.tgz#c77a171a5a8194088212295c2483a7003040d35d"
+ integrity sha512-F7Svd22CsvctkhgGksJf8sABdQWXmyOOH5EigrA6iq2fYRZFUryuiW95sQTOL7fhmc/VAA/vHneRtzJPHhPdow==
-"@carbon/motion@^10.29.0":
- version "10.29.0"
- resolved "https://registry.yarnpkg.com/@carbon/motion/-/motion-10.29.0.tgz#1e78c70d396ad3b9363f7a0c7e36ce9bac3d5702"
- integrity sha512-b8Cc9vgMlkQfLQAwq9Zt1/UfsrtGcWQpf0kK5gCamAuSmNSFWYJSwqbY9MeodxM2xNfXrxFcEFwqwy/E7egxUw==
+"@carbon/motion@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/motion/-/motion-11.0.0.tgz#2a6e4175ac0a29e9b9a9a83750deae46a0eeedb3"
+ integrity sha512-3KYZJEALeYq99EF/LyIbfa8NvkWeZAeAjlqlYGmCCs8rDihaX97NQ4QgfMT9kwzjD/3sEjV5CTmvI2CJJw0RfA==
-"@carbon/pictograms-react@^11.25.0":
- version "11.25.0"
- resolved "https://registry.yarnpkg.com/@carbon/pictograms-react/-/pictograms-react-11.25.0.tgz#816b43452f259bfa706f22bbeb15941447688ddc"
- integrity sha512-ueKBVgjRoiM0x1wWeoBuFd6l201uiXQOgAUfPytjXq1I9NIhgsjjKsjavbT1LZFs0wUtn8Xp7eJEh4/VprJBgQ==
+"@carbon/pictograms-react@^11.26.0":
+ version "11.26.0"
+ resolved "https://registry.yarnpkg.com/@carbon/pictograms-react/-/pictograms-react-11.26.0.tgz#ada43c23fbbf08281d7bf617541bf49804551226"
+ integrity sha512-mUIiYfwq4Q8NnAF8GOQiyAPx1+kHiCI5WO/Z9M4MPAWYQpTymeST123BvwT4yjwEETBb8+G2opAX3evRFmgpxw==
dependencies:
- "@carbon/icon-helpers" "^10.28.0"
+ "@carbon/icon-helpers" "^10.29.0"
"@carbon/telemetry" "0.1.0"
prop-types "^15.7.2"
-"@carbon/pictograms@^11.24.0":
- version "11.24.0"
- resolved "https://registry.yarnpkg.com/@carbon/pictograms/-/pictograms-11.24.0.tgz#55d490b82ae39b5eac20a1687858e8465f8b9a66"
- integrity sha512-dzlp7DIOYcuViFpQXHQKCH7cdfPmY3txc+SyzBXYyhWtwSjnjUOA/pv/wkvubR2gUQdxk9nCZK9CDl1HzahpiQ==
+"@carbon/pictograms@^12.0.0":
+ version "12.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/pictograms/-/pictograms-12.0.0.tgz#1a8878228b8b0dfacfd734fa1c326fcbcefec71e"
+ integrity sha512-tT3tq0ALMr4AXm1gVoqRxqGtj6xOylSjcG7t4iw3XZBEKbXtvv5LQUQOSnwvbpj72g8XNba9lBldWdxVULd/eQ==
-"@carbon/react@^0.17.0":
- version "0.17.0"
- resolved "https://registry.yarnpkg.com/@carbon/react/-/react-0.17.0.tgz#20e94f358488af2b972b1ed41df216adeb39a6e4"
- integrity sha512-mJDis2sc0FuVyVasxpbVPgpbcWkxAriyi8YtGh2c+wTfjJ9us/h+titl83pPAcQ6F0KFe3q4IqVho5vuFoWUwA==
+"@carbon/react@^1.0.0":
+ version "1.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/react/-/react-1.0.0.tgz#82fb9f0f4622591bff113267e11c23fb17eb556c"
+ integrity sha512-qlD6gpFHN2vSUxHUwDvn3n85PWK4M0rZeiTVGTLHWOG0k/V+dPs2kfl9BsXqtrv/U2RNQM4IqsP4Uw++v6WjTg==
dependencies:
+ "@babel/runtime" "^7.16.7"
"@carbon/feature-flags" "^0.7.0"
- "@carbon/icons-react" "^10.49.0"
- "@carbon/styles" "^0.17.0"
+ "@carbon/icons-react" "^11.0.0"
+ "@carbon/layout" "^11.0.0"
+ "@carbon/styles" "^1.0.0"
"@carbon/telemetry" "0.1.0"
- carbon-components "^10.56.0"
- carbon-components-react "^7.56.0"
- carbon-icons "^7.0.7"
+ classnames "2.3.1"
+ copy-to-clipboard "^3.3.1"
+ downshift "5.2.1"
+ flatpickr "4.6.9"
+ invariant "^2.2.3"
+ lodash.debounce "^4.0.8"
+ lodash.findlast "^4.5.0"
+ lodash.isequal "^4.5.0"
+ lodash.omit "^4.5.0"
+ lodash.throttle "^4.1.1"
+ prop-types "^15.7.2"
+ react-is "^17.0.2"
+ use-resize-observer "^6.0.0"
+ wicg-inert "^3.1.1"
+ window-or-global "^1.0.1"
-"@carbon/styles@^0.17.0":
- version "0.17.0"
- resolved "https://registry.yarnpkg.com/@carbon/styles/-/styles-0.17.0.tgz#8e3f0ff9cefee71ba27b772bf96fee7492057c4d"
- integrity sha512-L74nLSZyvmqVS+tWPbHKAbCstPJY2iJMTxw17ab1Ux0BPFp9M7ddkB486APRX9b1iQ15O4q8ibbjNaAEvv5/yg==
+"@carbon/styles@^1.0.0":
+ version "1.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/styles/-/styles-1.0.0.tgz#16a7819e20702bd009528ab40b4b8c0c333f87fd"
+ integrity sha512-DA/LPGVPFfqwyKUYONgFpOUMyK+WGE6lOpvF3M2CPMllRDL+nHe9treA7zKDhAKT4X96x0r8OkadOFGcgV1isQ==
dependencies:
- "@carbon/colors" "^10.37.0"
+ "@carbon/colors" "^11.0.0"
"@carbon/feature-flags" "^0.7.0"
- "@carbon/grid" "^10.43.0"
- "@carbon/layout" "^10.37.0"
- "@carbon/motion" "^10.29.0"
- "@carbon/themes" "^10.54.0"
- "@carbon/type" "^10.44.0"
+ "@carbon/grid" "^11.0.0"
+ "@carbon/layout" "^11.0.0"
+ "@carbon/motion" "^11.0.0"
+ "@carbon/themes" "^11.0.0"
+ "@carbon/type" "^11.0.0"
"@ibm/plex" "6.0.0-next.6"
"@carbon/telemetry@0.0.0-alpha.6":
@@ -1282,23 +1289,22 @@
resolved "https://registry.yarnpkg.com/@carbon/telemetry/-/telemetry-0.1.0.tgz#57b331cd5a855b4abbf55457456da8211624d879"
integrity sha512-kNWt0bkgPwGW0i5h7HFuljbKRXPvIhsKbB+1tEURAYLXoJg9iJLF1eGvWN5iVoFCS2zje4GR3OGOsvvKVe7Hlg==
-"@carbon/themes@^10.54.0":
- version "10.54.0"
- resolved "https://registry.yarnpkg.com/@carbon/themes/-/themes-10.54.0.tgz#2d310382298bf711eef18757acbab19f16b1b345"
- integrity sha512-Q//XENDqFcgJbide0QbaAvAOKg/u3HIR3na0DsmoWtX4ZWrSz8zpUdvN8Yy9ybJBg1dT+IOfNCdjjhjbCVikKA==
+"@carbon/themes@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/themes/-/themes-11.0.0.tgz#0f7a44df698a72fd774801a2b228c0d5ed578fef"
+ integrity sha512-iq1GE3AgfFXwUwtsV9dpNzNgTNr6Wd8RcXr36VcILPw251CUrn9RB53GWYTK8uMWTHXmnhg3BJnBac2GOq5X2Q==
dependencies:
- "@carbon/colors" "^10.37.0"
- "@carbon/layout" "^10.37.0"
- "@carbon/type" "^10.44.0"
+ "@carbon/colors" "^11.0.0"
+ "@carbon/layout" "^11.0.0"
+ "@carbon/type" "^11.0.0"
color "^3.1.2"
-"@carbon/type@^10.44.0":
- version "10.44.0"
- resolved "https://registry.yarnpkg.com/@carbon/type/-/type-10.44.0.tgz#f70944fe25b225d2dc44cea31fa2e7a400d4772c"
- integrity sha512-sLe4e9gu2QuM8k6PrXWc9xWpH6W9Q/FJ+/IHNFpx+8zBLkBsM6dbf4o76Zw9OcV2HuAA+8K3JOpZJ4r76fw8kg==
+"@carbon/type@^11.0.0":
+ version "11.0.0"
+ resolved "https://registry.yarnpkg.com/@carbon/type/-/type-11.0.0.tgz#0b263189fb60acfae496769143c5c71fed5d7101"
+ integrity sha512-D3ww1hrvfzXy2bnEmZTJoFDVZpB+78T1D2sOqXDjFaB+7A2+E/PAmla37Qzcz8ZMxF8kAorpG8wOTYAp2dg2kw==
dependencies:
- "@carbon/grid" "^10.43.0"
- "@carbon/import-once" "^10.7.0"
+ "@carbon/grid" "^11.0.0"
"@carbon/utils-position@1.1.1":
version "1.1.1"
@@ -3467,6 +3473,11 @@ argparse@^1.0.7:
dependencies:
sprintf-js "~1.0.2"
+argparse@^2.0.1:
+ version "2.0.1"
+ resolved "https://registry.yarnpkg.com/argparse/-/argparse-2.0.1.tgz#246f50f3ca78a3240f6c997e8a9bd1eac49e4b38"
+ integrity sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==
+
aria-query@^4.2.2:
version "4.2.2"
resolved "https://registry.yarnpkg.com/aria-query/-/aria-query-4.2.2.tgz#0d2ca6c9aceb56b8977e9fed6aed7e15bbd2f83b"
@@ -4745,32 +4756,6 @@ capture-stack-trace@^1.0.0:
resolved "https://registry.yarnpkg.com/capture-stack-trace/-/capture-stack-trace-1.0.1.tgz#a6c0bbe1f38f3aa0b92238ecb6ff42c344d4135d"
integrity sha512-mYQLZnx5Qt1JgB1WEiMCf2647plpGeQ2NMR/5L0HNZzGQo4fuSPnK+wjfPnKZV0aiJDgzmWqqkV/g7JD+DW0qw==
-carbon-components-react@^7.56.0:
- version "7.56.0"
- resolved "https://registry.yarnpkg.com/carbon-components-react/-/carbon-components-react-7.56.0.tgz#62e9de3e5ea505f7ba56f192a8ecd4e0d9963b98"
- integrity sha512-yO4+KhfG0Ujs9Eka0IsdIbB6U8ohtMXI4AWTaaBYqMgT4UNdcOUHqo6THgZpCRJfjYMyNnIh6Fi6d8NgyV6s4g==
- dependencies:
- "@babel/runtime" "^7.16.7"
- "@carbon/feature-flags" "^0.7.0"
- "@carbon/icons-react" "^10.49.0"
- "@carbon/layout" "^10.37.0"
- "@carbon/telemetry" "0.1.0"
- classnames "2.3.1"
- copy-to-clipboard "^3.3.1"
- downshift "5.2.1"
- flatpickr "4.6.9"
- invariant "^2.2.3"
- lodash.debounce "^4.0.8"
- lodash.findlast "^4.5.0"
- lodash.isequal "^4.5.0"
- lodash.omit "^4.5.0"
- lodash.throttle "^4.1.1"
- prop-types "^15.7.2"
- react-is "^17.0.2"
- use-resize-observer "^6.0.0"
- wicg-inert "^3.1.1"
- window-or-global "^1.0.1"
-
carbon-components@10.40.0:
version "10.40.0"
resolved "https://registry.yarnpkg.com/carbon-components/-/carbon-components-10.40.0.tgz#59c339dd964624cd07802dc695ceed6f32a07ef7"
@@ -4781,21 +4766,6 @@ carbon-components@10.40.0:
lodash.debounce "^4.0.8"
warning "^3.0.0"
-carbon-components@^10.56.0:
- version "10.56.0"
- resolved "https://registry.yarnpkg.com/carbon-components/-/carbon-components-10.56.0.tgz#bb5890f00f81cebcddfa2dbae4794477deb539f4"
- integrity sha512-GPLqHiu2SWvMxcQOi/CcgA/XA3aX/5HiEPSQjLwzjKAJsnkpzq043Jf7QwgLOVbTBzGSjFbFkJnE2lc73I2WBw==
- dependencies:
- "@carbon/telemetry" "0.1.0"
- flatpickr "4.6.1"
- lodash.debounce "^4.0.8"
- warning "^3.0.0"
-
-carbon-icons@^7.0.7:
- version "7.0.7"
- resolved "https://registry.yarnpkg.com/carbon-icons/-/carbon-icons-7.0.7.tgz#ebafe3e9fa25df973796a8eca06d8a7c501cc610"
- integrity sha512-3vgkdXJRgCViCrH3fLUdyAXo0I8wmohO6QETv7vWFx6yc7s+SirWFBSFL38zUx4MHtR8iTxIlLEzkeU6FlFtXg==
-
ccount@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/ccount/-/ccount-1.1.0.tgz#246687debb6014735131be8abab2d93898f8d043"
@@ -6779,6 +6749,11 @@ entities@^2.0.0:
resolved "https://registry.yarnpkg.com/entities/-/entities-2.2.0.tgz#098dc90ebb83d8dffa089d55256b351d34c4da55"
integrity sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==
+entities@~2.1.0:
+ version "2.1.0"
+ resolved "https://registry.yarnpkg.com/entities/-/entities-2.1.0.tgz#992d3129cf7df6870b96c57858c249a120f8b8b5"
+ integrity sha512-hCx1oky9PFrJ611mf0ifBLBRW8lUUVRlFolb5gWRfIELabBlbp9xZvrqZLZAs+NxFnbfQoeGd8wDkygjg7U85w==
+
envinfo@^7.8.1:
version "7.8.1"
resolved "https://registry.yarnpkg.com/envinfo/-/envinfo-7.8.1.tgz#06377e3e5f4d379fea7ac592d5ad8927e0c4d475"
@@ -8491,17 +8466,17 @@ gatsby-telemetry@^3.9.0:
lodash "^4.17.21"
node-fetch "^2.6.7"
-gatsby-theme-carbon@^3.0.0-next.7:
- version "3.0.0-next.7"
- resolved "https://registry.yarnpkg.com/gatsby-theme-carbon/-/gatsby-theme-carbon-3.0.0-next.7.tgz#b1e02fd2486bade7db8bf3787d9a1c878d6c02b4"
- integrity sha512-+QR/YUhPIbaLcXPTj+0ColS3JBxaOilMokI89LPnIklqgya1Mn2tRb0UccrMK/WPhUvgiTtPuoRpB0g6OGn35A==
+gatsby-theme-carbon@^3.0.0-next.9:
+ version "3.0.0-next.9"
+ resolved "https://registry.yarnpkg.com/gatsby-theme-carbon/-/gatsby-theme-carbon-3.0.0-next.9.tgz#77d1e5bd817b7e9657e982ac2b0ac0189123d2b3"
+ integrity sha512-aS5IOppmdJiWQ83A9RGF95zh/BIJLrYl6UP9sYBDZZlzUeLw69/NxwZeg0sYb1ylYr6TfTi9klzS5XHBLSjS/A==
dependencies:
"@babel/core" "^7.14.6"
- "@carbon/elements" "^10.55.0"
- "@carbon/grid" "^10.43.1"
- "@carbon/pictograms-react" "^11.25.0"
- "@carbon/react" "^0.17.0"
- "@carbon/themes" "^10.54.0"
+ "@carbon/elements" "^11.0.0"
+ "@carbon/grid" "^11.0.0"
+ "@carbon/pictograms-react" "^11.26.0"
+ "@carbon/react" "^1.0.0"
+ "@carbon/themes" "^11.0.0"
"@mdx-js/mdx" "^1.5.5"
"@mdx-js/react" "^1.5.5"
"@reach/router" "^1.2.1"
@@ -10628,10 +10603,10 @@ lines-and-columns@^1.1.6:
resolved "https://registry.yarnpkg.com/lines-and-columns/-/lines-and-columns-1.2.4.tgz#eca284f75d2965079309dc0ad9255abb2ebc1632"
integrity sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==
-linkify-it@^2.0.0:
- version "2.2.0"
- resolved "https://registry.yarnpkg.com/linkify-it/-/linkify-it-2.2.0.tgz#e3b54697e78bf915c70a38acd78fd09e0058b1cf"
- integrity sha512-GnAl/knGn+i1U/wjBz3akz2stz+HrHLsxMwHQGofCDfPvlf+gDKN58UtfmUquTY4/MXeE2x7k19KQmeoZi94Iw==
+linkify-it@^3.0.1:
+ version "3.0.3"
+ resolved "https://registry.yarnpkg.com/linkify-it/-/linkify-it-3.0.3.tgz#a98baf44ce45a550efb4d49c769d07524cc2fa2e"
+ integrity sha512-ynTsyrFSdE5oZ/O9GEf00kPngmOfVwazR5GKDq6EYfhlpFug3J2zybX56a2PRRpc9P+FuSoGNAwjlbDs9jJBPQ==
dependencies:
uc.micro "^1.0.1"
@@ -11139,14 +11114,14 @@ markdown-escapes@^1.0.0:
resolved "https://registry.yarnpkg.com/markdown-escapes/-/markdown-escapes-1.0.4.tgz#c95415ef451499d7602b91095f3c8e8975f78535"
integrity sha512-8z4efJYk43E0upd0NbVXwgSTQs6cT3T06etieCMEg7dRbzCbxUCK/GHlX8mhHRDcp+OLlHkPKsvqQTCvsRl2cg==
-markdown-it@^9.0.1:
- version "9.1.0"
- resolved "https://registry.yarnpkg.com/markdown-it/-/markdown-it-9.1.0.tgz#df9601c168568704d554b1fff9af0c5b561168d9"
- integrity sha512-xHKG4C8iPriyfu/jc2hsCC045fKrMQ0VexX2F1FGYiRxDxqMB2aAhF8WauJ3fltn2kb90moGBkiiEdooGIg55w==
+markdown-it@^12.3.2:
+ version "12.3.2"
+ resolved "https://registry.yarnpkg.com/markdown-it/-/markdown-it-12.3.2.tgz#bf92ac92283fe983fe4de8ff8abfb5ad72cd0c90"
+ integrity sha512-TchMembfxfNVpHkbtriWltGWc+m3xszaRD0CZup7GFFhzIgQqxIfn3eGj1yZpfuflzPvfkt611B2Q/Bsk1YnGg==
dependencies:
- argparse "^1.0.7"
- entities "~1.1.1"
- linkify-it "^2.0.0"
+ argparse "^2.0.1"
+ entities "~2.1.0"
+ linkify-it "^3.0.1"
mdurl "^1.0.1"
uc.micro "^1.0.5"