PL-300 Visualize and analyze the data Practice Question
Which TWO actions improve the accessibility of a Power BI report for users with visual impairments?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a high-contrast color theme.
Option A is correct because applying a high-contrast color theme in Power BI (via View > Themes or a custom JSON theme) increases the luminance difference between foreground text/visuals and background, which helps users with low vision or color-vision deficiencies distinguish content. Option B is correct because adding alt text to every visual in the Visualizations pane's Format > General > Alt Text field lets screen readers such as Narrator, JAWS, or NVDA announce a meaningful description of each chart, making the report navigable for blind users. Option C is wrong because small font sizes reduce legibility rather than improve it, working against accessibility best practices. Option D is wrong because high color saturation alone does not guarantee sufficient contrast and can actually worsen readability for users with color-vision deficiencies. Option E is wrong because complex drillthrough interactions add navigation complexity and are not an accessibility improvement; simpler, predictable navigation is preferred.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use a high-contrast color theme.
Why this is correct
High-contrast color themes in Power BI ensure that foreground data elements and backgrounds meet WCAG 2.1 contrast ratios (at least 4.5:1 for text, 3:1 for graphical objects). This directly supports users with low vision or color vision deficiencies, as it makes visual distinctions perceivable without relying on color alone. Power BI's built-in accessible color palettes, such as the High Contrast White/Black themes, automatically adjust color pairs to maintain these ratios.
- ✓
Add alt text to all visuals.
Why this is correct
Alt text on every visual provides a textual alternative that screen readers can vocalize, enabling blind or low-vision users to understand the chart's key message without seeing it. In Power BI Desktop, you set alt text via the Visual properties > Alt text pane, and it should describe the insight (e.g., 'Q3 sales increased 12% versus Q2') rather than just labeling the chart type. This also supports users with certain cognitive disabilities who may prefer text summaries over complex visual representations.
- ✗
Use small font sizes to fit more content.
Why it's wrong here
Using small font sizes to force more content degrades readability and violates WCAG success criterion 1.4.4 (Resize Text), which requires users to zoom in up to 200% without losing content or functionality. Power BI reports are primarily consumed on screens; instead of shrinking text, you should use paginated pages, drillthrough, or tooltips to separate content while keeping a comfortable minimum font size (typically 12pt or larger). Small fonts disproportionately affect older users or those with astigmatism, making the report unusable beyond a specific zoom level.
- ✗
Use high color saturation for all elements.
Why it's wrong here
High color saturation uniformly across all elements is harmful because it creates glaring edges and visual fatigue, making it harder for users with sensory sensitivities or migraine disorders to focus. More critically, saturation does not guarantee contrast—a highly saturated red against a bright background can still fail WCAG contrast thresholds and become indistinguishable for deuteranopic users. Accessibility best practice recommends using a restrained palette with sufficient contrast and avoiding reliance on single-color distinctions, which saturated themes often overemphasize.
- ✗
Include complex drillthrough interactions.
Why it's wrong here
Complex drillthrough interactions, which require right-clicking, Ctrl+Click, or navigating to hidden detail pages, create barriers for keyboard-only users because these gestures often lack accessible equivalents. They also introduce a non-linear navigation path that can confuse screen-reader users, who may not discover the drillthrough target or understand the context switch. Power BI accessibility guidelines favor simple, discoverable actions like clearly labeled buttons or bookmarks, and recommend providing a visible back-navigation mechanism when drillthrough is used.
Go deeper
Related to this question
About these practice questions
One of 524 original PL-300 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-300 exam.