Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: fix typos #16292

Merged
merged 4 commits into from
May 13, 2024
Merged

docs: fix typos #16292

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5ff5da6
fix typos
omahs Apr 30, 2024
670ed65
fix typos
omahs Apr 30, 2024
d92c33e
Merge branch 'main' into patch-1
tay1orjones May 2, 2024
765d737
chore: yarn format
tay1orjones May 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 9 additions & 9 deletions docs/guides/accessibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ tools <span aria-label="hammer and wrench">🛠</span>.
upper left.
6. Navigate back to the 'Options' menu for the DAP plugin and paste that copied
token into the input and hit 'Apply'.
7. Select the latest ruleset (it should have a month and a date in it's title).
7. Select the latest ruleset (it should have a month and a date in its title).

## AVT1

Expand All @@ -78,12 +78,12 @@ before you push a PR, feel free to disregard them.

If the component fails or has a violation an issue should be made so that
someone can fix the problem. Feel free to include in the issue any relevant
information you think would helpful, but make sure to at least include these
information you think would be helpful, but make sure to at least include these
points:

1. The environment where the failure happened. The browser make and version as
well as the ruleset and operating system.
2. A description of the failure (copy an pasted from DAP's logs is fine).
2. A description of the failure (copy and pasted from DAP's logs is fine).
3. A screenshot of the particular offending code.
4. Steps to reproduce the violation for anyone who may want to tackle the issue
but may not have read this guide.
Expand Down Expand Up @@ -113,7 +113,7 @@ release. To do that:
["Keyboard accessibility is one of the most important aspects of web accessibility."](https://webaim.org/techniques/keyboard/)
and it's the focus of part 1 of our AVT2 testing!

Here's what we're looking for during our AVT2 audit. Therea are two main parts:
Here's what we're looking for during our AVT2 audit. There are two main parts:

### Keyboard accessibility testing⌨️

Expand All @@ -130,7 +130,7 @@ Here's what we're looking for during our AVT2 audit. Therea are two main parts:
_Any variance on these standardized keystrokes should be outlined clearly
to the user beforehand_

3. If an element can receive keyboard focus it should reflect that in it's
3. If an element can receive keyboard focus it should reflect that in its
styling with a focused state.
4. If you can move focus to an element with the keyboard you should be able to
move focus away from that element with a keyboard.
Expand Down Expand Up @@ -176,14 +176,14 @@ can dig into those points further:

Depending on hover as a mouse action to trigger a dialogue or tooltip isn't
accessible. Commonly a screen magnifier shows a zoomed in view of the page
relative to the cursor position. This means that unless then tooltip or
relative to the cursor position. This means that unless the tooltip or
dialogue is quite small the user can't trigger the component _and_ scroll
it's content into view.
its content into view.

3. Don't obscure content on mouse hover

Obscuring all or some of the page on mouse hover with an overlay or blur is a
problem for user of screen magnifiers. Maintain required contrast ration and
problem for user of screen magnifiers. Maintain required contrast ratio and
instead signal to your users with some other visual distinction.

#### How to test
Expand All @@ -198,7 +198,7 @@ impairment every day.

##### Using DAP👷

Let's DAP! It's pretty straight forward, but there are a few gotchas. For
Let's DAP! It's pretty straightforward, but there are a few gotchas. For
consistency's sake we'll use DAP on the
[Dynamic Assessment Plug-in Homepage](https://ibm.biz/BdYkM9).

Expand Down
4 changes: 2 additions & 2 deletions docs/release-schedule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ features and fixes. The work we deliver into `main` every day is considered
unstable. Every two weeks we package up these changes into a new minor version
that is published from `main` to the current Active major.

For a look at what types of changes consitute patch, minor, or major version
For a look at what types of changes constitute patch, minor, or major version
bumps, see the
[versioning documentation](https://github.com/carbon-design-system/carbon/blob/main/docs/guides/versioning.md).

Expand All @@ -47,7 +47,7 @@ within the monorepo, see the
For a release in the Maintenance phase, patch releases are published containing
security patches and critical bug fixes. When a version moves from Active to
Maintenance, consuming projects should begin migrating to the new Active major
version.  During Maintenance we also consider adding non-critical bug fixes on
version. During Maintenance we also consider adding non-critical bug fixes on
an ad hoc basis, by request only. To request a fix be back-ported to a
Maintenance release, please
[open an issue](https://github.com/carbon-design-system/carbon/issues/new?assignees=&labels=type%3A+bug+%F0%9F%90%9B&projects=&template=BUG_REPORT.yaml&title=%5BBug%5D%3A+)
Expand Down