Techniques for WCAG 2.0

On this page:

-

# SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element

## Applicability

HTML and XHTML, script

This technique relates to:

- Success Criterion 2.1.1 (Keyboard)
  - How to Meet 2.1.1 (Keyboard)
  - Understanding Success Criterion 2.1.1 (Keyboard)
- Success Criterion 2.4.3 (Focus Order)
  - How to Meet 2.4.3 (Focus Order)
  - Understanding Success Criterion 2.4.3 (Focus Order)
- Success Criterion 2.4.7 (Focus Visible)
  - How to Meet 2.4.7 (Focus Visible)
  - Understanding Success Criterion 2.4.7 (Focus Visible)

## Description

The objective of this technique is to place inserted user interface elements into the Document Object Model (DOM) in such a way that the tab order and screen-reader reading order are set correctly by the default behavior of the user agent. This technique can be used for any user interface element that is hidden and shown, such as menus and dialogs.

The reading order in a screen-reader is based on the order of the HTML or XHTML elements in the Document Object Model, as is the default tab order. This technique inserts new content into the DOM immediately following the element that was activated to trigger the script. The triggering element must be a link or a button, and the script must be called from its onclick event. These elements are natively focusable, and their onclick event is device independent. Focus remains on the activated element and the new content, inserted after it, becomes the next thing in both the tab order and screen-reader reading order.

Note that this technique works for synchronous updates. For asynchronous updates (sometimes called AJAX), an additional technique is needed to inform the assistive technology that the asynchronous content has been inserted.

## Examples

### Example 1

This example creates a menu when a link is clicked and inserts it after the link. The onclick event of the link is used to call the ShowHide script, passing in an ID for the new menu as a parameter.

Example Code:

    <a href="#" onclick="ShowHide('foo',this)">Toggle</a>

The ShowHide script creates a div containing the new menu, and inserts a link into it. The last line is the core of the script. It finds the parent of the element that triggered the script, and appends the div it created as a new child to it. This causes the new div to be in the DOM after the link. When the user hits tab, the focus will go to the first focusable item in the menu, the link we created.

Example Code:

    function ShowHide(id,src)
    {
    	var el = document.getElementById(id);
    	if (!el)
    	{
    		el = document.createElement("div");
    		el.id = id;
    		var link = document.createElement("a");
    		link.href = "javascript:void(0)";
    		link.appendChild(document.createTextNode("Content"));
    		el.appendChild(link);
    		src.parentElement.appendChild(el);
    	}
    	else
    	{
    		el.style.display = ('none' == el.style.display ? 'block' : 'none');
    	}
    }

CSS is used to make the div and link look like a menu.

## Tests

### Procedure

1. Find all areas of the page that trigger dialogs that are not pop-up windows.

2. Check that the dialogs are triggered from the click event of a button or a link.

3. Using a tool that allows you to inspect the DOM generated by script, check that the dialog is next in the DOM.

### Expected Results

- #2 and #3 are true.

- Top
- Contents
- Intro
- Previous: Technique SCR24
- Next: Technique SCR27