Re: [aapi] presentation tables test file

Hi Cynthia,

> This is the test file I was using ihe call today.

Thanks for this.

I've made a similar file with <div> and <ul> elements, with and without 
role="presentation", and with and without tabindex="0" -- see attached.  
I tested it with FF to see what was exposed via AT-SPI.  Here are the 
results:

FF 35.0.1 and AT-SPI, using Accerciser inspection tool.

The plain <div> is mapped as ROLE_SECTION.

For the <div> with role="presentation", there is no accessible in the 
a11y tree, which is correct.  But, the text content of the <div> also is 
not present in the a11y tree.  This is a bug.

The <div> with role="presentation" and tabindex="0" is mapped as 
ROLE_SECTION, STATE_FOCUSABLE.

plain ul:
- ROLE_LIST
- the <li> children are exposed as ROLE_LISTITEM
- the <p> elements nested within a list item remain nested as such in 
the a11y tree, each with ROLE_PARAGRAPH.

ul with role="presentation":
- no accessible for the list.
- no accessibles for the list items, nor is their textual content 
present in a11y tree.  Again, the missing text is a bug.
- the nested <p> elements appear as children of the document frame 
accessible, which makes sense since there are no ROLE_LISTITEM 
containers.  But, if there were some generic container that maintained 
the hierarchy, then the ROLE_PARAGRAPH accessibles would be inside it.

ul with role="presentation" and tabindex="0":
- ROLE_LIST, STATE_FOCUSABLE
- the <li> children are exposed as ROLE_LISTITEM.
- the nested <p> elements are exposed (with ROLE_PARAGRAPH), but are 
siblings of the list item accessibles.  They are no longer nested within 
the ROLE_LISTITEM containers.  Is this a bug? Shouldn't the paragraphs 
remain children of the listitems in the a11y tree as in the case of the 
plain <ul> above?

Hope that's useful.

-- 
;;;;joseph.

'Array(16).join("wat" - 1) + " Batman!"'
            - G. Bernhardt -