– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

aagenda?

next item

<Eric_hind> Becca and Eric: Found github training useful. There will be more training tomorrow (and follow up screenreader training after that ).

<tburtin> I also attended the github training and found it helpful. I will likely join the second call too.

<Eric_hind> Lisa: Will be doing refresher on COGA processes and documents after main call

take up item 4

<Eric_hind> https://docs.google.com/document/d/1KvEnKdXe30e9BUxcR8RYEOB3PqM7Z9nbLGL8gG-vVW4/edit

eric leading the discussion

ping us in 20

tags are editorial or disscusion in erics docs

are we ok with fixing broken links

+1

<Becca_Monteleone> +1

<JustineP> +1

<abbey> +1

<Rain> +1

and objections

<tburtin> +1

?

no objections

324: to more ors in a sentence

<Rain> +1 to requesting bullet pointed list

<Rachael> +1 to bullet points as well.

editorial without change in meening. such as braking it into a list

rain: when there is long sentence , many cluses . limit each line to one idea

<Rain> +1

without changing the content

<Eric_hind> +1

with a second person cheking ideas and meening is not changed?

+1

<Becca_Monteleone> +1

<JustineP> +1

any objections?

issue 323 - wrong user need

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

link to task mangment (same user need,)

<JustineP> +1

+1

<Becca_Monteleone> +1

<Eric_hind> +1

any objections?

<tburtin> +1

<kirkwood> +1

<julierawe> +1

<Rain> +1

322 user need points to the wrong user need becuse titles are confucing (support, and help) which is which

rain: we need to resucture and come out with clear buckets

but diffrent work streem to what we are doing now in our subgroup

<Eric_hind> Lisa: Titles at the more granular level can be confusing... we have branched as a way to get changes in before major markups or versions? Alternatively, we could gather up items and forward to newer structures?

rain: yes move forward with editorial changes in erics branch

<Eric_hind> Rain: Editorial changes will help right now. Given the mapping isn't 1:1, referencing the public version will be a good thing as the most current could be referenced.

lisa: can you tell us when we need to stop editorial changes in a diffrent branch

<Eric_hind> Lisa: We need to coordinate branching so new structure pulls from the right time and place.

<Eric_hind> Lisa: Add document marker about decisions (e.g. # of +1s to change somthing in this issue)

<Eric_hind> +1

<Rain> +1

<kirkwood> +1

<abbey> +1

<Becca_Monteleone> +1

are we ok with changing the mapping, and opening a new issue that help and support are confucing titles

(as diffrent user stories)

no objections

<Eric_hind> +1

Proposed: Change Use Tapered prompts To : Use prompts that adapt with the user’s behavior (Tapered Prompts).

<tburtin> +1

issue 321

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

<Rain> +1

any objections

320 4.6.2.1 User Need has content from 3.2.2 Searchable (User Story) but link says Distractions (3.5.1).

<kirkwood> findable makes more sense to me…

320, might need more work

ds to be researched again and validated. (like search feature - searchable) Also, could review user needs and be sure they’re in the right place..

319 has simmilar issue

maybe we need a good review of user needs , titles and user stories are clear

<Eric_hind> +1

rain is concerned that we have too much

streched too thin

eric can take that action, lisa may help

318 318 4.5.6.4 More Details include reference to title that is not clear Context of ‘Title’ is not clear. Recommend (per comment) text be changed from “titles” to “title attributes (HTML)” - this seems to match the intended meaning. Change and add reference to HTML

any objections

rain: say html titles and alternitve text

+1

<kirkwood> heading too?

<Eric_hind> +1

<tburtin> +1

<Becca_Monteleone> +1

<kirkwood> +1

<Rain> +1

<JustineP> +1

317 Section 4 Design Guide Related User Story links are missing number heading (e.g. Clear Operation but should be 3.1.2 Clear Operation) Links are missing number heading Update Section 4. Design guide to include number headings. Proposal : do not add more numbers by created user stories. It is fine without. Send to list in email with a bunch of things that are low level Draft reply to issue Some feedback has been that people find the document is t[CUT]

+1

<JustineP> +1

<tburtin> +1

<Eric_hind> +1

<Becca_Monteleone> +1

any objections

can eric fix clear typos

+1

<tburtin> +1

<abbey> +1

<julierawe> +1

<Becca_Monteleone> +1

<Rain> +1 and a thank you!

<JustineP> +1

306 Use Github action instead of Travis CI - we feel this is not our issue

any objections?

clear editoral issues like sentences repepted

can eric just remove it?

<tburtin> +1

+1 with someone double checking

things that are aleready adressed -can we say thank you and close it ?

+1

<Eric_hind> +1

<Rain> +1

<tburtin> +1

<JustineP> +1

305 Underserved users described as “High Potential”

Julieawr mentioned that High Potential might be best replaced. Open discussion item as not clear if high potential infers high value to a business (e.g. CEO) or a m

defining it may be a can of worms

what we want to say, people who are stugling with increadible potential

<tburtin> Instead of "high potential" could we instead simply use "users"?

<julierawe> Thanks, everyone!