There is a mechanism to remap the shortcut to an unprintable character. The shortcut only works within a specific component and is only active when that component has focus. Users should be able to extend or disable time limits in content, unless that time limit is an essential part of an actual function, such as an auction. Users must be able to hide all blinking or scrolling functions. The only exception is true emergency alerts. No characteristic may flash more than three times in one second. A mechanism must exist to bypass duplicate content blocks. All page titles should describe the topic and purpose of the page. When a page is navigated sequentially, the components should receive focus in the correct order when accessed by keyboard. Any multiple-input gesture has only one input alternative. When a feature is click-enabled, it must use one of the individual email list following accessibility features: The down click alone does not activate the function. There is an option to cancel or abort the click. Releasing the pointer button cancels the click. The only exception is when the function is designed to emulate a keyboard or numeric keypad. When a button includes text or images, the button name contains that name or describes the visual content of the button. Motion-activated functions must also be able to be activated via the user interface. The only exception is when movement is an essential part of the activity and the GUI cannot replicate the function. The default language of a Web page can be determined by programming. Buttons and other interactive components cannot change their purpose when they receive user focus. Changing user settings should not change the context of buttons or interactive elements.