DroppedAttributeAxis

From HTML WG Wiki
Jump to: navigation, search


Dropped Attributes: "axis" and "abbr" attributes for TD and TH

Issue: Justification for the deprecation of the "axis" and "abbr" attributes defined for TD and TH elements in HTML 4.01.


Details

What Are the Attributes Being Dropped?

The "abbr" and "axis" attribute as defined in HTML 4.01

Source: HTML 4.01 Technical Specification

abbr = text CS

   This attribute should be used to provide an abbreviated form of the cell's content, and may be rendered by user agents when appropriate in place of the cell's content. Abbreviated names should be short since user agents may render them repeatedly. For instance, speech synthesizers may render the abbreviated headers relating to a particular cell before rendering that cell's content.

axis = cdata CI

   This attribute may be used to place a cell into conceptual categories that can be considered to form axes in an n-dimensional space. User agents may give users access to these categories (e.g., the user may query the user agent for all cells that belong to certain categories, the user agent may present a table in the form of a table of contents, etc.). Please consult the section on categorizing cells for more information. The value of this attribute is a comma-separated list of category names.

Rationale: Why the "axis" Attribute Should Not be Included in HTML5

 (Note: Is there a valid argument for seperating discussion of the "axis" attribute from the discussion of the "abbr" attribute? Please send reasons pro and con the seperation of these two issues to HTML Working Group's public-html@w3.org emailing list.)
  1. List Rationale
  2. List Rationale
  3. List Rationale
  4. List Rationale
  5. List Rationale
  6. Applicable Design Principles (proposed)
    • Accessibility
    • Device Independence
    • Backwards Compatibility

Rationale: Why the "axis" Attribute Should be Retained in HTML5

  1. List Rationale
  2. List Rationale
  3. List Rationale
  4. List Rationale
  5. List Rationale
  6. Applicable Design Principles (proposed)
    • Accessibility
    • Backwards Compatibility
    • Device Independence

Rationale: Why the "abbr" Attribute Should Not be Included in HTML5

  1. List Rationale
  2. List Rationale
  3. List Rationale
  4. List Rationale
  5. List Rationale
  6. Applicable Design Principles (proposed)
    • Accessibility
    • Device Independence
    • Backwards Compatibility

Rationale: Why the "abbr" Attribute Should be Retained in HTML5

  1. Provides a means of providing terse table heading information to the end user.
  2. Assists in non-visual or partially visible interactions with tables, and provides badly needed orientation information for blind,legally blind, and low vision users, as well as those with certain forms of cognative disabilities and certain types of dyslexia, who are benefitted by the use of supplemental speech.
  3. List Rationale
  4. List Rationale
  5. List Rationale
  6. Applicable Design Principles (proposed)
    • Accessibility
    • Backwards Compatibility
    • Device Independence

Use Cases


Research


Examples


Advice From Authorities


Policies, Guidelines, and Law


Related References


Related E-mail

Thread