Specification needs to be compliant with WCAG 2.0

[burnburn]

We are required to ensure that the document, when published, satisfies the WCAG 2.0 requirements. See https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0

At a minimum this must be done before CR publication. If done earlier, it needs to be kept up to date. While technically editorial, this is a non-trivial piece of work, especially as we add diagrams, so additional volunteers are encouraged.

[rhiaro]

I will do a first pass through applying these guidelines this week month and make a PR. We can leave this issue open to audit again before CR.

[rhiaro]

(WIP - flagged with ** things I'm not sure about, input gratefully received)

• 1.1 Non-text content alternatives
• 1.2 Time-based media: n/a
• 1.3 Adaptable
  • structure conveyed by presentation available programmatically
  • reading sequence available programmatically
  • content not depends on sensory characteristics: n/a
• 1.4 Distinguishable
  • meaningful color: n/a
  • resizeable text
  • contrast of images
  • images of text: n/a
  • audio: n/a
• 2.1 Keyboard accessible
• 2.2 Timing: n/a
• 2.3 Physical reactions: n/a
• 2.4 Navigable
  • bypass repeat blocks: I think n/a **
  • titles
  • focus order
  • link purpose
  • multiple ways to locate page: n/a
  • headings and labels
  • focus visible: with default browser components - okay? **
  • user location within set of pages: n/a
  • section headings
• 2.5 Input modalities: ??? **
• 3.1 Readable
  • programmatic language determination
  • identifying unusual phrases
  • expanding abbreviations
  • reading level lower than secondary education
  • pronunciation identified where necessary for meaning
• 3.2 Predictable
  • on focus doesn't change context
  • on input doesn't change context: n/a
  • consistent nav: n/a
  • consistent identification of components with same func.
  • change of context on request only
• 3.3 Input assistance: n/a
• 4.1 Compatible
  • valid markup
  • name and role of elements

[rhiaro]

(Will complete this audit closer to CR, but if anyone knows which of the markup/structure related things respec covers automatically please say so)

[msporny]

if anyone knows which of the markup/structure related things respec covers automatically please say so

Unfortunately, I don't know... looking now in ReSpec's documentation...

[msporny]

Still waiting on CR...

[msporny]

I have done an WCAG2 analysis on the document. The readability scores are borderline... requiring ~11 years of education (or 7th grade US level) to understand.

That said, we pass all checks. Closing.