22929 2013-08-13 02:13:00 +0000 input type text and other text inputs may share the description 2013-08-16 10:14:20 +0000 1 1 1 Unclassified HTML WG HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) unspecified PC All NEW a11y P2 normal --- 1 surkov.alexander faulkner.steve jason mark.sadecki+w3c mike public-html-admin public-html-bugzilla public-html-wg-issue-tracking sideshowbarker+html-a11y-api oldest_to_newest 91955 0 surkov.alexander 2013-08-13 02:13:00 +0000 input type text, email, tel etc have own descriptions, it should be nice to combine them into one item (note, these elements in case of autocomplete share the same description). Sounds good? 92028 1 jason 2013-08-14 07:44:52 +0000 (In reply to comment #0) > input type text, email, tel etc have own descriptions, it should be nice to > combine them into one item (note, these elements in case of autocomplete > share the same description). Sounds good? Possibly. input type search has a different AXRoleDescription. I wouldn't be surprised if things like type email and tel get different AXRoleDescriptions somewhere along the way. Perhaps we can leave them for now, until we can be certain which input types will have identical mappings across all APIs, and then at that time combine those that do into a single entry? 92039 2 surkov.alexander 2013-08-14 12:10:58 +0000 (In reply to comment #1) > (In reply to comment #0) > > input type text, email, tel etc have own descriptions, it should be nice to > > combine them into one item (note, these elements in case of autocomplete > > share the same description). Sounds good? > > Possibly. input type search has a different AXRoleDescription. I wouldn't be > surprised if things like type email and tel get different AXRoleDescriptions > somewhere along the way. Perhaps we can leave them for now, until we can be > certain which input types will have identical mappings across all APIs, and > then at that time combine those that do into a single entry? ok, makes sense, then the same must applicable to these controls having associated autocomplets, currently they are merged into single item 92143 3 faulkner.steve 2013-08-16 09:08:13 +0000 (In reply to comment #1) > (In reply to comment #0) > > input type text, email, tel etc have own descriptions, it should be nice to > > combine them into one item (note, these elements in case of autocomplete > > share the same description). Sounds good? > > Possibly. input type search has a different AXRoleDescription. I wouldn't be > surprised if things like type email and tel get different AXRoleDescriptions > somewhere along the way. Perhaps we can leave them for now, until we can be > certain which input types will have identical mappings across all APIs, and > then at that time combine those that do into a single entry? agree with jason here as UI may differ dependent type 92148 4 jason 2013-08-16 10:14:20 +0000 (In reply to comment #2) > ok, makes sense, then the same must applicable to these controls having > associated autocomplets, currently they are merged into single item That makes sense. I propose we wait until after heartbeat then confirm appropriate mappings and split into separate mappings where necessary.