Short version: we want every dealer, BDC manager, and vendor to be able to read the brief and use the tools, whatever device or assistive technology they rely on. The Site is built on plain, semantic HTML, most of it works well with assistive technology today, and we are specific below about where it does not yet. If something gets in your way, email hello@dealeraiguy.com and we will fix it or get you the content another way.

This statement covers dealeraiguy.com and its subdomains (the "Site"): the daily brief, the weekly recap, articles, the Dealer AI Company Directory, and the pages for our free tools, prompts, workflows, training, and consulting. It does not cover the separate websites our free tools run on, or the third-party sites we link to, which are responsible for their own accessibility.

1. The standard we are working to

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C). It is the standard most accessibility laws and regulators reference, and it is the one we hold ourselves to. In practice that means: everything you can do with a mouse you can do with a keyboard; everything you can see has a text equivalent; text stays readable when you enlarge it; color never carries meaning on its own; and nothing flashes, moves, or interrupts without your say-so.

2. Where we stand today

Partially conformant. In the W3C's vocabulary that means some parts of the content do not fully conform to the standard. The assessment behind that label is our own, completed on October 7, 2026: a review of the page templates and the stylesheet that generate every page, plus automated testing with the axe-core engine on representative pages (the home page, a daily brief, the privacy policy, this statement, and the cookie notice and its settings dialog). No outside firm has audited the Site yet, and we have not completed hands-on testing with screen readers. We would rather tell you that than imply otherwise.

3. What is already in place

  • Structure a screen reader can navigate. Every page has the same landmarks (a header, navigation, one main region, and a footer) and a single page title in the heading hierarchy, so you can jump straight to the content.
  • Real text, not pictures of text. Body copy is set at 17 to 18 pixels, the layout reflows down to narrow phone screens without sideways scrolling, and pinch-to-zoom is never disabled.
  • Text alternatives. Logos and article images carry alternative text. Daily briefs are written as text, with no information locked inside images.
  • A keyboard-operable menu. The mobile menu is a real button that announces whether it is open or closed, and every link and form control on the Site is a native HTML element you can reach with the Tab key.
  • Nothing that moves on its own. No autoplaying video or audio, no carousels, no flashing content.
  • A cookie notice that behaves. It is a labelled region that never steals your focus, its settings panel is a native dialog the browser manages (Escape closes it, focus stays inside it while it is open), every control is a real button, checkbox, or link with a visible focus ring, and its animation switches off when your system asks for reduced motion.
  • Readable without JavaScript. Every article, brief, and page renders as plain HTML. JavaScript is used only for the mobile menu toggle, the signup and inquiry forms, and the cookie settings.
  • No accessibility overlay. We do not use an overlay widget that promises to fix accessibility with one line of code. The people who rely on assistive technology have said loudly that overlays get in their way, so we fix the code instead.

4. Known limitations, and what we are doing about them

These are the gaps we know about as of October 7, 2026. Each one is on our list, in roughly this order.

  • No "skip to content" link yet. Keyboard users have to tab through the header navigation on every page before reaching the content. We are adding a skip link as the first focusable element on every page.
  • Focus indicators are the browser defaults. We have not yet added our own high-contrast focus style, so on some elements the focus ring can be hard to see. A consistent, high-contrast focus ring is being added site-wide.
  • Orange text falls short on contrast. White text on our brand orange buttons measures roughly 2.8:1, below the 4.5:1 ratio Level AA requires for text. Links in the header and inside page content use a darker orange that measures about 3.6:1; content links are underlined, so they never rely on color alone, but the ratio is still short. Automated testing flags both on every page. We are moving both to darker shades (the cookie notice already uses one that passes).
  • Form error messages are not announced. When a newsletter or inquiry form fails, the error appears on screen but a screen reader is not told about it automatically. We are adding live-region announcements.
  • One page has two top-level headings. The About page, which was imported from our previous publishing platform, repeats a level-one heading inside the content.
  • Footer social links open in a new tab without saying so. We are adding that warning to the link text.
  • Small animations ignore the reduced-motion setting. The menu and button transitions on the main Site do not yet switch off when your system asks for reduced motion (the cookie notice already does).
  • The free PDF has not been checked. "10 AI Tools Every Dealer Needs in 2026" has not been verified for tagging and reading order. Ask us and we will send you its content as plain text.
  • The vendor directory has not been audited page by page. Its listing, intro-request, and review forms use standard HTML controls, but we have not yet reviewed every profile and form individually.
  • Third-party content. The daily brief quotes and links to outside sources, and our free tools (Dealer Website Grader, DealerAEOAudit, and the others listed on the Tools page) run on separate sites. We cannot vouch for their accessibility, and this statement does not cover them.

5. Tell us what is not working

If you hit a barrier anywhere on the Site, email hello@dealeraiguy.com with "Accessibility" in the subject line. It helps to include the page address, what you were trying to do, what happened instead, and the browser and assistive technology you were using. We aim to reply within five business days, and genuine barriers get fixed as soon as we can republish the page.

If you need something on the Site in another format in the meantime, ask. We will send you the content as plain text by email, or read it to you over a call if that works better.

6. Technical details

The Site is built with HTML, CSS, and a small amount of JavaScript, with WAI-ARIA attributes only where native HTML has no equivalent. It is designed to work with current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile, and with the assistive technologies that rely on them, including screen readers, screen magnifiers, and voice control. If you are using an older browser and something does not work, tell us; we will not ask you to upgrade before we help.

7. How this statement is maintained

This statement was first published on October 7, 2026. We review it at least once a year, whenever the Site's templates change substantially, and whenever one of the limitations above is fixed. The review date at the top always reflects the current version.

See also our Privacy Policy and Terms & Conditions.