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.4.2 Audio Control
  3. 2.4.2: Page Titled
  4. 3.2.4 Consistent Identification
  5. 4.1.1: Parsing
  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
  7. 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
  8. 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
  9. 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
  10. ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls
  11. ARIA2: Identifying a required field with the aria-required property
  12. ARIA3: Identifying valid range information with the aria-valuemin and aria-valuemax properties
  13. ARIATechnique usingImgRole with aria-label forCSS-backgroundImage
  14. Acceptance Criteria for Success Criteria
  15. Addition to Techniques Introduction
  16. Administrative
  17. Ambiguous to users in general
  18. Animation caused by user interaction
  19. 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
  20. 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?
  21. 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"
  22. 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
  23. Aria-Edit: F87
  24. 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"
  25. Brainstorming Short Name Ideas for Issue 78
  26. Captcha Alternatives and thoughts
  27. Closed Actions
  28. Closed Functionality and 1.4.4
  29. Closed Functionality and 1.4.4, alternate
  30. Comments Needing Responses
  31. Comments on WCAG.Next Models
  32. CompanionDocsSurvey
  33. Comparing the Options
  34. Completed ARIA Techniques
  35. Components delivered as part of the initial page load conform
  36. Contrast ratio
  37. Creating Logical Tab Order with the Tabindex Attribute
  38. Creating a conforming alternate version for a web page designed with progressive enhancement
  39. Decisions
  40. Definition List usage
  41. Definition of "blinking"
  42. Definition of blinking
  43. Deliverables
  44. Design Driven Option
  45. Designing Silver
  46. EOTutorials review
  47. Edits Needed
  48. Edits to Add 2.4.10 to H69
  49. Ensuring conforming alternative is discoverable
  50. ErrorNotificationUsingAlertRoleOrAriaLive action=edit

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