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 categories

Jump to: navigation, search

Showing below up to 50 results in range #1 to #50.

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

  1. Using a WAI-ARIA role to expose the role of a user interface component‏‎ (4 categories)
  2. Unicode Character with an On-Screen Text Alternative‏‎ (4 categories)
  3. Using ARIA landmarks to identify regions of a page‏‎ (4 categories)
  4. Using aria-describedby for link purpose‏‎ (4 categories)
  5. Using aria-label for link purpose‏‎ (4 categories)
  6. 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 categories)
  7. Providing an Off-Screen Text Alternative for an Icon Font‏‎ (4 categories)
  8. Using aria-label to provide labels for objects‏‎ (4 categories)
  9. Using WAI-ARIA aria-checked=mixed‏‎ (4 categories)
  10. 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‏‎ (4 categories)
  11. Using aria-hidden=true on an icon font that AT should ignore‏‎ (4 categories)
  12. 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‏‎ (4 categories)
  13. Icon Font with an On-Screen Text Alternative‏‎ (4 categories)
  14. Using ARIA trees‏‎ (4 categories)
  15. Using aria-labelledby for link purpose‏‎ (4 categories)
  16. Using WAI-ARIA state and property attributes to expose the state of a user interface component‏‎ (4 categories)
  17. 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‏‎ (4 categories)
  18. Using aria-describedby for link purpose - May 2014‏‎ (4 categories)
  19. Using the WAI-ARIA aria-expanded state to mark expandable and collapsible regions‏‎ (4 categories)
  20. Using aria-labelledby to provide a text alternative for non-text content‏‎ (4 categories)
  21. 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‏‎ (4 categories)
  22. Using sufficient contrast for images that convey information‏‎ (4 categories)
  23. Using aria-labelledby to concatenate a label from several text nodes‏‎ (4 categories)
  24. Using title for 1.1.1‏‎ (4 categories)
  25. 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‏‎ (4 categories)
  26. Using aria-hidden="true" on Unicode characters that AT should ignore‏‎ (4 categories)
  27. Failure of 4.1.2 due to using Using Abstract Roles‏‎ (3 categories)
  28. Using role="heading" to identify headings‏‎ (3 categories)
  29. Using aria-label to provide an invisible label where a visible label cannot be used‏‎ (3 categories)
  30. Using aria-describedby to provide descriptions of images‏‎ (3 categories)
  31. Using aria-activedescendant‏‎ (3 categories)
  32. Using role=heading to identify headings‏‎ (3 categories)
  33. Techniques/General/Using a static text alternative to describe a talking head video‏‎ (3 categories)
  34. Using aria-activedescendant to allow changes in focus within widgets to be communicated to Assistive Technology‏‎ (3 categories)
  35. Using WAI-ARIA states and properties to create an interactive grid‏‎ (3 categories)
  36. Using ARIA role of alert for Error Feedback in Forms‏‎ (3 categories)
  37. Using aria-labelledby to provide a name for user interface controls‏‎ (3 categories)
  38. Using ARIA menus‏‎ (3 categories)
  39. Using WAI-ARIA states and properties to create a menu‏‎ (3 categories)
  40. Using grouping roles to identify related form controls‏‎ (3 categories)
  41. Using aria-flowto‏‎ (3 categories)
  42. Making actions keyboard accessible by using keyboard event handlers with WAI-ARIA controls‏‎ (3 categories)
  43. Using aria-alertdialog to Identify Errors‏‎ (3 categories)
  44. Using aria-expanded to indicate the state of a collapsible element‏‎ (3 categories)
  45. Using aria-label for 1.1.1‏‎ (3 categories)
  46. Using the TextTrack API to provide captions dynamically‏‎ (3 categories)
  47. Using aria-label to provide an invisible label‏‎ (3 categories)
  48. Using ARIA role=dialog to implement a modal dialog box‏‎ (3 categories)
  49. Using ARIA landmarks to bypass blocks of content, and provide programmatic structure.‏‎ (3 categories)
  50. Using WAI-ARIA range attributes for range widgets such as progressbar, scrollbar, slider, and spinbutton‏‎ (3 categories)

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