8000 Clarify ARIA, AOM and computed attributes by alice · Pull Request #64 · WICG/aom · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Clarify ARIA, AOM and computed attributes #64

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

Merged
merged 6 commits into from
Mar 17, 2017
Merged

Conversation

alice
Copy link
Member
@alice alice commented Mar 16, 2017

@@ -341,70 +348,77 @@ input.accessibleNode.activeDescendant = optionList.accessibleNode;

This would allow the relationship to be expressed naturally.

#### No reflection
#### AOM and ARIA
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may be obvious but should we explicitly define AOM the first time before using it as an acronym?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, done.

explainer.md Outdated
`clickBtn` would have a computed role of `"button"`
even though its `accessibleNode` has a `role` of `"link"`.

This means that:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This final paragraph sums up the overall "No reflection" section, but it appears to just be part of the "ARIA takes precedence" section. Maybe it needs a tiny subheading too?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, done.

explainer.md Outdated
it needs to work consistently across browsers,
so that developers don't need to write special case code for each.

Before we can create an API which allows accessing the computed properties,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence is kind of redundant with the previous paragraph. How about something like, we believe it will be possible to create an API that's consistent but it's significantly more complicated than the first three phases.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed re redundancy; reworded slightly differently from your suggestion.

Copy link
Collaborator
@minorninth minorninth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a few suggestions

@alice alice merged commit e0a802f into WICG:master Mar 17, 2017
@alice alice deleted the computed branch March 17, 2017 04:43
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 this pull request may close these issues.

2 participants
0