summary[role='button'] without accessible name not reported

[khiga8]

Hello! We are upgrading our axe version from 4.0.0 to 4.4.1 (yes we are a bit behind).

Previously axe reported summary[role='button'] without an accessible name as a violation. However, since the upgrade, it is no longer reported. I notice there were some changes with some of the logic in button-name being moved into a new aria-command-name.

I believe any element with [role='button'] without an accessible name should be reported.

[straker]

Thanks for the issue. I'm not exactly sure how to deal with this one as there seems to be a few things going on. I'll have to get with @WilcoFiers to see what he thinks.

[WilcoFiers]

I'm very surprised axe doesn't cover is. That's an unusually large gap. I think the solve is to add it to the button-name rule. Lets make sure we do this for the next minor release.

[padmavemulapati]

Verified with dev branch code base, for summary element if role=button is given, it should serve with the accessbile name. If role=button without an accessible name should be reported.

Test code snippet:

<details>
    <summary id="button-role-fail" role="button"></summary>
    Hello world
  </details>

Environment:

Label	Value
Product	axe-core
Version	4.10.0(Dev Branch Code base
OS-Details	_MAC- 14.4.1 _
BrowserDetails	Chrome Version 126.0.4