{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/wcag21/issues/2","repository_url":"https://api.github.com/repos/w3c/wcag21","labels_url":"https://api.github.com/repos/w3c/wcag21/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/w3c/wcag21/issues/2/comments","events_url":"https://api.github.com/repos/w3c/wcag21/issues/2/events","html_url":"https://github.com/w3c/wcag21/issues/2","id":171038609,"number":2,"title":"New SC Proposal: Programmatic notification is provided for each change in content that indicates an action was taken or that conveys information","user":{"login":"DavidMacDonald","id":2365411,"avatar_url":"https://avatars.githubusercontent.com/u/2365411?v=3","gravatar_id":"","url":"https://api.github.com/users/DavidMacDonald","html_url":"https://github.com/DavidMacDonald","followers_url":"https://api.github.com/users/DavidMacDonald/followers","following_url":"https://api.github.com/users/DavidMacDonald/following{/other_user}","gists_url":"https://api.github.com/users/DavidMacDonald/gists{/gist_id}","starred_url":"https://api.github.com/users/DavidMacDonald/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DavidMacDonald/subscriptions","organizations_url":"https://api.github.com/users/DavidMacDonald/orgs","repos_url":"https://api.github.com/users/DavidMacDonald/repos","events_url":"https://api.github.com/users/DavidMacDonald/events{/privacy}","received_events_url":"https://api.github.com/users/DavidMacDonald/received_events","type":"User","site_admin":false},"labels":[{"id":439000385,"url":"https://api.github.com/repos/w3c/wcag21/labels/COGA","name":"COGA","color":"bfdadc","default":false},{"id":443163503,"url":"https://api.github.com/repos/w3c/wcag21/labels/MATF","name":"MATF","color":"bfd4f2","default":false},{"id":412540552,"url":"https://api.github.com/repos/w3c/wcag21/labels/Ready%20for%20WG%20Review","name":"Ready for WG Review","color":"128A0C","default":false}],"state":"open","locked":false,"assignee":{"login":"WayneEDick","id":8195607,"avatar_url":"https://avatars.githubusercontent.com/u/8195607?v=3","gravatar_id":"","url":"https://api.github.com/users/WayneEDick","html_url":"https://github.com/WayneEDick","followers_url":"https://api.github.com/users/WayneEDick/followers","following_url":"https://api.github.com/users/WayneEDick/following{/other_user}","gists_url":"https://api.github.com/users/WayneEDick/gists{/gist_id}","starred_url":"https://api.github.com/users/WayneEDick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WayneEDick/subscriptions","organizations_url":"https://api.github.com/users/WayneEDick/orgs","repos_url":"https://api.github.com/users/WayneEDick/repos","events_url":"https://api.github.com/users/WayneEDick/events{/privacy}","received_events_url":"https://api.github.com/users/WayneEDick/received_events","type":"User","site_admin":false},"assignees":[{"login":"WayneEDick","id":8195607,"avatar_url":"https://avatars.githubusercontent.com/u/8195607?v=3","gravatar_id":"","url":"https://api.github.com/users/WayneEDick","html_url":"https://github.com/WayneEDick","followers_url":"https://api.github.com/users/WayneEDick/followers","following_url":"https://api.github.com/users/WayneEDick/following{/other_user}","gists_url":"https://api.github.com/users/WayneEDick/gists{/gist_id}","starred_url":"https://api.github.com/users/WayneEDick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WayneEDick/subscriptions","organizations_url":"https://api.github.com/users/WayneEDick/orgs","repos_url":"https://api.github.com/users/WayneEDick/repos","events_url":"https://api.github.com/users/WayneEDick/events{/privacy}","received_events_url":"https://api.github.com/users/WayneEDick/received_events","type":"User","site_admin":false}],"milestone":null,"comments":15,"created_at":"2016-08-14T02:38:14Z","updated_at":"2016-12-19T18:08:12Z","closed_at":null,"body":"# SC Short Name\r\n\r\nChange of content:\r\n# SC Text\r\n\r\nProgrammatic notification is provided for each change in content that indicates an action was taken or that conveys information, unless one or more of the following is true:  <br />\r\n1. The change immediately follows the control that triggered it, in the programmatic reading order.\r\n2. There is an accessibility supported programmatic relationship between the new content and the user activated control that triggers it.\r\n3. The user has been advised of the behavior before using the component. \r\n4. There are more than 5 notifications per minute.\r\n5. The change in content is not related to the the primary purpose of the page AND is not a result of a user action.\r\n6. The user action results in a success or failure response from the page, in which case visual feedback (such as text) AND a programmatic notification are provided.\r\n\r\n# Suggested Priority Level\r\n\r\nLevel AA\r\n# Related Glossary additions or changes\r\n\r\n<ul><li><b>Programmatic notification: </b>Notification by software from data provided in a user-agent-supported manner such that the user agents can extract and present this notification to users in different modalities, without further action by the user, except for focusing on the control which caused the change, or activating the control which caused the change.</li>\r\n<li><b>Change of content: </b>Changes made to a web page after it has been delivered to the user agent, whether or not initiated by the user.</li>\r\n<li><b>Programmatic Reading Order:</b> The order that a reading device such as a screen reader parses the content. This includes focus that is managed by the web page.<br />\r\n<b>Note: </b>Usually, this is the same order as the code, and is represented as an accessibility tree.  </li>\r\n</ul>\r\n\r\n# What Principle and Guideline the SC falls within\r\n\r\nPrinciple: Perceivable<br />\r\nProposed new Guideline 1.5:\r\n<b>Notification:</b> Make it easier for users to know about changes to dynamic content\r\n# Description (Intent)\r\n\r\nThis Success Criteria is intended to help users of assistive technology be aware of changes that many users can easily see and understand. \r\nThere are a number of cases where content changes on a page after it is loaded. Users who are blind or have low vision that rely on a screen reader may have trouble knowing that information on a page changed. They may be working on the part of the page which is not near where changes have occurred on a page. It may be on a part of the web page that they have already read and wouldn't consider reviewing that part of the page for unannounced changes. \r\n\r\nThese messages would be very short in nature, such as:\r\n- \"Your shopping cart has been updated, 5 items\"\r\n- \"Your form was successfully submitted.\"\r\n- \"There are 5 results for your search\"\r\n- \"There are 3 errors on this form\"\r\n- \"Scores updated\"\r\n- \"content loading\" (when a busy indicator is onscreen)\r\n\r\nExamples of situations where this type of notification would be appropriate include:\r\n<ul>\r\n <li>Interactive controls may change the page based on a users selection</li>\r\n<li> Filter / sort selections of data already displayed on page add/remove content</li>\r\n<li>Additions and subtractions to/from a cart</li>\r\n<li>A notification that 'support by chat' is available for this task at hand, or</li>\r\n<li>Results of form submission when they are displayed on same page</li>\r\n<li>A global error message placed above the form saying \"form submission failed etc.\" or a thank you message after completion of a multi-step process, </li>\r\n<li>On switching from grid view to list view, </li>\r\n<li>In data table when sort column is changed, </li>\r\n<li>On selecting a different pagination link</li>\r\n<li>When a graphical spinning \"busy\" signal notifies visual users. </li>\r\n</ul>\r\n\r\n<p>Dynamic changes to a page sometimes cause the page to become inactive for a period of time while it is being updated. Users of assistive technology may think the page has crashed and may loose their work if they either reload the page or leave the page thinking the browser crashed. This notification will ensure they are aware that something is happening in the background, the way that sighted users are aware when they see a spinning icon or the words \"loading\". If there is no such visual indication there is no requirement in the Success Criterion to provide programmatic notification, only when there is a visual notification, is there a requirement to make that notification also programmatic. This is not about the initial wait to load a new page. Those are announced to screen readers.</p>\r\n\r\n**Note:** SC 4.1.2 covers notification of changes in content that are a result of a change in the state of a control, such as selecting a new Tab in a tabbed interface, opening and closing a menu, clicking a link or button that  opens up a dialog or tooltip.  The text of 4.1.2 is \"... states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.\"\r\n# Specific Benefits of Success Criterion \r\n\r\nUsers of assistive technology will know what changed on the page, and will be able to make decisions based on that information. \r\n## Benefits\r\n- Users who are blind will know if a shopping cart was successfully updated, or if form was successfully submitted, or if there were errors on their form.\r\n- Helps people with visual disabilities, cognitive limitations, and motor impairments by reducing the chance that a control will be accidentally activated or action will occur unexpectedly.\r\n- Individuals who are unable to detect changes on the page will be able to know what people who can see those changes know.\r\n## Justification and Evidence\r\n\r\nThis issue is currently a best practice recommended by most WCAG evaluators, and most evaluators have come across situations where a screen reader user became confused because something changed on the page that they were unaware of. There is a long thread on the mail archives which started here: https://lists.w3.org/Archives/Public/w3c-wai-gl/2016AprJun/0808.html. The current wording is a result of those discussions and has good momentum from working group members on the list.\r\n\r\nThere was an issue which filed against WCAG for WCAG next. See Issue 12 here https://www.w3.org/WAI/GL/wiki/Post_WCAG_2_Issues_Sorted \r\n## Testability\r\n\r\nThis can be tested programmatically or functionally. In the code, identify elements that show/hide content etc,  and ensure they have programming that exposes the user to notifications about this new data. Functionally, a screen reader can be run while the page is updating to determine changes to the page are announced to the user.\r\n### Related Resources\r\n\r\nThis is also in the Pearson guideline 5 http://wps.pearsoned.com/accessibility/115/29601/7577872.cw/index.html \r\n\r\nCOGA has a similar notification SC which is a little wider currently. https://rawgit.com/w3c/coga/master/extension/rapid-and-direct-feedback.html\r\n## Techniques\r\n- Using aria-live to notify a user of changes in content<br />\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/wcag21/issues/comments/268034875","html_url":"https://github.com/w3c/wcag21/issues/2#issuecomment-268034875","issue_url":"https://api.github.com/repos/w3c/wcag21/issues/2","id":268034875,"user":{"login":"WayneEDick","id":8195607,"avatar_url":"https://avatars.githubusercontent.com/u/8195607?v=3","gravatar_id":"","url":"https://api.github.com/users/WayneEDick","html_url":"https://github.com/WayneEDick","followers_url":"https://api.github.com/users/WayneEDick/followers","following_url":"https://api.github.com/users/WayneEDick/following{/other_user}","gists_url":"https://api.github.com/users/WayneEDick/gists{/gist_id}","starred_url":"https://api.github.com/users/WayneEDick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WayneEDick/subscriptions","organizations_url":"https://api.github.com/users/WayneEDick/orgs","repos_url":"https://api.github.com/users/WayneEDick/repos","events_url":"https://api.github.com/users/WayneEDick/events{/privacy}","received_events_url":"https://api.github.com/users/WayneEDick/received_events","type":"User","site_admin":false},"created_at":"2016-12-19T18:08:12Z","updated_at":"2016-12-19T18:08:12Z","body":"How can a user turn these comments off? Sometimes actions can be relevant, but you want to concentrate on what you are doing.\r\n\r\n"}}
{"actor":{"display_login":"WayneEDick"}}