What it means
Data-visualization integrity and accessibility ensure charts, dashboards, maps, and reports represent data honestly and can be understood and operated by intended audiences, including people with disabilities.
Why it matters
A technically correct dataset can still mislead through truncated scales, inappropriate encodings, inaccessible color choices, missing context, or interaction that excludes users.
Practical focus
- Define the scope, owners, acceptable risk, and required outcome for data visualization integrity and accessibility before choosing a tool or platform feature
- Implement documented metric definitions, honest scales, uncertainty and source context, accessible color and text alternatives, keyboard operation, and user testing through documented, reviewable configuration and change control
- Collect calculation checks, source versions, accessibility tests, user comprehension, refresh status, and correction history and compare the results with approved baselines, service objectives, and policy requirements
- Exercise a visual exaggerating a difference, hiding missing data, using inaccessible interactions, or presenting stale results as current as a planned test case, including detection, containment, rollback, escalation, and evidence retention
Common mistakes
- Treating data visualization integrity and accessibility as a one-time technical setting instead of an operating control with owners and review cycles
- Using default thresholds or broad exceptions without connecting them to business, privacy, security, and availability requirements
- Keeping evidence in disconnected tools so reviewers cannot reconstruct who changed what, why it changed, or whether it worked
- Testing only the normal path and discovering during an incident that a visual exaggerating a difference, hiding missing data, using inaccessible interactions, or presenting stale results as current was never rehearsed
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: