Comment Summary 3-2-7

From WCAG WG

Existing SC Text

Programmatic notification is provided for each change of content that indicates a user action was taken or that conveys information, unless one or more of the following is true:

  • There is a programmatically determined relationship between the new content and the control that triggers it;
  • The user has been advised of the change of content before, or as a result of using the control;
  • The change of content both is not a result of a user action and is not related to the primary purpose of the page.

Updated SC Text

For content which does not take focus and which dynamically updates as a result of user action or application status changes, the following are true:

  • Changes in content are programmatically determinable through role or attributes;
  • Notification of changes to content is available to user agents, including assistive technologies.

Proposed responses to comments on Change of Content

365: Thanks for the comment. This SC has been scoped more narrowly to address status messages (a new defined term) and requiring that the changes are programmatically determinable. We hope that these changes will address your concerns.

385: Thanks for the comment. This SC has been scoped more narrowly to address status messages (a new defined term) and requiring that the changes are programmatically determinable. We hope that these changes will address your concerns.

462: Thanks for your comment, and hard work to improve the SC text and address your comment.

463: The term "programmatic notification" is no longer used in the SC.

464: Thanks for your comment, and hard work to improve the SC text and address your comment.

482: Thanks for the comment. This SC has been scoped more narrowly to address status messages (a new defined term) and requiring that the changes are programmatically determinable. We hope that these changes will address your concerns. Regarding the concern that this SC will create implementation problems or result in extraneous notification, we hope to gather more data on this during the implementation phase.

502: Thanks for your comment. The approach you describe is regularly used, and would provide a scenario where this SC would be automatically conformed to. If there are no changes of content that occur without changes of context then the web page will pass this SC.

527: Thanks for your comment. The definition your comment is about is no longer in the spec. Instead the SC is focused on "Status Messages" and includes "Changes in content that are not changes in context". We hope that this addresses your concern.

531: Thank you for your comment. Exception #1 is no longer in the SC text.

539: Thank you for your comment. Your comment indicates that you do not feel that this SC is needed. The Working Group does not agree. We have updated and hopefully clarified the SC. Please re-review it when the new working draft is available this week.

562: Thank you for the comment. This has been identified as a problem for users who need to keep their focus on the part of the page that they are active on, so we are working to provide a way. We have updated and hopefully clarified the SC. Please re-review it when the new working draft is available this week.