W3C

– DRAFT –
Exploring making site navigation more accessible, with "well-known destinations"

12 March 2024

Attendees

Present
janina
Regrets
-
Chair
Matthew Atkinson
Scribe
Lionel_Wolberger

Meeting minutes

<gb> Issue 10 Exploring making site navigation more accessible, with "well-known destinations" (by matatk) [session]

Pick a scribe

Lionel_Wolberger: Scribe is picked

Reminders: code of conduct, health policies, recorded session policy

Lionel_Wolberger: Code of conduct, https://www.w3.org/policies/code-of-conduct/

Lionel_Wolberger: Anti-trust, https://www.w3.org/policies/antitrust-2024/

Goal of this session

matatk_: Recording permission requested and granted

Lionel_Wolberger: Introduced the speakers and the topic

Slides for our session: https://raw.githack.com/w3c/adapt/main/presentations/breakouts-day-2024/

matatk_: Sharing screen, what is this all about.

matatk_: Presented the slides.

matatk_: Paused the recording to show the demo

matatk_: In a sample ecommerce site, an extension queries the website and asks, which well known destinations do you support?
… a dropdown list appears displaying which WKDs are supported on this site
… now changing to a different sample site
… this one is an informational site, with pages regarding a particular topic
… in the dropdown list fewer WKDs are shown on this site
… showing that the WKD is dynamic, portable, and can differ depending on site
… resumed recording

Abhinav: Presented the following slides, starting with "build on existing infrastructure"

matatk_: Presenting the last slides, starting with 'Next Steps'

matatk_: Last slide, recording stopped for discussion

<matatk_> w3c/adapt

Lionel_Wolberger: Note the spec supports human access to these well known destinations, by browsing to the well-known URL

janina: We could also support graying out functionality that is not germane to the functionality of the well-known destination

Daniel: How will this specification be localized to other languages? Will the folder path and term 'well-known' be translated to other languages?

matatk_: These are defined strings, that can be rendered in the localized language
… or even not in language, but in symbols
… once the infrastructure is in place, any terminology can be applied in the UI

Daniel: Indeed. A screen reader would read it in audio as well

<Zakim> dmontalvo, you wanted to ask for localization in an internationalization context

Lionel_Wolberger: The latin letters defined by the IANA spec, /well-known/ia, would need to be added to a site, regardless of the language of the site

matatk_: I can add to the demo a non-english language website to illustrate this
… and the explainer should make this clear
… perhaps using the word 'token' to refer to these strings required by WKD, to ensure people understand they are not there for their semantic meaning

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

Maybe present: Abhinav, Daniel, Lionel_Wolberger, matatk_

All speakers: Abhinav, Daniel, janina, Lionel_Wolberger, matatk_

Active on IRC: dmontalvo, janina, Lionel_Wolberger, matatk_, tpac-breakout-bot