ISSUE-44: Who prunes presentational children?
children presentational
Who prunes presentational children?
- State:
- CLOSED
- Product:
- ARIA 1.0
- Raised by:
- Aaron Leventhal
- Opened on:
- 2008-04-04
- Description:
- Quoting from
http://lists.w3.org/Archives/Member/w3c-wai-pf/2008AprJun/0041.html
Under 3.2 we have:
Children Presentational
role:childrenArePresentational
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
Action at http://www.w3.org/2008/04/28-pf-minutes#item04
Michael Cooper, 6 May 2008, 16:06:17Modify 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.
Display change log
