{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/wcag21/issues/883","repository_url":"https://api.github.com/repos/w3c/wcag21","labels_url":"https://api.github.com/repos/w3c/wcag21/issues/883/labels{/name}","comments_url":"https://api.github.com/repos/w3c/wcag21/issues/883/comments","events_url":"https://api.github.com/repos/w3c/wcag21/issues/883/events","html_url":"https://github.com/w3c/wcag21/issues/883","id":317698631,"number":883,"title":"1.4.4 Resize Text - Misunderstandings Update - Interpretation","user":{"login":"joe-watkins","id":3695795,"avatar_url":"https://avatars0.githubusercontent.com/u/3695795?v=4","gravatar_id":"","url":"https://api.github.com/users/joe-watkins","html_url":"https://github.com/joe-watkins","followers_url":"https://api.github.com/users/joe-watkins/followers","following_url":"https://api.github.com/users/joe-watkins/following{/other_user}","gists_url":"https://api.github.com/users/joe-watkins/gists{/gist_id}","starred_url":"https://api.github.com/users/joe-watkins/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joe-watkins/subscriptions","organizations_url":"https://api.github.com/users/joe-watkins/orgs","repos_url":"https://api.github.com/users/joe-watkins/repos","events_url":"https://api.github.com/users/joe-watkins/events{/privacy}","received_events_url":"https://api.github.com/users/joe-watkins/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":22,"created_at":"2018-04-25T16:16:53Z","updated_at":"2018-04-27T23:35:41Z","closed_at":null,"author_association":"NONE","body":"Hi! \r\n\r\nThroughout WCAG `1.4.4` Techniques there is reference to an upcoming clarification around a common misunderstanding of this SC. Is it text-only resize or browser zoom? Nobody knows.. is it both?\r\n\r\n**The callout states**:\r\nhttps://www.w3.org/TR/WCAG20-TECHS/F69\r\n\r\n> Note: The Working Group has discovered many misunderstandings about how to test this failure. We are planning to revise this failure in a future update. Until then, if the content passes the success criterion using any of the listed sufficient techniques, then it does not meet this failure.\r\n\r\nThere is disagreement around how this SC is interpreted. Some folks believe a browser zoom (where everything just scales up ctrl +/-) is a sufficient technique, while others interpret the SC so that enlarging the text only to 200% must not cause the text, image or controls to be clipped, truncated or obscured. I lean towards the latter myself.\r\n\r\nWith the responsive web, it is pretty easy to create an experience that would pass this SC with it only being browser zoom with modern browsers that support media queries and that have great browser zoom. Authoring experiences that work with text-only resize is much more difficult and relies on fluid non-fixed sizing.\r\n\r\nBoth Firefox and Safari allow for text-only as an option for native browser zoom now which makes things interesting.\r\n\r\nWhen will we see an update to some of these failures bringing more clarity around this SC? `2.1`?\r\n\r\nThanks for all your hard work :)\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/wcag21/issues/comments/385119184","html_url":"https://github.com/w3c/wcag21/issues/883#issuecomment-385119184","issue_url":"https://api.github.com/repos/w3c/wcag21/issues/883","id":385119184,"user":{"login":"patrickhlauke","id":895831,"avatar_url":"https://avatars1.githubusercontent.com/u/895831?v=4","gravatar_id":"","url":"https://api.github.com/users/patrickhlauke","html_url":"https://github.com/patrickhlauke","followers_url":"https://api.github.com/users/patrickhlauke/followers","following_url":"https://api.github.com/users/patrickhlauke/following{/other_user}","gists_url":"https://api.github.com/users/patrickhlauke/gists{/gist_id}","starred_url":"https://api.github.com/users/patrickhlauke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/patrickhlauke/subscriptions","organizations_url":"https://api.github.com/users/patrickhlauke/orgs","repos_url":"https://api.github.com/users/patrickhlauke/repos","events_url":"https://api.github.com/users/patrickhlauke/events{/privacy}","received_events_url":"https://api.github.com/users/patrickhlauke/received_events","type":"User","site_admin":false},"created_at":"2018-04-27T23:35:41Z","updated_at":"2018-04-27T23:35:41Z","author_association":"MEMBER","body":"1.4.4 says \"text can be resized\", without specifying how. whether you're getting different results depending on *how* a user chooses to resize, that's generally unimportant. what counts is: does at least one of these ways of resizing end up with the user being able to resize text \"up to 200 percent without loss of content or functionality\"? and of course, the method should be readily available to users (which arguably means, on desktop, we're likely looking at full-page zoom)"}}
{"actor":{"display_login":"patrickhlauke"}}