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.

Pages with the most revisions

Jump to: navigation, search

Showing below up to 50 results starting with #1.

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

  1. Techniques/ARIA‏‎ (448 revisions)
  2. Scribe List‏‎ (193 revisions)
  3. Using ARIA landmarks to identify regions of a page‏‎ (193 revisions)
  4. Comments Needing Responses‏‎ (190 revisions)
  5. Using aria-labelledby to concatenate a label from several text nodes‏‎ (168 revisions)
  6. Working Group Techniques Development Assignments‏‎ (103 revisions)
  7. EOTutorials review‏‎ (96 revisions)
  8. Using aria-describedby to provide descriptions of images‏‎ (85 revisions)
  9. Using aria-labelledby for link purpose‏‎ (83 revisions)
  10. Using aria-label to provide an invisible label‏‎ (83 revisions)
  11. Using aria-labelledby to provide a name for user interface controls‏‎ (78 revisions)
  12. Techniques/HTML5‏‎ (73 revisions)
  13. Using ARIA role=dialog to implement a modal dialog box‏‎ (72 revisions)
  14. Post WCAG 2‏‎ (69 revisions)
  15. 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‏‎ (68 revisions)
  16. Using ARIA role=alert or Live Regions to Identify Errors‏‎ (68 revisions)
  17. 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‏‎ (64 revisions)
  18. Using the aside element to indicate tangentially related content‏‎ (61 revisions)
  19. Using aria-labelledby to provide a text alternative for non-text content‏‎ (60 revisions)
  20. Edits Needed‏‎ (59 revisions)
  21. Using grouping roles to identify related form controls‏‎ (57 revisions)
  22. Using Aria-Invalid to Indicate An Error Field‏‎ (57 revisions)
  23. Using the region role to identify a region of the page‏‎ (55 revisions)
  24. Using the track element to provide captions‏‎ (55 revisions)
  25. ARIA-edit: F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link‏‎ (55 revisions)
  26. Grouping related links using the nav element‏‎ (55 revisions)
  27. Using aria-label for link purpose‏‎ (53 revisions)
  28. Using aria-flowto‏‎ (51 revisions)
  29. Failure of Success Criterion 1.3.1 for not correctly marking up table headers‏‎ (49 revisions)
  30. ARIA2: Identifying a required field with the aria-required property‏‎ (48 revisions)
  31. 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‏‎ (47 revisions)
  32. Creating Logical Tab Order with the Tabindex Attribute‏‎ (45 revisions)
  33. Using the WAI-ARIA aria-expanded state to mark expandable and collapsible regions‏‎ (45 revisions)
  34. Creating a conforming alternate version for a web page designed with progressive enhancement‏‎ (44 revisions)
  35. Using aria-describedby for link purpose‏‎ (43 revisions)
  36. Using aria-label to provide labels for objects‏‎ (43 revisions)
  37. Techniques/Failures‏‎ (42 revisions)
  38. Using aria-describedby for link purpose - May 2014‏‎ (41 revisions)
  39. Review of html4 to html5‏‎ (40 revisions)
  40. Using HTML5 section elements‏‎ (39 revisions)
  41. Using role="heading" to identify headings‏‎ (39 revisions)
  42. Making actions keyboard accessible by using keyboard event handlers with WAI-ARIA controls‏‎ (38 revisions)
  43. Using a WAI-ARIA role to expose the role of a user interface component‏‎ (36 revisions)
  44. Use of WCAG 2.0 Techniques and Failures‏‎ (35 revisions)
  45. Using WAI-ARIA range attributes for range widgets such as progressbar, scrollbar, slider, and spinbutton‏‎ (35 revisions)
  46. Using ARIA landmarks to bypass blocks of content, and provide programmatic structure.‏‎ (34 revisions)
  47. WCAG Myths‏‎ (34 revisions)
  48. Using aria-alertdialog to Identify Errors‏‎ (33 revisions)
  49. ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls‏‎ (33 revisions)
  50. Using ARIA menus‏‎ (32 revisions)

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