WCAG 2.1 - WET-BOEW documentation

• Edit this page
• Revision history
• Questions or comments?

Discussion notes how to implement WCAG 2.1 in WET.

New Success Criteria

• 1.3.4 Orientation (AA)
• 1.3.5 Identify Input Purpose (AA)
• 1.4.10 Reflow (AA)
• 1.4.11 Non-Text Contrast (AA)
• 1.4.12 Text Spacing (AA)
• 1.4.13 Content on Hover or Focus (AA)
• 2.1.4 Character Key Shortcuts (A)
• 2.5.1 Pointer Gestures (A)
• 2.5.2 Pointer Cancellation (A)
• 2.5.3 Label in Name (A)
• 2.5.4 Motion Actuation (A)
• 4.1.3 Status Messages (AA)

Level AAA

• 1.3.6 Identify Purpose (AAA)
• 2.2.6 Timeouts (AAA)
• 2.3.3 Animation from Interactions (AAA)
• 2.5.5 Target Size (AAA)
• 2.5.6 Concurrent Input Mechanisms (AAA)

Conformance for WET

The goal is having the Web Experience Toolkit (WET) designed to meet WCAG 2.1 Level AA.

Considering that a website conforming to WCAG 2.1 Level AA is also conforming to WCAG 2.0 Level AA, it was suggested that WET project initiate now the complete move in order to be conforming with WCAG 2.1 Level AA standard.

After a conformance check, any reference to WCAG 2.0 Level AA would be need to be update to WCAG 2.1 Level AA. At the end of the implementation of WCAG 2.1 project, no reference to WCAG 2.0 should remain in the active documentation.

Preliminary discussion topic

1.4.12 Text Spacing

Consider to add the following CSS, like what was done with the WCAG 2.1 CSS

body {
	word-wrap: break-word;
}

List of todo:

• Nominate a project lead
• Organise regular meeting with key stakeholder
• Identify the impact on each WET feature
• Draft proposal
• Discuss how each SC can be applied and how WET can accommodate if feasible
• Update the following content (in English and French):
  • Accessibility responsibility breakdown
    • @EricDunsworth drafted a table which show that breadown for the new SC
  • Web Accessibility Assessment Methodology (level AA) Web Accessibility Assessment Methodology (level AAA)