This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22929 - input type text and other text inputs may share the description
Summary: input type text and other text inputs may share the description
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2013-08-13 02:13 UTC by alexander surkov
Modified: 2013-08-16 10:14 UTC (History)
6 users (show)

See Also:

Attachments

Description alexander surkov 2013-08-13 02:13:00 UTC 
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?
Comment 1 Jason Kiss 2013-08-14 07:44:52 UTC 
(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?
Comment 2 alexander surkov 2013-08-14 12:10:58 UTC 
(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
Comment 3 steve faulkner 2013-08-16 09:08:13 UTC 
(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
Comment 4 Jason Kiss 2013-08-16 10:14:20 UTC 
(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.