An official website of the United States government
-
Here’s how you know
-
-
-
-
-
-
-
-
-
-
- Official websites use .gov
-
- A .gov website belongs to an official government organization in the United States.
-
-
-
-
-
-
-
- Secure .gov websites use HTTPS
-
- A lock (
-
-) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
-
diff --git a/docs/_utilities/images.md b/docs/_utilities/images.md
deleted file mode 100644
index cbe68261..00000000
--- a/docs/_utilities/images.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Images
-lead: This guidance is intended to help you use images effectively in Login.gov products.
-redirect_from:
- - /accessibility/policies/
- - /images/
----
-
-## Illustrations
-
-Login.gov uses illustrations throughout our products and services to help create an easy to follow guidance of our products and services. Below is guidance on how to use and create imagery that is in line with our brand.
-
-### Be useful
-
-Illustration provides context, adds clarity, builds consistency, and lead users to their next step. Ultimately, any illustration should provide a deeper understanding of the application or brand.
-
-### Be consistent
-
-Being consistent in illustration means considering details of a single illustration, as well as looking at the body of illustration work as a whole. Consistency speaks to quality: of the illustration and of the product it represents.
-
-### Be focused
-
-Illustration is most effective when it is precise in choosing a single message to deliver. With every narrative that is built there needs to be a focal point, a hierarchy of elements that contribute to the single, pointed message. With every illustration, we ask ourselves “what are we trying to say?”
-
-
-
-
-
-
-### Be accessible
-
-Illustrations are often decorative images. A decorative image does not add information to the content of a page. Unlike an informative image, a decorative image can be hidden from screen readers. We set decorative images as "hidden" from screen readers to help prevent a confusing, redundant and/or a tedious experience.
-
-For decorative images, the `alt` attribute should be set as empty. Avoid ommitting the `alt` attribute altogether. If the `alt` attribute is not used, a screen reader will read out the full filename to the user, which is not an accessible or good user experience.
-
-**Additional resources on decorative images:**
-
-- [18F Accessibility Guide: Images](https://accessibility.18f.gov/images/)
-- [Accessibility for Teams: UX Design - Images](https://accessibility.digital.gov/ux/images/)
-- [W3.org - Decorative Images](https://www.w3.org/WAI/tutorials/images/decorative/)
-- [W3.org - Tips and Tricks for Text Alternatives](https://www.w3.org/WAI/tutorials/images/tips/)
-- [W3.org WAI-ARIA - 5.2.7 Accessible Name Calculation](https://www.w3.org/WAI/PF/aria/complete#namecalculation) (When working with an aria-label attribute)
-- [WebAIM: Alternative Text - Context is Everything](https://webaim.org/techniques/alttext/#context)
diff --git a/docs/_utilities/typography.md b/docs/_utilities/typography.md
deleted file mode 100644
index 15c1f490..00000000
--- a/docs/_utilities/typography.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Typography
-lead: >
- When writing longform text (a page like this), wrap the text in div.usa-prose to activate these styles.
-redirect_from:
- - /typography/
----
-
-## Display, headings, and lead
-
-Use div.usa-prose to indicate that the immediately containing headings and paragraphs should be considered a longform text document.
-
-
-
How Login.gov keeps personal information private (div.usa-display)
-
-
Login.gov encrypts the personal information of each user separately, using a unique value generated from each user’s password. Our encryption method works like a safe deposit box in a bank vault. Only the user has the key. Only the user can open the box to reveal the contents. Only the user knows the password, and only the user can decrypt their information. (p.usa-intro)
-
-
The vault (h1)
-
-
It’s hard to break into the “vault” or database. Login.gov implements the latest National Institute of Standards and Technology (NIST) standards for secure authentication and verification. Our plans for ongoing security include regular penetration testing and external security reviews.
-
-
The safe deposit box (h2)
-
-
Individual accounts get a double layer of security. We require two-factor authentication as well as strong passwords that meet new NIST requirements. Two factor authentication requires that you login with your password and a code that we send to your phone.
-
-
We will evaluate and implement new authentication methods as they become widely available to make sure that Login.gov remains accessible and secure.
-
-
Your personal key (h3)
-
-
Encrypting personal data separately means that Login.gov cannot share any information with other government entities without users’ permission. Not even database administrators can decrypt a user’s personal information without the user’s password.
-
-
Join us on GitHub (h4)
-
-
We welcome external review of our privacy-protection measures. All of our code is available for public inspection in an open-source repository. Our goal: make sure that at every step users know their privacy is being protected by design.
-
-
More information on Login.gov (h5)
-
-
For more information, please visit the Login.gov Help Center or contact us. You can also visit our open-source repository.
-
-
Simple and secure (h6)
-
-
Dedicated teams of design and security experts will continuously improve it.
-
-
-
We welcome external review of our privacy-protection measures. All of our code is available for public inspection in an open-source repository. Our goal: make sure that at every step users know their privacy is being protected by design.
-
For more information, please visit the Login.gov Help Center or contact us. You can also visit our open-source repository.
-
Dedicated teams of design and security experts will continuously improve it.
-
-
diff --git a/docs/accessibility.md b/docs/accessibility.md
deleted file mode 100644
index 7fd70f6b..00000000
--- a/docs/accessibility.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-permalink: /accessibility/
-title: Accessibility
-redirect_to: https://login.gov/accessibility/
----
diff --git a/docs/brand.md b/docs/brand.md
deleted file mode 100644
index 90918aed..00000000
--- a/docs/brand.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-permalink: /brand/
-title: Brand
-sidenav:
- - text: Logo
- href: "#logo"
- - text: Logo usage
- href: "#logo-usage"
- - text: Tagline
- href: "#tagline"
-lead: >
- When working with the Login.gov brand, follow these guidelines to ensure you're representing the product in a consistent way across all mediums.
----
-
-## Logo
-
-Consistent and repeated use of the logo and lockups will establish equity and strengthen the visual identity of Login.gov. To ensure consistency, it is critical that every person who uses the logo does so in accordance with the guidelines that follow, regardless of personal preference.
-
-### The shield and wordmark
-
-The Login.gov logo is the cornerstone of our brand. Whenever possible, the red and blue version should be used. A white (or reverse) version can be used on a dark background.
-
-
-
-
-
-### Whitespace
-
-The logo should always be surrounded by generous white space. The diagram below defines the minimum amount of clear space needed, which is based on the cap-height of the typography.
-
-
-
-### Minimum size
-
-Establishing a minimum size ensures that the impact and legibility of the logo is not compromised in application.
-
-
-
-## Logo Usage
-
-### Incorrect color usage
-
-For optimum legibility and brand consistency, the logo should never be used in white with a light background. Conversely, the standard logo should never appear on a dark background.
-
-
-
-
-
-### Do not modify the logo
-
-
-
- Do not outline.
-
-
-
- Do not skew.
-
-
-
- Do not apply effects.
-
-
-
- Do not adjust spacing.
-
-
-
- Do not apply drop shadows.
-
-
-
- Do not distort.
-
-
-
- Do not apply brand colors.
-
-
-
- Do not apply gradients.
-
-
-
- Do not rotate.
-
-
-
- Do not mask images or graphics.
-
-
-
- Do not use additional colors.
-
-
-
- Do not separate the shield from the wordmark.
-
-
-
-
-## Tagline
-
-Taglines help to create a continued, consistent brand messaging. Login.gov has created a plain language tagline:
-
-**"The public's one account for government."**
-
-This tagline is meant to be used alongside our logo and other marketing materials to simply describe our program.
diff --git a/docs/img/login-gov-logo-brand-colored.svg b/docs/img/login-gov-logo-brand-colored.svg
deleted file mode 100644
index 2bb1cf70..00000000
--- a/docs/img/login-gov-logo-brand-colored.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-colored.svg b/docs/img/login-gov-logo-colored.svg
deleted file mode 100644
index eafa54df..00000000
--- a/docs/img/login-gov-logo-colored.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-distorted.svg b/docs/img/login-gov-logo-distorted.svg
deleted file mode 100644
index 67e81f18..00000000
--- a/docs/img/login-gov-logo-distorted.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-gradiented.svg b/docs/img/login-gov-logo-gradiented.svg
deleted file mode 100644
index 8c11c1b8..00000000
--- a/docs/img/login-gov-logo-gradiented.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-masked.svg b/docs/img/login-gov-logo-masked.svg
deleted file mode 100644
index 404d15c7..00000000
--- a/docs/img/login-gov-logo-masked.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-minimum-size.svg b/docs/img/login-gov-logo-minimum-size.svg
deleted file mode 100644
index e882caee..00000000
--- a/docs/img/login-gov-logo-minimum-size.svg
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-outlined.svg b/docs/img/login-gov-logo-outlined.svg
deleted file mode 100644
index 8b580ba1..00000000
--- a/docs/img/login-gov-logo-outlined.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-rotated.svg b/docs/img/login-gov-logo-rotated.svg
deleted file mode 100644
index b0fbc0d3..00000000
--- a/docs/img/login-gov-logo-rotated.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-shadowed.svg b/docs/img/login-gov-logo-shadowed.svg
deleted file mode 100644
index 6397566f..00000000
--- a/docs/img/login-gov-logo-shadowed.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-skewed.svg b/docs/img/login-gov-logo-skewed.svg
deleted file mode 100644
index 177b7f6d..00000000
--- a/docs/img/login-gov-logo-skewed.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-spaced.svg b/docs/img/login-gov-logo-spaced.svg
deleted file mode 100644
index d8de6ea3..00000000
--- a/docs/img/login-gov-logo-spaced.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-spacing.svg b/docs/img/login-gov-logo-spacing.svg
deleted file mode 100644
index eeb395b0..00000000
--- a/docs/img/login-gov-logo-spacing.svg
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-logo-with-effects.svg b/docs/img/login-gov-logo-with-effects.svg
deleted file mode 100644
index 4af77f61..00000000
--- a/docs/img/login-gov-logo-with-effects.svg
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/img/login-gov-shield.svg b/docs/img/login-gov-shield.svg
deleted file mode 100644
index cac9baee..00000000
--- a/docs/img/login-gov-shield.svg
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
\ No newline at end of file
diff --git a/docs/index.md b/docs/index.md
deleted file mode 100644
index 2d3347b1..00000000
--- a/docs/index.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-permalink: /
-layout: home
-title: Overview
-lead: >
- Use the Login.gov Design System when developing Login.gov sites to consistently identify the Login.gov brand.
----
-
-
-
-
-# Installs in seconds
-
-Install images, stylesheets, and script files in both their original and compiled forms with npm.
-
-
-
-
-
-
-# Built with USWDS
-
-The {{ site.title }} is built using the [U.S. Web Design System](https://designsystem.digital.gov/) for a consistent appearance across government sites.
-
-
-
-
-
-
-# A work in progress
-
-The latest version is {{ site.package_json.this_version }} which uses uswds@{{ site.package_json['@uswds/uswds_version'] }}. Spot an issue? We’d love to hear about it [on GitHub](https://github.com/18F/identity-design-system/issues).
-
-
-
-
-
-
diff --git a/docs/security-experience-principles.md b/docs/security-experience-principles.md
deleted file mode 100644
index 10d6c867..00000000
--- a/docs/security-experience-principles.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-permalink: /security-experience-principles/
-title: Security Experience Principles
-lead: >
- Login.gov is a human-centered design product and service with a specific focus on creating an optimal security experience for the public.
----
-
-Our team leverages the following principles to guide us to create the best security product for the public.
-
-We also leverage the [U.S. Web Design System’s design principles](https://designsystem.digital.gov/design-principles/) to guide our work.
-
-## Security experience is everyone’s job.
-
-**Creating a secure, usable experience is a priority for everyone at Login.gov.** We are all responsible for maintaining the integrity of our products and services. We prioritize protecting the public’s data in sync with our practice of continuously improving our product. As users use Login.gov, we should ensure their security awareness is raised. We want to affect users to keep their entire digital presence secure, not just their Login.gov presence. [You can read more about our security and privacy practices](https://login.gov/policy/our-security-practices/).
-
-### Key considerations
-
-- Will a change to the visual design or content of our product impact the users' understanding of the security of the product?
-- What are we doing to keep track of the security implications for any changes made to Login.gov?
-- What are we doing to continue the practice of keeping our data private?
-- Are users given options to show/hide sensitive data?
-- Will a change to visual design or content require storing new data via the server or the browser?
-- Does this change share new data not previously shared? Or share that data with a new audience?
-- Will error states or displayed messages reveal too much information and create a security risk?
-
-## The public controls their data, not us.
-
-**Users are in control of their data. We prioritize user privacy and do not profit from sharing user data.** Personally Identifiable Information (PII) is only shared as needed and all sensitive data is encrypted. Our encryption methods are like putting data in a safety deposit box and only users have the key. Users have the ability to share or hide sensitive information, give or revoke consent to share that data or delete that data at any time.
-
-### Key considerations
-
-- Are users aware of what data they are sharing, who they are sharing it with and how it is used?
-- Is language around consent for sharing their data written in [plain language](https://www.plainlanguage.gov/) and [accessible](https://login.gov/accessibility/)?
-- Does the public understand that they have the right to revoke consent of the sharing of their data?
-
-## Simple, secure login for everyone.
-
-**Using our product is simple and secure.** Whether users interact with our product once or multiple times a day, their experience with Login.gov will be seamless. Design and content facilitates ease of use and allows users to focus on the task they are trying to complete with our partner agencies.
-
-### Key considerations
-
-- Is our design and content helping or hindering users from completing the task at hand?
-- Are we consistently testing our designs and content with the public?
-- Are we looking for things to remove or streamline to help users quickly get on their way to the partner site?
-- Are we guiding users with low security awareness towards the most secure options?
diff --git a/test/accessibility.test.js b/test/accessibility.test.js
index 7b9ca0e3..4acde1d7 100644
--- a/test/accessibility.test.js
+++ b/test/accessibility.test.js
@@ -1,12 +1,13 @@
/* eslint-disable no-await-in-loop */
import path from 'path';
-import { getURLsFromSitemap } from './support/sitemap';
+const LOCAL_HOST = `http://localhost:${process.env.JEST_PORT}`;
const MESSAGE_TYPE_ERROR = 1;
test('accessibility', async () => {
- const urls = await getURLsFromSitemap();
+ await page.goto(LOCAL_HOST);
+ const urls = await page.$$eval('.usa-nav__link', (links) => links.map((link) => link.href));
for (const url of urls) {
await page.goto(url);
diff --git a/test/color.test.js b/test/color.test.js
deleted file mode 100644
index 8345b739..00000000
--- a/test/color.test.js
+++ /dev/null
@@ -1,26 +0,0 @@
-const host = `http://localhost:${process.env.JEST_PORT}`;
-
-const rgb2hex = (rgb) => {
- const [, red, green, blue] = /rgb\((\d+), (\d+), (\d+)\)/.exec(rgb);
- const parts = [red, green, blue].map((d) => `0${Number(d).toString(16)}`.slice(-2));
- return `#${parts.join('')}`;
-};
-
-test('hex codes match background color on the color documentation page', async () => {
- await page.goto(`${host}/utilities/color/`);
- const colors = await page.$$eval("[data-test='color-swatch']", (els) =>
- [...els].map((el) => {
- const text = el.innerText.trim();
- const background = window.getComputedStyle(el).backgroundColor;
-
- return { text, background };
- }),
- );
-
- expect(colors.length).toBe(56);
-
- colors.forEach((swatch) => {
- const backgroundColor = rgb2hex(swatch.background);
- expect(swatch.text).toBe(backgroundColor);
- });
-});
diff --git a/test/screenshot.test.js b/test/screenshot.test.js
index 52334e08..9890e3bc 100644
--- a/test/screenshot.test.js
+++ b/test/screenshot.test.js
@@ -5,7 +5,6 @@ const { join } = require('path');
const assert = require('assert');
const { PNG } = require('pngjs');
const match = require('pixelmatch');
-const { getURLsFromSitemap } = require('./support/sitemap');
const { writeFile, mkdir } = fsPromises;
@@ -80,7 +79,9 @@ function fillImageToSize(image, width, height) {
}
test('screenshot visual regression', async () => {
- const paths = (await getURLsFromSitemap()).map(getURLPath);
+ await page.goto(LOCAL_HOST);
+ const urls = await page.$$eval('.usa-nav__link', (links) => links.map((link) => link.href));
+ const paths = urls.map(getURLPath);
for (const path of paths) {
const local = await getScreenshot(LOCAL_HOST + path);
diff --git a/test/support/sitemap.js b/test/support/sitemap.js
deleted file mode 100644
index dcf66e15..00000000
--- a/test/support/sitemap.js
+++ /dev/null
@@ -1,12 +0,0 @@
-const LOCAL_HOST = `http://localhost:${process.env.JEST_PORT}`;
-const REMOTE_HOST = 'https://design.login.gov';
-
-function getNormalizedURL(url) {
- return url.replace(REMOTE_HOST, LOCAL_HOST);
-}
-
-export async function getURLsFromSitemap() {
- await page.goto(`${LOCAL_HOST}/sitemap.xml`);
- const urls = await page.$$eval('url loc', (locs) => locs.map((loc) => loc.textContent));
- return urls.map(getNormalizedURL);
-}