<Lisa_Seeman> agenda: this

<Lisa_Seeman> scribe: ayelet_seeman

<Lisa_Seeman> nexyt item

<Lisa_Seeman> next item

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/issue-papers/links-buttons.html

LS: We won't have a call next week, as I (Lisa) will be traveling and we will have a joint call the next morning

<Lisa_Seeman> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2015Oct/0047.html

LS: what we actually want aria-importance

MP: doesn't like calling it personalisation, but rather a simplification for the average user

LS: It is a personalisation because you enable people to control how many features they want

MP: yes, the personalisation is built on top of the simplifacation

<Lisa_Seeman> aria-importance= "critical" this content is essential for the key function of the page (Example: The send button for an email draft) OR if it is sometimes critical to a user being able to use the site, such as "save my work" or "emergency instructions" OR if it is used by over 90% of users most times they use the content, If you were making an interface as simple as posible, this is what you...

<Lisa_Seeman> ...would keep

LS: should we keep it as personalisation, and change the description to "the simplest possible interface"?

AS: what with aria-simplification?

MP: best

AS: how would we name the different levels?

LS: Simplest, high, med, low

<Lisa_Seeman> ?

TD: talked to a web developers about this, and there was a discussion over advertisements, as well as the revenue generators versus the highest traffic

LS: that's why frequency has to be included. If they are conforming to the spec, it will be the traffic
... Suggests adding this as an open issue
... we could change it to 90% of this user group
... would you like me to write up something adding context?

<Lisa_Seeman> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2015Oct/0045.html

<Lisa_Seeman> <div>

<Lisa_Seeman> <span rel="alternative" aria-type="easylang numberfree vocab500" class="hidden">most people prefer simple text<span>

<Lisa_Seeman> In studies it was found that only 30% of users prefer long convoluted text with obtuse words and lots of numbers, with 56% claiming there preferred the simplified text , with the remainder unsure or stated it depends on the context </div>

LS: this is the replacement for the easylang tag

<Lisa_Seeman> <div easylang="most people prefer simple text" >

<Lisa_Seeman> In studies it was found that only 30% of users prefer long convoluted text with obtuse words and lots of numbers, with 56% claiming there preferred the simplified text , with the remainder unsure or stated it depends on the context </div>

the problem is that we had a long list of different tags for different users.

<Tony> Simple is good :)(

LS: it sounds like we don't know what we want, whicjh is a problem as we'll be eaten alive in the call in a week
... from the developers point of view the second option is simpler

TD: what we do is say we need to provide alternative text so that everyone could understand it. but the content providers see it as that the content needs to be understandable by everyone

LS: some people like the full information
... or content with numbers, non literal, etc.

(in answer to why would someone want the non simplified version)

MP: the issue is that there need to be different alternatives

LS: back to the question, which way of doing it is bette, do we want to make the developers insert a span in to the div, or do we prefer to enable them to provide only one alternative

TD: the content provider should see if the numbers are needed and if they are include

LS: do we want to enable both?

TD: It enables an easy way of doing it, and lets people who know what they're doing do it in a better more robust way

<Lisa_Seeman> <button type="button" >undo

<Lisa_Seeman> <div aria-more="morehelp" aria-hidden="true"> pressing the undo button will erase all your work on this page. Use this button with care. If you press it by mistake, press control and y at the same time and your answers will come back. </div>

<Lisa_Seeman> <a href="functiongethelp()" aria-more

<Lisa_Seeman> ="humanhelp" aria-hidden="true">I want a person to help me</a>

<Lisa_Seeman> </button>

<Lisa_Seeman> or

<Lisa_Seeman> <button type="button" >undo

<Lisa_Seeman> <a href="functiongethelp()" aria-more

<Lisa_Seeman> ="humanhelp" aria-hidden="true">I want a person to help me</a>

LS: unless anyone objects, we will ask for both

<Lisa_Seeman> </button>

<Lisa_Seeman> or (option 4 - can be with option 1,2 and 3)

<Lisa_Seeman> <button type="button" >undo

<Lisa_Seeman> <link aria-more="morehelp" aria-hidden="true" href="myhelpfile.html#undo/> </button>

<Lisa_Seeman> replacing the following:

<Lisa_Seeman> <button type="button" aria-moreinfo="uri2 uri3" >undo</button>

<Lisa_Seeman> URI 2 may read:

<Lisa_Seeman> <div id="uri2" aria-extrahelp="morehelp" aria-hidden="true"> pressing the undo button will erase all your work on this page. Use this button with care. If you press it by mistake, press control and y at the same time and your answers will come back. </div>

<Lisa_Seeman> <a href="functiongethelp()" aria-extrahelp="humanhelp" aria-hidden="true">I want a person to help me</a>

<Tony> I need to drop off - sorry

<Lisa_Seeman> whjat is neater?

<Lisa_Seeman> chaals are you there?

LS: we could put them both in the proposal, and let them decide

<Lisa_Seeman> ayelet?

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: ayelet_seeman
Inferring ScribeNick: ayelet_seeman

WARNING: No "Topic:" lines found.

Present: Mike_Pluke Lisa_Seeman Ayelet_Seeman Chaohai_Ding Janina Tony Doran
Regrets: John Rochford

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 19 Oct 2015
Guessing minutes URL: http://www.w3.org/2015/10/19-coga-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report