This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information. Much of the content of this wiki is being migrated to the WCAG wiki at W3C.

From WCAGWiki

Note: To make editing this page a bit easier, I've removed the wiki template stuff. 
Please include details about where these came from (meeting resolution, techniques form 
submission, etc.) if you edit this page. 

ARIA

• Using the Accessible Rich Internet Applications aria-describedby property to provide a programmatically determined description
• Identifying valid range information with the "aria-valuemin" and "aria-valuemax" properties
• Using the WAI-ARIA aria-label and aria-labelledby properties to associate text labels with form elements
• Using the WAI-ARIA aria-live property to mark live regions
• Using the WAI-ARIA presentation role to indicate elements are purely presentational
• Identifying required fields with the aria-required property
• Using Accessible Rich Internet Applications to programmatically identify form fields as required

Ideas

• Add a scripting technique for building accessible trees (old action from Issue 1893)

SC 1.2.6

• Providing a new page that has the video with the sign language interpretation of the audio track (not completed before PR)

SC 3.3.5

• Using scripts to provide context-sensitive bubble help (not completed before PR)

SC 4.1.1

• Ensuring that id attributes are unique on a Web page
• Ensuring that elements do not contain duplicate attributes

SC 4.1.2

• Using WAI-ARIA to provide semantic role information for a JavaScript/CSS dialog
• Using CSS positioning to position label elements offscreen when visible text labels can not be used

Conformance

• Creating an equivalent to a user interface control @@ cynthia, requiremet 1 (not listed in Understanding document, no record of title acceptance)