Accessibility

One standard across all three, and each product’s own gaps.

dalDesk, dalMap, and dalSDR hold to one accessibility standard. This page states it, says what these introductory pages do themselves to meet it, and says where to tell us something is in your way. Each product's own guide states how it meets the standard for its own interface — what it currently gets right and what it does not yet.

The standard every product holds to

All three are built to meet WCAG 2.2 AA for contrast and keyboard access:

• Visible focus, in an order that makes sense. Semantic labels, a logical reading and tab order, and state changes that are announced, not only shown.
• Nothing that depends on one sense alone. No control relies on color, sound, motion, hover, or gesture by itself to be understood.
• A name for every control. An icon-only button carries a name a screen reader can speak, not just an appearance.
• A layout that holds together when space is short. The controls you need stay reachable at narrow and short viewports.
• Your preferences are honored. Light, Dark, and Auto everywhere; motion that is functional and brief, or effectively static when you have asked your system for less of it.

That is the standard, not a claim that every surface has already been checked against it. Where a product knows of a gap, its own guide states it rather than leaving you to find it:

dalDesk accessibility ↗ dalMap accessibility ↗ dalSDR accessibility ↗

What these pages do themselves

Two addresses serve these introductory pages — this site, and the single page at dal.kf2em.com that an old dalDesk link still arrives at. Both are built the same way and carry the same answers.

• A skip link. The first stop on the page, reachable before the header, moves past the navigation and into the content.
• Visible keyboard focus. Every link, button, and control shows where you are. The appearance menu closes on Escape and returns focus to the control that opened it, rather than leaving you at the top of the page.
• Text sized to your browser. Sizes are set relative to your browser's font size rather than fixed, so a larger default size carries through the whole page.
• Reduced motion is honored. Asking your system for less motion removes the small amount of transition these pages use.
• Light, Dark, and Auto. Matching your system by default, with nothing on the page that depends on color alone to make its point.

If something is in the way

Support says how to report a problem with any of the three products, and an accessibility barrier is reported the same way as anything else that is not behaving: what you were trying to do, what you were using to do it — a screen reader and its version, a switch device, keyboard only, magnification, your browser and operating system — and what happened instead. That is information nobody else can supply.