Accessibility Insights errors on new Power BI card visual (aria-allowed-attr, aria-required-children

[santosh1213]

Hi community,

I'm encountering some Accessibility Insights for Web issues after switching from the old card visual to the new card visual in Power BI.

When using the old card visual, where we could add only a single measure per visual, all ARIA-related accessibility rules passed without issues. However, after updating to the new card visual—which allows displaying multiple measures in a single card visual—Accessibility Insights flags errors related to the following ARIA rules:

• aria-allowed-attr

• aria-required-children

• aria-required-parent

These violations are not seen with the old card, so it appears to be specific to the structure or ARIA implementation in the new visual. We're aiming to ensure full accessibility compliance in our reports, and these issues are now blockers in our accessibility validation process.

Has anyone else faced this with the new card visual? Are there any workarounds or updates planned by Microsoft to fix these ARIA-related errors?

Thanks in advance for any guidance!

[v-tsaipranay]

Hi @santosh1213 ,

Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback.

Thank you.

[v-tsaipranay]

Hi @santosh1213 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-tsaipranay]

Hi @santosh1213 ,

Thank you for reaching out to the Microsoft Fabric Community Forum.

The ARIA accessibility issues you’re experiencing with the new card visual such as aria-allowed-attr, aria-required-children, and aria-required-parent are likely caused by changes in the DOM structure when multiple measures are shown. As you noted, these issues don’t occur with the older single-measure card visual.

To address this, you can try the following steps:

• If accessibility is a priority, use the classic card visual as a workaround.
• You might also try placing the new visuals inside accessible containers to help with screen reader compatibility, though this may not resolve all errors.
• Since this involves a built-in visual, consider submitting feedback through the Power BI feedback portal: Fabric Ideas - Microsoft Fabric Community

Let us know if you need help exploring alternative approaches or setting up a formal feedback submission.

Thank you.