Re: code samples for extended description

Hi Jason, in your suggested use of the summary element, would the text
information be adequate for machine processing? (i.e. recognisable
vocabulary for search/filtering purposes) Or ; as is my assumption ; would
that be human-readable text, meant to be displayed / rendered in a form
suitable for end-user consumption? Daniel
On 12 Jan 2016 10:17 p.m., "White, Jason J" <jjwhite@ets.org> wrote:

>
> > On Jan 12, 2016, at 14:57, Siegman, Tzviya - Hoboken <tsiegman@wiley.com>
> wrote:
> >
> > One of the issues that we have not fully resolved is that, especially
> when using <details> and <summary>, there is nothing to indicate to users
> that the content is a description. We have talked about adding an attribute
> to ARIA or HTML.  How does a user know that she is looking at a description
> of a video as opposed to video metadata?
> This can be solved today by providing suitable text in the SUMMARY
> element, as your examples demonstrate. I wouldn’t be opposed to a new ArIA
> property, but I suspect the need for it is overestimated.
>
> I tested the examples successfully in Safari/VoiceOver under OS X.
>
>
> ________________________________
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
>
> Thank you for your compliance.
>
> ________________________________
>