Enlarge more info dialog accessibility

[steverep]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

When a more info dialog is displayed, the user can click the title to enlarge the dialog. From an accessibility standpoint, this has multiple failures: no clear label, not sequentially focusable, no role as a control, etc. And there's no clear way to make it accessible because sighted users do not appear to have any indication of the function either (unless I'm missing something?).

Describe the behavior you expected

For general UX, there should be a visible indication of some sort of the capability. Then for assistive technology, that indicator and control should meet accessibility guidelines.

Steps to reproduce the issue

1. Open any dashboard item with a more info dialog
2. Click the title to enlarge it
3. Click title again to shrink it

What version of Home Assistant Core has the issue?

n/a

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[Wetalya]

I will also add: There is no way to "manage" the increase in the width of the dialog box. There are 2 states available: 1) can't see anything 2) all interface elements are very far away

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[steverep]

Still an issue

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[steverep]

Still an issue

[rekinet]

I confirm the problem.

[karwosts]

Possible implementation of a fix in #17371

[steverep]

Thanks for trying to take this on @karwosts. I'll take a look.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[steverep]

Still an issue

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.