eBay MIND Patterns
  • Introduction
  • Messaging
    • Alert Dialog
    • Confirm Dialog
    • File Preview Card
    • Form Validation
    • Inline Notice
    • Input Meter
    • Input Validation
    • Page Notice
    • Star Rating (static)
    • Time
    • Toast Dialog
    • Tourtip
  • Input
    • Button
    • Checkbox
    • Chips Combobox
    • Combobox
    • Date Picker
    • File Input
    • Input Dialog
    • Listbox
    • Listbox Button
    • Menu
    • Menu Button
    • Phone Input
    • Radio
    • Select
    • Star Rating (interactive)
    • Switch
    • Toggle Button
    • Toggle Button Group
  • Navigation
    • Breadcrumbs
    • Fake Menu Button
    • Fake Tabs
    • Link
    • Pagination
    • Skip Navigation
    • Tile
  • Disclosure
    • Accordion
    • Carousel
    • Lightbox Dialog
    • Details
    • Flyout
    • Footnote
    • Infotip Button
    • Panel Dialog
    • Pulldown List
    • Segmented Buttons
    • Tabs
    • Tooltip
  • Structure
    • Description List
    • Form
    • Heading
    • Image
    • Item Tile
    • Layout Grid
    • Region
    • Table
    • Table Cell
  • Techniques
    • Active Descendant
    • Ambiguous Label
    • Background Icon
    • Keyboard Trap
    • Live Region
    • Offscreen Text
    • Roving Tabindex
    • Skip to Main Content
    • Alternative Text
  • Anti-Patterns
    • Disabling Pinch-to-Zoom
    • Hand Cursor on Buttons
    • JavaScript HREF
    • Layout Table
    • Mouse Hover on Static Elements
    • Open New Window
    • Setting Focus on Page Load
    • Tabindex-itis
    • Title Tooltip
  • Appendix
    • ARIA Essentials
    • Checklist
    • FAQ
    • Keyboard Interface
    • Known Issues
    • Legacy Patterns
      • Fullscreen Dialog
    • MIND Pattern Template
    • Pattern Naming Scheme
    • References
    • Utilities
Powered by GitBook
On this page
  • Introduction
  • Example
  • FAQ
  1. Disclosure

Footnote

Symbols that guide users towards another section of the document for additional information.

Introduction

Users must be able to perceive the association between a symbol and and its associated text.

The symbol is usually one of the following:

  • Asterisk: *

  • Double Asterisk: **

  • Dagger: †

  • Double Dagger: † †

  • Numbers: 1, 2, 3, etc

Example

Here is a footnote symbol contained under a "Seller Fees" section of the page:

<h2>Seller Fees</h2>
<p>This text has a footnote<sup>*<span class="clipped"> - See Seller Fees Notes</span></sup></p>

Here is the associated notes section of the page:

<section role="region" aria-label="Notes - Seller Fees">
  <h2 class="clipped">Notes - Seller Fees</h2>
  <ol>
    <li>This is an actual note</li>
    ..
  </ol>
</section>

Sometimes there are multiple footnote sections on the same page, therefore both the source symbol and target section much be uniquely identified (as in the example above).

FAQ

Why is the symbol not hyperlinked to the footnotes section?

While it is certainly possible to create a page anchor relationship between the symbol and the footnote section, doing so opens its own can of worms. For the time being we believe the strong visual affordance and semantics laid out above will allow all users to identify, navigate and discover the system of footnotes using their keyboard (to scroll the page) or screen reader (to jump to landmark or heading).

Why not use aria-describedby on the symbol to read out the description/footnote?

For sighted users, the symbol gives a visual clue that there is a footnote elsewhere on the page. The user is not forced to read the footnote. This reduces cognitive load for the user. Whilst we could use aria-describedby on the symbol, so that a screen reader would automatically announce the footnote content, we have determined that this would be overly verbose in most cases, and would increase cognitive load for the user.

Should I use role="note" or role="region"?

PreviousFlyoutNextInfotip Button

Last updated 11 months ago

We are currently looking into the current support status of the . For the time being, please use region.

ARIA note role