Make the dashboard usable on a phone — Smart Study Module 16

Managers open reports on small screens, under time pressure and with different visual abilities.

Outcomes

• Design a reading order
• Provide labels beyond color
• Check filtered and empty states

Understand

Use one overview page for the decision, one branch detail and one QA/methodology page. Label every metric with period, unit and definition. A target shortfall needs a number and text, not only red color.

Set meaningful titles and alt text, logical tab order and adequate contrast. Include a text/table alternative for important findings. Check that slicers and drill-through do not leave an unexplained filtered state.

Native mobile layout must be authored and inspected in Power BI tooling. The in-site specification and answer checks are learning aids; they do not claim a real device or screen-reader test of your report.

Follow along

1. Sketch overview, branch detail and QA pages.
2. Build the native report when Desktop is available.
3. Test January, February, Nashik and an empty selection.
4. Review keyboard order, data labels and a narrow mobile layout.

Worked example

Overview: period → Collection/Target/Efficiency → branch variance → next action
QA: source dates → row counts → reconciliation → known limitations

January report should expose ₹12,000 total shortfall without depending on color.

Practice

Enter January total target minus collection.

Create a free personalized study plan · Download project instructions

Interactive practice runs in your browser.