– DRAFT –
WAI Adapt Task Force Teleconference

<sharon> TAG Follow-up (Janina)

BCI Registry Specification

<janina> https://w3c.github.io/adapt-registry/#symbols-entry-requirements

janina: we have a document written mostly by Roy and Michael with some updates from Janina (see above link)

janina: please review above, if document and edits make sense, are we ready to ask APA for a cfc

roy: I think we need acknowledgement and editors section, I can do that tomorrow and provide snapshot link

janina: want to run cfc through midnight Boston time on Dec. 6

CharlesL: in section 3 symbol registry, the symbols for regular characters are way to small to be easily read, symbols are okay but characters are not

sharon: small edit in 2 symbols entry requirements - reads akwardly.

Janina: I will fix

<janina> https://w3c.github.io/adapt-registry/#symbols-entry-requirements

<janina> https://w3c.github.io/adapt-registry/#symbols-entry-requirements

<janina> https://w3c.github.io/adapt-registry/#symbols-entry-requirements

sharon: group is reviewing about link for edits or comments

CharlesL: There is a reference to content module that should be symbols module

Roy: I can fix repository name and links

matatk: should we be mentioning the adapt spec in this registry document

janina: focus is on getting this published with clean up of minor issues after

matatk: I will update the example that Becky was going to address ( update to id in example)

matatk: A linked page to Bliss is just a basic page asking for donations rather than a technical page.

roy: need to get Bliss folks to give us a process for adding new symbols

janina: agreed with need to document process for updating the registry

matatk: If we remove the above mentioned link there is no other link to Bliss

janina: we should ask Bliss for an appropriate link; I will remove the generic link to Bliss

mike_beganyi: item #2 need a hyphen between English and need

<Github> https://github.com/w3c/adapt/pull/2 : fixing typo

CFC launch

<Roy> https://github.com/w3c/aac-registry

roy: updated the repository name (see above link)

<Roy> https://w3c.github.io/aac-registry/

roy: above link is editors draft

<janina> DRAFT RESOLUTION: Wai-Adapt Task Force requests APA conduct a Call for Consensus to publish the WAI-Adapt Registry as a First Public Working Draft (FPWD) https://github.com/w3c/aac-registry

<janina> +1

sharon: please vote on this draft resolution

<CharlesL> +1

<matatk> +1

<mike_beganyi> +1

<sharon> +1

<Lionel_Wolberger> +1

<Roy> +1

becky+1

RESOLUTION: WAI-Adapt Task Force requests APA conduct a Call for Consensus to publish the WAI-Adapt Registry as a First Public Working Draft (FPWD) https://github.com/w3c/aac-registry

Adapt Symbols Module Status

janina: I think we have a few more tweaks; We voted on taking registry to cfc is so our Adapt Symbols module can reference it

janina: I will send an email to Tag to explain our changes based on their request;

janina: have a few more tweaks to the CR draft before going to CfC

Readiness of Explainers

janina: explainer fixes are important but not critical. We are not creating a separate explainer for TAG unless required.

Due Diligence regarding our attributes vs existing alternatives (CSS Media Queries, @autocomplete, microformats, ePub, etc.)

matatk: last week we discussed this a bit, specifically the rel attribute. See last week's minutes for details

<matatk> ARIA DPUB module, adds extra roles: https://www.w3.org/TR/dpub-aria-1.1/

<janina> https://rawgit.com/w3c/aria/master/aria/dpub.html

CharlesL: DPUB aria roles has roles for different parts of books, some can be used on the web as well - example is TOC or bibliography. EPUB has schema.org metadata for accessibility

<matatk> e.g. doc-introduction, ...

matatk: the dpub module is an example of having a separate spec to the parent one -but is still in W3C space

<matatk> https://www.w3.org/TR/epub-a11y-11/#sec-disc-package is the W3C spec, which links to the features list: https://schema.org/accessibilityFeature

CharlesL: values for different accessibility features are not regulated anywhere but we created a W3C taskforce to create a document and process for adding new values;

CharlesL: So there is a schema.org list of values and this other W3C document for further discussion

matatk: Seems that have brought more of the schema.org into the W3C

CharlesL: values are organic, as they get used and adopted, crawlers find them and they get added into schema.org. But, DPUB group wanted a more formal process for adding, updating, correcting

<CharlesL> Here is our GitHub repo on this: https://github.com/w3c/a11y-discov-vocab/issues

matatk: The microformats and rel attribute is similar; Anyone can add to the table but there is no guaranteed for support by browsers. So, am interested in any process available to make certain the new values are vetted.

<CharlesL> https://w3c.github.io/a11y-discov-vocab/

matatk: group needs to ponder this question. Is the process used by DPUB something we can adopt or do we need a different process or no formal W3C process at all?