Not at a pc but I am fairly certain that this is not correct as the code is used in many places where it is correct. Can a layout override not be created for the specific issue and not be so generic as this is

AXE and other tools mark this as an issue not only for pagebreak but also on other places, for example in menuitem type modal. See also https://www.w3.org/WAI/ARIA/apg/patterns/accordion/examples/accordion/

We found another issue in this bootstrap method, but it is not in scope of this PR.

You are absolutely correct that the slider should not have any roles.

The problem, as I suspected, is that the bootstrap accordion is used in other places where it is absolutely correct for it to have the roles we have specified. The main example of this in the core is the mobile display in the admin of the options page. This uses the bootstrap accordion to display the tabs vertically and collapsed. This view is correctly using role=tab etc.

Please update this PR to not update the accorsdion in th library but to just correct the output of only the pagebreak slider.

I am currently at JoomlaDagen and have verified this with one of the leading accessibility consultants in the Netherlands.

The function addSlide in the library Bootstrap.php is being used only on four places:
administrator\components\com_finder\src\Service\HTML\Filter.php
administrator\components\com_menus\tmpl\menutypes\default.php
components\com_config\tmpl\modules\default_options.php
plugins\content\pagebreak\pagebreak.php
all having the same issues.

The bootstrap accordion itself is correct. But the code generated in the Helper is wrong.

@chmst I've added two page breaks to article = Typography and changed the setting of page-break plugin to sliders.
The JooA11y plugin does not notice a failure on the page.

@hans2103 jooa11y discovers only some rules like missing alt texts, coloour contrast issues for example, but not all issues.

Use another tool and you get this:

Interesting: different Tools find different issues. In this accordion alsió the expanded attribute is wrong.

@brianteeman said that he found a better solution. Looking forward ...

This pull request has been automatically rebased to 4.4-dev.

@brianteeman said that he found a better solution. Looking forward ...

I did?

This pull request has been automatically rebased to 5.2-dev.

I have tested this item ✅ successfully on 29111d5

The role was removed once the patch applied in the area suggested.

I have tested this item ✅ successfully on 29111d5

Tested this, for the accordion only. Noticed an empty space left before closing button tag, where role was declared.

RTC

#40578 (comment)

I chcked this again and again, in backend, with every device, with modals and option panel but cannot see where the role is needed.

ARIA: tabpanel role
The ARIA tabpanel is a container for the resources of layered content associated with a tab.

The tabpanel role indicates the element is a container for the resources associated with a tab role, where each tab is contained in a tablist.

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/tabpanel_role#description)

What you say is correct @brianteeman but we are talking about the output of the pagebreak plugin that is incorrect

my bad - the accordion in the component options doesnt use the library as I had expected. Luckily it uses its own custom-element

according to the WAI best practices there should still be a role but this type =region to indicate a landmark region that contains the currently expanded accordion panel.

https://www.w3.org/WAI/ARIA/apg/patterns/accordion/examples/accordion/

I have tested this item ✅ successfully on a9a836d

Before PR: error in accessibility testing tools because of wrong "tab" role in the slider layout
After PR: no error

I have tested this item ✅ successfully on a9a836d

Issue with 'Child roles required' from parent "tablist" role, no longer present.

RTC

Thank you!