View source for WCAG 2.0 Techniques Applicable to Mobile without Changes

==General Techniques Applicable to Mobile without Changes==
[http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140311/Overview.html#contents WCAG 2.0 Techniques]
{| class="wikitable"
|-
! Technique !! Applies to 
|-
| G5: Allowing users to complete an activity without any time limit || Mobile Web, Native Apps
|-
| G8: Providing a movie with extended audio descriptions || Mobile Web, Native Apps
|-
| G11: Creating content that blinks for less than 5 seconds || Mobile Web, Native Apps
|-
| G13: Describing what will happen before a change to a form control that causes a change of context to occur is made || Mobile Web, Native Apps
|-
| G14: Ensuring that information conveyed by color differences is also available in text || Mobile Web, Native Apps
|-
| G15: Using a tool to ensure that content does not violate the general flash threshold or red flash threshold || Mobile Web
|-
| G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text || Mobile Web
|-
| G19: Ensuring that no component of the content flashes more than three times in any 1-second period || Mobile Web, Native Apps
|-
| G54: Including a sign language interpreter in the video stream|| Mobile Web, Native Apps
|-
| G55: Linking to definitions || Mobile Web, Native Apps
|-
| G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content|| Mobile Web, Native Apps
|- 
| G57: Ordering the content in a meaningful sequence|| Mobile Web, Native Apps
|- 
| G58: Placing a link to the alternative for time-based media immediately next to the non-text content|| Mobile Web, Native Apps
|- 
| G59: Placing the interactive elements in an order that follows sequences and relationships within the content || Mobile Web, Native Apps
|-
| G62: Providing a glossary || Mobile Web, Native Apps
|-
| G63: Providing a site map || Mobile Web
|-
| G64: Providing a Table of Contents|| Mobile Web, Native Apps
|- 
| G65: Providing a breadcrumb trail || Mobile Web, Native Apps
|-
| G69: Providing an alternative for time based media || Mobile Web, Native Apps
|-
| G70: Providing a function to search an online dictionary || Mobile Web, Native Apps
|-
| G71: Providing a help link on every Web page || Mobile Web, Native Apps
|-
| G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content || Mobile Web
|-
| G74: Providing a long description in text near the non-text content, with a reference to the location of the long description in the short description|| Mobile Web
|- 
| G75: Providing a mechanism to postpone any updating of content || Mobile Web, Native Apps
|-
| G76: Providing a mechanism to request an update of the content instead of updating automatically|| Mobile Web, Native Apps
|- 
| G79: Providing a spoken version of the text || Mobile Web, Native Apps
|-
| G81: Providing a synchronized video of the sign language interpreter that can be displayed in a different viewport or overlaid on the image by the player || Mobile Web, Native Apps
|-
| G86: Providing a text summary that requires reading ability less advanced than the upper secondary education level || Mobile Web, Native Apps
|-
| G91: Providing link text that describes the purpose of a link || Mobile Web, Native Apps
|-
| G92: Providing long description for non-text content that serves the same purpose and presents the same information|| Mobile Web, Native Apps
|-
| G93: Providing open (always visible) captions || Mobile Web, Native Apps
|-
| G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content || Mobile Web, Native Apps
|-
| G95: Providing short text alternatives that provide a brief description of the non-text content || Mobile Web, Native Apps
|-
| G96: Providing textual identification of items that otherwise rely only on sensory information to be understood  || Mobile Web, Native Apps
|-
| G97: Providing the first use of an abbreviation immediately before or after following the expanded form|| Mobile Web, Native Apps
|- 
| G98: Providing the ability for the user to review and correct answers before submitting || Mobile Web, Native Apps
|-
| G99: Providing the ability to recover deleted information || Mobile Web, Native Apps
|-
| G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content || Mobile Web, Native Apps
|-
| G101: Providing the definition of a word or phrase used in an unusual or restricted way|| Mobile Web, Native Apps
|- 
| G102: Providing the expansion or explanation of an abbreviation || Mobile Web, Native Apps
|-
| G103: Providing visual illustrations, pictures, and symbols to help explain ideas, events, and processes || Mobile Web, Native Apps
|-
| G105: Saving data so that it can be used after a user re-authenticates || Mobile Web, Native Apps
|-
| G107: Using "activate" rather than "focus" as a trigger for changes of context || Mobile Web, Native Apps
|-
| G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes || Mobile Web, Native Apps
|-
| G110: Using an instant client-side redirect|| Mobile Web, Native Apps
|- 
| G111: Using color and pattern || Mobile Web, Native Apps
|-
| G112: Using inline definitions || Mobile Web, Native Apps
|-
| G115: Using semantic elements to mark up structure || Mobile Web, Native Apps
|-
| G117: Using text to convey information that is conveyed by variations in presentation of text|| Mobile Web, Native Apps
|- 
| G120: Providing the pronunciation immediately following the word|| Mobile Web, Native Apps
|- 
| G121: Linking to pronunciations || Mobile Web, Native Apps
|-
| G123: Adding a link at the beginning of a block of repeated content to go to the end of the block || Mobile Web
|-
| G124: Adding links at the top of the page to each area of the content || Mobile Web
|-
| G125: Providing links to navigate to related Web pages || Mobile Web
|-
| G126: Providing a list of links to all other Web pages || Mobile Web
|-
| G127: Identifying a Web page's relationship to a larger collection of Web pages || Mobile Web
|-
| G128: Indicating current location within navigation bars || Mobile Web, Native Apps
|-
| G130: Providing descriptive headings || Mobile Web, Native Apps
|-
| G131: Providing descriptive labels || Mobile Web, Native Apps
|-
| G133: Providing a checkbox on the first page of a multipart form that allows users to ask for longer session time limit or no session time limit || Mobile Web, Native Apps
|-
| G134: Validating Web pages || Mobile Web
|-
| G135: Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes || Mobile Web, Native Apps
|-
| G136: Providing a link at the beginning of a nonconforming Web page that points to a conforming alternate version || Mobile Web
|-
| G138: Using semantic markup whenever color cues are used || Mobile Web, Native Apps
|-
| G139: Creating a mechanism that allows users to jump to errors || Mobile Web, Native Apps
|-
| G140: Separating information and structure from presentation to enable different presentations || Mobile Web, Native Apps
|-
| G141: Organizing a page using headings || Mobile Web, Native Apps
|-
| G143: Providing a text alternative that describes the purpose of the CAPTCHA || Mobile Web, Native Apps
|-
| G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality || Mobile Web, Native Apps
|-
| G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text || Mobile Web, Native Apps
|-
| G146: Using liquid layout || Mobile Web, Native Apps
|-
| G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults || Mobile Web, Native Apps
|-
| G149: Using user interface components that are highlighted by the user agent when they receive focus || Mobile Web, Native Apps
|- 
| G150: Providing text based alternatives for live audio-only content || Mobile Web, Native Apps
|-
| G151: Providing a link to a text transcript of a prepared statement or script if the script is followed || Mobile Web 
|-
| G152: Setting animated gif images to stop blinking after n cycles (within 5 seconds) || Mobile Web
|-
| G153: Making the text easier to read || Mobile Web
|-
| G155: Providing a checkbox in addition to a submit button || Mobile Web
|-
| G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text || Mobile Web
|-
| G157: Incorporating a live audio captioning service into a Web page || Mobile Web
|-
| G158: Providing an alternative for time-based media for audio-only content || Mobile Web
|-
| G159: Providing an alternative for time-based media for video-only content || Mobile Web
|-
| G160: Providing sign language versions of information, ideas, and processes that must be understood in order to use the content || Mobile Web
|-
| G161: Providing a search function to help users find content || Mobile Web
|-
| G163: Using standard diacritical marks that can be turned off || Mobile Web
|-
| G164: Providing a stated period of time after submission of the form when the order can within which an online request (or transaction) may be updated, amended or canceled by the user after making the request || Mobile Web
|-
| G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over || Mobile Web
|-
| G166: Providing audio that describes the important video content and describing it as such || Mobile Web
|- 
| G167: Using an adjacent button to label the purpose of a field || Mobile Web
|- 
| G168: Requesting confirmation to continue with selected action || Mobile Web
|-
| G169: Aligning text on only one side || Mobile Web
|-
| G170: Providing a control near the beginning of the Web page that turns off sounds that play automatically || Mobile Web
|-
| G171: Playing sounds only on user request || Mobile Web
|-
| G172: Providing a mechanism to remove full justification of text || Mobile Web
|-
| G173: Providing a version of a movie with audio descriptions || Mobile Web
|-
| G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast || Mobile Web
|-
| G175: Providing a multi color selection tool on the page for foreground and background colors || Mobile Web
|-
| G176: Keeping the flashing area small enough || Mobile Web
|-
| G177: Providing suggested correction text || Mobile Web
|-
| G178: Providing controls on the Web page that allow users to incrementally change the size of all text on the page up to 200 percent || Mobile Web
|-
| G179: Ensuring that there is no loss of content or functionality when the text resizes and text containers do not change their width || Mobile Web
|-
| G180: Providing the user with a means to set the time limit to 10 times the default time limit || Mobile Web
|- 
| G181: Encoding user data as hidden or encrypted data in a re-authorization page || Mobile Web
|-
| G182: Ensuring that additional visual cues are available when text color differences are used to convey information || Mobile Web
|-
| G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them || Mobile Web
|-
| G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input || Mobile Web
|-
| G185: Linking to all of the pages on the site from the home page || Mobile Web
|-
| G186: Using a control in the Web page that stops moving, blinking, or auto-updating content || Mobile Web
|-
| G187: Using a technology to include blinking content that can be turned off via the user agent|| Mobile Web
|-
| G188: Providing a button on the page to increase line spaces and paragraph spaces|| Mobile Web
|- 
| G189: Providing a control near the beginning of the Web page that changes the link text || Mobile Web
|-
| G190: Providing a link adjacent to or associated with a non-conforming object that links to a conforming alternate version || Mobile Web
|-
| G191: Providing a link, button, or other mechanism that reloads the page without any blinking content || Mobile Web
|-
| G192: Fully conforming to specifications || Mobile Web
|-
| G193: Providing help by an assistant in the Web page || Mobile Web
|-
| G194: Providing spell checking and suggestions for text input || Mobile Web
|-
| G195: Using an author-supplied, highly visible focus indicator || Mobile Web
|-
| G196: Using a text alternative on one item within a group of images that describes all items in the group || Mobile Web
|-
| G197: Using labels, names, and text alternatives consistently for content that has the same functionality || Mobile Web
|-
| G198: Providing a way for the user to turn the time limit off || Mobile Web
|-
| G199: Providing success feedback when data is submitted successfully || Mobile Web
|-
| G200: Opening new windows and tabs from a link only when necessary || Mobile Web
|-
| G201: Giving users advanced warning when opening a new window || Mobile Web
|-
|}

==HTML Applicable to Mobile without Changes==
{| class="wikitable"
|-
! Technique !! Applies to 
|-
|H4: Creating a logical tab order through links, form controls, and objects || Mobile Web
|-
|H25: Providing a title using the title element || Mobile Web
|-
|H27: Providing text and non-text alternatives for object || Mobile Web
|-
|H28: Providing definitions for abbreviations by using the abbr and acronym elements || Mobile Web
|-
|H30: Providing link text that describes the purpose of a link for anchor elements || Mobile Web
|-
|H33: Supplementing link text with the title attribute || Mobile Web
|-
|H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline|| Mobile Web
|- 
|H35: Providing text alternatives on applet elements || Mobile Web
|-
|H37: Using alt attributes on img elements || Mobile Web
|-
|H39: Using caption elements to associate data table captions with data tables || Mobile Web
|-
|H40: Using definition lists || Mobile Web
|-
|H42: Using h1-h6 to identify headings || Mobile Web
|-
|H43: Using id and headers attributes to associate data cells with header cells in data tables || Mobile Web
|-
|H44: Using label elements to associate text labels with form controls || Mobile Web
|-
|H45: Using longdesc || Mobile Web
|-
|H46: Using noembed with embed || Mobile Web
|-
|H48: Using ol, ul and dl for lists or groups of links || Mobile Web
|-
|H49: Using semantic markup to mark emphasized or special text || Mobile Web
|-
|H51: Using table markup to present tabular information || Mobile Web
|-
|H53: Using the body of the object element || Mobile Web
|-
|H54: Using the dfn element to identify the defining instance of a word || Mobile Web
|-
|H56: Using the dir attribute on an inline element to resolve problems with nested directional runs || Mobile Web
|-
|H57: Using language attributes on the html element || Mobile Web
|-
|H58: Using language attributes to identify changes in the human language || Mobile Web
|-
|H59: Using the link element and navigation tools || Mobile Web
|-
|H60: Using the link element to link to a glossary || Mobile Web
|-
|H62: Using the ruby element || Mobile Web
|-
|H64: Using the title attribute of the frame and iframe elements || Mobile Web
|-
|H65: Using the title attribute to identify form controls when the label element cannot be used || Mobile Web
|-
|H67: Using null alt text and no title attribute on img elements for images that AT should ignore || Mobile Web
|-
|H69: Providing heading elements at the beginning of each section of content || Mobile Web
|-
|H70: Using frame elements to group blocks of repeated material || Mobile Web
|-
|H71: Providing a description for groups of form controls using fieldset and legend elements || Mobile Web
|-
|H73: Using the summary attribute of the table element to give an overview of data tables || Mobile Web
|-
|H74: Ensuring that opening and closing tags are used according to specification || Mobile Web
|-
|H75: Ensuring that Web pages are well-formed || Mobile Web
|-
|H76: Using meta refresh to create an instant client-side redirect || Mobile Web
|-
|H77: Identifying the purpose of a link using link text combined with its enclosing list item || Mobile Web
|-
|H78: Identifying the purpose of a link using link text combined with its enclosing paragraph || Mobile Web
|-
|H79: Identifying the purpose of a link using link text combined with its enclosing table cell and associated table headings || Mobile Web
|-
|H80: Identifying the purpose of a link using link text combined with the preceding heading element || Mobile Web
|-
|H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested || Mobile Web
|-
|H84: Using a button with a select element to perform an action || Mobile Web
|-
|H85: Using OPTGROUP to group OPTION elements inside a SELECT|| Mobile Web
|-
|H86: Providing text alternatives for ASCII art, emoticons, and leetspeak|| Mobile Web
|-
|H88: Using HTML according to spec || Mobile Web
|-
|H90: Indicating required form controls using label or legend || Mobile Web
|-
|H93: Ensuring that id attributes are unique on a Web page || Mobile Web
|-
|H94: Ensuring that elements do not contain duplicate attributes|| Mobile Web
|-
|}

==CSS Applicable to Mobile without Changes==
{| class="wikitable"
|-
! Technique !! Applies to 
|-
| C6: Positioning content based on structural markup || Mobile Web
|-
|C7: Using CSS to hide a portion of the link text || Mobile Web
|-
|C8: Using CSS letter-spacing to control spacing within a word || Mobile Web
|-
|C9: Using CSS to include decorative images || Mobile Web
|-
|C13: Using named font sizes || Mobile Web
|-
|C14: Using em units for font sizes || Mobile Web
|-
|C17: Scaling form elements which contain text || Mobile Web
|-
|C18: Using CSS margin and padding rules instead of spacer images for layout design || Mobile Web
|-
|C19: Specifying alignment either to the left OR right in CSS || Mobile Web
|-
|C21: Specifying line spacing in CSS|| Mobile Web
|- 
|C22: Using CSS to control visual presentation of text|| Mobile Web
|- 
|C24: Using percentage values in CSS for container sizes || Mobile Web
|-
|C26: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text || Mobile Web
|-
|C27: Making the DOM order match the visual order || Mobile Web
|-
|C28: Specifying the size of text containers using em units || Mobile Web
|-
|C29: Using a style switcher to provide a conforming alternate version || Mobile Web
|-
|C30: Using CSS to replace text with images of text and providing user interface controls to switch|| Mobile Web
|-
|}

==Client Scripting Techniques Applicable to Mobile without Changes==
{| class="wikitable"
|-
! Technique !! Applies to 
|-
| SCR1: Allowing the user to extend the default time limit  || Mobile Web
|- 
|SCR2: Using redundant keyboard and mouse event handlers  || Mobile Web
|-
|SCR14: Using scripts to make nonessential alerts optional   || Mobile Web
|-
|SCR16: Providing a script that warns the user a time limit is about to expire  || Mobile Web
|- 
|SCR18: Providing client-side validation and alert  || Mobile Web
|- 
|SCR19: Using an onchange event on a select element without causing a change of context  || Mobile Web
|- 
|SCR20: Using both keyboard and other device-specific functions  || Mobile Web
|- 
|SCR21: Using functions of the Document Object Model (DOM) to add content to a page  || Mobile Web
|- 
|SCR22: Using scripts to control blinking and stop it in five seconds or less   || Mobile Web
|-
|SCR24: Using progressive enhancement to open new windows on user request  || Mobile Web
|-
|SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element   || Mobile Web
|-
|SCR27: Reordering page sections using the Document Object Model   || Mobile Web
|-
|SCR28: Using an expandable and collapsible menu to bypass block of content   || Mobile Web
|-
|SCR29: Adding keyboard-accessible actions to static HTML elements  || Mobile Web
|- 
|SCR32: Providing client-side validation and adding error text via the DOM   || Mobile Web
|-
|SCR33: Using script to scroll content, and providing a mechanism to pause it  || Mobile Web
|- 
|SCR36: Providing a mechanism to allow users to display moving, scrolling, or auto-updating text in a static window or area || Mobile Web
|}

==Failure Techniques Applicable to Mobile without Changes==
{| class="wikitable"
|-
! Technique !! Applies to 
|-
|F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS 
|| Mobile Web
|- 
|F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text 
|| Mobile Web
|- 
|F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information 
|| Mobile Web
|- 
|F4: Failure of Success Criterion 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than five seconds 
|| Mobile Web
|- 
|F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialogue or important sound effects 
|| Mobile Web
|- 
|F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element 
|| Mobile Web
|- 
|F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism for saving user's input and re-establishing that information upon re-authentication 
|| Mobile Web
|- 
|F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image 
|| Mobile Web
|- 
|F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location  
|| Mobile Web
|- 
|F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely 
|| Mobile Web
|- 
|F16: Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content  
|| Mobile Web
|- 
|F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML 
|| Mobile Web
|- 
|F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur 
|| Mobile Web
|- 
|F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user 
|| Mobile Web
|- 
|F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off 
|| Mobile Web
|- 
|F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa 
|| Mobile Web
|- 
|F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents 
|| Mobile Web
|- 
|F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information 
|| Mobile Web
|- 
|F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text) 
|| Mobile Web
|- 
|F31: Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages 
|| Mobile Web
|- 
|F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word) 
|| Mobile Web
|- 
|F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content 
|| Mobile Web
|- 
|F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content 
|| Mobile Web
|- 
|F36: Failure of Success Criterion 3.2.2 due to automatically submitting a form and presenting new content without prior warning when the last field in the form is given a value 
|| Mobile Web
|- 
|F37: Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the status of a radio button, check box or select list is changed 
|| Mobile Web
|- 
|F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-text content used for decorative purposes only in HTML 
|| Mobile Web
|- 
|F39: Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology 
|| Mobile Web
|- 
|F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit 
|| Mobile Web
|- 
|F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out 
|| Mobile Web
|- 
|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 
|| Mobile Web
|- 
|F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content 
|| Mobile Web
|- 
|F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability 
|| Mobile Web
|- 
|F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables 
|| Mobile Web
|- 
|F47: Failure of Success Criterion 2.2.2 due to using the blink element 
|| Mobile Web
|- 
|F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information 
|| Mobile Web
|- 
|F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized 
|| Mobile Web
|- 
|F50: Failure of Success Criterion 2.2.2 due to a script that causes a blink effect without a mechanism to stop the blinking at 5 seconds or less 
|| Mobile Web
|- 
|F52: Failure of Success Criterion 3.2.1 and 3.2.5 due to opening a new window as soon as a new page is loaded  
|| Mobile Web
|- 
|F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out 
|| Mobile Web
|- 
|F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML 
|| Mobile Web
|- 
|F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field 
|| Mobile Web
|- 
|F61: Failure of Success Criterion 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content 
|| Mobile Web
|- 
|F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML 
|| Mobile Web
|- 
|F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link 
|| Mobile Web
|- 
|F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type "image" 
|| Mobile Web
|- 
|F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages 
|| Mobile Web
|- 
|F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information 
|| Mobile Web
|- 
|F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable 
|| Mobile Web
|- 
|F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup 
|| Mobile Web
|- 
|F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative 
|| Mobile Web
|- 
|F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative 
|| Mobile Web
|- 
|F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision 
|| Mobile Web
|- 
|F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative 
|| Mobile Web
|- 
|F75: Failure of Success Criterion 1.2.2 by providing synchronized media without captions when the synchronized media presents more information than is presented on the page 
|| Mobile Web
|- 
|F76: Failure of Success Criterion 3.2.2 due to providing instruction material about the change of context by change of setting in a user interface element at a location that users may bypass 
|| Mobile Web
|- 
|F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID 
|| Mobile Web
|- 
|F78: Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator 
|| Mobile Web
|- 
|F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available 
|| Mobile Web
|- 
|F80: Failure of Success Criterion 1.4.4 when text-based form controls do not resize when visually rendered text is resized up to 200% 
|| Mobile Web
|- 
|F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only 
|| Mobile Web
|- 
|F82: Failure of Success Criterion 3.3.2 by visually formatting a s et of phone number fields but not including a text label 
|| Mobile Web
|- 
|F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text) 
|| Mobile Web
|- 
|F84: Failure of Success Criterion 2.4.9 due to using a non-specific link such as "click here" or "more" without a mechanism to change the link text to specific text. 
|| Mobile Web
|- 
|F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order 
|| Mobile Web
|- 
|F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number 
|| Mobile Web
|- 
|F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS 
|| Mobile Web
|- 
|F88: Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins) 
|| Mobile Web
|- 
|F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link 
|| Mobile Web
|- 
|F90: Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes 
|| Mobile Web
|- 
|F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers
|| Mobile Web
|}