content/test/data/accessibility/input-text-name-calc-expected-win.txt - Issue 10823073: Improve accessible name calculation on Windows.

Side by Side Diff: content/test/data/accessibility/input-text-name-calc-expected-win.txt

Issue 10823073: Improve accessible name calculation on Windows. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Remove unintentionally modified file Created 8 years, 4 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
(Empty)
	1 ROLE_SYSTEM_DOCUMENT name='' READONLY FOCUSABLE description=''

	2 IA2_ROLE_SECTION name='' READONLY description=''

	3 ROLE_SYSTEM_TEXT name='Title' FOCUSABLE description=''

	4 ROLE_SYSTEM_TEXT name='Label' FOCUSABLE description='Title'

	5 ROLE_SYSTEM_TEXT name='AriaLabel' FOCUSABLE description='Title'

	6 ROLE_SYSTEM_TEXT name='LabelledBy' FOCUSABLE description='Title'

	7 ROLE_SYSTEM_TEXT name='Placeholder' FOCUSABLE description=''
	aboxhall 2012/08/01 01:56:57 Placeholder is not mentioned in the accessible nam Placeholder is not mentioned in the accessible name computation either, but I agree it makes sense to use it in this way (including combining it with the title). dmazzoni 2012/08/01 03:22:41 It's here: http://www.w3.org/TR/html-aapi/#calc W Show quoted text On 2012/08/01 01:56:57, aboxhall wrote: > Placeholder is not mentioned in the accessible name computation either, but I > agree it makes sense to use it in this way (including combining it with the > title). It's here: http://www.w3.org/TR/html-aapi/#calc Were you looking at the ARIA platform implementation guide? I looked at that one too, but the AAPI seemed to be a little more specific about how to apply it to platform-specific attributes. It's quite possible they conflict. :( aboxhall 2012/08/06 01:55:49 Yep, I was looking at the ARIA guide. They don't q Show quoted text On 2012/08/01 03:22:41, Dominic Mazzoni wrote: > On 2012/08/01 01:56:57, aboxhall wrote: > > Placeholder is not mentioned in the accessible name computation either, but I > > agree it makes sense to use it in this way (including combining it with the > > title). > > It's here: > http://www.w3.org/TR/html-aapi/#calc > > Were you looking at the ARIA platform implementation guide? I looked at that one > too, but the AAPI seemed to be a little more specific about how to apply it to > platform-specific attributes. > > It's quite possible they conflict. :( Yep, I was looking at the ARIA guide. They don't quite conflict (both agree on the label > title > placeholder precedence order), but they are a bit ambiguous taken together where the description is concerned.
	8 ROLE_SYSTEM_TEXT name='Title' FOCUSABLE description='Placeholder'

	9 ROLE_SYSTEM_TEXT name='Label' FOCUSABLE description='Title Placeholder'

	10 ROLE_SYSTEM_TEXT name='AriaLabel' FOCUSABLE description='Title Placehold er'

	11 ROLE_SYSTEM_TEXT name='LabelledBy' FOCUSABLE description='Title Placehol der'

	12 ROLE_SYSTEM_TEXT name='LabelledBy' FOCUSABLE description='DescribedBy Pl aceholder'
	aboxhall 2012/08/01 01:56:57 I'm not sure we want to include the placeholder if I'm not sure we want to include the placeholder if there is an aria-describedby attribute. I would expect developers to include all necessary information in the description. Do other browsers do it this way? aboxhall 2012/08/06 01:55:49 I still think this shouldn't include the placehold Show quoted text On 2012/08/01 01:56:57, aboxhall wrote: > I'm not sure we want to include the placeholder if there is an aria-describedby > attribute. I would expect developers to include all necessary information in the > description. Do other browsers do it this way? I still think this shouldn't include the placeholder, at least going by my reading of the specs. If there is a precedent for this, and you think this is better, then I guess an argument could be made, but based on the spec I don't see why you'd include placeholder, and especially not placeholder but not title, given title has a higher precedence.
OLD	NEW

« content/test/data/accessibility/checkbox-name-calc.html ('K') | « content/test/data/accessibility/input-text-name-calc-expected-mac.txt ('k') | no next file » | no next file with comments »