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 without language links

Jump to: navigation, search

The following pages do not link to other language versions.

Prefix  

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

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

  1. "Purpose" and doc/app names
  2. 1-3-5 Revision
  3. 1.4.2 Audio Control
  4. 2-2-6 Revision
  5. 2-2-9 Revision
  6. 2.2.7 Revision
  7. 2.2.7 comments
  8. 2.2.8 responses
  9. 2.4.2: Page Titled
  10. 3.2.4 Consistent Identification
  11. 4.1.1: Parsing
  12. 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
  13. ARIA-edit: F63: Failure of Success Criteria 2.4.4 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link
  14. 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
  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
  16. ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls
  17. ARIA2: Identifying a required field with the aria-required property
  18. ARIA3: Identifying valid range information with the aria-valuemin and aria-valuemax properties
  19. ARIATechnique usingImgRole with aria-label forCSS-backgroundImage
  20. Acceptance Criteria for Success Criteria
  21. Accepted WCAG 2.1 SC
  22. Addition to Techniques Introduction
  23. Administrative
  24. Allowing for Spacing Override
  25. Ambiguous to users in general
  26. Animation caused by user interaction
  27. Are there any new structures or relationships in HTML 5 or ARIA that could be used to link multiple reading-level versions of the same content
  28. Are there any new structures or relationships in HTML 5 or ARIA that could be used to link multiple reading-level versions of the same content?
  29. 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"
  30. 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
  31. Aria-Edit: F87
  32. Aria-EditF65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type "image"
  33. Brainstorming Short Name Ideas for Issue 78
  34. Captcha Alternatives and thoughts
  35. Closed Actions
  36. Closed Functionality and 1.4.4
  37. Closed Functionality and 1.4.4, alternate
  38. Comment Summary 1-3-4
  39. Comment Summary 1-4-10
  40. Comment Summary 1-4-11
  41. Comment Summary 1-4-13
  42. Comment Summary 1-4-14
  43. Comment Summary 2-2-6
  44. Comment Summary 2-2-7
  45. Comment Summary 2-5-1
  46. Comment Summary 2-5-2
  47. Comment Summary 2-6-1
  48. Comment Summary 2-6-2
  49. Comment Summary 3-2-7
  50. Comments Needing Responses

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