Techniques/ToDo
General
- Using a static text alternative to describe a "talking head" video
- Using relative lightness in addition to color to convey information
CSS
- Using CSS to highlight the focused element
- Using an invisible header text in the sidebar navigation
- Techniques/CSS/Using CSS Clipping with Sprites
- Techniques/CSS/Using the speak-as property to clarify the meaning of counters and bullets
- Techniques/CSS/Technique which counter-styles require clarification using speakas and which ones work as-is
- Techniques/CSS/Using CSS borders to draw focus rings
- CSS for focus visible?
- CSS responsive layouts
- CSS for icon fonts
- CSS for contnet:before images and sprites
HTML
- Using data table markup to label form elements (e.g. single Likert-type scale radio buttons used for multiple rows). [Bruce]
- Use markup to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. [Bruce]
- Failure of 1.3.1 for not including table title in CAPTION. [Bruce]
HTML5
- Using figure and figcaption (this is in both situation A and situation B, because figcaption is a visible element, and can be long) - [Alastair]
- Using a sub DOM with HTML 5 Canvas SubDOM for Canvas for non-text content [James]
- Modify H30 due to links being allowed to wrap block level elements - http://simplyaccessible.com/article/html5-block-links/)
- Using a shadow DOM with HTML 5 Canvas
- Using details and summary [Paul)] - make sure to add user agent notes for where details doesn't meet 2.1.1
- Using Menus [Marc]
- Using Commands [Marc]
- Using @title attribute on img elements
- Using the TextTrack API to provide captions dynamically [Loretta & Paul]
- Playing a sign language video from a video element's video track list [Loretta & Paul]
- Using section elements Single Page of HTML5 Section element examples
- The <section> element
- The <article> element
- The <nav> element
- The <aside> element
- Is there a technique for <audio> and <video>?
- Creating resizable text in HTML 5 canvas
- Edit H91 in order to add the new control labeling mechanisms [Paul] - also look to see why file is missing
- Edit H91 to account the AAPI mappings in the HTML5 [Paul]
- Add a technique like H91 for HTML5 interactive controls such as details, menu & dialog [Paul]
- Keyboard accessible video players in HTML 5
- Using HTML 5 menu and commands (not in html5 only 5.1 - do not create a technique)
- Using HTML 5 structural elements (is that the right name? <nav> etc) TODO: expand this [James] - base on http://www.w3.org/WAI/GL/wiki/Using_HTML5_section_elements (similar to http://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks_to_identify_regions_of_a_page )
- Using headings and hgroup (HTML5 outlining mechanism) - look at http://accessiblehtmlheadings.com/ . Is this HTML5 or 5.1??
- Using tabindex [Adam]
- Drawing focus rings for HTML 5 Canvas
- Maybe edit http://www.w3.org/TR/2013/NOTE-WCAG20-TECHS-20130905/G141 to allow other ways to create headings
- Using an audio element to provide the pronunciation
- autofocus (maybe an advisory technique for 3.2 or 3.3 here - but low priority)
- Using Sectioning elements consistently across pages [James] (perhaps just add to Generic one)
- Error Identification:
- Using @required [Marc]
- Using @maxlength [Marc]
- Using <input type=number> [Marc]
- Using <input type=range> [Marc]
- Using <input type=url> [Marc]
- Using <input type=email> [Marc]
- Using <input type=tel> [Marc]
- Using <input type=date|datetime|month etc> [Marc]
- Using @pattern [James]
- Using @min and @max [James]
- Using @step [James]
- Using 4.10.21 Constraints (there are probably LOTS of techniques here) [James/Paul]
- Using Custom Error messages [Paul] ( http://www.html5rocks.com/en/tutorials/forms/constraintvalidation/ , http://pauljadam.com/forma11y/#slide09 )
- Using @placeholder on input The placeholder disappearing on type-in is a problem for people with cognitive disabilities. Advisory? [Paul]
- Using aria-describedby to associate instructions with a user input control [Loretta]
- Using aria-labelledby to associate a label with a user input control [Loretta]
- Using lists and datalists instead of freeform input (datalist is new for HTML5) [Marc]
- Using select and option instead of freeform input (is there already one for this?) [Marc] See also H85.
- Using @autocomplete or Turning off @autocomplete (not really sure there is a technique here - sometimes it helps and sometimes it hurts; it is on by default) [Loretta,John]
- Using @readonly Adam (low priority - we think this might be displaying the same page as readonly for the confirmation page)
- ADD NOTE to H74 and H75 that opening and closing rules are different in HTML 5
- Using the HTML5 Accessible Name calculation hierarchy. [Loretta]
Client Side Script
- Inserting elements into the DOM in meaningful order
- Using innerHTML, outerHTML, insertAdjacentHTML, and document.write
- Failure due to inserting new elements at the end of the DOM, rather than near their related elements (needs rewrite) - for example to show a modal dialog. [Paul/James]
- Creating an accessible popup definition
- Managing focus for modal dialogs
- Using a script load toggle for feature detection libraries to provide a conforming alternate version
ARIA
- Using the WAI-ARIA aria-expanded state to mark expandable and collapsible regions [Loretta - 08-Oct-2012, Needs Info - See Jason Kiss comments sent to WCAG list 1st Nov]
- Using Aria role=dialog to expose a custom dialog (pop-up div box) [JCraig, Detlev]
- Making actions keyboard accessible by using keyboard event handlers with WAI-ARIA controls [Loretta, Josh]
- Using ARIA menus [Jon Gunderson]
- Using ARIA trees [Jon Gunderson]
- Using aria-describedby for link purpose [Jon Gunderson]
- Using aria-activedescendant [Adam]
- Using aria-describedby [Detlev - has made a small closed button example that needs to be added to an existing tech - Maybe Davids.]
- Using WAI-ARIA aria-checked=mixed [Jon Gunderson]
- Using WAI-ARIA states and properties to create a menu [James Nurthen]
- 4.1.2 Failure of 4.1.2 due to using Using Abstract Roles [James]
- Using WAI-ARIA range attributes for range widgets such as progressbar, scrollbar, slider, and spinbutton [Loretta]
- Using the region role to identify a region of the page
- Using WAI-ARIA states and properties to create an interactive grid
- Failure of 1.3.1 due to using role="application" when not all content is navigable