{"action":"created","issue":{"url":"https://api.github.com/repos/18F/web-design-standards/issues/751","labels_url":"https://api.github.com/repos/18F/web-design-standards/issues/751/labels{/name}","comments_url":"https://api.github.com/repos/18F/web-design-standards/issues/751/comments","events_url":"https://api.github.com/repos/18F/web-design-standards/issues/751/events","html_url":"https://github.com/18F/web-design-standards/issues/751","id":108906420,"number":751,"title":"Consistency of input types, dates should be a single field","user":{"login":"IDisposable","id":874059,"avatar_url":"https://avatars.githubusercontent.com/u/874059?v=3","gravatar_id":"","url":"https://api.github.com/users/IDisposable","html_url":"https://github.com/IDisposable","followers_url":"https://api.github.com/users/IDisposable/followers","following_url":"https://api.github.com/users/IDisposable/following{/other_user}","gists_url":"https://api.github.com/users/IDisposable/gists{/gist_id}","starred_url":"https://api.github.com/users/IDisposable/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/IDisposable/subscriptions","organizations_url":"https://api.github.com/users/IDisposable/orgs","repos_url":"https://api.github.com/users/IDisposable/repos","events_url":"https://api.github.com/users/IDisposable/events{/privacy}","received_events_url":"https://api.github.com/users/IDisposable/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-29T16:25:44Z","updated_at":"2015-09-29T18:01:27Z","closed_at":null,"body":"Giving this;\r\n> Avoid breaking numbers with distinct sections (such as phone numbers, Social Security Numbers, or credit card numbers) into separate input fields.\r\n\r\nI have to strongly disagree with this:\r\n> Three text fields are the easiest way for users to enter most dates.\r\n\r\nPlease change this to a more reasonable single input field.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/18F/web-design-standards/issues/comments/144136972","html_url":"https://github.com/18F/web-design-standards/issues/751#issuecomment-144136972","issue_url":"https://api.github.com/repos/18F/web-design-standards/issues/751","id":144136972,"user":{"login":"jcbelanger","id":1147452,"avatar_url":"https://avatars.githubusercontent.com/u/1147452?v=3","gravatar_id":"","url":"https://api.github.com/users/jcbelanger","html_url":"https://github.com/jcbelanger","followers_url":"https://api.github.com/users/jcbelanger/followers","following_url":"https://api.github.com/users/jcbelanger/following{/other_user}","gists_url":"https://api.github.com/users/jcbelanger/gists{/gist_id}","starred_url":"https://api.github.com/users/jcbelanger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcbelanger/subscriptions","organizations_url":"https://api.github.com/users/jcbelanger/orgs","repos_url":"https://api.github.com/users/jcbelanger/repos","events_url":"https://api.github.com/users/jcbelanger/events{/privacy}","received_events_url":"https://api.github.com/users/jcbelanger/received_events","type":"User","site_admin":false},"created_at":"2015-09-29T18:01:27Z","updated_at":"2015-09-29T18:01:27Z","body":"I also strongly agree.  You should always avoid trying to be clever and use a single, traditional input.  My reasons are:\r\n\r\n* A field broken into sections also requires proper aria markup to ensure each section is properly handled readers.\r\n* How form errors be represented to a screen reader when the input is split into sections?\r\n* This prevents the user from selecting the entire input (to copy/paste or clear contents).\r\n* A user should be able to input for a field without having to hit tab / use the mouse.  The extra steps are not conventional and can cause issues for users with cognitive/motor disabilities!\r\n  * A field broken into sections often includes scripting to manage field focus / cursor placement.  This will not work without JavaScript enabled.\r\n  * Even changing the user focus pragmatically can be distracting and can cause issues for people with cognitive disabilities if it isn't exactly as they expect / used to.\r\n  * If focus goes forward to the next section automatically, it should go backwards automatically with backspace.  This means supporting ALL of the platforms cursor keyboard shortcut conventions: shift+left/right=select text, ctrl+left=move cursor a word in reverse, ctrl+shift+left = move cursor and select a word in reverse, home/end/etc...  This all has to work across potentially multiple sections!  Any mix can cause issues for users with cognitive/motor disabilities!\r\n"}}