W3C

– DRAFT –
WAI Adapt Weekly Teleconference Monday October 23, 2023

23 October 2023

Attendees

Present
Abhinav, Lionel_Wolberger, Roy, Sharon
Regrets
-
Chair
Lionel_Wolberger
Scribe
Lionel_Wolberger

Meeting minutes

v

Welcome, general updates

<Roy> gb, help

<gb> Roy, I am a bot to look up and create GitHub issues and

<gb> … action items. I am an instance of GHURLBot 0.3.

<gb> … Try "gb, help commands" or

<gb> … see https://w3c.github.io/GHURLBot/manual.html

Lionel: Would like to review how we connect our IRC name to our GitHub name

gb, Lionel_Wolberger is lwolberg
… The command I was looking for is 'gb, Lionel_Wolberger is lwolberg'

ACTION: Lionel_Wolberger to test gb

<trackbot> Sorry, but no Tracker is associated with this channel.

<gb> Created action #246

<Roy> Close action #246

<gb> Action 246 test gb (on lwolberg) due 2023-10-30

<Roy> close #246

<gb> Closed action #246

Symbol Module Implementations: One-pager in HTML

Lionel_Wolberger: Thanks to Sharon for a great job rendering the handout in HTML

Roy: We can host this HTML in WAI Adapt's main branch on GitHub
… I will load these into GitHub and supply three URLs:
… (1), the side-by-side version as Sharon did it
… (2) and (3), single versions; (2) being the Blissymbolics and (3) being the ARASAAC, each alone on a page

Lionel_Wolberger: Once we have these, we can decide where and how to edit the explainer to link to these files

ACTION: Roy to Symbols Explainer Made Available as HTML Pages on GitHub

<gb> Created action #247

Issue 240 discussion (Unicode / Registry)

Sharon: Russell did update us by email last week
… He wrote, I have been responding on Github to issue 240...
… Russell plans to respond to the last comment, expects to complete by next week.

well-known URI for accessibility proposal/discuss. include in Gap analysis (Lionel)

Lionel_Wolberger: We understand we are waiting for Matt to settle his new credentials
… but meanwhile we have a demo from Abhinav

Abhinav: (Shared screen with a short PPT with his speaking notes)
… Well-known URI for accessibility
… What is Well-known URI? It is a URL prefix starting with /.well-known/
… implemented to provide a well known and predictable location
… one well-known used one is security.txt
… it allows security researchers to disclose security vulnerabilities
… it is implemented by many companies such as SAP, Google, Amazon
… and is used to provide a well known URL for people to report security vulnerabilities
… proposes /.wellknown/a11y.html to provide a consistent location
… suggesting the .html suffix as this may be more compatible with screen readers
… (shows a sample of a page, where a table has rows
… Each row can supply a field with an example and description
… (shows a sample page)
… (demonstrates security.txt.
… it lists contact URL, contact email, and other fields are added as the standard is extensible
… (demonstrates a similar a11y.html page listing ACR, WCAG level, and links for accessibility help and a contact to get help

Sharon: I am seeking to map this to agenda items that are specific to the WAI Adapt task force
… and help looks like a great match

Lionel_Wolberger: This aligns strongly as well with the new 3.2.6 Consistent Help (A) in WCAG 2.2

<Roy> https://www.w3.org/2023/07/apa-wg-charter

Lionel_Wolberger: examining the Adapt Working Group Charter
… WAI-Adapt: Help and Support Module
… provide use cases and a vocabulary of terms that can be used to enhance alternative or supportive content that may be useful for people with disabilities.

Lionel_Wolberger: I am excited by the standardization of defect reporting
… the comparison with security that Abhinav made is very relevant
… this has been a win-win with the security community
… as incentives are aligned
… both for the reporter, who can earn a bounty
… and the company that receives the report, as they have a chance to patch and avoid an attack
… I can imagine similar virtuous cycle on a11y issue reporting
… assistive technologies could integrate with such a well-known URL
… and submit some record of a problem when a user struggles to complete a task

Sharon: Having an easy and common way to get support would be great
… it has nothing to do with disabilities: everyone has trouble finding support
… finding a support person more easily is a real curb cut

Lionel_Wolberger: Note the difference between accepting an issue report, as opposed to making support available
… which can have a potentially high cost particularly for high volume websites

Abhinav: Happy to present the crux of the idea
… it is very extensible and can likely support anything we decide on

Summary of action items

  1. Lionel_Wolberger to test gb
  2. Roy to Symbols Explainer Made Available as HTML Pages on GitHub
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: Lionel_Wolberger

Maybe present: Lionel

All speakers: Abhinav, Lionel, Lionel_Wolberger, Roy, Sharon

Active on IRC: Abhinav, Lionel_Wolberger, Roy, Sharon