This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8309 - semantics of footnotes : why not using <aside> elements as well?
Summary: semantics of footnotes : why not using <aside> elements as well?
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: NE
Depends on:
Blocks:
 
Reported: 2009-11-15 22:17 UTC by Philippe Verdy
Modified: 2010-10-04 14:56 UTC (History)
4 users (show)

See Also:


Attachments

Description Philippe Verdy 2009-11-15 22:17:18 UTC
I don't understand why the <aside> semantic can't be applied to footnotes. The HTML5 draft currently suggests using <a> links, but this does not properly set the semantics, and does not also allow alternate rendering for footnotes, notably between paged media, aural media, and non-paged visual media.
The links also does not allow setting properly the relations between groups of footnotes with document sections.

Why can't <aside> element include some properties to suggest the intended location, such as after the section end and before the next section, or at end of the current page, or at end of another higher-level section (such as the current chapter, or current book), or below the current paragraph or block (the smallest section level), or by default beside it (if possible, otherwise it could become another block possibly rendered with indentation (by default), or a frame around it (the effective style for the note's block could be defined also by a stylesheet).

Using the title="" attribute is also bad from a pure accessibility point of view (it won't work properly for pages medias, notably when printing, where another visible location would be preferable, with the same additional grouping semantics)

I then suggest extending <aside> to offer:
- an identifier for the side/foot note : this would be the visible number, or typographic symbol used to access the note from the text where it is referenced, and that would also be automatically inserted at the begining of the note's content. Aural medias may need to change this identifier. Optionally, this identifier could also be a number, generated automatically, according to the notes numbering rules in the group of notes to which it is added.
- a notes grouping mode (or an automatically computed group according to some rules, such as a set of sub-section levels, generally identified by its heading type like chapter, book) which describes how far the note will be located from the main content section where the note is inserted.
- some rendering hints (probably part of CSS styles) for various media types (notably for visual paged and non-paged medias)

And then to deprecate, from a semantics perspective, but also from an accessibility perspective, the legacy use of the title attribute, or of links.
Instead, <aside> notes will just be used to define the content of the note, and there will be a way to insert a reference to it within the main content, where a visible link could be automatically inserted according to the <aside> element properties and its associated CSS styles.
Comment 1 Ian 'Hixie' Hickson 2010-01-06 08:33:21 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: It seems like this is possible already. Just put the footnotes in an <aside>, and link to them using <a>. The position of the <aside> is a stylistic matter; CSS is how that should be handled.

I don't really follow why title="" would be bad for accessibility; it's a purely semantic attribute so ATs can expose it however they deem best. It can also be styled as a footnote if you prefer that presentation to tooltips  that's again a stylistic issue.

We might want to consider a more explicit footnote mechanic in a future version, though.