PL-300 Visualize and analyze the data Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Apply a high-contrast theme.

  Why it's wrong here

  A high-contrast theme changes the color palette of a Power BI report to improve visual legibility for users with low vision, but it does not add any textual metadata to visuals. Screen readers rely on the accessibility tree built from the report's semantic model and document structure; they cannot infer descriptions from pixels or color contrast. Therefore, while a high-contrast theme addresses color and luminance, it fails to provide the non-visual text descriptions required for an accessible screen reader experience.

• ✗

  Enable data labels on all visuals.

  Why it's wrong here

  Enabling data labels on all visuals increases the amount of visible text on the canvas, but screen readers do not read visual data points or their labels as discrete text elements. In Power BI, the accessibility framework exposes visuals as single objects with an associated alt-text description; data labels are rendered as part of the visual's graphical output and are not individually exposed to assistive technologies. Thus, adding data labels may help sighted users but does not satisfy the requirement that each visual has a textual alternative.

• ✓

  Add alt text to each visual.

  Why this is correct

  Adding alt text to each visual is the correct approach because Power BI's accessibility model exposes visuals to screen readers through their 'Accessibility' pane's 'Alt text' field. When a screen reader encounters a visual, it reads the provided alt text instead of attempting to interpret the visual content, giving non-sighted users a meaningful summary. To be effective, alt text must be concise yet descriptive, and it should be set consistently for charts, slicers, and images; this directly fulfills the requirement to make the report accessible to users who rely on assistive technologies.

• ✗

  Set custom tab order for visuals.

  Why it's wrong here

  Setting a custom tab order improves keyboard navigation by controlling the sequence in which elements receive focus, which is helpful for users who navigate without a mouse. However, tab order does not affect how screen readers describe the content of a visual; it only determines the order in which elements are encountered. Without alt text, a screen reader will still encounter a visual and have no description to announce, so custom tab order alone fails to make the report accessible to users who need screen reader output.

Go deeper

Related to this question