<shawn> [Introductions. Welcome Norah!]

<Brent> 24 March Agenda

Web Accessibility Policies

Brent: Thanks to everyone for quick response to the survey, a dozen responses.
... the group (Robert, Andrew, MaryJo) will take the responses, work it into next iteration.

Robert: Yes, add my thanks for your good responses, will defintiely be turning those into action. Of course GitHub is always open so continue to add comments as they occur to you.

Brent: Will you have more to bring to the group next week? If so, please ty to bring to the planning group on Thursday.

<shawn> +1 for timeline ... can go here: https://www.w3.org/WAI/EO/wiki/EOWG_Current_Projects#Policies_Relating_to_Web_Accessibility_update

Sharron: Can you determine the deadline this week?

Robert: Sure, we will make that a priority

Web Accessibility Tutorials

Brent: Eric has been working on the draft tutorials. Updates, Eric?

<yatil> https://w3c.github.io/wai-tutorials/menus/

<yatil> https://github.com/w3c/wai-tutorials/pull/466

Eric: This week I processed the last round of comments from Shadi and the group. Much of it has been editorial, worksmithing, those kind of changes. No real restructuring or major content changes. Some minor content changes that you may want to review or can wait for the final thorough review.

<yatil> https://github.com/w3c/wai-tutorials/pull/467/files

Eric: More significant changes to the Page Structure tutorial, can see those here. Still some discussion about the section about headings so we do not have the approval survey yet until that is resolved.

<yatil> https://github.com/w3c/wai-tutorials/issues/421

Eric: am working on making that more straight forward.
... working on a public comment related to the alignment with WCAG, am working with Shadi on how to address that comment.

<yatil> https://w3c.github.io/wai-tutorials/page-structure/

Eric: You may notice that we are using NotoSans since that will be the font for the new website and will be prepared for that. Next steps are to complete the minor clean-up and updates and then send along to Norah and KrisAnne for copyediting. Once those are done, will bring to EO for the Approval survey. That would mean that we could then publish Page Structures, Menus, and Carousels tutorials.

Brent: Thank you so much Eric - I know how hard you have worked on these with Shadi guidance and support. Excellent progress, thanks again!

<Andrew> +1 to great progress

Caleb: Great job guys, these are amazing.

Sharron: +1

Eric: Thanks to all who gave such helpful comments.

Brent: anything else on these?

How People Use Web

Brent: Shadi has worked to implement the suggestions from the face to face and resulting comments in GitHUb, Shadi?

<shadi> https://github.com/w3c/wai-people-use-web/issues

Shadi: This has been great help, the survey is still open until Monday, please do get to it if you have not yet done so. I have been making changes as they come along. As you comment, note the closed issues that have been rolled into the document as they were received.

<shawn> *reminder to all*: Approval to publish survey deadline Monday 27 for How People with Disabilities Use the Web https://www.w3.org/2002/09/wbs/35532/PWD-use-Web/

<shadi> https://w3c.github.io/wai-people-use-web/browsing.html

Shadi: A substantial change was the revision of the headings on Diversity of Web use section

<shawn> diff-marked version: https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FWAI%2Fintro%2Fpeople-use-web%2Fbrowsing.html&doc2=https%3A%2F%2Fw3c.github.io%2Fwai-people-use-web%2Fbrowsing.html

<shawn> ... how information is being perceived...

Shadi: Here is the current and the diff marked version so you can see the changes.
... Open for discussion between Sensory Perception and Sensory Access as a heading title

Shawn: When you were explaining it, you said "How information is perceived" How about that as a section title?

Brent: looking at how it reads, if Sensory Access was chosen, would that change the first sentence?

Shawn: It is helpful to look at the sections as a whole
... do the other section titles synch with either of these choices?

<shawn> "Sensory perception - hearing, feeling, and seeing"

<yatil> +1

Andrew: Sensory Perception echoes the language of WCAG principle 1

Shadi: Shawn can you say more about the relation to the other section titles.

Shawn: Are we trying to say more about the designer perspective or the user perspective? It is not clear.

Howard: There is a confusion between sensory delivery, which is a focus on the designer as opposed to sensory perception which is user focused. So the choice will have an impact on the language of the headings as well as the paragraph content.

Shadi: OK this is a very good point. I can see that now but not sure how to tie that back to the headings. It is more about understanding that there are different ways to perceive.

Shawn: What if we took out the first words in the section titles?

Shadi: How do people feel about that?

Andrew: I like the one or two word summary with the expansion afterward.

Eric: I think it would be a good change, the simplification would be a good direction.

<shawn> Perception, Presentation, Input, Interaction

<Brent> +1

Shawn: What about a one word handle - Perception, Presentation, Input, Interaction with the expansion that follows
... it will give you the one word handle but the detail follows.

<Andrew> +1

Shadi: Any objection to this approach?

<shawn> [ and tweak wording thorughout to focus on user perspective :-]

Shadi: I also want to alert people to issue #4

<shadi> https://github.com/w3c/wai-people-use-web/issues/4

Shadi: may want to broaden the discussion a bit. We have updated some of the terms. For example cognitive and neurological has more commonly become cognitive and learning in most references within the text.
... I have been sharpening that section and have gotten comments about ADD and it is now outdated and become ADHD. Would like more input and wondered if we might run past the COGA group.

<shadi> [ neuro-diversity ]

Judy: i have always felt that the categorization is most difficult. Overlap, ambiguity, regional differences make it hard to pin down. Neurological references are important to include things like photosenstivity and such that don't neatly map to other terms. Autism as well. A term more frequently used recently is neuro-diversity. I support getting updated opinion on that.

Brent: Dr. Shari Butler in Person is working with COGA, I will ask her to review.

Shadi: Can the chairs ask COGA to look at that section?

Brent: I can do that

<shadi> https://w3c.github.io/wai-people-use-web/principles

<Brent> ACTION: Brent reach out to specific COGA members to weigh in on the discussion around issue #4. [recorded in http://www.w3.org/2017/03/24-eo-minutes.html#action01]

<trackbot> Created ACTION-378 - Reach out to specific coga members to weigh in on the discussion around issue #4. [on Brent Bakken - due 2017-03-31].

Shadi: I would like to ask for a volunteer to look at the references to UAAG 1 and ATAG 1, those links need to be updated to current links and dropped into principles page. who would volunteer?

Howard: I can do that.

Shadi: Thank you Howard, can you do that this week?

Howard: Will I have access to change it in GitHub - like with a fork ?

Shadi: Pull request and I will merge it, thank you so much!

<shawn> [ /me notes that we are hoping to call this done by first week of April ]

<shadi> https://github.com/w3c/wai-people-use-web/issues/1

<shawn> https://w3c.github.io/wai-people-use-web/Overview

Shadi: On the Overview page we have a Tips section at the end, also link to Better Web Browsing (still in draft). Want to talk about personas but don't have good info there and it draws people away from WAI site.
... suggestion to create another heading for those links that lead away from WAI. May be a separate topic of its own - developing a persona, involving users.
... so that is the issue, since there is no immediate reaction, ask for consideration as you complete the survey, thanks everyone.

Brent: In this week's survey, do you want to put a pointer for particular focus from EO?

Shadi: Sure

Brent: OK I will put in the weekly survey. Any other comments, questions?
... thanks for your work Shadi and good feedback all.

New Tutorials/BAD

Brent: Judy introduced this topic a few weeks ago and has an update.

Judy: A few weeks ago a gave a brief overview of some work we have funding for. Asking for feedback from EO paralled with technical feedback from AGWG and others. Now want to introduce the approach and ask you to provide feedback in a survey this week.

<Brent> New Tutorials Requirements Analysis: https://www.w3.org/WAI/EO/wiki/New_Accessibility_Tutorials_Requirements_Analysis

Judy: there is a somewhat different approach on each of these that you may want to comment on. Have provided an outline of the four tutorials. They may change significantly as feedback comes in. Will have opportunity to comment on high level requirements as well as outlines.
... want to look at them individually, links in the agenda. Start with ARIA one. The approach is to serve as gateway from tutorial suite into growing set of tutorial-like resources in ARIA Authoring Guide.
... would be hands-on tutorial but also the introduction to a more complete set of ARIA resources.
... had thought of using for a gateway to UI Components Library but have learned that library is not yet ready for the public. Want to consider building in that connection even if it can only be activated at a later time.
... Next is captioning. Have outlined what I think would be a useful approach within W3C space, address misunderstandings, use WAI resources, pay attention to WCAG2 conformance as well as using other W3C resources. Provide overview of auto and assisted auto captioning.
... no matter how often we tell people that WCAG applies to mobile, it still happens that people seem to expect to find things that are specific to mobile and leave the WAI site if they do not find that. This is meant to reiterate that WCAG applies to mobile and show people that while introducing and navigating the new work from mobile TF. Welcome your ideas about this approach.
... quick upcoming opportunities for immediate high level feedback.
... relating to the BAD update, want feedback about the requirements. We now feel that we are not likely to have the resources to do everything that people want. Will have to be a limited update beginning with visual redesign. There is a huge amount here, many levels of function and information. Shadi has led this work for years.
... want to update code samples with HTML5, ARIA, and some level of responsive design.
... next is how to use BAD in a tutorial setting.
... this may change significantly and your early input can help guide that. BAD curriculum usage is mapped across 3 distinct space where it may be used instructionally.
... types of excercises may vary and we will not try to do anything comprehensive here but will provide guidance for use in various settings.

<Howard> I use it in my classes

Judy: This will be an ongoing process. There may be drafts to look at very soon.

Brent: We want to be sure that the priorities are respected. How People first, then look at this. What will you do with our feedback Judy and then what will come next for EO?

Judy: Completely support the priorities and if you are pressed for time, even brief comments about anything that you are particularly excited about or puzzled about. Depending on what I get by Wednesday, I may revise the tutorial outlines that may cycle back withing a week or so. Could aslo be some drafting that begins on the stable parts. Will try not to bring these in too often but want to start off by getting the aim right. The foundational work may cause EO to see it repetitively over the next few weeks.

Brent: As EO looks through these surveys, can make quick high level comments "don't forget this" or "why is this included" can be submitted with high level impressins and can put detail later.

<Judy> +1 to Brent's description of how to approach this survey

Judy: May be contradictions but will work toward a common approach. Anything else?

Brent: any other business to bring up, reporting, stories, jokes?

WrapUp

Brent: How People survey is high priority, closes on Monday, must complete, can do it in parts, save your work, come back to it. New Tutorials/BAD survey will post today as well as the weekly survey. So please be aware that three surveys will be open for a few days this week, overlapping.
... How People will close on Monday
... weekly survey closes on Wednesday
... BAD/new tutorial survey will have requested deadline of the 29th but remain open until the 5th
... any questions?
... we are adjourned for today, thanks all!

CORRECTION: post meeting notice

Please note that as surveys were being reviewed for posting, Chairs determined that three surveys were not needed. Instead only two will be posted as follows:

• How People with Disabilities Use the Web - Highest priority, complete by Monday 27 March.
• New Tutorials and BAD update requested to complete by Wednesday 29 March (but will remain open until 4 April)