Remove F42

F42 discusses two issues; keyboard support and semantics. F54 and F59 discuss each issue. Thus F42 is redundant and we should get rid of it.

F42: Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable
http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140724/F42.html

F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function
http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140724/F54.html

F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control
http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140724/F59.html

## Keyboard Support

In F42,

> A control or link created in this manner cannot be tabbed to from the keyboard and does not gain keyboard focus like other controls and/or links.

This is discussed in F54.

> When pointing device-specific event handlers are the only mechanism available to invoke a function of the content, users with no vision (who cannot use devices such as mice that require eye-hand coordination) as well as users who must use alternate keyboards or input devices that act as keyboard emulators will be unable to access the function of the content. 

## Semantics

In F42,

> If scripting events are used to emulate links, user agents including assistive technology may not be able to identify the links in the content as links. 

This is discussed in F59.

> Many HTML elements have well defined roles, such as links, buttons, text fields, etc. Generic elements such as div and span do not have any predefined roles. When these generic elements are used to create user interface controls in HTML the assistive technology may not have the necessary information to describe and interact with the control.