Should Role::GenericContainer translate to AT-SPI's Panel role?

[Tropix126]

Currently Role::GenericContainer is treated as an AT-SPI Role::Section, which is described as such:

The object is a containing instance of document content which constitutes a particular ‘logical’ section of the document. The type of content within a section, and the nature of the section division itself, may be obtained by querying the object’s attributes. Sections may be nested.

accesskit/platforms/atspi-common/src/node.rs

Line 151 in 96a7ca2

| Role::Ruby => AtspiRole::Section,

This seems to imply that the section role at least could have some semantic meaning to consumers (being a "logical section of the document"). While digging through what a GenericContainer actually entails (it seems like it's possibly useful to magnifiers due to providing layout information about a node), I came across ATSPI's Panel role which, based on the description, seems to fit the purpose of GenericContainer much better.

A generic container that is often used to group objects.

Any thoughts on this? I have no experience using AT-SPI or any platform-native a11y API directly, but it seemed to be worth bringing up here.

[DataTriny]

Hello @Tropix126,

In practice, nodes with Role::GenericContainer are filtered out, and don't end up in the platform's accessibility tree. Unlike nodes with Role::Group or Role::Pane for instance, which are mapped to the AT-SPI Panel role.