Adding AccessibleObject for ListViewItem's image#7672
Conversation
Tanya-Solyanik
left a comment
There was a problem hiding this comment.
Looks good, please see my comments.
60fb54a to
d83b172
Compare
vladimir-krestov
left a comment
There was a problem hiding this comment.
It looks really complex. I would consider not using any index for the image AO at all. It will allow to keep the code more clear, we will just insert one object. But I will check if it work
d83b172 to
ad165f0
Compare
| <value>Gets or sets the parameter that is passed to the Command property's object on execution or on execution context request.</value> | ||
| </data> | ||
| <data name="ListViewItemImageAccessibleObjectDescription" xml:space="preserve"> | ||
| <value>Image of the ListViewItem.</value> |
There was a problem hiding this comment.
Does WPF have anything similar? I don't think that the current description is useful. Can we use "Image of <Item AccessibleName>" instead? Or even leave it empty?
5be2f78 to
7a91efe
Compare
|
The resources are out of sync. Please rebase on top of the latest main. |
7a91efe to
e90041a
Compare
e90041a to
d8e423e
Compare
I agree with Vladimir, maybe we can unify to having only one kind of index in the code and convert it right before it's returned to the accessibility tools. I'm not sure if conversion methods are much help |
|
I tried to rework it, but |
d8e423e to
de392c2
Compare
If you think this change makes the code more readable, then sure. I'm concerned that when this code is maintained by somebody else, they would not be able to distinguish one index from the other. |
Tanya-Solyanik
left a comment
There was a problem hiding this comment.
Looks good! I added some suggestions for naming.
|
@dmitrii-drobotov - did you have a chance to re-review the latest? |
Used AO for image inside ListViewItemImageAccessibleObject Added unit tests
de392c2 to
dea0733
Compare
|
@dmitrii-drobotov - please re-review this change. |
|
@NikitaSemenovAkvelon - please send this change to testing. |
f556107
|
CTI detected an error that image bounds don't draw on mouse navigation in AI/Inspect. I've added a fix in a separate commit to clarity. After reviewing I'll squash it with the previous one. |
Tanya-Solyanik
left a comment
There was a problem hiding this comment.
Please fix the tests.
f556107 to
7888516
Compare
|
Tested this PR fixing with no new issue found finally. |
* Added ListViewItemImageAccessibleObject Used AO for image inside ListViewItemImageAccessibleObject Added unit tests
Fixes #4690 Details.Case 2
Proposed changes
Customer Impact
Regression?
Risk
Screenshots
Before
After
Test methodology
Accessibility testing
Test environment(s)
Microsoft Reviewers: Open in CodeFlow