-
Notifications
You must be signed in to change notification settings - Fork 0
[pull] gh-pages from WICG:gh-pages #2
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
Open
pull
wants to merge
32
commits into
Qdigital:gh-pages
Choose a base branch
from
WICG:gh-pages
base: gh-pages
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update and clarify API shape After some recent internal experiementation and research into other ATs and a variety of offline feedback, we're updating our proposal. Notable changes include: * API `ariaNotify` now support on elements (not just the document) * Lots of clarity on the queuing behaviors and control surface for web authors
…to make it clear InputEvents are abandoned, and not related to the implemented "User Action Events from AT" section.
Resolves #190 I think
m. cross-referencing some relevant notes with superscript footnote indicators.
* Update notification-api.md * Match the changes to the Readme file.
Updated problem statement, use cases Updated prose around API usage and queue management New labelling feature for potential screen reader notification customizations Updated parameter and parameter values New parameter for interruptibility New specification for clearing queues
Removed `progress bar` since that widget type is not expected to be user-adjustable.
`ariaActiveDescendantElement` was misspelled
… have been abandoned
ExportID feature explainer. --------- Co-authored-by: Alice Boxhall <95208+alice@users.noreply.github.com>
…e TAG issue, rather than "no"
* Add reference to most recent AriaNotify explainer * Update notification API with link to up-to-date explainer. * Add a note in README.md pointing to updated explainer. * Update contacts
Reference Target is a new feature that enables creating ARIA links to elements inside a component's shadow DOM, while maintaining encapsulation of the internal details of the shadow DOM.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )