Preview

Shield Nest Hub is not open for listings yet. Every vehicle on this site is an illustrated demonstration, not a car for sale.Demo listings only. Nothing here is for sale. What works today

Accessibility

Accessibility Statement

How we are working to make Shield Nest Hub usable for everyone, where we know it falls short, and how to tell us about a barrier.

Last updated November 13, 2026Pre-launch draft
Pre-launch draft

This statement describes the Shield Nest Hub preview site as it works today. It will be reviewed by legal counsel and updated before Shield Nest Hub accepts listings or collects personal information through the site.

Our commitment

We want everyone to be able to use Shield Nest Hub, including people who use a screen reader, a keyboard instead of a mouse, voice control, screen magnification, or other assistive technology.

Buying or selling a car involves a lot of detail: prices, mileage, title status, paperwork, and safety advice. All of it should be available to every visitor, in a form they can use.

We build accessibility into the site's code and design directly. We do not use accessibility overlay tools.

The standard we are working toward

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C).

We have not yet confirmed that the site meets WCAG 2.2 Level AA, and we do not claim that it does. No independent audit has been done so far.

What we have done so far

  • Structure. Every page uses landmarks for the header, navigation, main content, and footer, and headings in a logical order, so you can move around with a screen reader or browser tools.
  • Skip link. A "Skip to main content" link is the first thing on every page for keyboard and screen reader users.
  • Keyboard. Menus, dialogs, and search filters can be operated with a keyboard alone.
  • Visible focus. A clear outline shows which link, button, or field has keyboard focus.
  • Contrast. Text has a contrast ratio of at least 4.5:1 against its background. Body text is about 15:1.
  • Forms. Form fields have labels and, where needed, instructions. Error messages say what needs to be fixed.
  • Zoom. We do not block zooming, so you can enlarge pages with your browser or device settings.
  • Motion. If you turn on your device's reduce-motion setting, the site reduces animation to match.
  • Without JavaScript. Guides, policies, and other content pages work with JavaScript turned off. Only the interactive demonstration tools, such as listings, search filters, saved vehicles, and comparisons, need it.
  • Images. Vehicle illustrations and other meaningful images have text alternatives. Images that add no information are marked as decorative so screen readers skip them.

Known limitations

  • No independent audit yet. Our review so far is our own, so there are likely issues we have not found.
  • Limited screen reader testing. We have done only limited testing with screen readers, so some content may be announced in ways we have not yet checked.
  • Simplified vehicle illustrations. The vehicles shown are simplified drawings, not photos. They show a general body style and color, not the condition or features of a real car. The listing text carries those details.
  • Interactive demonstration tools need JavaScript. Listings, search filters, saved vehicles, and comparisons do not work with JavaScript turned off.
  • External websites. We link to government and other third-party sites, such as recall and title-history resources. Their accessibility is outside our control.

If any of these affects you, contact us and we will provide the information another way.

Technology the site relies on

The site is built with standard HTML and CSS, with WAI-ARIA attributes where native HTML is not enough, and JavaScript for interactive features. It is intended to work in current versions of common desktop and mobile browsers together with the assistive technology people use with them.

We have not yet completed structured testing across combinations of browsers and assistive technology.

How and when we checked

This statement was last reviewed on November 13, 2026. It is based on a self-assessment by the people who build the site, not on an independent audit.

We intend to have the site reviewed independently and will update this statement with the results. We will also review this statement whenever we add a major feature, such as real listings or contact forms that send messages.

Report a barrier or ask for another format

If something on the site is hard or impossible for you to use, or you need information from the site in a different format, please tell us:

  • Email: [Support email — not yet provided]
  • Phone: [Phone — not yet provided]
  • Mail: [Legal entity name — not yet provided], [Mailing address — not yet provided]

It helps if you tell us the page address, what you were trying to do, and, if you are comfortable sharing it, the browser and assistive technology you use. We aim to respond within five business days.

You can also use the email option on our contact page. Messages you send us are handled as described in our Privacy Policy.