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. Accepted WCAG 2.1 SC
  16. Addition to Techniques Introduction
  17. Administrative
  18. Allowing for Spacing Override
  19. Ambiguous to users in general
  20. Animation caused by user interaction
  21. 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
  22. 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?
  23. 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"
  24. 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
  25. Aria-Edit: F87
  26. 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"
  27. Brainstorming Short Name Ideas for Issue 78
  28. Captcha Alternatives and thoughts
  29. Closed Actions
  30. Closed Functionality and 1.4.4
  31. Closed Functionality and 1.4.4, alternate
  32. Comments Needing Responses
  33. Comments on WCAG.Next Models
  34. CompanionDocsSurvey
  35. Comparing the Options
  36. Completed ARIA Techniques
  37. Components delivered as part of the initial page load conform
  38. Consensus Tally for Adapting Text SC Text
  39. Contrast ratio
  40. Creating Logical Tab Order with the Tabindex Attribute
  41. Creating a conforming alternate version for a web page designed with progressive enhancement
  42. Decisions
  43. Definition List usage
  44. Definition of "blinking"
  45. Definition of blinking
  46. Deliverables
  47. Design Driven Option
  48. Designing Silver
  49. EOTutorials review
  50. Edits Needed

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