A.2.1.1 Alternative Content

Proposal how we might break-up A.2.1.1 in a way that is similar to WCAG 2.0's 1.1 (Text Alternatives) and 1.2 (Time-based Media):

Proposal:

A.2.1.1 Text Alternatives for Rendered Non-Text Content: If an *editing-view* *renders* *non-text content* with *programmatically associated* *text alternatives*, then the text alternatives can be *programmatically determined*. (Level A)

A.2.1.X Alternatives for Rendered Time-Based Media: If an *editing-view* *renders* time-based media, then at least one of the following is true: (Level A)
(a) alternatives rendered: alternatives for the time-based content are also rendered; or
(b) user agent option: the author has the option to have the content being edited *previewed* in a pre-existing *user agent*.

Ed. Note: WCAG2 does not define time-based media. I've taken a shot but I haven't come up with anything more clear than the term itself

Ed. Note2: The reason for (b) in A.2.1.X is that the alternative might be in a media the authoring tool doesn't ever render. (e.g., an audio editor might not have the capability to render a video alternative)

Summary

Details

Proposed

B.1.1.2 (NEW) Content Auto-Generation During Authoring Sessions (WCAG): Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true:

@@Note 1: Automatic generation includes automatically selecting templates for authors.

Note 2: This success criterion applies only to automatic processes specified by the authoring tool developer. It does not apply when author actions prevent generation of accessible web content.

(a) Accessible: The content is accessible web content (WCAG) without author input; or
(b) Prompting: During the automatic generation process, authors are prompted for any required accessibility information (WCAG); or
(c) Checking Active: After the automatic generation process, accessibility checking is active on the output; or
(d) Checking Suggested: Authors have the default option to have accessibility checking suggested. The WCAG 2.0 Level A success criteria are met (Level A); or
The WCAG 2.0 Level A and Level AA success criteria are met (Level AA); or
The WCAG 2.0 Level A, Level AA, and Level AAA success criteria are met (Level AAA).

Summary

Details

Proposed A.2.2.2

Access to Text Presentation (Minimum): If an editing-view renders text content, then any of the following properties that can be communicated by the supported platform accessibility service(s) can be programmatically determined: (Level A)
(a) Font; and
(b) Font Style; and
(c) Font Variant; and
(d) Front Weight;
(e) Font Size; and
(f) Font Color; and
(g) Background Color

Summary

(1 response didn't contain an answer to this question)

Details

Proposed A.2.2.3

If an editing-view renders text content, then all editable properties that can be communicated by the supported platform accessibility service(s) can be programmatically determined. (Level AAA)

Summary

(1 response didn't contain an answer to this question)

Details

Proposed A.3.5.1 Text Search

add option (d):

(d) No Match: Authors are informed when no results are found.

Link to A.3.5.1 in the latest draft

Summary

Details