Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Need to integrate accessibility from the start
  • The annotation language used to describe the a11y in the wireframes should fit your community
    • provide a glossary in a separate document to define the terms in the notes
      • e.g., "skip nav" is noted in the wireframe; the glossary defines what a "skip nav" is and its function.
  • Examples of things to describe
    • tab order
    • controls for interactive widgets (e.g. carousels require play/pause and etc, and individual panels may have links and other interactive elements within that need to be accessible)
    • labels
    • skip links
  • Can incorporate some of the information in a style guide. For example that headings are actually marked up in proper heading tags.