Skip to content
Tutorials Center
My learning

Topics

Lesson 37 of 56 ยท Visuals and Reports

Formatting, Themes and Report Design

Design clearer Power BI reports: page layout, alignment, colour, theme JSON files, accessibility, alt text, tab order and mobile layout, with a contrast checker.

Two reports can show exactly the same numbers and feel completely different. One looks like a pile of charts that happened to land on the page, and the reader has to hunt for the message. The other leads the eye from the headline number to the detail, uses a small set of colours and works for people who see colours differently or use a screen reader. The difference is design, and most of it comes from a few rules that you apply consistently.

In this lesson you learn how to lay out a page, format visuals, use and write a theme so formatting is applied everywhere at once, and make a report accessible and usable on a phone. The work happens in the Power BI Desktop interface, so the steps are described in text and the theme file is shown read-only. Two Python stand-ins let you test the ideas: a contrast-ratio calculator and a small theme checker. For choosing the chart types themselves, see Choosing the Right Visual.

Design in four moves

Layout Grid, alignment, reading order.
Colour Few colours, used with meaning.
Theme One file styles everything.
Access Contrast, alt text, tab order.

Do the theme first, then adjust single visuals only when you must.

1 / 2

Layout: a grid and a reading order

People read a page top to bottom and left to right, so place the most important thing top left. A common structure that works well:

  1. A title row with the report name and key slicers.
  2. A KPI row of cards: the three to five numbers that matter.
  3. The main chart that explains the story, large.
  4. Supporting visuals and a detail table below or to the right.

Some practical points for the canvas:

  • Keep to the default page size (16:9) unless you have a reason. Under Format > Page > Canvas settings you can change the size and the Page background; you can also set a Wallpaper colour around the page.
  • Use a consistent margin and gap. Turn on View > Gridlines and Snap to grid so visuals line up.
  • Select several visuals and use Format > Align and Distribute (horizontally or vertically). Misaligned edges are the quickest way to make a report look careless.
  • Leave white space. A crowded page is hard to scan; if you have more than about six or seven visuals, split the report into pages.
  • Name your visuals in the Selection pane (View > Selection). Meaningful names such as "Revenue by month" matter later for tab order and bookmarks.

Formatting a visual

Select a visual and open the Format tab in the Visualizations pane. Each visual has Visual options (axes, labels, legend, colours, data labels) and General options (title, size, position, border, shadow, background, Alt text). A few rules of thumb:

  • Give each visual a title that says something: "Revenue by region, 2025" is better than "Sum of Revenue by Region".
  • Show data labels when readers need exact values; remove gridlines and the value axis if the labels carry the information.
  • Use consistent number formats: thousands separators, the same number of decimals, a clear currency or unit. Set formats on the field or measure itself (under Measure tools) so every visual agrees.
  • Do not use 3-D effects, heavy borders or shadows. They add no information.
  • Turn off the legend when a title or direct labels already identify the series.

The Format painter copies the formatting of one visual to another, which is handy for a one-off. For anything you repeat across the report, use a theme.

Colour that means something

Colour is for meaning, not decoration. Choose a small palette and apply it consistently:

  • Use one highlight colour for the thing that matters and neutral grays for context.
  • Keep a consistent meaning: if blue means "this year" on one page, do not use it for "budget" on another.
  • Use a sequential palette (light to dark) for values that go from low to high, and a diverging palette (two hues around a neutral midpoint) for values with a meaningful centre such as variance to target.
  • Do not rely on red and green alone. About one man in twelve has some form of colour vision deficiency. Add an icon, a sign (+/-) or a label as a second cue.
  • Use good, neutral and bad colours from the theme for status, so they are the same everywhere.

Themes: format once, apply everywhere

A theme is a set of defaults for colours, fonts and visual styling that applies to every visual in the report. In Desktop open the View tab and choose from the built-in themes, or select Customize current theme to change the colours, text and visual defaults through a dialog. When you want to share a theme or keep it under version control, save it as a JSON file with Save current theme, and load it in another report with Browse for themes.

A small theme file looks like this (read-only):

JSON
{
  "name": "Contoso Blue",
  "dataColors": ["#1F4E79", "#2E86C1", "#E67E22", "#1E8449", "#7D3C98", "#7F8C8D"],
  "background": "#FFFFFF",
  "foreground": "#252423",
  "tableAccent": "#1F4E79",
  "good": "#1E8449",
  "bad": "#C0392B",
  "textClasses": {
    "title": { "fontSize": 14, "fontFace": "Segoe UI Semibold", "color": "#252423" }
  }
}

The main keys are:

Key Purpose
name The theme's name in the gallery.
dataColors The ordered series colours that charts use.
background, foreground Base light and dark colours used by the default styles.
tableAccent Accent colour for table and matrix headers.
good, neutral, bad, minimum, center, maximum Colours for status and for gradients.
textClasses Fonts and sizes for standard text such as titles and labels.
visualStyles Detailed defaults for each visual type, by name or * for all.

You do not have to write the file by hand. Customize a theme in the dialog, export it, and edit only the entries you need. Because the format is plain text, you can keep a company theme in source control and give every report the same look. A theme will not rescue a cluttered layout, but it removes hundreds of manual clicks.

The stand-in below treats a theme the way Power BI does: it reads the JSON, checks the colours are valid hex values, and flags any series colour that is hard to see against the background. The contrast measure is introduced in the next section.

Python Check a theme file

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The orange third series gets only 2.85:1 against white, so the checker flags it. A real theme would darken that colour a little or give the series a border. Power BI itself does not run a check like this for you, so a quick test like this one is a useful habit when you create a palette.

Accessibility

An accessible report works for people with low vision, colour blindness, motor impairments or screen readers, and it is usually clearer for everyone. Power BI gives you several tools.

Contrast. The Web Content Accessibility Guidelines (WCAG) ask for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text and for graphical objects such as chart bars. The ratio compares the relative luminance of two colours. The next example computes it.

Python Contrast ratios

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Dark gray text on white scores 15.49:1 and white on dark blue 8.66:1, both comfortable for text. The mid blue (3.97:1) is fine for bars or lines but too weak for small text. Light gray (1.92:1) and yellow (1.51:1) fail. These are common colours for "subtle" captions, and they are exactly the ones that readers cannot see.

Alt text. Select a visual and open Format > General > Alt text. Describe what the visual shows and why it matters ("Line chart: monthly revenue grew from 310 to 510 between January and June"), not just its type. Mark purely decorative shapes as decorative so screen readers skip them.

Tab order and reading order. Keyboard and screen-reader users move through the visuals in a set order. In the Selection pane you can reorder the layers, and the Tab order list defines the sequence; put the title and key cards first.

Other options.

  • Use Show as a table (the "More options" menu of a visual, or Shift+Alt+F11) to let people see the data behind any chart, which helps screen-reader users and anyone who prefers numbers.
  • Set a title on every visual, because screen readers announce it.
  • Choose markers or different line styles in addition to colour when several series share a chart.
  • Test the report with high-contrast mode and keyboard-only navigation (Tab and Enter to move to and operate visuals).

Mobile layout

The Power BI mobile app shows a report in portrait on a phone, where a wide desktop page would be tiny. Under View > Mobile layout you can arrange the visuals of a page on a narrow canvas. Drag only the visuals a phone user needs, stack them in a single column, and make the cards large. Visuals that you leave out of the mobile layout stay on the desktop page. A phone page with the key cards and one or two charts beats a shrunken copy of the full page. If a report is mostly viewed on phones, design the mobile layout first and add the desktop view afterwards.

A short design checklist

  • The most important number is top left and large.
  • Every visual has a title that states a point, and every number has a consistent format.
  • The report uses a saved theme, with a highlight colour and neutral grays.
  • No colour pair has a contrast below the recommended ratios, and no meaning depends on colour alone.
  • Alt text, tab order and mobile layout are set before publishing.

Once the report looks good, add ways for readers to explore it in Filters, Slicers and Sync.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. Where is the best place to define fonts and colours that every visual in a report should use?

    A theme sets defaults for colours, fonts and visual styles across the whole report, and can be saved as a JSON file and reused.
  2. 2. What is the WCAG minimum contrast ratio for normal-sized text?

    Normal text needs at least 4.5:1. Large text and graphical objects need at least 3:1.
  3. 3. Which of these makes a visual accessible to a screen reader user?

    Alt text is announced by screen readers and should describe the message of the visual, not just its type.
  4. 4. What does the dataColors key in a theme file hold?

    dataColors is the ordered list of series colours. The background is set by its own key.
  5. 5. Why would you build a mobile layout?

    The mobile layout is a separate arrangement for portrait phone screens. Visuals you leave out stay on the desktop page.

Summary

  • Lead with the key number top left, use a grid, align visuals and leave white space.
  • Write titles that state a point, and keep number formats consistent.
  • Use few colours with consistent meaning, and never use colour as the only cue.
  • A theme JSON file (dataColors, background, foreground, textClasses, visualStyles) applies formatting everywhere and can be shared.
  • Check contrast (4.5:1 for text, 3:1 for graphics), add alt text, set the tab order and design a mobile layout.

Next: Filters, Slicers and Sync.