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.

Most linked-to pages

Jump to: navigation, search

Showing below up to 50 results starting with #1.

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

  1. Using aria-labelledby for link purpose‏‎ (6 links)
  2. Using aria-labelledby to concatenate a label from several text nodes‏‎ (5 links)
  3. Using aria-label to provide labels for objects‏‎ (5 links)
  4. Using WAI-ARIA state and property attributes to expose the state of a user interface component‏‎ (5 links)
  5. Using aria-labelledby to provide a text alternative for non-text content‏‎ (5 links)
  6. Using the role attribute to expose the role of a user interface component‏‎ (4 links)
  7. Using aria-labelledby to name controls‏‎ (4 links)
  8. Task Forces‏‎ (4 links)
  9. Using the track element to provide captions‏‎ (4 links)
  10. Working Group Techniques Development Assignments‏‎ (3 links)
  11. Using aria-describedby for link purpose‏‎ (3 links)
  12. Using ARIA landmarks to identify regions of a page‏‎ (3 links)
  13. Category:Techniques‏‎ (3 links)
  14. Using WAI-ARIA range attributes for range widgets such as progressbar, scrollbar, slider, and spinbutton‏‎ (3 links)
  15. Using grouping roles to identify related form controls‏‎ (3 links)
  16. Using aria-label‏‎ (3 links)
  17. Using the TextTrack API to provide captions dynamically‏‎ (3 links)
  18. Using the WAI-ARIA aria-expanded state to mark expandable and collapsible regions‏‎ (3 links)
  19. Technique Instructions‏‎ (3 links)
  20. Using aria-labelledby to provide a name for user interface controls‏‎ (3 links)
  21. Making actions keyboard accessible by using keyboard event handlers with WAI-ARIA controls‏‎ (3 links)
  22. Using aria-label for link purpose‏‎ (3 links)
  23. Playing a sign language video from a video element's video track list‏‎ (3 links)
  24. Techniques/ARIA‏‎ (2 links)
  25. Category:HTML5 Techniques‏‎ (2 links)
  26. Using aria-describedby to provide descriptions of images‏‎ (2 links)
  27. Category:Technique Status‏‎ (2 links)
  28. Ensuring correct tab and reading order in PDF documents‏‎ (2 links)
  29. Using Aria role=dialog to expose a custom dialog (pop-up div box)‏‎ (2 links)
  30. Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information‏‎ (2 links)
  31. Using WAI-ARIA aria-checked=mixed‏‎ (2 links)
  32. ARIA2: Identifying a required field with the aria-required property‏‎ (2 links)
  33. Category:ARIA Techniques‏‎ (2 links)
  34. Using ARIA Live Regions or role=alert to Identify Errors‏‎ (2 links)
  35. Techniques/HTML/Combining adjacent image and text links for the same resource‏‎ (2 links)
  36. Mobile Accessibility Task Force‏‎ (2 links)
  37. Using ARIA landmarks‏‎ (2 links)
  38. Using aria-flowto‏‎ (2 links)
  39. Using aria-labelledby to name regions and landmarks‏‎ (2 links)
  40. Using aria-activedescendant to allow changes in focus within widgets to be communicated to Assistive Technology‏‎ (2 links)
  41. Using aria-label to provide an invisible label where a visible label cannot be used‏‎ (2 links)
  42. Failure of 4.1.2 due to using Using Abstract Roles‏‎ (2 links)
  43. Using ARIA landmarks to bypass blocks of content‏‎ (2 links)
  44. Using WAI-ARIA states and properties to create a menu‏‎ (2 links)
  45. Using aria-labelledby to provide a text alternative the serves the equivalent purpose‏‎ (2 links)
  46. Techniques/HTML/Providing a title using the title element‏‎ (2 links)
  47. ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls‏‎ (2 links)
  48. Task Force Reports‏‎ (2 links)
  49. Using ARIA menus‏‎ (2 links)
  50. Resource Redesign/Quickref/Planning‏‎ (2 links)

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