Difference between revisions of "User:Sfaulkne/main-usecases"

From HTML WG Wiki
Jump to: navigation, search
(Use cases)
Line 26: Line 26:
 
* Enable users to be able to navigate to and recognise the boundaries of the main content area  
 
* Enable users to be able to navigate to and recognise the boundaries of the main content area  
 
* Enable authors to style the main content area of a page specifically.
 
* Enable authors to style the main content area of a page specifically.
* Enable authors to markup an area of a page as the main content area, that builds on existing authoring practices
+
* Enable authors to markup an area of a page as the main content area that with an element that has the semantics built in and discoverable by users.
 
* Provide a means for browsers to map role, state and property information to a HTML structure representing a common significant distinct content structure.
 
* Provide a means for browsers to map role, state and property information to a HTML structure representing a common significant distinct content structure.
 
* Re-use an existing ARIA semantic that currently has to be bolted on by authors and for which where there is already an existing relationship and use with common HTML authoring practices.
 
* Re-use an existing ARIA semantic that currently has to be bolted on by authors and for which where there is already an existing relationship and use with common HTML authoring practices.
 
* Bake in to HTML an existing ARIA role semantic which is [http://www.html5accessibility.com/tests/landmarks.html interoperably supported] across browsers and AT and [http://www.paciellogroup.com/blog/2011/07/html5-accessibility-chops-aria-landmark-support/ utilised in AT] to provide understanding and utility of an HTML content structure, to the benefit of end users.
 
* Bake in to HTML an existing ARIA role semantic which is [http://www.html5accessibility.com/tests/landmarks.html interoperably supported] across browsers and AT and [http://www.paciellogroup.com/blog/2011/07/html5-accessibility-chops-aria-landmark-support/ utilised in AT] to provide understanding and utility of an HTML content structure, to the benefit of end users.

Revision as of 22:08, 26 November 2012

Rationale and use cases for standardizing a 'main content' HTML feature

This document captures the rationale and use cases for standardizing a feature for identification of the main content section of a web page

Introduction

  • HTML has a pattern of providing an explicit declaritive method for the identification and marking up of significant semantic structures via elements and attributes. Additonal semantics can also be applied by an author to elements in HTML using ARIA attributes.
  • There is an existing pattern in browsers of mapping these elements to roles, states and properties in accessibility APIs
  • There is an emerging pattern in browsers of mapping ARIA semantics to HTML features when roles, states and properties are not already present in an accessibility API.
  • There is an existing pattern of authors defining a distinct container for the main content area of a web page using semantic id values.
    • It has a high correlation with the use of the ARIA role=main which is a semantic marker for the main content area of a web page
    • It has a high correlation with the use of the the id value as a document fragment identifer used as target for 'skip links' to the main content area of a web page.
  • Existing authoring practices for the identification of content structures has previously been used as a reason to add header/footer/article/aside and other elements.
  • Assistive technology have a pattern of using the explicit semantic information exposed by HTML elements via accessibility APIs and/or the DOM to make users aware of the structures and represent their relationship with other structures:

Typical support patterns of HTML elements by screen readers:

  • Identification of an element by role as the user moves through the content.
  • Announcement of the text content of an element.
  • Announcement of the start and end of an element.
  • Change in voice as the content of an element is announced.
  • Announcement of an elements accessible name and/or description
  • Announcement of states and properties.
  • Emission of a beep or other sound when an element with a particulat state or property receives virtual focus.
  • Instructions on how to operate interactive elements such as form controls.
  • Navigation of elements by keyboard and “quick access” lists of a particular elements, list items are linked to each instance of an element on the page.

Use cases

  • Enable users to be able to navigate to and recognise the boundaries of the main content area
  • Enable authors to style the main content area of a page specifically.
  • Enable authors to markup an area of a page as the main content area that with an element that has the semantics built in and discoverable by users.
  • Provide a means for browsers to map role, state and property information to a HTML structure representing a common significant distinct content structure.
  • Re-use an existing ARIA semantic that currently has to be bolted on by authors and for which where there is already an existing relationship and use with common HTML authoring practices.
  • Bake in to HTML an existing ARIA role semantic which is interoperably supported across browsers and AT and utilised in AT to provide understanding and utility of an HTML content structure, to the benefit of end users.