I'd not sure the screen reader test should be part of the web content accessibility test procedure because bugs from screen reader will then be mistakenly attributed to the authoring tool or web content. The flip side is also true that just because screen reader present the content to users does not necessarily mean that the content meet WCAG 2.0 SCs.

If the accessibility guideline (for the platform) that was used by the developer is known, this should be used to test the accessibility of the user interface. If the user interface has followed the guidelines, then select PASS, otherwise select FAIL.

If the accessibility guideline (for the platform) that was used by the developer is not known, choose the most relevant from this list of user interface accessibility guidelines for various platforms and use it to test the accessibility of the user interface. If you find instances where the user interface has not followed the guidelines, then select FAIL, otherwise select PASS.

Check if the authoring tool allows the content being edited to be be previewed in a user agent (e.g. browser or media player) where the alternatives can be rendered. If so, go to the next editing view that renders audio-video.

Check if the authoring tool can be set to render the alternatives itself. If not, select FAIL.

Go to the next editing view that renders audio-video (if any).

Select PASS(all editing views must have passed)

Test 0002 Assertion: Any editing views that render video-only media include an option to display alternatives or an option to preview the media in user agent capable of rendering the alternatives.

If the authoring tool does not include editing views that are capable of rendering video-only, then select SKIP.

Check if the authoring tool allows the content being edited to be be previewed in a user agent (e.g. browser or media player) where the alternatives can be rendered. If so, go to the next editing view that renders audio-only media.

Check if the authoring tool can be set to render the alternatives itself. If not, select FAIL.

Remeber this is an authoring tool for multimedia, either audio or video and as such, the alternatives may not be available because this is raw content. Needs some kind of qualifier that doesn't automatically assume that an alternative is already in existance. Your not going to have a closed caption transcript for video ready until the video has been edited. No one is going to bother producing alternatives for content that ends up on the cutting room floor. Chicken, meet egg. Egg say hello to chicken.

The test should be whether authoring tool can render the alternative, not whether the authoring tool can be set to render the alternative. It is possible for the authoring tool to obtain user preference from the OS or other sources where it will automatically render alternate content.

Success Criteria

A.2.1.2 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) Option to Render: The authoring tool provides the option to render alternatives for the time-based media; or
(b) User Agent Option: Authors have the option to preview the time-based media in a user agent that is able to render the alternatives.

Test(s)

Test 0001 Assertion: Any editing views that render audio-video include an option to display alternatives or an option to preview the media in user agent capable of rendering the alternatives.

If the authoring tool does not include editing views that are capable of rendering audio-video, then select
SKIP.

Check if the authoring tool allows the content being edited to be be previewed in a user agent (e.g. browser or media player) where the alternatives can be rendered. If so, go to the next editing view that renders audio-video.

Check if the authoring tool can be set to render the alternatives itself. If not, select FAIL.

Go to the next editing view that renders audio-video (if any).

Select PASS(all editing views must have passed)

Test 0002 Assertion: Any editing views that render video-only media include an option to display alternatives or an option to preview the media in user agent capable of rendering the alternatives.

If the authoring tool does not include editing views that are capable of rendering video-only, then select SKIP.

Check if the authoring tool allows the content being edited to be be previewed in a user agent (e.g. browser or media player) where the alternatives can be rendered. If so, go to the next editing view that renders audio-only media.

Check if the authoring tool can be set to render the alternatives itself. If not, select FAIL.

Success Criteria

A.2.2.1 Editing-View Status Indicators:
If an editing-view adds status indicators to the content being edited, then the information being conveyed by the status indicators can be programmatically determined. (Level A)

Test(s)

Check all of the editing-views for status indicators (often used to indicate errors (e.g., spelling errors), tracked changes, hidden elements, or other information.), possibly from a product feature list or trial and error.

If the authoring tool does not provide status indicators in any of its editing-views, select SKIP.

For each type of status indicator:

Open or author content that will trigger the status indicator (e.g. with spelling errors, add a hidden element, etc.), then examine the indicator with the Web Content Accessibility Test Procedure. If an indicator does not pass, then select FAIL.

Check all of the editing-views for status indicators (often used to indicate errors (e.g., spelling errors), tracked changes, hidden elements, or other information.), possibly from a product feature list or trial and error.

If the authoring tool does not provide status indicators in any of its editing-views, select SKIP.

For each type of status indicator:

Open or author content that will trigger the status indicator (e.g. with spelling errors, add a hidden element, etc.), then examine the indicator with the Platform Accessibility Service Test Procedure to determine if the indicator (e.g. the validation error) has been communicated to the accessibility API. If an indicator does not pass, then select FAIL.

Success Criteria

A.2.2.2 Access to Rendered Text Properties:
If an editing-view renders any text formatting properties that authors can also edit using the editing-view, then the properties can be programmatically determined. (Level AA)

Test(s)

Test 0001 Assertion: For web-based tools, if rich text formatting can be produced then authors the same formatting is programmatically determinable within the authoring tool.

Test 0001 Author: Jan

If the authoring tool does not include any web-based editing views, then select SKIP.

If the authoring tool cannot be used to author rich text content (e.g. because it is only edits non-text graphics), then select SKIP.

If the authoring tool can be used to author rich text content, but none of its editing views render this rich text content, then select SKIP. (Note: Some text editors render text content (e.g. markup tags, programming keywords, etc.) with various colors, bold weight, etc. These author supports are not part of the content and do not qualify here)

For each editing view that renders rich text content:

Add some text content and (one per line to avoid overlap), use as many rich text formats as possible (e.g. bold, italic, font face, superscript, etc).

If the authoring tool omly includes web-based editing views, then select SKIP.

If the authoring tool cannot be used to author rich text content (e.g. because it is only edits non-text graphics), then select SKIP.

If the authoring tool can be used to author rich text content, but none of its editing views render this rich text content, then select SKIP. (Note: Some text editors render text content (e.g. markup tags, programming keywords, etc.) with various colors, bold weight, etc. These author supports are not part of the content and do not qualify here)

For each editing view that renders rich text content:

Add some text content and (one per line to avoid overlap), use as many rich text formats as possible (e.g. bold, italic, underlined, font face, superscript, etc).

Using a screen reader that is appropriate to the platform attempt to identify the following text formatting properties (if they could be edited in the previous step): font face, font size, font color, whether text is bold, whether text is italic. If they cannot be identified, then selectFAIL.