This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

List of redirects

Jump to: navigation, search

Showing below up to 50 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

  1. 1.4.2 →‎ 1.4.2 Audio Control
  2. 3.2.4 alternate →‎ 3.2.4 Consistent Identification
  3. ARIA-edit: F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML →‎ ARIA-edit: 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
  4. ARIA-edit: 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 →‎ ARIA-edit: 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 determined
  5. ARIA1: Using the aria-describedby property to provide a descriptive label for input controls →‎ ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls
  6. ARIA2: Identifying required fields with the aria-required property →‎ ARIA2: Identifying a required field with the aria-required property
  7. AccessiblePrices →‎ Failure of Success Criterion 1.3.1 due to marking up prices in a way which results in incorrect information
  8. Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text alternatives for img elements, area elements, and input elements of type image →‎ Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type image
  9. Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text equivalents for img elements, area elements, and input elements of type image →‎ Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text alternatives for img elements, area elements, and input elements of type image
  10. Aria-Edit: 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 →‎ Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text equivalents for img elements, area elements, and input elements of type image
  11. CSS providing sufficient contrast for placeholder text →‎ Providing sufficient contrast for forms
  12. Creating Logical Tab Order With Tabindex →‎ Creating Logical Tab Order with the Tabindex Attribute
  13. Creating a conforming alternate version for a responsive web page designed with progressive enhancement →‎ Creating a conforming alternate version for a web page designed with progressive enhancement
  14. Creating a conforming alternate version for web pages which are designed to be responsive / progressively enhanced →‎ Creating a conforming alternate version for a web page designed with progressive enhancement
  15. David review of html4 to html5 →‎ Review of html4 to html5
  16. F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows Assistive technology to ignore them →‎ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows Assistive technology to ignore them
  17. F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows assitive technology to ignore them →‎ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows Assistive technology to ignore them
  18. F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-presentation images and applets used only for decorative purposes in HTML →‎ F38: Failure of Success Criterion 1.1.1 to markup decorative images and applets to be ignored by assistive technology
  19. 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 →‎ F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-presentation images and applets used only for decorative purposes in HTML
  20. F38: Failure of Success Criterion 1.1.1 to markup decorative images and applets to be ignored by assistive technology →‎ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows assitive technology to ignore them
  21. Failure of Success Criterion 1.3.1 due to marking up prices in a way which results in incorrect information →‎ Failure of Success Criterion 1.3.1 due to marking up prices a where the decimal is not shown but the visual presentation indicates the need for a decimal
  22. Failure of Success Criterion 1.3.1 due to the use of role=presentation on content which conveys semantic information →‎ Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information
  23. H69Edit →‎ Edits to Add 2.4.10 to H69
  24. HTML5 Technique H25 Providing a title using the title element →‎ Techniques/HTML/Providing a title using the title element
  25. HTML5 Technique H2 Combining adjacent image and text links for the same resource →‎ Techniques/HTML/Combining adjacent image and text links for the same resource
  26. Headings using role=heading →‎ Using role=heading
  27. Making actions keyboard accessible by using the keyboard event handlers with WAI-ARIA controls →‎ Making actions keyboard accessible by using keyboard event handlers with WAI-ARIA controls
  28. Making actions keyboard accessible by using the onclick event on WAI-ARIA controls →‎ Making actions keyboard accessible by using the keyboard event handlers with WAI-ARIA controls
  29. PDF Accepted →‎ Some tech in development
  30. PDF Techniques →‎ Techniques/PDF
  31. Proper use of WCAG 2.0 Techniques and Failures →‎ Use of WCAG 2.0 Techniques and Failures
  32. Providing sufficient contrast for forms →‎ Using CSS to provide sufficient contrast for forms
  33. Real time Event →‎ Real-time event
  34. Sing grouping roles to identify related form controls when using fieldset-legend is not practical →‎ Using grouping roles to identify related form controls when using fieldset-legend is not practical
  35. Techniques/ARIA/ariarguments →‎ ARIA for Images Decision
  36. Techniques/ARIA/completed →‎ Completed ARIA Techniques
  37. Techniques/ARIA/image data →‎ Image ARIA support data
  38. Techniques/CSS/General →‎ Techniques/General/a static text alternative to describe a "talking head" video
  39. Techniques into →‎ Addition to Techniques Introduction
  40. Using ARIA Live Regions →‎ Using ARIA Live Regions or role=alert to Identify Errors
  41. Using ARIA Live Regions or role=alert to Identify Errors →‎ Using ARIA role=alert or Live Regions to Identify Errors
  42. Using ARIA landmarks →‎ Using ARIA landmarks to identify regions of a page
  43. Using ARIA landmarks to bypass blocks of content →‎ Using ARIA landmarks to bypass blocks of content, and provide programmatic structure.
  44. Using Aria role=dialog to expose a custom dialog (pop-up div box) →‎ Using Aria role=dialog to implement a modal dialog box
  45. Using Aria role=dialog to implement a modal dialog box →‎ Using ARIA role=dialog to implement a modal dialog box
  46. Using WAI-ARIA range properties for range widgets such as progressbar, scrollbar, slider, and spinbutton →‎ Using WAI-ARIA range attributes for range widgets such as progressbar, scrollbar, slider, and spinbutton
  47. Using WAI-ARIA state attributes to expose the state of a user interface component →‎ Using WAI-ARIA state and property attributes to expose the state of a user interface component
  48. Using WAI-ARIA states and properties for range widgets (progressbar, scrollbar, slider, spinbutton) →‎ Using WAI-ARIA range properties for range widgets such as progressbar, scrollbar, slider, and spinbutton
  49. Using WAI-ARIA states and properties in a tree widget →‎ Using the WAI-ARIA aria-expanded state in a tree widget
  50. Using a script load toggle for feature detection libraries to provide a conforming alternate version →‎ Creating a conforming alternate version for web pages which are designed to be responsive / progressively enhanced

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)