ISSUE-44: Who prunes presentational children?

children presentational

Who prunes presentational children?

ARIA 1.0
Raised by:
Aaron Leventhal
Opened on:
Quoting from

Under 3.2 we have:

Children Presentational
The children are presentational. Assistive technologies may choose to hide
the children from the user, in order to avoid confusing third party APIs
using accessibility APIs. If assistive technologies do not hide the
children, user agents may read some information twice.
Boolean (true | false)

Mozilla actually does the trimming when exposing to accessibility APIs.
The children are their in the DOM but the accessible object children are
not. This means we expose these objects the way they typically are in the
equivalent desktop widgets, the AT will automatically interact with them
the right way.

So we should change the definition to say that "User agents must hide the
children, in order to avoid the presentation of redundant or
presentational content."
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

April 28, 2008. Group agrees that the user agent must prune presentational children when mapping to accessibility api.

Michael Cooper to include Aaron's text

Richard Schwerdtfeger, 28 Apr 2008, 21:05:23

Action at

Michael Cooper, 6 May 2008, 16:06:17

Modify section 4.2.8

The DOM children are presentational. User agents SHOULD NOT expose descendants of this element through the platform accessibility API. If user agents do not hide the children, some information may be read twice.

Richard Schwerdtfeger, 19 May 2008, 20:18:04

Display change log ATOM feed

James Nurthen <>, Valerie Young <>, Chairs, Daniel Montalvo <>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 44.html,v 1.1 2023/05/22 16:31:57 carcone Exp $