– DRAFT –
Monday 9 October Adapt Task Force Weekly Teleconference

Introductions and New Members

Lionel_Wolberger: Introduced myself as co-facilitator of this group

Abhinav: Excited to work on well known URL

<Abhinav> present

rrsagent make minutes

Review open issues

Lionel: The following are the leading open issues

Abhinav: Can you clarify how a symbol is associated with a given word?

Lionel_Wolberger: Lionel showed the markup method in https://w3c.github.io/adapt/symbols/ and the registry https://www.w3.org/TR/aac-registry/

Lionel_Wolberger: I have an action to provide the handout as marked up HTML. To be done by next week.

Gap Analysis, https://github.com/w3c/adapt/wiki/Gap-Analysis

Lionel_Wolberger: The gap analysis is here, https://github.com/w3c/adapt/wiki/Gap-Analysis,-WAI-Adapt-Content-Attributes

Lionel_Wolberger: We see an overlap in the ideas behind 'destination' with the new direction towards 'well known URL'
… for example, on many web pages, there is a convention that the company logo is a link to the home page
… sometimes, this is decorated with a small 'house' icon, expressing visually that the destination is 'home' for the site
… if we look at the SAP home page, https://www.sap.com/index.html, convention indicates that this is the 'home page' but there is no specifid semantics stating this
… the 'destination' attribute enables a solution to this potential problem

Abhinav: Please elaborate on the benefits of 'destination'

Lionel_Wolberger: The destination markup would enable AT to announce 'home' whereas now, there is nothing (beyond convention) to indicate that this is the home page

Abhinav: But it is a logo, doesn't that confuse things?

Lionel_Wolberger: (Did a demonstration of VoiceOver. It said Image, SAP, visited link.
… with 'destination' the screen reader could announce, 'Home' which would be a better experience.

Lionel_Wolberger: The spec for well known URI, https://www.ietf.org/rfc/rfc8615.txt
… with the list of registered well known URIs here, https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml

Vikas: We have some preliminary thoughts that we are ready to present.

Abhinav: We have a document to share to anchor this discussion, how do we share it?

Lionel_Wolberger: You can send to the public list public-adapt@w3.org
… or provide an online link here in the IRC

Abhinav: Sharing screen, to share this preliminary version
… section one, introduction, showing the example of security.txt
… section two, the need for simplified access to expected accessibility deliverables such as the ACR, contact for help, text matrix
… attach a sample of such a well known uri
… section three, next steps towards standardizing