Quicksight Accessibility Issues (WCAG 2.1.1, WCAG 1.4.3, WCAG 4.1.2, WCAG 2.4.3)

Q&A
,
1

1- The popover is not readable by screen reader and also not accessible by keyboard (WCAG 2.1.1). 2- The foreground text color does not provide sufficient contrast against its background (WCAG 1.4.3).
3- The text for charts where color specification shown lacks visible text, aria-label, or a valid aria-labelled by reference (WCAG 4.1.2).
4- Keyboard focus indicator(cursor) is not clearly visible for the dropdown (WCAG 2.4.7) which has select criteria for the dashboard.
5- Dropdown is not included in the order/sequence (WCAG 2.4.3).
Please suggest if these to be fixed in near future or anyway we can handle in our application with iframe?

2

Hi @nibeditar333 and welcome to the Quick Community!
It seems like you may be referring to assets that are within a private account, is that the case? This is a public facing forum, we would not have access to this information to understand the scenario.

Maybe you could provide some additional context on what you are referring to throughout these questions?

3

Hello Brett,

Thanks for your response.

We have embedded Amazon QuickSight dashboards inside our web application using an <iframe> (registered user embedding). During accessibility testing using NVDA / Narrator and keyboard-only navigation, we identified several WCAG 2.1 AA issues that appear to originate from QuickSight-rendered UI components inside the iframe, rather than from our host application.

We would like clarification on:

  1. Whether these are known QuickSight accessibility gaps.

  2. If any fixes or improvements are planned.

  3. Whether there are supported workarounds or configuration options we can apply from the host application.

Below are the findings, with WCAG references and context.

  1. Popovers are not accessible via keyboard or screen reader (WCAG 2.1.1 – Keyboard)

Observation
QuickSight popovers (for example, visual tooltips or option popovers) are:

  • Not reachable using keyboard navigation

  • Not announced by screen readers when they appear

This prevents keyboard-only and screen reader users from accessing the content or actions exposed via these popovers.

Impact
Users relying on keyboard or assistive technology cannot interact with or perceive important contextual information.

Note
Since these popovers are rendered entirely within the QuickSight iframe, we are unable to modify their focus handling or ARIA semantics from the host application.

  1. Insufficient text contrast in certain dashboard elements (WCAG 1.4.3 – Contrast (Minimum))

Observation
Some foreground text (labels, metadata text, or UI hints) does not meet the minimum 4.5:1 contrast ratio against its background.

Clarification
We understand that data colors inside charts may be user-configurable, but this issue was observed in QuickSight UI text elements, not just chart series colors.

Question
Is there a roadmap or guidance for ensuring WCAG-compliant contrast in QuickSight system UI text?

  1. Chart legends / color indicators lack accessible text alternatives (WCAG 4.1.2 – Name, Role, Value)

Observation
For certain visuals:

  • Color indicators or legend elements do not expose a readable name to screen readers

  • No visible text, aria-label, or valid aria-labelledby association is announced

As a result, screen reader users cannot determine what the color indicators represent.

Impact
The information conveyed purely through color is not programmatically determinable, limiting non-visual access to chart data.

Questions:

  1. Are the above issues known accessibility limitations in embedded QuickSight dashboards?
  2. Are there any planned fixes or timelines for improving WCAG 2.1 AA compliance?
  3. Are there recommended configurations, themes, or embedding options to improve accessibility?
  4. Is there any official guidance for handling accessibility gaps when QuickSight is embedded via iframe?

We appreciate any direction or updates from the team, as these issues directly impact our ability to deliver an accessible experience to users relying on assistive technologies.

Regards

nibeditar333

4

Hi @nibeditar333,
Since your questions are in relation to compliance scenarios, I would suggest creating a support ticket to get more defined answers/assistance directly from the AWS customer support team.