This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
James' comment: 6.1. Documents, Handling frame and iframe elements """ Computing the accessible name for an accessibility node for contained documents: If a sub-document, do a depth-first name computation using aria-labelledby from the <frame> or <iframe>. If the name is still empty, use the title attribute from the <frame> or <iframe>. If the name is still empty, use a depth-first name computation from aria-labelledby on the document's root WAI-ARIA node. If it is still empty use the title attribute on the root WAI-ARIA node. If the name is still empty, and the title element or some other means exists of getting the accessible name, use that. """ This is incorrect because it leaves out the host language labeling mechanism (document.title) and uses a different order than the text alternative computation.
More comments from James on this section: 6.1. Documents, Handling frame and iframe elements """ Computing the accessible description for an accessibility node for contained documents: If a sub-document, do a depth-first description computation using aria-describedby from the frame or iframe. If the description is still empty, use a depth-first name computation from aria-describedby on the document's root WAI-ARIA node. """ Thist could also use description (or summary) meta tag as the host language description mechanism. -------------------------------------------------------------- 6.1. Documents, Handling frame and iframe elements """ This allows the author of the root document to control what gets spoken. They might include an otherwise polite chat program in an iframe and make it assertive. """ This also allows authors to override potentially assertive content that should not be assertive, for example, from included ad banners. -------------------------------------------------------------- 6.1. Documents, Handling frame and iframe elements """ When entering a parent document, refresh the state to again allow override of each of these object properties """ Refresh is the wrong word here because it implies document.reload. Should probably be "update the cache of the accessibility tree"
Added frame/iframe example to bullet 2C in accessible name computation algorithm. Removed this text from the handling frame and iframe elements section: Computing the accessible name for an accessibility node for frame elements: Accessibility properties for the accessibility node for frame elements are exposed as they normally are for an element. <remove> Computing the accessible name for an accessibility node for contained documents: If a sub-document, do a depth-first name computation using aria-labelledby from the <frame> or <iframe>. If the name is still empty, use the title attribute from the <frame> or <iframe>. If the name is still empty, use a depth-first name computation from aria-labelledby on the document's root WAI-ARIA node. If it is still empty use the title attribute on the root WAI-ARIA node. If the name is still empty, and the title element or some other means exists of getting the accessible name, use that. Computing the accessible description for an accessibility node for contained documents: If a sub-document, do a depth-first description computation using aria-describedby from the frame or iframe. If the description is still empty, use a depth-first name computation from aria-describedby on the document's root WAI-ARIA node. </remove>
Write up the general steps. This is basically saying the following: In most cases, attributes on the document override attributes on the sub-document. But in the case of aria-live, -atomic, -relevant, and -busy the attributes of the sub-document override the attributes on the frame in the document. David will provide Cynthia a test case to see what IE does. Need to find out how other APIs handle this.
Per discussion at PF F2F meeting October 31st, we agreed to remove this section. http://www.w3.org/2011/10/31-pf-minutes.html