W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13629] New: Identifying repeated and non-repeated content

From: <bugzilla@jessica.w3.org>
Date: Wed, 03 Aug 2011 19:58:19 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13629-2486@http.www.w3.org/Bugs/Public/>

           Summary: Identifying repeated and non-repeated content
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: a11y
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: gcl-0039@access-research.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, public-html-a11y@w3.org

HTML5 should provide a mechanism by which site authors can identify blocks of
content that repeat across pages, and portions within repeated blocks that are
customized for a particular page.

One method would be to allow elements inside nav, header, or footer blocks to
be marked with an attribute that identified them as page-specific, while
another method would be to enclose those same elements in an element (like
aside) that identifies them as being related to other content (like the main
article). A third would be that rather than assume nav, header and footer are
repeating across pages, to allow any element to be marked with an attribute
that identified it as repeating, not repeating (page-specific), or unspecified
(e.g. repeated=yes, =no, or blank meaning unspecified). 

Another aspect would be to allow marking up an element with an arbitrary name
identifying a group of pages on which the element repeated (e.g. pages at
sample.com/software have <header group="software">, while pages at
sample.com/hardware have <header group="hardware">).

Note that while nav, header and footer elements often repeat across pages,
other content may as well. 

Use case: Ellen is using a screen reader and as she visits successive pages on
a site, she does not want to listen to repeated blocks of content such as the
header, footer, and bar. The simple solution is to ask her screen reader to
skip over or her web browser to hide elements with the header, footer, and nav
roles. However, she frequently visits a site on which these blocks, while
generally repeating, contain information that is customized for each page. For
example, each page also contain a side bar with several sections that repeat on
each page (Calendar, Top Stories, Users Online) but also some sections that are
specific to the page (a tag cloud and set of "Related" links). Similarly,  the 
the navigation bar always shows links to the high-level segments of the site,
but it also shows links to the sub-segments under the current segment; thus,
any of the Samples pages would have links for Home, Biography, Bibliography,
and Samples with subsidiary links for Sample 1, Sample 2, and Sample 3, while
any of the Bibliography pages would have links for Home, Biography,
Bibliography with subsidiary links for Non-Fiction, Fiction, and Short Works,
and finally Samples. Ideally these non-repeated sections of the navigation and
side bars would be marked as non-repeating, so that the user could have only
those segments read to her.

Use case: Ronald uses a mobile device and visits the same site. Because space
is precious, and he doesn't want to have to scroll through many, many lines of
repeated content, an add-in for his browser provides a mode wherein all
repeated content is hidden, including everything in the navigation bar and side
bar except those portions marked as page-specific. This greatly reduces the
number of inputs he has to use to navigate the page, as well as reducing
bandwidth. When he decides he wants to use the repeated navigation links, he
can chooses one of the mostly hidden regions and have it shown by itself, again
keeping the amount of screen space and navigation commands to a minimum.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 3 August 2011 19:58:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:59 UTC