– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

<lisa> ow do we write up citations in issue papers? Options : Reference the line number Links Full citations https://www.w3.org/Guide/manual-of-style/

<lisa> close item 5

<lisa> next item

Lisa: Reminder for Github Editor training call tomorrow, 7 March

Lisa: Added training section to main COGA wiki page, including link to IRC training, Github for editors, Github for members

Lisa: Github for Editors training includes key terms and processes for on- and offline editing

Lisa: Github for Members training page links to AG primer, as well as key terms for basic processes

Github Editor training tomorrow, 7 March, EST 9:00 AM CET 2:00 PM Uk 1:00 PM Israel 3:00 PM

<JMcSorley> Can we record the call tomorrow so that we have that available for review later?

<jeanne_ec> +1 for the recording

Lisa: Will try to record tomorrow

<lisa> next item

Lisa: Last week voted to make separate issue paper on supported decision-making. Lisa has started to compile elements of this paper from other documents and draft a structure.

Lisa: Created "to-do" tags on the document so people can contribute small sections at a time

Lisa: Will review structure next week.

<lisa> next item

Rashmi: New proposal #13: Findability. Suggesting change in text re: appropriate type of hierarchy

Lisa: This suggestion comes from a lot of research in mental health about findability. There is conflicting research about deep vs. flat hierarchies

Lisa: current pattern 4.3.2 does not make reference to how deep a hierarchy should be

Lisa: Recommendation is to suggest testing with users based on the site's content

John: Suggest focusing on methods for making things more findability (e.g. in-line search) rather than only focusing on hierarchy - since how flat or how deep is findable depends on individual cognitive load.

John: There are conflicting access needs, so pointing to tools for finding vs. how to chunk seems important

John will look at current pattern on findability

<lisa> https://www.w3.org/TR/coga-usable/#make-the-site-hierarchy-easy-to-understand-and-navigate-pattern

<lisa> https://www.w3.org/TR/coga-usable/#objective-2-help-users-find-what-they-need-0

Lisa: Do we also need to recommend site maps?

Tiffany: Utilizing multiple ways to navigate raises concerns about wording - on flat pages, can still be hard to find the correct information even with headings and find function

Lisa: Can Tiffany and John come to next Mental Health subgroup to create a new proposal?

Jan: has research explored utility of user being able to convert a modular design to a flat design? Making sure semantic markup follows - also interested in discussing the research on this

Lisa: Current proposal does already reference redundant ways of finding content, which addresses some of these concerns

Rashmi: research says that deeper hierarchy it is easier for users to go back; users more likely to get lost in flatter hierarchy

<rashmi> Research tracking doc https://docs.google.com/spreadsheets/d/1eKNrofGubnpQE6mO-vxmI-1MW5nA2LDj0LxebREPRGA/edit?resourcekey#gid=1686096268

Lisa: reviewing current research, there is not consensus, which led subgroup to think it is more about the content.

<lisa> proposal 8

<lisa> https://docs.google.com/document/d/1K4tI9SV4lsDXzCdaEAXExeL3f061__Sy06lfGV9mLvY/edit#heading=h.lhdm88jj5cym

Rashmi: revised proposal 8 - 8.1 recommends making it easy to go to starting directly. 8.2 deals with multistep processes.

John: question the word "starting point" for 8.1 instead of "homepage." Starting point more relevant for process (8.2)

Lisa: Will replace starting point with home page in 8.1

Rashmi: reviewing proposed pattern 8.2: https://docs.google.com/document/d/1K4tI9SV4lsDXzCdaEAXExeL3f061__Sy06lfGV9mLvY/edit#heading=h.z6oo3zn072u6

John: Getting back to first step or just where you were in the process?

<lisa> proposal

<lisa> 8.1: Make it easy to return/go directly to home page of a site or sub- site.

<lisa> +1 is agree, 0 more time, -1 real issue

<lisa> +1

<Eric_hind> +1

+1

<kirkwood> +1

<jeanne_ec> +1

<EA> +1

<Frankie> +1

<Jennie> +1

<rashmi> +1

<tburtin> I have questions about the wording.

Tiffany: language around "returning to a subpage" is not clear to me.

Lisa: Subsite in 8.1 refers to different homepages nested in a larger site (e.g. departments in a university). Both should be clear to navigate to.

Tiffany: wording around clear menu navigation or page navigation?

Lisa: Already covered in content usable Objective 2

Lisa: This new proposed objective specifically calls out homepage and/or first step

Tiffany: The word subsite is still not clear in 8.1. Sounds like these are major navigation sections.

Lisa: Call for suggestions for a clearer term to differentiate

Tiffany: major navigation page, landing page?

Jan: Landing page and home page are the same to me.

Lisa: We are trying to call attention to when there is a new template for a specific section of a site.

<EA> "A landing page is a standalone web page that a person "lands" on after clicking through from an email, ad, or other digital location" https://mailchimp.com/marketing-glossary/landing-pages Seems to have several meanings!

Lisa: want to be able to recommend not only going to homepage of website, but first page of specific section

Jennie: one place this comes up was the employment section of an organization's website. Like "relevant landing page" but maybe add additional explanation - like "for a major section" or "a group of webpages"

<JMcSorley> maybe "section landing pages?"

<JMcSorley> I think the use of the term "relevant" might be confusing

Jennie: make a note that we should use the same language as WCAG 3

<kirkwood> i like: a landing page of a section of a site

<JMcSorley> +1 to John's wording on landing page

Rashmi: some confusion around "landing page" for when you go to a page through an external link.

<JMcSorley> I agree with Rashmi - the use of the term landing page can be the same as a home page

Lisa: will define landing page.

Jennie: to a user, landing page is the place they arrived at; to a designer, it may be different because of site design.

<Jennie> * Rashmi - I am glad you brought up that perspective.

<tburtin> +1 Jennie I recognize balancing the definition between user and developer/designer.

<lisa> Make it easy to return/go directly to the home page of a site or relevant landing page of a set of Web pages. (to change with wcag

<lisa> +1 is agree, 0 more time, -1 real issue

<tburtin> +1

<Eric_hind> +1

<Frankie> +1

<kirkwood> +1

+1

<JMcSorley> +1

<Jennie> +1

I need to leave for another meeting - sorry!

<lisa> New Pattern 8.2: Allow the user to return directly to the starting point of a multistep process

<lisa> +1 is agree, 0 more time, -1 real issue

<tburtin> +1

<lisa> +1

<Eric_hind> +1

<rashmi> +1

<JMcSorley> +1

<EA> Trying to catch up but I think +1

<kirkwood> +1

<lisa> john thinks it is ok, but we need to look at objective 2 all together as a draft