Comment: 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.

JR: The "loop" wording is used in
case of multiple editing views. If only one is present, the
"loop" only runs once.

COOMMENT: Test 0002 step 2.1 has
ambiguous If statement.

Agreed: There is a typo: There should be a
different 2.2 which should read: "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
video-only media."

COMMENT: 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.