It sounds like three solutions are needed depending on the use case and the third one below is missing: 1) Use name/description. 2) Use a relation to another accessible. 3) Return a string which is different than name/description (and there is no accessible to build a relation to).
Pete On 8/9/2011 9:31 AM, Alexander Surkov wrote: > Hi, Pete. I don't know why are relations or name/description not > enough since caption and summary are exposed via them too. I bet AT > knows better :) > > Variant should fit perfect. > > Thank you. > Alex. > > > On Tue, Aug 9, 2011 at 11:02 PM, Pete Brunet <[email protected]> wrote: >> Hi Alex, Why are relations sufficient? A relation is a connection to >> another accessible but you said you don't want to fabricate another >> accessible. >> >> We probably should have had caption and summary return a variant so either >> an accessible or a BSTR could be returned. Would that have solved the >> problem? >> >> Pete >> -- >> Pete Brunet >> >> a11ysoft - Accessibility Architecture and Development >> (512) 467-4706 (work), (512) 689-4155 (cell) >> Skype: pete.brunet >> IM: ptbrunet (AOL, Google), [email protected] (MSN) >> http://www.a11ysoft.com/about/ >> Ionosphere: WS4G >> >> On 8/9/2011 8:47 AM, Alexander Surkov wrote: >> >> Hi, Benjamin. >> >> I believe Jamie meant proposed summaryText and captionText when asked >> about accName/accDescription. >> >> More general question can be asked, i.e. why we need to have interface >> to expose caption and summary and it can be worded as "why are >> labelled_by/for and described_by/for relations insufficient". >> >> Thank you. >> Alex. >> >> >> On Tue, Aug 9, 2011 at 3:23 PM, Benjamin Hawkes-Lewis >> <[email protected]> wrote: >> >> On Tue, Aug 9, 2011 at 4:42 AM, James Teh <[email protected]> wrote: >> >> Why are accName/accDescription insufficient? >> >> The content model of HTML <caption> is "flow" (with no descendant >> table elements): >> >> http://www.whatwg.org/specs/web-apps/current-work/multipage/tabular-data.html#the-caption-element >> >> That means it a wide variety of structured markup, including headings, >> changes of language marked up with @lang, and links and form controls. >> A practical use of this complex content model might be to include >> controls for modifying the display of the table or linking to sources >> for the table's data. >> >> accName is a string, so any complex content is flattened into text: >> >> http://msdn.microsoft.com/en-us/library/accessibility.iaccessible.accname.aspx >> >> By contrast, the caption property returns an IAccessible or >> IAccessible2 object that could have children represents the structure >> of the caption. >> >> -- >> Benjamin Hawkes-Lewis >> _______________________________________________ >> Accessibility-ia2 mailing list >> [email protected] >> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 >> >> _______________________________________________ >> Accessibility-ia2 mailing list >> [email protected] >> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 >> >> >> >> >> _______________________________________________ >> Accessibility-ia2 mailing list >> [email protected] >> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 >> >> _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
