1 of 13

WCAG 3.0�Scoring and Conformance Proposal

Present by:�John Foliot�Deque Systems Inc

Aug 7, 2020

2 of 13

Scoring Requires Points!

  • Not all Requirements (Success Criteria� / Methods) are should be equal.
  • Impact of requirement on Functional �Requirements by User Group.
  • Scalable Scoring: The distance between �0 and 1 is wrong.
  • ACT Rules Format (Atomic Tests)
    • Different Atomic Tests have different point values
    • Complex interaction can be mapped back to multiple atomic tests
    • The ‘score’ of a complex interaction is the sum of Atomic Tests (perhaps with additional points based on other usability criteria – TBD)

3 of 13

Scoring Requires Points!

Key Take-Away: individual requirements impact users differently; some requirements are more impactful overall.

4 of 13

Intersectional Needs Are Still Accounted For

Deep Dive on one current Success Criteria (SC 1.3.1)

  • Atomic & Manual tests for multiple requirements currently under SC 1.3.1
  • Getting ‘well-formed’ tables is slightly more critical than grouped controls.
  • Ungrouped controls impact more user-types, but less severely. �But because it *CAN* impact more users, it’s overall score remains high.
  • Fairness without reducing everything to Pass or Fail

​

5 of 13

Views vs. Paths

  • A ‘View’ is all content presented on the screen at a single moment*.
    • (Examples: Web = Web Page, Native Mobile Application = User Interface)
  • A ‘Path’ can happen on one screen (SPAs), or multiple screens.
  • Paths can be (likely always will be) a sub-set of a Single View or Multiple Views
  • Views can be applied to Components, Design Systems, Templates, etc.
  • Paths always include Editorial Content

​

6 of 13

Testing and Gaining Points

  • Purely Mechanical (Atomic)
  • Mechanically Assisted�(Contextual)
  • User-tests & Outcomes�(Holistic)

7 of 13

Flexible Scoring By Content Type

“Editorial” Free assets:

  • Components & Frameworks (ReAct, Angular, etc.)
  • Design Systems
  • Empty Layout Templates (WordPress Themes, SaaS, etc.)

Content Complete assets:

  • Web sites (Representative Sampling) / Single Page Apps
  • Native Mobile Applications
  • PDFs, ePub, “Document Accessibility”
  • XR (VR / AR)
  • …Future Technologies

8 of 13

Flexible Scoring By Content Type

  • Different Content Types can be scoped by determining all Atomic Tests needed
  • Scoping can also address maturity level � (Editorial Free vs. Full content type)

9 of 13

Flexible Scoring By Content Type

10 of 13

Dashboards and Accessibility Health Monitoring

  • Pre-Launch
  • Post-Launch
    • Ongoing Monitoring

​

​

​

​

See Also: https://docs.google.com/document/d/1PgmVS0s8_klxvV2ImZS1GRXHwUgKkoXQ1_y6RBMIZQw/edit#heading=h.s2f3av3tk0j8

11 of 13

Dashboards and Accessibility Health Monitoring

12 of 13

Dashboards and Accessibility Health Monitoring

13 of 13

Thank You