-
Notifications
You must be signed in to change notification settings - Fork 147
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into rc-file-input-checklist
- Loading branch information
Showing
16 changed files
with
1,737 additions
and
546 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,4 @@ | ||
# Supported browsers | ||
> 2% | ||
last 2 versions | ||
IE 11 | ||
not dead |
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
* @uswds/admins | ||
|
||
# This is a comment. | ||
# Each line is a file pattern followed by one or more owners. | ||
|
||
# These owners will be the default owners for everything in | ||
# the repo. Unless a later match takes precedence, | ||
# @global-owner1 and @global-owner2 will be requested for | ||
# review when someone opens a pull request. | ||
# * @global-owner1 @global-owner2 | ||
|
||
# Order is important; the last matching pattern takes the most | ||
# precedence. When someone opens a pull request that only | ||
# modifies JS files, only @js-owner and not the global | ||
# owner(s) will be requested for a review. | ||
# *.js @js-owner #This is an inline comment. | ||
|
||
# You can also use email addresses if you prefer. They'll be | ||
# used to look up users just like we do for commit author | ||
# emails. | ||
# *.go docs@example.com | ||
|
||
# Teams can be specified as code owners as well. Teams should | ||
# be identified in the format @org/team-name. Teams must have | ||
# explicit write access to the repository. In this example, | ||
# the octocats team in the octo-org organization owns all .txt files. | ||
# *.txt @octo-org/octocats | ||
|
||
# In this example, @doctocat owns any files in the build/logs | ||
# directory at the root of the repository and any of its | ||
# subdirectories. | ||
# /build/logs/ @doctocat | ||
|
||
# The `docs/*` pattern will match files like | ||
# `docs/getting-started.md` but not further nested files like | ||
# `docs/build-app/troubleshooting.md`. | ||
# docs/* docs@example.com | ||
|
||
# In this example, @octocat owns any file in an apps directory | ||
# anywhere in your repository. | ||
# apps/ @octocat | ||
|
||
# In this example, @doctocat owns any file in the `/docs` | ||
# directory in the root of your repository and any of its | ||
# subdirectories. | ||
# /docs/ @doctocat | ||
|
||
# In this example, any change inside the `/scripts` directory | ||
# will require approval from @doctocat or @octocat. | ||
# /scripts/ @doctocat @octocat | ||
|
||
# In this example, @octocat owns any file in a `/logs` directory such as | ||
# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes | ||
# in a `/logs` directory will require approval from @octocat. | ||
# **/logs @octocat | ||
|
||
# In this example, @octocat owns any file in the `/apps` | ||
# directory in the root of your repository except for the `/apps/github` | ||
# subdirectory, as its owners are left empty. | ||
# /apps/ @octocat | ||
# /apps/github | ||
|
||
# In this example, @octocat owns any file in the `/apps` | ||
# directory in the root of your repository except for the `/apps/github` | ||
# subdirectory, as this subdirectory has its own owner @doctocat | ||
# /apps/ @octocat | ||
# /apps/github @doctocat |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
ruby 3.2.5 | ||
nodejs 20.9.0 | ||
nodejs 22.11.0 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,4 @@ | ||
- **Use semantic heading levels.** Though our default code uses an `<h4>`, use the correct heading level in your own implementation. | ||
- **Use aria-label="progress".** Placing this `aria-label` on the element with the class `usa-step-indicator` helps provide important context to screen readers. | ||
- **Use visually hidden text on labels.** Use visually hidden text make the completion status of each step explicit. | ||
- **Indicate the current step.** When using labeled segments, use `aria-current="true"` on the list item representing the current step. | ||
- **Hide unlabeled segments.** There is no content inside the segments when labels aren't used, so it is safe to add `aria-hidden="true"` to the element with the class name `usa-step-indicator__segments`. | ||
- **Hide unlabeled segments.** There is no content inside the segments when labels aren't used, so it is safe to add `aria-hidden="true"` to the element with the class name `usa-step-indicator__segments`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.