This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24482 - AX: AAPI mappings does not explicitly allow for UAs to determine presentational heuristics
Summary: AX: AAPI mappings does not explicitly allow for UAs to determine presentation...
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-03 22:56 UTC by James Craig
Modified: 2014-02-13 23:45 UTC (History)
7 users (show)

See Also:


Attachments

Description James Craig 2014-02-03 22:56:25 UTC
AX: AAPI mappings does not explicitly allow for UAs to determine presentational heuristics.

For example, <table> is not exposed as AXTable if WebKit can determine that it is a layout table versus a data table. Likewise, web authors use <ul> as layout lists in a bunch of places, too. The HTML AAPI should explicitly require these to be mapped to these semantic elements if the UA can determine they are not used in a semantically meaningful context.
Comment 1 Jason Kiss 2014-02-04 00:07:45 UTC
Is that something that might be better addressed in the document with
one or more statements regarding AAPI behaviour generally? Perhaps it could
fit well into the reworked Core and HTML5.1 User Agent Implementation
Guide framework [1] proposed by Richard?


[1] http://www.w3.org/WAI/PF/wiki/Outline_Core_User_Agent_Implementation_Guide
Comment 2 James Craig 2014-02-04 00:12:26 UTC
Yes, I think a few sentences stating this somewhere is fine, but it may also be prudent to include a footnote or asterisk reference from a few elements in the list, particularly <ul>, <ol>, and <table>. 

It might also to be good to change a few references like:

> li (parent is an ol or ul)

to:

> li (parent is a non-presentational ol or ul)
Comment 3 alexander surkov 2014-02-05 13:17:34 UTC
For the recored: in case of Firefox and layout tables we do create table related accessibles and expose table related interfaces but we set a layout flag on the table so AT knows this table is layout one.
Comment 4 James Craig 2014-02-13 23:45:35 UTC
In the case of WebKit, we determine if it's a layout table, and if so, we expose it as a generic grouping container.

http://trac.webkit.org/browser/trunk/Source/WebCore/accessibility/AccessibilityTable.cpp#L93