MCAG 2.0 - What's the context, and what's the point?

[qbalsdon]

What happened in MCAG 1.0? Goals / Objectives

• Is there a link to the talk?

MCAG is intended to be a document that reflects the conformance requirements of WCAG but also refers to the unique differences and challenges of mobile technologies that are not adequately expressed in WCAG. The document results from cross-referencing WCAG 2.2 success criteria with the accessibility guidelines of the different platforms and other sources.

MCAG was written into the template and structure of WCAG, and it preserves the four POUR. However, since its use is intended for development teams, its internal division relies more on Apple's Human Interface Guidelines and Android's Accessibility Principles. Accordingly, the guidelines' names, divisions, and success criteria are different. The differences are reflected mainly in wording and affiliation. However, any changes were made with reference and an affinity to WCAG and its content.

MCAG does not pretend to replace WCAG but only provides a uniform interpretation of it for mobile technologies while preserving its conformance requirements.

The document in front of you is a first draft and an invitation to cooperation and community discussion on the need for clear and dedicated guidelines for mobile technologies that will meet the needs of users and regulatory requirements.

Why MCAG 2.0?

• Is the objective still development teams?
• Is following specific corporations' guidelines a long term solution?
• Did MCAG 1.0 achieve it's goals?

Are there any "north stars"?