Edit comment LC-2851 for Accessibility Guidelines Working Group

Quick access to LC-2844 LC-2846 LC-2847 LC-2848 LC-2849 LC-2850 LC-2851 LC-2853 LC-2854 LC-2856 LC-2857 LC-2858 LC-2859 LC-2860 LC-2863 LC-2865 LC-2866 LC-2867 LC-2869 LC-2870 LC-2871

Comment LC-2851

Comment Shortname:

Commenter: Laura Carlson <laura.lee.carlson@gmail.com>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeIntroduction to Techniques for WCAG 2.0 G1: Adding a link at the top of each page that goes directly to the main c... G4: Allowing the content to be paused and restarted from where it was paused G5: Allowing users to complete an activity without any time limit G8: Providing a movie with extended audio descriptions G9: Creating captions for live synchronized media G10: Creating components using a technology that supports the accessibilit... G11: Creating content that blinks for less than 5 seconds G13: Describing what will happen before a change to a form control that ca... G14: Ensuring that information conveyed by color differences is also avail... G15: Using a tool to ensure that content does not violate the general flas... G17: Ensuring that a contrast ratio of at least 7:1 exists between text (a... G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text ... G19: Ensuring that no component of the content flashes more than three tim... G21: Ensuring that users are not trapped in content G53: Identifying the purpose of a link using link text combined with the t... G54: Including a sign language interpreter in the video stream G55: Linking to definitions G56: Mixing audio files so that non-speech sounds are at least 20 decibels... G57: Ordering the content in a meaningful sequence G58: Placing a link to the alternative for time-based media immediately ne... G59: Placing the interactive elements in an order that follows sequences a... G60: Playing a sound that turns off automatically within three seconds G61: Presenting repeated components in the same relative order each time t... G62: Providing a glossary G63: Providing a site map G64: Providing a Table of Contents G65: Providing a breadcrumb trail G68: Providing a descriptive labelshort text alternative that describes th... G69: Providing an alternative for time based media G70: Providing a function to search an online dictionary G71: Providing a help link on every Web page G73: Providing a long description in another location with a link to it th... G74: Providing a long description in text near the non-text content, with ... G75: Providing a mechanism to postpone any updating of content G76: Providing a mechanism to request an update of the content instead of ... G78: Providing a second, user-selectable, audio track that includes audio ... G79: Providing a spoken version of the text G80: Providing a submit button to initiate a change of context G81: Providing a synchronized video of the sign language interpreter that ... G82: Providing a text alternative that identifies the purpose of the non-t... G83: Providing text descriptions to identify required fields that were not... G84: Providing a text description when the user provides information that ... G85: Providing a text description when user input falls outside the requir... G86: Providing a text summary that requires reading ability less advanced ... G87: Providing closed captions G88: Providing descriptive titles for Web pages G89: Providing expected data format and example G90: Providing keyboard-triggered event handlers G91: Providing link text that describes the purpose of a link G92: Providing long description for non-text content that serves the same ... G93: Providing open (always visible) captions G94: Providing short text alternative for non-text content that serves the... G95: Providing short text alternatives that provide a brief description of... G96: Providing textual identification of items that otherwise rely only on... G97: Providing the first use of an abbreviation immediately before or afte... G98: Providing the ability for the user to review and correct answers befo... G99: Providing the ability to recover deleted information G100: Providing a short text alternative which is the accepted name or a d... G101: Providing the definition of a word or phrase used in an unusual or r... G102: Providing the expansion or explanation of an abbreviation G103: Providing visual illustrations, pictures, and symbols to help explai... G105: Saving data so that it can be used after a user re-authenticates G107: Using "activate" rather than "focus" as a trigger for changes of context G108: Using markup features to expose the name and role, allow user-settab... G110: Using an instant client-side redirect G111: Using color and pattern G112: Using inline definitions G115: Using semantic elements to mark up structure G117: Using text to convey information that is conveyed by variations in p... G120: Providing the pronunciation immediately following the word G121: Linking to pronunciations G123: Adding a link at the beginning of a block of repeated content to go ... G124: Adding links at the top of the page to each area of the content G125: Providing links to navigate to related Web pages G126: Providing a list of links to all other Web pages G127: Identifying a Web page's relationship to a larger collection of Web pages G128: Indicating current location within navigation bars G130: Providing descriptive headings G131: Providing descriptive labels G133: Providing a checkbox on the first page of a multipart form that allo... G134: Validating Web pages G135: Using the accessibility API features of a technology to expose names... G136: Providing a link at the beginning of a nonconforming Web page that p... G138: Using semantic markup whenever color cues are used G139: Creating a mechanism that allows users to jump to errors G140: Separating information and structure from presentation to enable dif... G141: Organizing a page using headings G142: Using a technology that has commonly-available user agents that supp... G143: Providing a text alternative that describes the purpose of the CAPTCHA G144: Ensuring that the Web Page contains another CAPTCHA serving the same... G145: Ensuring that a contrast ratio of at least 3:1 exists between text (... G146: Using liquid layout G148: Not specifying background color, not specifying text color, and not ... G149: Using user interface components that are highlighted by the user age... G150: Providing text based alternatives for live audio-only content G151: Providing a link to a text transcript of a prepared statement or scr... G152: Setting animated gif images to stop blinking after n cycles (within ... G153: Making the text easier to read G155: Providing a checkbox in addition to a submit button G156: Using a technology that has commonly-available user agents that can ... G157: Incorporating a live audio captioning service into a Web page G158: Providing an alternative for time-based media for audio-only content G159: Providing an alternative for time-based media for video-only content G160: Providing sign language versions of information, ideas, and processe... G161: Providing a search function to help users find content G162: Positioning labels to maximize predictability of relationships G163: Using standard diacritical marks that can be turned off G164: Providing a stated period oftime after submission of the form when t... G165: Using the default focus indicator for the platform so that high visi... G166: Providing audio that describes the important video content and descr... G167: Using an adjacent button to label the purpose of a field G168: Requesting confirmation to continue with selected action G169: Aligning text on only one side G170: Providing a control near the beginning of the Web page that turns of... G171: Playing sounds only on user request G172: Providing a mechanism to remove full justification of text G173: Providing a version of a movie with audio descriptions G174: Providing a control with a sufficient contrast ratio that allows use... G175: Providing a multi color selection tool on the page for foreground an... G176: Keeping the flashing area small enough G177: Providing suggested correction text G178: Providing controls on the Web page that allow users to incrementally... G179: Ensuring that there is no loss of content or functionality when the ... G180: Providing the user with a means to set the time limit to 10 times th... G181: Encoding user data as hidden or encrypted data in a re-authorization page G182: Ensuring that additional visual cues are available when text color d... G183: Using a contrast ratio of 3:1 with surrounding text and providing ad... G184: Providing text instructions at the beginning of a form or set of fie... G185: Linking to all of the pages on the site from the home page G186: Using a control in the Web page that stops moving, blinking, or auto... G187: Using a technology to include blinking content that can be turned of... G188: Providing a button on the page to increase line spaces and paragraph... G189: Providing a control near the beginning of the Web page that changes ... G190: Providing a link adjacent to or associated with a non-conforming obj... G191: Providing a link, button, or other mechanism that reloads the page w... G192: Fully conforming to specifications G193: Providing help by an assistant in the Web page G194: Providing spell checking and suggestions for text input G195: Using an author-supplied, highly visible focus indicator G196: Using a text alternative on one item within a group of images that d... G197: Using labels, names, and text alternatives consistently for content ... G198: Providing a way for the user to turn the time limit off G199: Providing success feedback when data is submitted successfully G200: Opening new windows and tabs from a link only when necessary G201: Giving users advanced warning when opening a new window G202: Ensuring keyboard control for all functionality G203: Using a static text alternative to describe a talking head video H2: Combining adjacent image and text links for the same resource H4: Creating a logical tab order through links, form controls, and objects H24: Providing text alternatives for the area elements of image maps H25: Providing a title using the title element H27: Providing text and non-text alternatives for object H28: Providing definitions for abbreviations by using the abbr and acronym... H30: Providing link text that describes the purpose of a link for anchor e... H32: Providing submit buttons H33: Supplementing link text with the title attribute H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) ... H35: Providing text alternatives on applet elements H36: Using alt attributes on images used as submit buttons H37: Using alt attributes on img elements H39: Using caption elements to associate data table captions with data tables H40: Using definition lists H42: Using h1-h6 to identify headings H43: Using id and headers attributes to associate data cells with header c... H44: Using label elements to associate text labels with form controls H45: Using longdesc H46: Using noembed with embed H48: Using ol, ul and dl for lists or groups of links H49: Using semantic markup to mark emphasized or special text H51: Using table markup to present tabular information H53: Using the body of the object element H54: Using the dfn element to identify the defining instance of a word H56: Using the dir attribute on an inline element to resolve problems with... H57: Using language attributes on the html element H58: Using language attributes to identify changes in the human language H59: Using the link element and navigation tools H60: Using the link element to link to a glossary H62: Using the ruby element H63: Using the scope attribute to associate header cells and data cells in... H64: Using the title attribute of the frame and iframe elements H65: Using the title attribute to identify form controls when the label el... H67: Using null alt text and no title attribute on img elements for images... H69: Providing heading elements at the beginning of each section of content H70: Using frame elements to group blocks of repeated material H71: Providing a description for groups of form controls using fieldset an... H73: Using the summary attribute of the table element to give an overview ... H74: Ensuring that opening and closing tags are used according to specification H75: Ensuring that Web pages are well-formed H76: Using meta refresh to create an instant client-side redirect H77: Identifying the purpose of a link using link text combined with its e... H78: Identifying the purpose of a link using link text combined with its e... H79: Identifying the purpose of a link using link text combined with its e... H80: Identifying the purpose of a link using link text combined with the p... H81: Identifying the purpose of a link in a nested list using link text co... H83: Using the target attribute to open a new window on user request and i... H84: Using a button with a select element to perform an action H85: Using OPTGROUP to group OPTION elements inside a SELECT H86: Providing text alternatives for ASCII art, emoticons, and leetspeak H87: Not interfering with the user agent's reflow of text as the viewing w... H88: Using HTML according to spec H89: Using the title attribute to provide context-sensitive help H90: Indicating required form controls using label or legend H91: Using HTML form controls and links H92: Including a text cue for colored form control labels H93: Ensuring that id attributes are unique on a Web page H94: Ensuring that elements do not contain duplicate attributes C6: Positioning content based on structural markup C7: Using CSS to hide a portion of the link text C8: Using CSS letter-spacing to control spacing within a word C9: Using CSS to include decorative images C12: Using percent for font sizes C13: Using named font sizes C14: Using em units for font sizes C15: Using CSS to change the presentation of a user interface component wh... C17: Scaling form elements which contain text C18: Using CSS margin and padding rules instead of spacer images for layou... C19: Specifying alignment either to the left OR right in CSS C20: Using relative measurements to set column widths so that lines can av... C21: Specifying line spacing in CSS C22: Using CSS to control visual presentation of text C23: Specifying text and background colors of secondary content such as ba... C24: Using percentage values in CSS for container sizes C25: Specifying borders and layout in CSS to delineate areas of a Web page... C26: Providing options within the content to switch to a layout that does ... C27: Making the DOM order match the visual order C28: Specifying the size of text containers using em units C29: Using a style switcher to provide a conforming alternate version C30: Using CSS to replace text with images of text and providing user inte... SCR1: Allowing the user to extend the default time limit SCR2: Using redundant keyboard and mouse event handlers SCR14: Using scripts to make nonessential alerts optional SCR16: Providing a script that warns the user a time limit is about to expire SCR18: Providing client-side validation and alert SCR19: Using an onchange event on a select element without causing a chang... SCR20: Using both keyboard and other device-specific functions SCR21: Using functions of the Document Object Model (DOM) to add content t... SCR22: Using scripts to control blinking and stop it in five seconds or less SCR24: Using progressive enhancement to open new windows on user request SCR26: Inserting dynamic content into the Document Object Model immediatel... SCR27: Reordering page sections using the Document Object Model SCR28: Using an expandable and collapsible menu to bypass block of content SCR29: Adding keyboard-accessible actions to static HTML elements SCR30: Using scripts to change the link text SCR31: Using script to change the background color or border of the elemen... SCR32: Providing client-side validation and adding error text via the DOM SCR33: Using script to scroll content, and providing a mechanism to pause it SCR34: Calculating size and position in a way that scales with text size SCR35: Making actions keyboard accessible by using the onclick event of an... SCR36: Providing a mechanism to allow users to display moving, scrolling, ... SCR37: Creating Custom Dialogs in a Device Independent Way SVR1: Implementing automatic redirects on the server side instead of on th... SVR2: Using .htaccess to ensure that the only way to access non-conforming... SVR3: Using HTTP referer to ensure that the only way to access non-conform... SVR4: Allowing users to provide preferences for the display of conforming ... SVR5: Specifying the default language in the HTTP header SM1: Adding extended audio description in SMIL 1.0 SM2: Adding extended audio description in SMIL 2.0 SM6: Providing audio description in SMIL 1.0 SM7: Providing audio description in SMIL 2.0 SM11: Providing captions through synchronized text streams in SMIL 1.0 SM12: Providing captions through synchronized text streams in SMIL 2.0 SM13: Providing sign language interpretation through synchronized video st... SM14: Providing sign language interpretation through synchronized video st... T1: Using standard text formatting conventions for paragraphs T2: Using standard text formatting conventions for lists T3: Using standard text formatting conventions for headings WAI-ARIA Technology Notes ARIA1: Using the aria-describedby property to provide a descriptive label ... ARIA2: Identifying required fields with the aria-required property ARIA3: Identifying valid range information with the aria-valuemin and aria... Flash Technology Notes FLASH1: Setting the name property for a non-text object FLASH2: Setting the description property for a non-text object in Flash FLASH3: Marking objects in Flash so that they can be ignored by AT FLASH4: Providing submit buttons in Flash FLASH5: Combining adjacent image and text buttons for the same resource FLASH6: Creating accessible hotspots using invisible buttons FLASH7: Using scripting to change control labels FLASH8: Adding a group name to the accessible name of a form control FLASH9: Applying captions to prerecorded synchronized media FLASH10: Indicating required form controls in Flash FLASH11: Providing a longer text description of an object FLASH12: Providing client-side validation and adding error text via the ac... FLASH13: Using HTML language attributes to specify language in Flash content FLASH14: Using redundant keyboard and mouse event handlers in Flash FLASH15: Using the tabIndex property to specify a logical reading order an... FLASH16: Making actions keyboard accessible by using the click event on st... FLASH17: Providing keyboard access to a Flash object and avoiding a keyboa... FLASH18: Providing a control to turn off sounds that play automatically in Flash FLASH19: Providing a script that warns the user a time limit is about to e... FLASH20: Reskinning Flash components to provide highly visible focus indication FLASH21: Using the DataGrid component to associate column headers with cells FLASH22: Adding keyboard-accessible actions to static elements FLASH23: Adding summary information to a DataGrid FLASH24: Allowing the user to extend the default time limit FLASH25: Labeling a form control by setting its accessible name FLASH26: Applying audio descriptions to Flash video FLASH27: Providing button labels that describe the purpose of a button FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspe... FLASH29: Setting the label property for form components FLASH30: Specifying accessible names for image buttons FLASH31: Specifying caption text for a DataGrid FLASH32: Using auto labeling to associate text labels with form controls FLASH33: Using relative values for Flash object dimensions FLASH34: Turning off sounds that play automatically when an assistive tech... FLASH35: Using script to scroll Flash content, and providing a mechanism t... FLASH36: Using scripts to control blinking and stop it in five seconds or less Silverlight Technology Notes SL1: Accessing Alternate Audio Tracks in Silverlight Media SL2: Changing The Visual Focus Indicator in Silverlight SL3: Controlling Silverlight MediaElement Audio Volume SL4: Declaring Discrete Silverlight Objects to Specify Language Parts in t... SL5: Defining a Focusable Image Class for Silverlight SL6: Defining a UI Automation Peer for a Custom Silverlight Control SL7: Designing a Focused Visual State for Custom Silverlight Controls SL8: Displaying HelpText in Silverlight User Interfaces SL9: Handling Key Events to Enable Keyboard Functionality in Silverlight SL10: Implementing a Submit-Form Pattern in Silverlight SL11: Pausing or Stopping A Decorative Silverlight Animation SL12: Pausing, Stopping, or Playing Media in Silverlight MediaElements SL13: Providing A Style Switcher To Switch To High Contrast SL14: Providing Custom Control Key Handling for Keyboard Functionality in ... SL15: Providing Keyboard Shortcuts that Work Across the Entire Silverlight... SL16: Providing Script-Embedded Text Captions for MediaElement Content SL17: Providing Static Alternative Content for Silverlight Media Playing i... SL18: Providing Text Equivalent for Nontext Silverlight Controls With Auto... SL19: Providing User Instructions With AutomationProperties.HelpText in Si... SL20: Relying on Silverlight AutomationPeer Behavior to Set AutomationProp... SL21: Replacing A Silverlight Timed Animation With a Nonanimated Element SL22: Supporting Browser Zoom in Silverlight SL23: Using A Style Switcher to Increase Font Size of Silverlight Text Elements SL24: Using AutoPlay to Keep Silverlight Media from Playing Automatically SL25: Using Controls and Programmatic Focus to Bypass Blocks of Content in... SL26: Using LabeledBy to Associate Labels and Targets in Silverlight SL27: Using Language/Culture Properties as Exposed by Silverlight Applicat... SL28: Using Separate Text-Format Text Captions for MediaElement Content SL29: Using Silverlight "List" Controls to Define Blocks that can be Bypassed SL30: Using Silverlight Control Compositing and AutomationProperties.Name SL31: Using Silverlight Font Properties to Control Text Presentation SL32: Using Silverlight Text Elements for Appropriate Accessibility Role SL33: Using Well-Formed XAML to Define a Silverlight User Interface SL34: Using the Silverlight Default Tab Sequence and Altering Tab Sequence... SL35: Using the Validation and ValidationSummary APIs to Implement Client ... PDF Technology Notes PDF1: Applying text alternatives to images with the Alt entry in PDF documents PDF2: Creating bookmarks in PDF documents PDF3: Ensuring correct tab and reading order in PDF documents PDF4: Hiding decorative images with the Artifact tag in PDF documents PDF5: Indicating required form controls in PDF forms PDF6: Using table elements for table markup in PDF Documents PDF7: Performing OCR on a scanned PDF document to provide actual text PDF8: Providing definitions for abbreviations via an E entry for a structu... PDF9: Providing headings by marking content with heading tags in PDF documents PDF10: Providing labels for interactive form controls in PDF documents PDF11: Providing links and link text using the Link annotation and the /Li... PDF12: Providing name, role, value information for form fields in PDF documents PDF13: Providing replacement text using the /Alt entry for links in PDF do... PDF14: Providing running headers and footers in PDF documents PDF15: Providing submit buttons with the submit-form action in PDF forms PDF16: Setting the default language using the /Lang entry in the document ... PDF17: Specifying consistent page numbering for PDF documents PDF18: Specifying the document title using the Title entry in the document... PDF19: Specifying the language for a passage or phrase with the Lang entry... PDF20: Using Adobe Acrobat Pro's Table Editor to repair mistagged tables PDF21: Using List tags for lists in PDF documents PDF22: Indicating when user input falls outside the required format or val... PDF23: Providing interactive form controls in PDF documents F1: Failure of Success Criterion 1.3.2 due to changing the meaning of cont... F2: Failure of Success Criterion 1.3.1 due to using changes in text presen... F3: Failure of Success Criterion 1.1.1 due to using CSS to include images ... F4: Failure of Success Criterion 2.2.2 due to using text-decoration:blink ... F7: Failure of Success Criterion 2.2.2 due to an object or applet, such as... F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialo... F9: Failure of Success Criterion 3.2.5 due to changing the context when th... F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due ... F12: Failure of Success Criterion 2.2.5 due to having a session time limit... F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alt... F14: Failure of Success Criterion 1.3.3 due to identifying content only by... F15: Failure of Success Criterion 4.1.2 due to implementing custom control... F16: Failure of Success Criterion 2.2.2 due to including scrolling content... F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient info... F19: Failure of Conformance Requirement 1 due to not providing a method fo... F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text... F22: Failure of Success Criterion 3.2.5 due to opening windows that are no... F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where t... F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying... F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not... F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol al... F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text altern... F31: Failure of Success Criterion 3.2.4 due to using two different labels ... F32: Failure of Success Criterion 1.3.2 due to using white space character... F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space... F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space... F36: Failure of Success Criterion 3.2.2 due to automatically submitting a ... F37: Failure of Success Criterion 3.2.2 due to launching a new window with... F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute ... F39: Failure of Success Criterion 1.1.1 due to providing a text alternativ... F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redire... F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using met... F42: Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting e... F43: Failure of Success Criterion 1.3.1 due to using structural markup in ... F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a ... F46: Failure of Success Criterion 1.3.1 due to using th elements, caption ... F47: Failure of Success Criterion 2.2.2 due to using the blink element F48: Failure of Success Criterion 1.3.1 due to using the pre element to ma... F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table ... F50: Failure of Success Criterion 2.2.2 due to a script that causes a blin... F52: Failure of Success Criterion 3.2.1 and 3.2.5 due to opening a new win... F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-... F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using scri... F58: Failure of Success Criterion 2.2.1 due to using server-side technique... F59: Failure of Success Criterion 4.1.2 due to using script to make div or... F60: Failure of Success Criterion 3.2.5 due to launching a new window when... F61: Failure of Success Criterion 3.2.5 due to complete change of main con... F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient info... F63: Failure of Success Criterion 2.4.4 due to providing link context only... F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute ... F66: Failure of Success Criterion 3.2.3 due to presenting navigation links... F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long de... F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association o... F69: Failure of Success Criterion 1.4.4 when resizing visually rendered te... F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and ... F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to r... F72: Failure of Success Criterion 1.1.1 due to using ASCII art without pro... F73: Failure of Success Criterion 1.4.1 due to creating links that are not... F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a sy... F75: Failure of Success Criterion 1.2.2 by providing synchronized media wi... F76: Failure of Success Criterion 3.2.2 due to providing instruction mater... F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID F78: Failure of Success Criterion 2.4.7 due to styling element outlines an... F79: Failure of Success Criterion 4.1.2 due to the focus state of a user i... F80: Failure of Success Criterion 1.4.4 when text-based form controls do n... F81: Failure of Success Criterion 1.4.1 due to identifying required or err... F82: Failure of Success Criterion 3.3.2 by visually formatting a set of ph... F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background ... F84: Failure of Success Criterion 2.4.9 due to using a non-specific link s... F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that... F86: Failure of Success Criterion 4.1.2 due to not providing names for eac... F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative co... F88: Failure of Success Criterion 1.4.8 due to using text that is justifie... F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null ... F90: Failure of Success Criterion 1.3.1 for incorrectly associating table ... F91: Failure of Success Criterion 1.3.1 for not correctly marking up table...
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody Abma, Jake Abou-Zahra, Shadi Allan, Jim Auclair, Christopher Avila, Jonathan Babinszki, Tom Bailey, Bruce Bernard, Renaldo Bernier, Alex Blake, Matthew Boudreau, Denis Brewer, Judy Butler, Shari Campbell, Alastair Carlson, Laura Chakravarthula, Srinivasu Cirrincione, Pietro Conway, Vivienne Cooper, Michael Crutchfield, Elizabeth Deltour, Romain Dick, Wayne Ding, Chaohai Dirks, Kim Dixit, Shwetank Draffan, E.A. Duggin, Alistair Eggert, Eric Elledge, Michael Faulkner, Steve Ferraz, Reinaldo Fiers, Wilco Fischer, Detlev Foliot, John Garrish, Matt Garrison, Alistair Gower, Michael Guarino Reid, Loretta Hakkinen, Markku Haritos-Shea, Katie Henry, Shawn Hoffmann, Thomas Horton, Sarah Isager, Kasper Jensen, Tobias Christian Johansson, Stefan Johlic, Marc Johnson, Rick Jones, Crystal Joys Andersen, Wilhelm Kapoor, Shilpi Keim, Oliver Kirkpatrick, Andrew Kirkwood, John Kiss, Jason Kraft, Maureen Ku, JaEun Kurapati, Sujasree Lauke, Patrick Lauriat, Shawn Lee, Steve Lemon, Gez Li, Alex Li, Kepeng Li, Liangcheng Loiselle, Chris Lowney, Greg Lui, Edwina Lund, Adam Ma, Jia MacDonald, David Mace, Amanda Manser, Erich Martin, Debra McCormack, Scott McMeeking, Chris McSorley, Jan Milliken, Neil Montgomery, Rachael Mueller, Mary Jo nicole, windmann Niemann, Gundula Nurthen, James O Connor, Joshue Oh, Jeong-Hun Panchang, Sailesh Pandhi, Charu Pasi, Aparna Patch, Kimberly Philipp, Melanie Pluke, Mike Pouncey, Ian Repsher, Stephen Rochford, John Runyan, Marla Savva, Andreas Sawczyn, Steve Schnabel, Stefan Seeman-Kestenbaum, Lisa Sims, Glenda Singh, Avneesh Skotkjerra, Stein Erik Sloan, David Smith, Alan Smith, Jim Solomon, Adam Spellman, Jeanne F Strobbe, Christophe Suprock, Greg Swallow, David Thompson, Kenneth Thyme, Anne Ueki, Makoto Vaishnav, Jatin Vanderheiden, Gregg Venkata, Manoj Wahlbin, Kathleen Wang, Can WANG, WEI White, Jason Zelmanowicz, Erica Zerner, Adam Zhang, Mengni

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

Thank you very much for agreeing to provide on-page longdesc syntax in order to help people understand how it works and what limitations exist. I agree with the direction you are taking but suggest helping authors to overcome any limitations by incorporating a end-point solution into H45's verbiage and example as well as pointing out the advantages of using a separate resource by changing:


H45: http://www.w3.org/TR/WCAG-TECHS/H45.html

Authors can provide a description for an image by including text in a separate resource or within the text of the page containing the image.
<ins>An advantage of using a separate resource for the description is that it is easily reusable for multiple instances of the same image, it does not add on-page visual clutter to the original document, and the description's end-point is self evident.</ins> An advantage of providing the description within the same page as the image is that all users can access the description. A limitation of <del>this</del><ins>the on-page</del> method, as well as in providing multiple descriptions on a single separate page, is that current implementations supporting longdesc <del>read all text on the page that follows the start of the long description</del><ins>do not identify the long description's end-point</ins>. <del>As a result, an end user may hear the long description and all content on the page following it, without knowing where the long description is intended to end unless authors provide text to help users identify the end-point of the description.</del><ins>Authors can solve this by providing a well-formed description, which identifies the where the description ends.</ins>

[On-page Example]
(suggested change is in addition of H3 and P inside the div#desc)

<img longdesc="thispage.html#desc"
alt="Line graph of the number of subscribers"
src="http://www.company/images/graph.png">
<div id="desc">
<h3>Long Description: Line graph of the number of subscribers</h3>
<!-- Full Description of Graph -->
<p>Long description ends.</p>
<div>


Laura also suggests various resources for inclusion, below:

Related Resources:

Description Available in a Separate Document Provides Efficiency http://www.d.umn.edu/~lcarlson/research/constriants/separate-doc.html

Forced Visual Encumbrance Adds Visual Clutter http://www.d.umn.edu/~lcarlson/research/constriants/visual-encumbrance.html

In addition WCAG WG may want to consider demonstrating to authors how to provide an actual long description by replacing the comment: <!-- Full Description of Graph --> with markup.

For example:
http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/examples/pages/graph2.html#desc

More longdesc Examples:

http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/examples/long.html

http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/104ex1_fixed.html#browsers_stats

http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/104ex1_fixed.html#painting

Related issues: (space separated ids)

WG Notes: @@ changes to description paragraph 2 @@ change to example code @@ changes to resources

Resolution: Thank you for your comment. We will implement the suggested changes to the second paragraph of the description for H45 (http://www.w3.org/TR/WCAG-TECHS/H45.html). We will also implement the suggested change to the example and add links to relevant resources. @@Authors can provide a description for an image by including text in a separate resource or within the text of the page containing the image. <ins>An advantage of using a separate resource for the description is that it is easily reusable for multiple instances of the same image, it does not add on-page visual clutter to the original document, and the description's end-point is apparent to the user.</ins> An advantage of providing the description within the same page as the image is that all users can access the description. A limitation of <del>this</del><ins>the on-page</del> method, as well as in providing multiple descriptions on a single separate page, is that current implementations supporting longdesc <del>read all text on the page that follows the start of the long description</del><ins>do not identify the long description's end-point</ins>. <del>As a result, an end user may hear the long description and all content on the page following it, without knowing where the long description is intended to end unless authors provide text to help users identify the end-point of the description.</del><ins>Authors can solve this by providing a well-formed description, which identifies the where the description ends.</ins> [On-page Example] (suggested change is in addition of H3 and P inside the div#desc) <img longdesc="thispage.html#desc" alt="Line graph of the number of subscribers" src="http://www.company/images/graph.png"> <div id="desc"> <h3>Long Description: Line graph of the number of subscribers</h3> <!-- Full Description of Graph --> <p>Long description ends.</p> <div> Resources Add listing of tools with support for Longdesc: http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/longdesc_tools.html

(Please make sure the resolution is adapted for public consumption)