All lessons

Module 7: Visuals and report design · Lesson 7.5 · about 14 min

Layout, themes and accessibility

Arrange a page so the eye finds the answer first, use a theme for consistent colours and fonts, and make reports usable with a keyboard, a screen reader and colour-blind eyes.

Module 7 · about 14 minutes. You’ll be able to lay out a clean page, apply a theme and check accessibility.

1. Why this matters

People decide in seconds whether a report is trustworthy. A tidy, consistent page reads as reliable; a cluttered one doesn’t. Accessibility is also a legal and practical requirement in Canadian, UK and US public bodies and many companies.

2. Layout

  • Top left to bottom right: headline cards on top, the main trend next, detail at the bottom.
  • A grid: turn on View > Gridlines and Snap to grid; align edges; keep equal gaps.
  • Five or six visuals per page at most. More is a second page or a drill through.
  • One message per visual, stated in its title: “Sales are 29 % ahead of last year” beats “Sales by Month”.
  • Consistent page size (16:9 for screens) and a mobile layout (View > Mobile layout) for phones.

3. Themes

View > Themes applies colours, fonts and visual defaults to the whole report. Customise the current theme or import a JSON theme file so every report from your team looks the same. Pick: one neutral colour for most data, one accent colour for what matters, red/amber/green only for status, and a readable font size (at least 10 pt in visuals, 12 pt in tables).

4. Accessibility checklist

  1. Alt text on every visual (Format > General > Alt text), dynamic where useful.
  2. Tab order (View > Selection > Tab order) follows reading order; hide decorative shapes from it.
  3. Contrast: text at least 4.5:1 against its background.
  4. Not colour alone: add markers, labels, or + and − signs to good/bad colours.
  5. Titles and labels that make sense when read aloud.
  6. Test with the keyboard (Ctrl+F6 moves between panes, Tab between visuals) and with Show as a table (Alt+Shift+F11).
Principle

Principle: design for the reader’s attention. Each element either helps answer the page’s question or competes with it. Remove what competes, emphasise what answers, and make every answer reachable without a mouse or perfect colour vision.

Try it: look at a report you use. What is the one question each page answers? If you can’t say it in one sentence, the page is doing too much.

5. Worked example

Tidying the Northbay overview. Before: 11 visuals, three fonts, a 3D pie, rainbow colours. After: four cards across the top, one line chart (this year in the accent colour, last year in grey), one sorted bar chart of categories, one matrix; a theme with the company’s blue as accent; titles that state the finding; alt text on each visual. Same data, read in ten seconds instead of a minute.

6. Practice

  1. Rewrite the title “Sales by Store” as a message.
  2. Give two ways to show “below target” that don’t rely on colour.
  3. Where do you set the order in which a keyboard user moves through visuals?
Answers
  1. For example: “Queen Street sells the most; Forks Market is still building up”.
  2. A ▼ arrow or − sign; a “Below target” label; a target line on the bar.
  3. View > Selection pane > Tab order.

Check yourself

1Where should the most important number go on a report page?
2Why not show good/bad with red and green only?
3What does alt text on a visual do?

Sources

Your ticks stay in this browser. Save them as a file on the course home.

Updated 2026-11-22. Northbay Goods is a made-up shop and its numbers are generated. Power BI changes every month: menu names can move, so check Microsoft Learn if a button is not where the lesson says. The practice editor runs in your browser; nothing you type is sent anywhere.