W3C home > Mailing lists > Public > public-html-a11y@w3.org > June 2010

Media--Sec. 25. Content Navigation by Content Structure

From: Janina Sajka <janina@rednote.net>
Date: Thu, 24 Jun 2010 16:41:01 -0400
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-ID: <20100624204101.GO21613@sonata.rednote.net>
Following from Janina and Judy ...

Definition of "ansillary content" isn't jumping out at people.

Suggest: flip phrase to say "Note that, just as books may have ancillary
content such as footnotes and sidebars, ...
ancillary (accessory, auxiliary, adjuvant; e.g. footnotes, sidebars,
etc.)

On first use of "granularity control," say: "which we are calling
"granularity control" ...

In explanatory material rephrase sentence:

This realtime control, which we are calling a "granularity control,"
will allow the user to adjust where "next" and
"previous" controls go, based on DOM structure. Examples are provided
below.

Responding to Eric's comments:
We need to clarify that: we only require this xyz functionality to be
provided in user agents that have the capability to support this
           functionality.

RE File formats: Yes, but these need to be spec'd in HTML5 in
order that user agents which can support this functionality be able to
do so.

Response to Marco: We see you understand granularity well! <grin>

Aurelien: Ansillary -- See above.
Denise: Also a problem with ansillary -- See above:

Rephrase CN5:
Systems supporting content navigation should also support
third-party-provided navigation markup files.

Suggest removing CN1 as it's redundant with requirements for
controls elsewhere in this document.

CN2 -- rewrite from users need perspective

Provide a means to structure a media resource so that user can navigate
it by semantic content structure, e.g. through adding a track to the
video that contains navigation markers (in table-of-content style).
Support keeping all media representations synchronised when users
navigate. 

John: Our response to scoping concern --
Media in HTML5 will be used heavily and broadly. These user requirements
from accessibility will often find broad applicability. Further, we've
clarified these features are to be supported in user agents only where possible
to do so.

Janina and Judy

-- 

Janina Sajka,	Phone:	+1.443.300.2200
		sip:janina@asterisk.rednote.net

Chair, Open Accessibility	janina@a11y.org	
Linux Foundation		http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative	http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)
Received on Thursday, 24 June 2010 20:41:32 GMT

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