- From: lisa.seeman <lisa.seeman@zoho.com>
- Date: Sun, 18 Oct 2015 16:47:18 +0300
- To: "public-cognitive-a11y-tf" <public-cognitive-a11y-tf@w3.org>
- Cc: "james nurthen" <james.nurthen@oracle.com>
- Message-ID: <1507b3453d3.11e3f13e71776704.4765570923644741000@zoho.com>
Suggested change for aria proposal on https://rawgit.com/w3c/coga/master/issue-papers/links-buttons.html - specifically the section on Language type support and proposed attributes of aria-hasAlt and aria-alttype and the different language options such as easylang numberfree and even summery. It might be cleaner. It needs to be as simple as possible to implement and although the easylang in the draft is easier, all the different ways may make it harder to grasp and remember. It might be easier to have one slightly harder way to implement it that works for all our cases (in fact we can make the metadate approach very similar) Suggestion replace easylang numberfree litral aria-hasAlt and aria-alttype with rel="alternative" and additions to HTML type : Option 1: <div> <span rel="alternative" aria-type="easylang numberfree vocab500" class="hidden">most people prefer simple text<span> 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> and we can add to html types as they are mime types (I think) or Option 2: (even simpler) <div> <span aria-alternative="easylang" class="hidden">most people prefer simple text</span> 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> and part of this suggestion is we get rid of the following <span aria-easylang="some text that is easy to read"> some convoluted obtuse text</span> As an option 3 we could also have the same approach to merge all the ways to add help such as aria-explain or aria-feedback aria-moreinfo and aria-extrahelp into one attribute aria-moreinfo such as <button type="button" >undo <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> <a href="functiongethelp()" aria-more ="humanhelp" aria-hidden="true">I want a person to help me</a> </button> or <button type="button" >undo <a href="functiongethelp()" aria-more ="humanhelp" aria-hidden="true">I want a person to help me</a> </button> or (option 4 - can be with option 1,2 and 3) <button type="button" >undo <link aria-more="morehelp" aria-hidden="true" href="myhelpfile.html#undo/> </button> replacing the following: <button type="button" aria-moreinfo="uri2 uri3" >undo</button> URI 2 may read: <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> <a href="functiongethelp()" aria-extrahelp="humanhelp" aria-hidden="true">I want a person to help me</a> All the best Lisa Seeman Athena ICT Accessibility Projects LinkedIn, Twitter
Received on Sunday, 18 October 2015 13:47:43 UTC