Accessibility

Statement and conformance report, reviewed 5 November 2026

decoy.day aims to meet WCAG 2.2 at levels A and AA. That also covers the web requirements of the Revised Section 508 standards, which adopt WCAG 2.0 A and AA.

At a glance

51 WCAG 2.2 A and AA criteria

Supports: 43
Partially supports: 1
Not applicable: 7

How it is checked

Every change runs an automated audit (axe, all WCAG 2.0 to 2.2 A and AA rules and best practices, any severity) on the dashboard, a visit, the side-by-side view, the replay, the weekly reports, the FAQ and this page, at 320 and 1280 pixels wide, light and dark. The same run tabs through the dashboard and a visit with the keyboard and checks that every stop is visible and shows focus, and fails on sideways scrolling at 320 pixels.

Known limitations

Text sent by visitors is shown exactly as sent, in whatever language it's in, and may itself be hard to read.
The world map is visual. Its text summary, the live feed and the visitor log carry the same information.
The decoy pages (fake logins, leaked files) imitate a careless company's site on purpose and aren't meant for use.

Report a problem

Write to contact@decoy.day with the page and what got in the way. We aim to reply within five working days.

Conformance by criterion

WCAG 2.2, levels A and AA

Product: decoy.day dashboard and reports (https://decoy.day). Standard: WCAG 2.2, levels A and AA. Section 508 (Revised) chapters 3 and 5 functional and software requirements are met through these web criteria; this page is the chapter 6 support documentation.

Criterion	Level of support	Notes
1.1.1 Non-text content	Supports	Icons and avatars are decorative and hidden from assistive tech; the map has a text summary; flag marks sit beside text labels.
1.2.1–1.2.5 Time-based media	Not applicable	No audio or video.
1.3.1 Info and relationships	Supports	Headings, landmarks, lists, data tables with header cells, labelled groups.
1.3.2 Meaningful sequence	Supports	Reading order follows the layout at every width.
1.3.3 Sensory characteristics	Supports	Instructions never rely on shape, colour or position alone.
1.3.4 Orientation	Supports	Works in portrait and landscape.
1.3.5 Identify input purpose	Supports	The only personal-data fields (a decoy login form) carry autocomplete tokens.
1.4.1 Use of color	Supports	MCP and web, flag kinds and visitor groups are each named in text and, for flags, also by shape.
1.4.2 Audio control	Not applicable	No audio.
1.4.3 Contrast (minimum)	Supports	Checked automatically on every page and state.
1.4.4 Resize text	Supports	Text scales with the browser; layouts reflow.
1.4.5 Images of text	Supports	No images of text.
1.4.10 Reflow	Supports	Tested at 320 CSS pixels with no sideways scrolling; wide data tables scroll on their own, as allowed for two-dimensional content.
1.4.11 Non-text contrast	Supports	Chart and map colours were checked at 3:1 or more against their panel; focus rings are bright cyan on dark.
1.4.12 Text spacing	Supports	Tested with the criterion’s spacing overrides: nothing clipped or overflowing.
1.4.13 Content on hover or focus	Supports	Map and timeline tips close with Escape, never cover the pointer and stay while hovered.
2.1.1 Keyboard	Supports	Every control works from the keyboard; the replay timeline is a slider with arrow keys and presets, besides dragging.
2.1.2 No keyboard trap	Supports	Tested by tabbing through every page.
2.1.4 Character key shortcuts	Supports	The j and k shortcuts on a visit only work while focus is in the request list.
2.2.1 Timing adjustable	Not applicable	No time limits.
2.2.2 Pause, stop, hide	Supports	Pause motion stops every animation; the live feed has its own pause; reduced-motion settings are honoured.
2.3.1 Three flashes	Supports	Nothing flashes more than three times a second.
2.4.1 Bypass blocks	Supports	Landmarks and headings on every page; phones get a section jump bar.
2.4.2 Page titled	Supports
2.4.3 Focus order	Supports	Follows the visual order.
2.4.4 Link purpose (in context)	Supports	Repeated links such as “Compare visits” name what they open.
2.4.5 Multiple ways	Supports	Site navigation, the dashboard, weekly reports, a sitemap and an FAQ.
2.4.6 Headings and labels	Supports
2.4.7 Focus visible	Supports	Checked automatically for every focus stop.
2.4.11 Focus not obscured (minimum)	Supports	Sticky bars never fully cover the focused control (tested).
2.5.1 Pointer gestures	Supports	No multipoint or path gestures are needed.
2.5.2 Pointer cancellation	Supports	Actions run on release.
2.5.3 Label in name	Supports	Accessible names start with the visible label.
2.5.4 Motion actuation	Not applicable	Nothing responds to device motion.
2.5.7 Dragging movements	Supports	Drag-to-zoom on the timeline has preset, slider and start/end alternatives.
2.5.8 Target size (minimum)	Supports	Controls are at least 24 by 24 pixels or spaced to that; inline text links are exempt.
3.1.1 Language of page	Supports
3.1.2 Language of parts	Partially supports	Text sent by visitors (tool names, paths, client names) is shown as sent and is not marked with its language.
3.2.1 On focus	Supports
3.2.2 On input	Supports	Filters change the view they belong to, nothing else.
3.2.3 Consistent navigation	Supports
3.2.4 Consistent identification	Supports
3.2.6 Consistent help	Supports	The contact address is in the same place on every page.
3.3.1 Error identification	Supports
3.3.2 Labels or instructions	Supports
3.3.3 Error suggestion	Supports
3.3.4 Error prevention (legal, financial, data)	Not applicable	No transactions.
3.3.7 Redundant entry	Not applicable	No multi-step forms.
3.3.8 Accessible authentication (minimum)	Not applicable	Nothing here needs signing in. The login forms are decoys and never sign anyone in.
4.1.2 Name, role, value	Supports	Checked automatically; custom controls use native elements or full ARIA roles.
4.1.3 Status messages	Supports	Filter counts and copy confirmations are announced politely; the live feed is deliberately not announced on every event.