W3C home > Mailing lists > Public > public-html-a11y@w3.org > May 2011

Re: Agenda: HTML-A11Y Media Subteam on 25 May at 21:30Z for 90 Minutes

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 26 May 2011 12:22:44 +1000
Message-ID: <BANLkTinhgSwyWNmcgqa7SQiJWQOvuH_tWw@mail.gmail.com>
To: John Foliot <jfoliot@stanford.edu>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>, James Craig <jcraig@apple.com>
Hi John,

such a shame that you weren't able to attend today's meeting.

We discussed where aria-describedby retains the markup and Janina
indicated that her feedback says that yes it should, even if
implemented reality in current screenreaders is not yet so. That
should address both the i18n and the url part of your issues.

The rendering part of multiple aria-describedby references is indeed
something to take up with screenreader developers.

As for the roles, I wonder what the use case would be. Why would they
be required?

Cheers,
Silvia.


On Wed, May 25, 2011 at 10:45 AM, John Foliot <jfoliot@stanford.edu> wrote:
> Silvia Pfeiffer wrote:
>>
>> > agenda+ Paused Media: Continuing Discussion
>>
>> And on this point, it would be good to get people's opinions/feedback
>> on http://lists.w3.org/Archives/Public/public-html-
>> a11y/2011May/0466.html
>
> Hi Silvia,
>
> I have been thinking about this more, and have a Draft email that I hope
> to complete this evening. Sadly I will also be posting my regrets for
> tomorrow's teleconference as I have a campus commitment I cannot avoid.
>
> There *may* be some issues/problems with our scheme, but I need/want to
> involve some others into the discussion. At issue is how the text that
> aria-describedby is subsequently processed - does it retain its markup
> (for example when using <span lang="fr">) or does it become flattened
> unstructured text. If it is the latter we might have a problem both with
> i18n, but also with the solution to the longer description (<a
> href="longerdescription.html">).
>
> There is also a question about support for multiple values of
> aria-describedby, both in terms of browser support, but equally if not
> more importantly with AT support. This may not have a huge impact on
> browsers, but coordination with AT vendors will be critical. For example,
> we are looking at using 2 <p>'s with unique ids to provide text for both
> visual objects. The question is/will be how is this read aloud?  Will it
> be "text describing the video" [pause] "text describing the still image",
> or will it be "text describing the video text describing the still image"?
> (remembering that the describedby is referencing the *content* of the
> container of the id, and not grabbing the semantics or behavior of the <p>
> - this *might* be able to be mitigated by CSS3 Speech
> (http://www.w3.org/TR/2003/WD-css3-speech-20030514/#pause-props) *IF* we
> get some support from the screen readers and others (Voiceover, Chromevox,
> etc.).)
>
> Finally, I want to ping PFWG and the ARIA Working Group about the
> possibility of adding new roles (role="mediadescription" and
> role="posterdescription") as having them may also factor into a more
> scalable and robust solution moving forward.
>
> I recognize that we are building something for the future, so even
> identifying these issues does not necessarily invoke stop-effort, but this
> will require a fair bit of discussion and finessing to get right, and
> involves numerous other players in the big picture game.
>
> More this evening (all being well).
>
> JF
>
Received on Thursday, 26 May 2011 02:23:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:38 GMT