wicg / accessible-loading-and-searching-of-content Goto Github PK
View Code? Open in Web Editor NEWEnable ATs to recognize and account for virtualized content when navigating a web page.
License: Other
Enable ATs to recognize and account for virtualized content when navigating a web page.
License: Other
In review of more app scenarios there appears to be a clear need for a mechanism that allows authors to register shortcuts or actions that can be fired by ATs in order to load more virtualized content.
The default behavior of loading content, as specified by the proposal, is for an AT to trigger scrollIntoVIew
to the element marked as aria-virtualcontent
. There are many advantages of this approach - author side script that's handling content loading wouldn't recognize if a scroll was triggered by AT or user (privacy); most apps that virtualize content between server/client today are already tuned to handle loading based on scroll (low author cost), etc.
However, there are use cases of input being redirected and captured by app logic in order to provide more advanced content handling. It will be helpful to enable authors to specify the shortcuts used for fetching content.
The concern here is if the user is using the AT to search for content and that content is outside of the virtual-content element, the AT will scroll the the virtual-content region until there's no more scrolling (...what happens in infinite scrolling cases...) before searching outside of the virtual-content element.
This could result in poor performance and overall experience for the user, and in the worst case, like infinite scrolling, the user could become "suck" in the virtual-content element
ATs often pull details such as the heading structure on a page or section of a page so they can present the number and depth of headings without actually having the user navigate by heading. It would be useful to perhaps query for this information without causing a visual change that might impact sighted users of assistive technology.
Checking for status of this incubation. There appears to have been little activity in the last few years so wondering if this repository can be archived?
Unless anyone objects, we will archive this in a week or so.
Essentially re-stating #4: can we come up with ways to provide AT users with familiar interactions like find in page and go to next heading, in such a way that the use of AT is not revealed to the page?
This might look like providing well-known, or author-registerable, keyboard shortcuts for a specific vocabulary of actions.
For example, if "Ctrl Alt H" was a well known keyboard shortcut to go to the next heading, a non-AT user could hit that shortcut to signal to the page to fetch content through the next heading. Conversely, an AT user could use their normal "go to next heading" interaction with the AT, and the browser could forward that intent as a keyboard event combination to the page, making it indistinguishable to the page whether or not an AT was used.
Can we change the name of the repo to something more agnostic, like “accessible loading or searching of content”? Leaving the repo titled with the proposed solution limits the flexibility of an incubation effort. Even if we all agreed on a declarative approach, there were specific concerns with the term "virtual" as people though it might be related to virtual reality (VR) interfaces, or associated with the AOM effort to load a virtual accessibility tree for HTML <canvas>
or other custom views.
In addition to the proposed declarative approach (specifically “aria-virtualcontent” or other ones we discussed), there was chatter that this might be solved a number of other ways. For example, common AT actions (like jump to next heading) could be mapped to web-app-specific commands (opt-h?). There are probably a number of other ways to solve these problems, including new JavaScript API.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.