Accessibility Statement.

DBIT Defense aims to conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and the relevant provisions of Section 508 of the Rehabilitation Act. We treat accessibility as a continuous engineering responsibility — built into every design pass, code review, and release — rather than a one-time audit.

The following accessibility features are live across our marketing site and client portal:

Keyboard navigation

• Every interactive control — links, buttons, form fields, table sort headers, filter chips, the command palette — is reachable with the Tab key and operable with Enter or Space.
• A "Skip to main content" link is the first focusable element on every page.
• The dashboard command palette (⌘K / Ctrl+K) supports full keyboard navigation: arrow keys to move, Enter to run, Escape to close.
• Focus is visible on every element via a high-contrast vermillion focus ring (uses :focus-visible so it appears for keyboard users without distracting mouse users).

Screen-reader semantics

• Semantic HTML landmarks throughout: <header>, <nav>, <main>, <section>, <footer>.
• aria-label on every icon-only control and navigation region; aria-current on the active sidebar/tab link.
• Form labels are programmatically associated with every input; error messages are announced via aria-live regions where applicable.
• Tables use proper <thead>/<th> structure so screen readers announce column headers when you tab into a cell.

Visual presentation

• Body text targets a minimum contrast ratio of 4.5:1 against its background; UI components target 3:1 (WCAG AA thresholds).
• No information is conveyed by color alone — status pills, readiness bars, and threat chips all carry text labels.
• Touch targets on mobile are at least 40px tall, with extra padding on tap-only surfaces.
• Body type respects the user's font size setting; we use rem and clamp() throughout, never fixed pixel sizes for body copy.

Motion & animation

• Every animation respects the user's prefers-reduced-motion setting — including the hero watermark rotation, scroll-progress bar, panel reveals, and command-palette transitions.
• No content auto-plays sound or video. The live mission-bar clock and deadline countdown update silently.
• No content flashes more than three times per second.

Images & media

• Every meaningful image carries descriptive alt text. Decorative images (HUD brackets, watermark seals, grid overlays) are marked with aria-hidden so screen readers skip them.
• The custom cursor is purely visual — it does not replace any standard cursor functionality and is automatically disabled on touch devices and for users who prefer reduced motion.

We try to be honest about where we have more work to do:

• The Resources card section uses hand-drawn SVG agency monograms. These are decorative and we provide source text labels; we are still tuning the color contrast on certain hover states.
• The Continuous Monitoring page uses some compact tabular layouts that benefit from horizontal scrolling on narrow viewports. We are evaluating a card-stack alternative for very small screens.
• External primary-source links in the Resources section open in new tabs. We currently rely on the standard "→" icon and the rel="noopener noreferrer" attribute to indicate this; we plan to add a visually persistent "opens in new tab" indicator.
• Some informational tooltips on the family-heatmap strip use the native title attribute, which is not reliably exposed to all screen readers. We are migrating these to a proper popover with aria-describedby.

These items are tracked on our internal accessibility backlog and worked alongside product features in every sprint.

• Automated — axe-core checks run against every page during development.
• Manual keyboard — every release is tested with the mouse unplugged on the homepage, services pages, signup, signin, and the full client portal flow.
• Screen reader — spot-checked with VoiceOver (macOS Safari) and NVDA (Windows Firefox).
• Color contrast — every text/background pairing in the design tokens is verified against WCAG AA before being merged.
• Mobile — tested on iOS Safari and Chrome for Android with the system font size set to large.

If you encounter an accessibility barrier on dbitdefense.com — anywhere, at any time — please tell us. We will fix it.

Email accessibility@dbitdefense.com with:

• The page URL or feature where you ran into the problem.
• A short description of what happened and what you expected to happen.
• Your assistive technology and browser, if you are comfortable sharing.

We will acknowledge your message within two business days and aim to resolve or provide a workaround within five business days. If a fix requires more time, we will tell you the planned remediation date.

The site is built to current web standards and is intended to work with modern screen readers and browsers. The combinations we actively support:

• Latest two major versions of Chrome, Firefox, Safari, and Edge.
• Latest two major versions of iOS Safari and Chrome for Android.
• NVDA 2024+ with Firefox or Chrome on Windows.
• VoiceOver on macOS 13+ with Safari.
• VoiceOver on iOS 16+.
• TalkBack on Android 13+ with Chrome.

Older browsers and assistive technologies may receive a degraded but still functional experience.

We update this statement whenever we ship a significant accessibility improvement or identify a new limitation. The "Last reviewed" date at the top of this page reflects the most recent intentional review.