Accessibility

How this site is built for keyboards, screen readers, and both languages

The DLA Imaging site is built with semantic HTML, keyboard navigation, visible focus, bilingual content, responsive layouts, reduced-motion support, and light and dark themes. WCAG conformance is not represented as a certification on this page.

At a glance

Where this site stands today

  1. Core content and navigation remain available without JavaScript.
  2. Interactive tools have keyboard controls, labels, live status, and a static explanation.
  3. Reduced-motion settings remove nonessential movement.
  4. WCAG 2.2 Level AA guides the design and testing approach; this statement does not present a certification.
01

Which accessibility features are designed into the site?

The site includes a skip link, landmarks, one primary heading, sequential sections, visible focus, keyboard-operable navigation, labeled controls, text alternatives, responsive layouts, language metadata, reduced motion, and color themes. Content appears before JavaScript enhancements so the page remains readable when scripts fail.

Interactive maps and tools have textual alternatives and status regions. Decorative SVGs are hidden from assistive technology; informative diagrams are paired with explanations.

Spanish layouts are tested independently because longer phrases can expose clipping and focus problems.

02

Which standards and tests apply?

The testing approach covers WCAG 2.2 Level AA criteria, automated accessibility checks, valid HTML, documented contrast, keyboard operation, zoom and reflow, reduced motion, and manual review of representative templates in both languages and themes.

Automated tools cannot establish full conformance. Manual checks must cover names, roles, states, reading order, focus movement, errors, tables, details elements, the map, report viewer, matcher, stepper, and contact helper.

Accessibility is treated as ongoing product quality: substantive component changes should be tested before release.

03

How can a visitor report a barrier?

To describe an accessibility barrier, identify the page, browser or assistive technology, task, and barrier without including medical or patient information. Existing facility partners may use the business route defined in their agreement.

This public site does not publish an accessibility email or phone. Never use a clinical or emergency channel solely to report a website barrier.

Do not ask a visitor to disclose a diagnosis or disability to report a barrier.

04

How will this statement stay accurate?

This statement should be updated after substantial component changes and remediation cycles. Known limitations should be named with a practical alternative rather than hidden behind a broad commitment.

The QA folder should record tools, versions, dates, tested routes, viewport and theme coverage, findings, fixes, and remaining limitations.

Accessibility feedback should enter the same tracked remediation process as automated and expert-review findings.

FAQ

Common questions

Does DLA Imaging claim WCAG conformance today?

No certification is claimed. WCAG 2.2 Level AA guides the design and testing approach.

Can the site be used with a keyboard?

The design supports keyboard operation with visible focus, logical order, Escape behavior, and accessible controls.

Does the site respect reduced motion?

Yes by design. The reduced-motion preference removes nonessential animation, while all information and controls remain available.

How can I report an accessibility barrier?

Existing facility partners may use the business route defined in their agreement. Describe the page and task without sharing patient or medical information.

Content record: Published July 30, 2026. Substantive content revisions are dated here.