Best Communication Approach for Visually Impaired Dashboard Stakeholders

DA0-002 By islever Editorial Last updated

Communicate analysis results Create effective visuals Deliver reports

Short answer

C Incorporating audio accessibility functions into the dashboard graphics for all interface instances lets visually impaired stakeholders access the analysis independently.

Question

A data analyst is creating a dashboard for a group of visually impaired stakeholders. Which of the following communication approaches is best?
  1. Inform the supervisor that the stakeholders need assistance during the meeting.
  2. Partner with the human resources department to advocate on behalf of the stakeholders.
  3. Incorporate audio accessibility functions into graphics for all instances of the interface. Correct Answer
  4. Present a custom slide presentation with interactive sound effects.

Key Takeaways

This question tests inclusive communication of analysis results; the trap is treating accessibility as an accommodation handled by other people (a supervisor or HR) rather than as a design feature of the deliverable itself.

When building a dashboard for visually impaired stakeholders, the analyst should build accessibility directly into the interface by adding audio-based functions to the graphics. The DA0-002 answer is C: built-in audio accessibility (such as screen-reader-compatible audio output) is superior to escalating to a supervisor, involving HR, or swapping the dashboard for a slide deck.

Common mistake: The most common wrong choices are A and B, which assume accessibility is someone else's responsibility — telling a supervisor about the need or lobbying through human resources fixes nothing in the actual dashboard and leaves stakeholders still unable to consume the data.

Expert Analysis

Why the Answer Is Correct

Option C embeds audio accessibility functions into the graphics across the whole interface, which directly satisfies the objective of communicating analysis results to visually impaired users. Screen-reader support, audio descriptions, and audible data labels let stakeholders perceive the same insights as sighted users without depending on visual cues alone. Building the feature into every instance of the interface means access is consistent and self-service, not contingent on meeting-day help.

Why the Other Options Are Wrong

Option A merely reports the problem upward; a supervisor cannot make a static, inaccessible dashboard readable during the meeting, so the stakeholders remain excluded. Option B routes the issue through human resources as an advocacy matter, which is an HR/HR process rather than an analytical or design fix and still leaves the interface unchanged. Option D substitutes a different deliverable — a custom slide deck with sound effects — for the requested dashboard; interactive sound effects are also not the same as structured accessibility support such as screen-reader compatibility.

Community Comment Notes

Amelia233 independently landed on C, reasoning that "the dashboard should include accessibility features such as audio descriptions or screen-reader support" so users need not rely "solely on visual elements." That reasoning matches the accessibility-by-design principle the question is probing, and the vote trend toward C is consistent with it.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

On DA0-002 communication questions, choose the option that changes the deliverable itself so all stakeholders can consume it independently; answers that delegate the problem to management, HR, or on-the-spot assistance are distractors. Look for keywords like built into, all instances, and every user.

Frequently Asked Questions

Why is escalating to a supervisor or HR the wrong answer here?

Neither A nor B changes the dashboard itself, so visually impaired stakeholders would still be unable to read it. Accessibility must be designed into the deliverable, not referred elsewhere.

Why is a custom slide presentation with sound effects wrong for this dashboard?

Option D replaces the requested dashboard with a different artifact, and ad-hoc sound effects do not provide structured screen-reader support. C applies audio accessibility consistently across the interface.

More DA0-002 FAQ →

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

  1. Amelia233 👍 1 Answered C
    For visually impaired stakeholders, the dashboard should include accessibility features such as audio descriptions or screen-reader support. This allows them to understand the information without relying solely on visual elements. Answer: C

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All DA0-002 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DA0-002 Practice Test →

← Back to DA0-002 Study Guide