- Important note: This Wiki page is edited by participants of the User Agent Accessibility Guidelines working group (UAWG). 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.

Dead-end pages

Jump to: navigation, search

The following pages do not link to other pages in WAI UA Wiki.

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

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

  1. Text size
  2. Appendix E: Alternative Content
  3. Applying UAAG to Mobile Phones
  4. Browser Compliance Notes
  5. Comment Response 20 March 2015
  6. Comments & Responses 30 April 2015
  7. Comments on Web Applications Working Group Charter
  8. Components of UAAG 2.0 Conformance Claims - Platform Limitations Note
  9. DRAFT - Input to Guidelines from UAWG
  10. Definition of User Agent
  11. Definition of a User Agent & Examples
  12. Examples of Mobile Phones in UAAG
  13. Existing Standards that apply to Mobile Accessibility
  14. Extensions needed for Implementation Examples
  15. Guideline 1.11
  16. Guideline 1.4 Text Customization Proposal
  17. Guideline 2.8
  18. Guideline 2.9
  19. IOS User Agents
  20. Keyboard Concepts for HTML5 Discussion
  21. Keyboard Interface use cases
  22. Latest Draft of Exit Criteria
  23. Location Hierarchy
  24. Low vision use cases
  25. Mobile accessibility and UAAG20
  26. Overview of Testing for UAAG
  27. SC Testing Criteria
  28. Sample pages for testing
  29. Talking Points - UAAG 2.0
  30. Talking Points for Low Vision Support
  31. Test Writing Style Guide
  32. Test for Show: The user can choose to display any controls available within the user agent user interface, including user-installed extensions. It is acceptable to limit the total number of controls that are displayed onscreen.
  33. Test for Simplify: The user can simplify the default user interface by choosing to display only commands essential for basic operation (e.g. by hiding some controls).
  34. Test for Reposition
  35. Test for Assign Activation Keystrokes or Gestures: The user can choose to view, assign or change default keystrokes or gestures used to activate controls.
  36. Test for Reset: The user has the option to reset the containers and controls to their default configuration.
  37. Thoughts for UAAG 3
  38. Use Cases for UAAG Applicability
  39. User Agent issues effecting A11y

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