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. 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
  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. 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"
  21. 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
  22. Aria-Edit: F87
  23. 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"
  24. Captcha Alternatives and thoughts
  25. Closed Actions
  26. Closed Functionality and 1.4.4
  27. Closed Functionality and 1.4.4, alternate
  28. Comments Needing Responses
  29. Comments on WCAG.Next Models
  30. CompanionDocsSurvey
  31. Completed ARIA Techniques
  32. Components delivered as part of the initial page load conform
  33. Contrast ratio
  34. Creating Logical Tab Order with the Tabindex Attribute
  35. Creating a conforming alternate version for a web page designed with progressive enhancement
  36. Decisions
  37. Definition List usage
  38. Definition of "blinking"
  39. Definition of blinking
  40. Deliverables
  41. Designing Silver
  42. EOTutorials review
  43. Edits Needed
  44. Edits to Add 2.4.10 to H69
  45. Ensuring conforming alternative is discoverable
  46. ErrorNotificationUsingAlertRoleOrAriaLive action=edit
  47. Examples of Real-time event - action item
  48. Extension Integration
  49. 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
  50. F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows Assistive technology to ignore them

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