W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2011

Draft of HTML 5 technique titles

From: Cynthia Shelly <cyns@microsoft.com>
Date: Sat, 9 Jul 2011 00:35:25 +0000
To: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
CC: Cynthia Shelly <cyns@microsoft.com>, "Loretta Guarino Reid (lorettaguarino@google.com)" <lorettaguarino@google.com>
Message-ID: <C7E43C8B2FFAC740A28B5E52CF7EA9190ACE00@TK5EX14MBXC293.redmond.corp.microsoft.com>
Here's a draft of technique titles for HTML 5 and ARIA, with a few script ones thrown in for good measure.  

1.1.1 Non-text content
	Situation A: If a short description *can* serve the same purpose and present the same information as the non-text content
	*Using aria-labeledby (note:  on img, you must also use @alt to be valid HTML 5 as of last call draft)
	*Using aria-label (note:  on img, you must also use @alt to be valid HTML 5 as of last call draft) 
	*using title

	Situation B: If a short description *can not* serve the same purpose and present the same information as the non-text content (e.g., a chart or diagram):
	* Using aria-describedby
	* Using figure and figcaption (this is in both situation A and situation B, because figcaption is a visible 		element, and can be long)
	* Using a shadow DOM with HTML 5 Canvas

	Situation C: If non-text content is a control or accepts user input:
	* ??? shouldn't H30 be in here too???
	* Using a shadow DOM with HTML 5 Canvas
	* Using aria-label
	* Using aria-labeledby
	* Using details and summary
	* Using Menus
	* Using Commands
	* TODO:  do the other new controls have any special sauce?

	Situation D: If non-text content is time-based media (including live video-only and live audio-only); a test or exercise that would be invalid if presented in text; or primarily intended to create a specific sensory experience
	* Not in LC, but under discussion, is a text alternative for video poster
	* TODO:  check if there's anything else...

	Situation F: If the non-text content should be ignored by assistive technology:
	* Using role=presentation along with H67 (note that this is still being discussed by the WG)

	Short text alternative techniques for use in sufficient techniques above
	* Using @title attribute on img elements
	* Using figure and figcaption
	* (not in the LC decision but still being discussed by the WG: aria-labeledby and aria-label)

	Long text alternative techniques for use in sufficient techniques above
	* Using aria-describedby
	* Using a shadow DOM with HTML 5 Canvas
	
1.2.1 Audio-only and Video-only (prerecorded)
	* using <track> for Video

1.2.2 Captions (prerecorded)
	* Using the <track> element

1.2.3 Audio Description or Media Alternative (pre-recorded)
	* Using the <track> element

1.2.4 Captions (live)
	* Using the <track> element

1.2.5 Audio Description (pre-recorded)
	* Using the <track> element

1.2.6 Sign Language (pre-recorded)
	* Using the <track> element

1.2.7 Extended Audio Description (Prerecorded)
	* Using the <track> element

1.3.1 Info and Relationships
	* Using ARIA roles and properties (this applies to both situation A and situation B, because some of these duplicate things in HTML 5, and others provide semantics that HTML 5 does not)
	* Using ARIA relationships (this is more situation B, since HTML doesn't have most of these things, but in some situations, authors are duplicating HTML functionality)

	Situation A:  
	* Using a shadow DOM with HTML5 Canvas
	* Using aria-label, aria-labledby, and aria-describedby to provide labels and descriptions
	* TODO: List out all the other aria stuff....

	Failures
	* Is there an equivalent to F62 for ARIA relationships?

1.3.2 Meaningful Sequence
	* Using aria-flowto
	* Using a shadow DOM with HTML 5 canvas (maybe a stretch here?)

	Also, we should add this SCRIPT technique and SCRIPT Failure
	* Inserting elements into the DOM in meaningful order
	* Failure due to inserting new elements at the end of the DOM, rather than near their related elements (needs rewrite)

1.4.1 Use of Color
	* Canvas version of G111
	* Using a shadow DOM with HTML 5

1.4.2 Audio Control
	* Is there a technique for <audio> and <video>?
	
1.4.4 Resize text
	* Creating resizable text in HTML 5 canvas (is there a way to do this???)

1.4.5 Images of Text
	* Is there a way to use canvas to achieve logo or font treatment and have it work with HC, large fonts and screen readers????

2.1.1 Keyboard
	* Using tabindex=0
	* Using aria-activedecendant
	* Using new form controls
	* Using <details>
	* Using menus and commands
	* Using role with scripted event handlers (to fix F42)
	* Using a shadow DOM with HTML 5 canvas
	* Keyboard accessible video players in HTML 5???? (talk to media subteam of html-a11y-tf)

2.3.1 Three Flashes or Below Threshold
	* Canvas specific techniques or failures?
	* Video specific techniques or failures?

2.4.1 Bypass Blocks
	* Using HTML 5 menu and commands
	* Using HTML 5 structural elements (is that the right name?  <nav> etc) TODO: expand this
	* Using headings and hgroup
	* Using ARIA menus
	* Using ARIA trees
	* Using ARIA landmark roles
	* TODO:  there are probably other ways to do this....

2.4.3 Focus Order
	* Using tabindex
	* Using aria-flowto
	* Using aria-activedecendant
	* Using HTML 5 menu and command
	* Using HTML details and summary
	* TODO: there are probably other ways to do this....

2.4.4 Link Purpose (in context)
	* Using aria-label
	* Using aria-labeledby
	* Using aria-describedby
	* Using title on image (related to text alternatives changes in HTML 5, may change)
	* Using figure and figcaption (does this make sense for links?)
	* TODO: look at new HTML 5 heading stuff.  Are there new techniques there?

2.4.5 Multiple Ways
	* RDFa and Microformats???
	* Anything here we can use? http://dev.w3.org/html5/spec/browsers.html#browsers
	* Anything here we can use? http://dev.w3.org/html5/spec/sections.html#sections

2.4.6 Headings and Lables
TODO: This one is about the text in the heading or label, not the structure.  Is there a way to impact this with the new hgroup stuff?

2.4.7 Focus Visible
	* Drawing focus rings for HTML 5 Canvas
	* TODO:  are there any other new ways to draw 

2.4.8 Location
	* same as 2.4.5

2.4.10 Section Headings
	* Using headings and hgroups
	* Using section elements
	* Using ARIA landmarks

3.1.1 Language of Page
	* TODO:  check if there is anything new in html 5 or ARIA for this

3.1.2 Language of Parts
	* TODO:  check if there is anything new in html 5 or ARIA for this

3.1.3 Unusual Words
	* Using details and summary
	* SCRIPT:  creating an accessible popup definition

3.1.4 Abbreviations
	* Using details and summary
	* SCRIPT:  creating an accessible popup definition

3.1.5 Reading Level
TODO:  are there any new structures or relationships in HTML 5 or ARIA that could be used to link multiple reading-level versions of the same content?  

3.1.6 Pronunciation
(might be a stretch... using one of the below to provide popup pronunciation guides)
	* Using details and summary
	* SCRIPT:  creating an accessible popup definition

3.2.1 On Focus
TODO: research whether there are new failures for any of the new form or interactive elements.

3.2.2 On Input
TODO: research whether there are new failures for any of the new form or interactive elements.

3.2.3 Consistent Navigation
	* SCRIPT: Using components and component libraries

3.2.4 Consistent Identification
	* SCRIPT: Using components and component libraries

3.2.5 Change on Request
TODO: research whether there are new failures for any of the new form or interactive elements.

3.3.1 Error Identification
	* Using media.error
	* Using onerror event (?)
	* Using aria-alertdialog
	* Using ARIA Live Regions
	* Using @required
	* Using @maxlength
	* Using <input type=number>
	* Using <input type=range>
	* Using <input type=url>
	* Using <input type=email>
	* Using lists and datalists instead of freeform input
	* Using select and option instead of freeform input (is there already one for this?)
	* Using @autocomplete
	* Using @readonly
	* Using @pattern
	* Using @min and @max
	* Using @step
	* TODO:  are there more?

3.3.2 Labels or Instructions
	* Using aria-label (does this work?  Needs to be visible, right?)
	* Using @title (tooltip.  Is the keyboard issue blocking here?)
	* Using aria-labeledby
	* Using aria-describedby
	* Using @placeholder on input
	* TODO: is there anything in aria for linking instructions?

3.3.3 Error Suggestion
3.3.4 Error Prevention (legal, financial, data)
TODO:  figure out which client validation features of HTML 5 are Error ID, Error Suggestion, and Error prevention
	* Using @required
	* Using @maxlength
	* Using <input type=number>
	* Using <input type=range>
	* Using <input type=url>
	* Using <input type=email>
	* Using lists and datalists instead of freeform input
	* Using select and option instead of freeform input (is there already one for this?)
	* Using @autocomplete
	* Using @readonly
	* Using @pattern
	* Using @min and @max
	* Using @step
	* TODO:  are there more?

3.3.5 Help
	* Using details and summary
	* Using aria-describedby

3.3.6 Error Prevention (All)
Same as 3.3.4

4.4.1 Parsing
	* ADD NOTE to H74 and H75 that opening and closing rules are different in HTML 5
Received on Saturday, 9 July 2011 00:35:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 9 July 2011 00:35:56 GMT