{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/wcag21/issues/806","repository_url":"https://api.github.com/repos/w3c/wcag21","labels_url":"https://api.github.com/repos/w3c/wcag21/issues/806/labels{/name}","comments_url":"https://api.github.com/repos/w3c/wcag21/issues/806/comments","events_url":"https://api.github.com/repos/w3c/wcag21/issues/806/events","html_url":"https://github.com/w3c/wcag21/issues/806","id":305575386,"number":806,"title":"Addressing weak SC Classifications","user":{"login":"mbgower","id":14298245,"avatar_url":"https://avatars1.githubusercontent.com/u/14298245?v=4","gravatar_id":"","url":"https://api.github.com/users/mbgower","html_url":"https://github.com/mbgower","followers_url":"https://api.github.com/users/mbgower/followers","following_url":"https://api.github.com/users/mbgower/following{/other_user}","gists_url":"https://api.github.com/users/mbgower/gists{/gist_id}","starred_url":"https://api.github.com/users/mbgower/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbgower/subscriptions","organizations_url":"https://api.github.com/users/mbgower/orgs","repos_url":"https://api.github.com/users/mbgower/repos","events_url":"https://api.github.com/users/mbgower/events{/privacy}","received_events_url":"https://api.github.com/users/mbgower/received_events","type":"User","site_admin":false},"labels":[{"id":823801349,"url":"https://api.github.com/repos/w3c/wcag21/labels/CR%20Comment","name":"CR Comment","color":"b13fe2","default":false},{"id":573513250,"url":"https://api.github.com/repos/w3c/wcag21/labels/Member%20Comment","name":"Member Comment","color":"d4c5f9","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":18,"created_at":"2018-03-15T14:28:23Z","updated_at":"2018-03-16T17:40:09Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I sent the below material out last year. Given the discussion on 1.3.4 and 3.2.6 -- and the clear inference that changes in classification are allowed at this stage in the process -- I want to submit a review of all the SCs listed here as an issue for consideration. I have not altered my original material, other than updating changes to the SC language since the December draft (which I've noted in square brackets). \r\n\r\n**Identify Common Purpose** [Same name but language only covers inputs now] - under Perceivable>Adaptable. I get the SC can be theoretically used to do adaptation, but it doesn't really fit with what is covered by the [webaim Transformability](https://webaim.org/articles/pour/perceivable) topic. Surely its primary purpose is [Understandable](https://webaim.org/articles/pour/understandable). Again, realizing this is webaim material not w3c, the topics on meaning seem perfectly aligned. Not a great fit in a subcategory... Readable, isn't horrible. Input Assistance is bang on for the input purposes.\r\n\r\n**Identify Purpose** [previously Contextual Information]- also under Perceivable>Adaptable. Same argument as Identify Common Purpose. Should be Understandable\r\n\r\n**Reflow** - under Perceivable>Distinguishable. Seems to make more sense under Perceivable>Adaptable. The very title of the SC is something of an argument for this. I understand this is more of a subtle difference, but taking in all the criteria in these two subcategories, it seems to make more sense.\r\n\r\n**Text spacing** - also under Perceivable>Distinguishable. Same argument as Reflow. The SC is about adapting the text. Seems to meet the short description of Adaptable: \"presented in different ways (for example simpler layout) without losing information or structure.\" \r\n\r\n**Content on Hover of Focus** - also under Perceivable>Distinguishable. I get that the goal of this is to ensure everyone can take advantage of the content, but a dispassionate examination of the actual language of the SC suggests that it is dictating Operation. As a double-barrelled SC, it belongs under both Keyboard Accessible and Pointer Accessible. A pragmatic compromise may be to dump it under Navigable with some cross references or something.\r\n\r\nAccessible Authentication [no longer in the CR] - under Operable>Enough time.  Definitely agree it belongs under Operable, but since there is no time factor in the SC, it is a loose fit. There isn't really anywhere better. It could be possibly addressed by altering 2.6 from Additional Sensor Inputs to something more generic like Additional Modalities.\r\n\r\n**Animation from Interactions** - under Operable>Enough time. Originally the language had some timing factors in it, so was an 'okay' fit. But there is no time consideration now. I think it much more appropriately belongs under Operable>Seizures. I'd also advocate the \"Seizures\" category be reworded and broadened, but I guess that would be a 2.0 normative change and so is sacrosanct.\r\n\r\n**Character Key Shortcuts** - under Operable>Navigable. I think this fits better under Operable>Keyboard Accessible. Yes, it is there because of voice control, but ultimately it's about an unambiguous keyboard affordance. If people buy into my Operable>Additional Modalities suggestion, it could also fit quite comfortably in there.\r\n\r\n**Label in Name** - under Operable>Navigable. Makes more sense under the proposed Operable>Additional Modalities suggestion. Can actually clarify intent, just by being located there, as otherwise very unclear from from SC language alone what the intent is.\r\n\r\nMost Pointer SCs (Gestures, Cancellation, Target Size) - fine as is except...\r\n\r\n**Concurrent Input Mechanisms** - under Operable>Pointer Accessible. Since this covers a whole lot more than pointer, it makes a lot more sense under Operable>Additional Modalities.\r\n\r\n**Status Changes** - under Operable>Predictable. I think this actually makes more sense under Perceivable. Subcategory? Probably Distinguishable, or maybe Adaptable.\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/wcag21/issues/comments/373790425","html_url":"https://github.com/w3c/wcag21/issues/806#issuecomment-373790425","issue_url":"https://api.github.com/repos/w3c/wcag21/issues/806","id":373790425,"user":{"login":"alastc","id":216630,"avatar_url":"https://avatars2.githubusercontent.com/u/216630?v=4","gravatar_id":"","url":"https://api.github.com/users/alastc","html_url":"https://github.com/alastc","followers_url":"https://api.github.com/users/alastc/followers","following_url":"https://api.github.com/users/alastc/following{/other_user}","gists_url":"https://api.github.com/users/alastc/gists{/gist_id}","starred_url":"https://api.github.com/users/alastc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alastc/subscriptions","organizations_url":"https://api.github.com/users/alastc/orgs","repos_url":"https://api.github.com/users/alastc/repos","events_url":"https://api.github.com/users/alastc/events{/privacy}","received_events_url":"https://api.github.com/users/alastc/received_events","type":"User","site_admin":false},"created_at":"2018-03-16T17:40:09Z","updated_at":"2018-03-16T17:40:09Z","author_association":"CONTRIBUTOR","body":"Just to summarise in situe, I think that would look like this, with asterix at the start of each change.\r\n\r\n```\r\n1. Perceivable\r\n    1.1 Text Alternatives\r\n...\r\n    1.3 Adaptable\r\n        1.3.1 Info and Relationships\r\n        1.3.2 Meaningful Sequence\r\n        1.3.3 Sensory Characteristics\r\n*       1.3.4 Status Changes (I’ve no problem with 4.1.x for this)\r\n    1.4 Distinguishable\r\n        1.4.1 Use of Color\r\n        1.4.2 Audio Control\r\n...\r\n \r\n2. Operable\r\n \r\n...\r\n*   2.3 Seizures and physical reactions\r\n        2.3.1 Three Flashes or Below Threshold\r\n        2.3.2 Three Flashes\r\n*       2.3.3 Animation from Interactions\r\n    2.4 Navigable\r\n        2.4.1 Bypass Blocks\r\n...\r\n    2.5 Pointer Accessible\r\n        2.5.1 Pointer Gestures\r\n        2.5.2 Pointer Cancellation\r\n        2.5.3 Target Size\r\n       2.5.4 Concurrent Input Mechanisms\r\n*   2.6 Other modalities\r\n        2.6.1 Motion Actuation\r\n        2.6.2 Orientation\r\n*       2.6.3 Label in Name\r\n*       2.6.4 Character Key Shortcuts\r\n \r\n3. Understandable\r\n \r\n*   3.1 Meaningful\r\n        3.1.1 Language of Page\r\n        3.1.2 Language of Parts\r\n        3.1.3 Unusual Words\r\n        3.1.4 Abbreviations\r\n        3.1.5 Reading Level\r\n        3.1.6 Pronunciation\r\n*       3.1.7 Identify Input Purpose\r\n  (just throwing ‘input’ in – if we add others, it needs to still work)\r\n*       3.1.8 Identify Purpose\r\n    3.2 Predictable\r\n...\r\n```"}}
{"actor":{"display_login":"alastc"}}