Skip to content

Details and Summary mappings should include details/details-for AtkRelationType #147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
joanmarie opened this issue Sep 5, 2018 · 3 comments · Fixed by #224
Closed

Details and Summary mappings should include details/details-for AtkRelationType #147

joanmarie opened this issue Sep 5, 2018 · 3 comments · Fixed by #224

Comments

@joanmarie
Copy link
Contributor

ATK has the following relation types:

ATK_RELATION_DETAILS
Reciprocal of ATK_RELATION_DETAILS_FOR. Indicates that this object has a detailed or extended description, the contents of which can be found in the target object(s). This relation type is most appropriate for information that is sufficiently lengthy as to make navigation to the container of that information desirable. For less verbose information suitable for announcement only, see ATK_RELATION_DESCRIBED_BY. If the detailed information describes an error condition, ATK_RELATION_ERROR_FOR should be used instead. Since : ATK-2.26.

ATK_RELATION_DETAILS_FOR
Reciprocal of ATK_RELATION_DETAILS. Indicates that this object provides a detailed or extended description about the target object(s). See also ATK_RELATION_DESCRIPTION_FOR and ATK_RELATION_ERROR_FOR. Since : ATK-2.26.

These should be included in the implementations of the details and summary elements so that Orca can quickly figure out what information should be presented upon expansion of the element.

@scottaohara
Copy link
Member

ping @stevefaulkner

let's look at this next week per our discussion today.

@scottaohara
Copy link
Member

@joanmarie, i'm going to include this work with my PR #224 and will let you know as soon as I get that done for review.

sound good?

@joanmarie
Copy link
Contributor Author

Yup! Thanks @scottaohara.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants