– DRAFT –
ARIA Authoring Practices Task Force

<MarkMcCarthy> Is there a link to the agenda?

<Jem> https://github.com/w3c/aria-practices/wiki/December-6%2C-2022-Agenda

<Jem> https://github.com/w3c/aria-practices/wiki/December-6%2C-2022-Agenda

update on about page

<Jem> https://github.com/w3c/aria-practices/wiki/December-6%2C-2022-Agenda

<Jem> https://github.com/w3c/aria-practices/pull/2558

<Jem> https://github.com/w3c/aria-practices/issues/2535

<Jem> mck: plan to go through the design updates as a group

<Jem> ... the priority is support table design update

<Jem> ... who is working on support table

<Jem> alex: Howard will work on support table

<Jem> mck: hoping that we have a way to validate the support table..

<Jem> alex: embeded support table will have iframe and and url.

<Jem> ... url will point to embed link to the aria AT app.

<Jem> mck: how would I as the editor be able to figure out the link?

<Jem> .. will the url be visible?

<Jem> alex: in the at app, we have references to all the patterns.

<Jem> ... we would know the url in iframe because it is from AT url itself.

<Jem> mck: That may be a little less stable.

<Jem> ... I want to make sure that two examples under one pattern can be clear so that APG use it without error.

<Jem> ... button has two examples.

<Jem> .. I as apg editor would like to have control for the distinction of two examples

<Jem> ... looking for the clean and correct way to connect between AT and APG examples

<Jem> howard: multiple instance of listbox will generate multiple embed links is one way.

<Jem> mck: can you propose different options for the implementation if any regarding https://github.com/w3c/aria-practices/issues/2520?

<Jem> mck: could you document multiple options to discuss at next meeting?

<Jem> alex: iframe is automatically created.

<Jem> ... it is one design, rather than multiple design.

<Jem> mck: it would be great to see some code snippet which will go into APG

<Jem> alex: that is a good idea.

Mockups for card and list view toggle and search in Patterns and Practices pages #2534

<Github> https://github.com/w3c/aria-practices/issues/2534 : Mockups for card and list view toggle and search in Patterns and Practices pages

<Jem> mck: I would like to see the implementation of list view in About page first.

<Jem> alex: I will look at the list design in about page after restructure project.

<Jem> mck: I have new contents for about page and we would need the review.

<Jem> ... I am looking forward to the feedback about the "about" page contents

<Jem> ... can we have the draft privew url of "about" page regarding PR 2558?

<Jem> the group discussed the issue 2535 design.

<Jem> Jemma and helen will add comments to the issue.

Create a patterns directory tree with a separate file for each pattern and move all examples inside the patterns directory tree #2417

<Github> https://github.com/w3c/aria-practices/pull/2417 : Create a patterns directory tree with a separate file for each pattern and move all examples inside the patterns directory tree

<Jem> mck: are we all done?

<Jem> all the changes are reflected here. https://deploy-preview-173--aria-practices.netlify.app/aria/apg/

<Jem> Helen and Jemma will do another final review till tomorrow morning and Matt will update it tomorrow.

<Jem> the goal is publishing this update this week for the production.

<Jem> mck: how about landmark example redirect?

<Jem> .. landmark name can use detailed one, not index.html?

<Jem> alex matt: will do minium update for landmark page for now. We will update the example to go with APG template.

<Jem> Alex will respond to the issue.

<Jem> mck: we are really getting close to be done with repo project except About page.