- From: Lionel Wolberger <lionel@userway.org>
- Date: Mon, 27 Mar 2023 18:24:51 +0300
- To: public-a11yedge@w3.org
- Cc: Janina Sajka <janina@rednote.net>
- Message-ID: <CAHOHNHdZySV4JzSYYBjj54Gf45keEr3vZ4-HTjC-xSrH8_uXJQ@mail.gmail.com>
Hi All, Sharing some discussion from the Teleconference 20 Monday 2023. Sharing this for further discussion, which will have an impact on our document. This is an opportunity to note the URI to the Capabilities document, https://a11yedge.github.io/capabilities. Discussed: External Link Targets: The validation of external link targets at the time of page load -- meaning at the edge -- is useful, as many links may 'rot' since they were authored. Some URLs will resolve on content that does not replace the content being looked for; e.g., a link that now goes to malware. This can occur as links age, rot or are attacked. Invocation and dismissal: The invocation of edge accessibility capabilities should be a distinctive action. On mobile the touch targets should not be adjacent to other touch targets. Closing overlays needs to be simple, obvious, intuitive. Also consider the back button. Provenance: The Web is built for mingling, mixing and hosting of components. In general it would be useful to be able to understand the provenance of components, interactive widgets and data services on a page. Many advertisements have a small "i" for information button, giving some provenance information-- this is an example of providing the information discussed here. Edge technologies including JavaScript interactive components, accessibility overlays, cookie management overlays, chat overlays, user-agent extensions and so on should have a method for revealing their provenance. - Lionel, scribing for the Accessibility at the Edge Community Group. Join us on Mondays, https://www.w3.org/groups/cg/a11yedge/calendar
Received on Monday, 27 March 2023 15:25:43 UTC