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.

Framing WAI2020

From WCAG WG
Jump to: navigation, search

Framing the WAI2020 Discussion

[JOSH NOTES] These thoughts are in no particular order but are to act as a guide to enhance of my own sense of where we are at, some options and avenues.

What is WAI2020?

  • We need to clearly articulate what problems WAI2020 aims to address (Needs analysis).
  • What is the scope of WAI2020? What is out of scope?
  • Do we need modular sets of guidelines that address potential verticals? Or a common set of guidelines that work horizontally across multiple domains?

NOTE Will an exclusively vertical approach work? And can that be called ‘WAI2020’ – The various domains include ‘Wearables’, ‘The Internet of things’, ‘Automotive Web’, ‘TV’. How would this work – bespoke WAI groups and TFs looking at these areas?

  • For either case - should this work be normative (with its implicit time/cost overhead)? Or should we be moving towards more modular, agile, documents that can be changed as needed. This implies a different approach to standards development (which could be a good thing).
  • Whatever we do we need to create *user focused* guidelines, techniques, tutorials, tools, and support inclusive design methods.
  • Should WAI stop developing standards exclusively in W3C space? Should we join forces and develop our future standards/guidelines more with relevant organisations that promote good usability, inclusive design best practices in industry?
  • We could look at the common accessibility patterns that can span multiple domains – these are the practices that support accessibility and positive user experience for PWDS. Canonise them, and use them as a reference point for any vertical. These are (for example):
  1. Content must be structured correctly.
  2. All Inputs need to be well formed.
  3. Users must be informed of any changes in a systems ‘state’ in a way that is accessible.
  4. Error suggestion/correction – must be accessible.
  5. All media must be multi-modal (have suitable alternatives)
  6. Colour contrast should ideally be high (should we revisit our contrast algorithm to make it more robust).

@@ [add others]

  • What about the approaches of GPII/Prosperity for all and other initiatives? What would the delta be with future initiatives like WAI2020?

Other non WAI2020 ideas

  • We need a delta for WCAG/UAAG/ATAG/WTAG. WCAG SCs may not be exclusively met by the author – the UA plays a vital role. Should we create a note identifying this WCAG/UAAG delta? Kind of like a UAAG for content developers?
  • Guidelines need to factor in heuristics and repair mechanisms within browsers and UAs.
  • Should WCAG be simplified? Many AAA SCs seem impractical and virtually redundant (in real world usage and conformance)