I know there has been lots of discussion around whether a details block is an accordion or not

It's not an accordion block, but I am concerned about discoverability.

If you're not a developer, it will be difficult to discover the Details block, which is a suitable (and accessible) replacement for accordions in most scenarios.

We could always add an accordion block...

We could always add an accordion block...

Sure!

I would be strongly in favour of an accordion block! But making the details block discoverable as an accordion sets an unhelpful precedent. An accordion has requirements and needs to be accessible in a manner that the details block doesn't support.

They are two different things even if on the surface they seem similar.

But making the details block discoverable as an accordion sets an unhelpful precedent.

The block has its own name; it's not an accordion. If the block was named "Accordion" that'd be suggesting it was an accordion wholesale.

I equate this change to if we removed the "image" keyword from the Cover and Media & Text blocks.

I equate this change to if we removed the "image" keyword from the Cover and Media & Text blocks.

That's really not the same thing. The image keyword is helpful because you can add and work with images in the Cover and Media & Text block, and it's correct to use images in those blocks if you so wish – they support it well and accessibly.

The only reason to add accordion as a keyword is because an accordion shows/hides things, which the Details block does too.

But if people start using the Details block as a replacement for accordions, instead of actual accessible accordions, we'll create more accessibility issues because you can't navigate/jump to a details block like you can to an accordion. When people search for accordion in the Inserter, it should correctly pull up accordion block options available in the plugin repository, instead of suggesting the Details block.

The details block is fantastic when you need to add an aside, when you need to add information that is helpful but not primary, which is why you can't inherently navigate/tab/announce a heading in the summary section of the Details block.

Most people use show/hide (aka accordion functionality) for important things like FAQs and tabs with lots of valuable information that you do need to be able to jump and navigate through. We shouldn't encourage people to use the Details block for things like an FAQ.