Drag and Drop Question You are designing a canvas app that will be used by all users including users who have vision impairments. Which outcome is achieved by each action? To answer, drag the…

Question

Exhibit

Answer Area

Explanation

The question tests understanding of Power Apps accessibility features, specifically how to make content available to screen readers while hiding it from sighted users.

Approach. The correct interaction, as indicated by the solution image, is to drag 'Visible to screen-reader users only' to all three action targets. Here's the reasoning for each:

1. Action: Set the values for the X and Y properties of a control to move the control off-screen.
   • Reasoning: Moving a control off-screen (e.g., to very large negative X, Y coordinates) makes it visually inaccessible to sighted users. However, the control still exists within the app's logical structure (DOM or accessibility tree). Screen readers typically traverse this logical structure and will announce the content of controls, regardless of their visual position on the canvas. This is a common technique for providing 'skip links' or additional context only to screen reader users.
2. Action: Set the Color and other related properties of a control to transparent.
   • Reasoning: Making a control's background, text, and border colors transparent effectively makes it invisible to sighted users, as it blends with the background. Like moving off-screen, this only affects visual presentation. The control itself is still part of the app's structure and its content will be read by screen readers.
3. Action: Set the Height and Width properties of a control to 1.
   • Reasoning: Reducing a control's height and width to a minimal size (like 1, or even 0) renders it practically invisible or extremely difficult to perceive for sighted users. Similar to the other two actions, this is a visual change only. The control and its content remain accessible in the app's underlying accessibility tree, allowing screen readers to detect and announce them.

All three actions are methods to visually hide content while retaining its presence in the accessibility tree, making it available exclusively to screen-reader users.

Common mistakes.

• common_mistake. Other choices are incorrect because they misinterpret how screen readers interact with hidden elements:
• Not visible to any users: This outcome would typically be achieved by setting the control's 'Visible' property to 'false'. The actions described (moving off-screen, transparency, minimal size) specifically hide controls visually but do not inherently hide them from screen readers that interpret the underlying app structure.
• Visible to sighted users only: This is generally not possible for meaningful content. If content is visually present, a screen reader will typically pick it up unless explicit accessibility properties (like 'AccessibleLabel' being blank, or 'TabIndex' set to -1 for interactive elements) are used to suppress it. The given actions explicitly hide content from sighted users.
• Visible to both sighted and screen-reader users: This is the default state for most controls that are visible and have content. The actions provided are specifically designed to alter this default, making controls invisible to sighted users.

Concept tested. Power Apps accessibility and inclusive design principles, specifically understanding how visual properties of controls affect visibility for sighted users versus their accessibility to screen readers.

No community discussion yet for this question.