Skip to content

Conversation

@IlianaB
Copy link
Contributor

@IlianaB IlianaB commented Nov 3, 2025

related to #7729

@ui5-webcomponents-bot
Copy link
Collaborator

ui5-webcomponents-bot commented Nov 3, 2025

@ui5-webcomponents-bot ui5-webcomponents-bot temporarily deployed to preview November 3, 2025 13:37 Inactive
@ui5-webcomponents-bot ui5-webcomponents-bot temporarily deployed to preview November 18, 2025 11:15 Inactive
@ui5-webcomponents-bot ui5-webcomponents-bot temporarily deployed to preview November 19, 2025 11:10 Inactive
@ui5-webcomponents-bot ui5-webcomponents-bot temporarily deployed to preview November 24, 2025 10:34 Inactive

get accessibilityInfo() {
if (this.mode === IconMode.Decorative) {
return undefined;
Copy link
Contributor

@ilhan007 ilhan007 Nov 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @IlianaB

although the code is completely fine, we would like to suggest a small change - returning empty object {}, instead of undefined when the Icon is decorative.

Context
There was one thing we did not think of until now and it's that the base class (UI5Element) returns undefined by default. And, when decorative, the Icon also returns undefined.

In this case, the component that reads the accessibilityInfo of the components it contains, can't determine if the child component does not implement accessibilityInfo at all or the child component implements it, but must remain hidden from a11y point of view (as the decorative Icon).

For example, the Table has logic by design to provide default accessibility for elements that don't provide such. And in this case, it can't determine if it should provide such default accessibility or not. It reads the accessibilityInfo from the Icon, gets undefined, and applies default accessibility logic (but should not as it's decorative icon and should be hidden from a11y point of view).

We had to decide between these 3 options and picked up the first:

  • returning {}
  • returning null
  • or removing the base implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants