ayelet-seeman / coga.personalisation

coga.personalisation

This is a project to help personlisation for any use - including people with learning and memory issues. It is described more at: https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Easy_Personalization

It is made of 4 parts:

1. Json files for user setting: https://github.com/ayelet-seeman/coga.personalisation/tree/JSON-Script
2. Aria proposal for new syntax: https://rawgit.com/w3c/coga/master/issue-papers/links-buttons.html
   note we are still working on it. more items will come/change
3. An HTML page that uses some of the new aria syntax: https://github.com/ayelet-seeman/coga.personalisation/tree/ExampleWebPage/
4. Scripts that a web auther can use or include that read the user settings in the JSON files and adapt the page for the user needs: https://github.com/ayelet-seeman/coga.personalisation/tree/Script-Options
5. Stuctured HTML that idetifies the prefrences. Cascading: sort by order specified: if two declarations, the latter specified wins

To Do List

• store as stuctured html in place of cookie- assigned to Chaohai
• Cascading: sort by order specified: if two declarations, the latter specified wins - assigned to Chaohai in the stuctured htmle, and to ayelet in the implemtation
• upgade the terms used with the new proposal update and coga prefex
• write 2 or 3 example JSON descriptions/files for MCI and dyscalcilia using the aria proposal on Adaptable Links and Buttons dyscalcilia coga-numberfree= always, prefered , none (defualt)- assigned to Chaohai (on hond becuse we want to discuss settings with the group)
• implement aria button and link functions to add pannel for extra help with button added to main menu
• define and enable cascading
• add later aria properties to the html page
• add later aria properties to the json
• reminders and disterbences
• add later aria properties to the script
• add later api (speach foalso for feedback, speach text highlighting, and other web components) to the html page, the json , the script
• enable different default values for aria-importance
• overide importance
• proposed issues
  • Position of elements
  • Sentences can not be reliably divided. For that use aria-easylang or aria-hasalt as described abov
  • enlarged cursor
  • screen reading when available
  • a view bar for isolating text while reading,
  • Speak text and symbols
  • Highlighting: off, by word, phrase, sentence (do we need spans to identify divisions?)Misspelling in question posed. I'm not sure I understand the question. Divisions of what, the content that would be read? Wouldn't that simply follow normal document/information structure (e.g. paragraph, line of info being displayed, sentence, etc.)
  • Disable background audio
  • Color and background color preference
  • How about persistent user settings for captioning or audio description or for filtering background noise in media?
  • F1 is help about the browser npt the content
  • Issues: a universal way for saying I need help – help panel and humen help
  • Ambiguity in link types contact us could be a link or section
  • Option - make the names unabiuses contucuslink
  • Or trigger with both role and function (unless role is implide by element type suc as ancor or section)
  • Local storage in html 5 not in cookie
  • Video and api
  • 1. I want tooltips / I do not want tooltips when an item has focus
  • 2. I want side panel that with show the “morehelp” open by defula
  • 3. I want side panel that can be opened when I click on my help icon
  • 4. I want extra help in a popup window
  • 5. Show “more info” link
  • 6. I want links to "more information" when ever possible
  • 7. I want definitions in the side panel
  • 8. Iwant link to human help to be shown/not shown

  Done items (note we only started keeping this as of novermber)

  • parse the the json to identify any attribute as a variable
  • identify the local storage

  removed items

  • button for choosing what json file to load, reads the name from the json and provides that as an option - this is handeled by the stuctred html
  • implement aria button and link functions to add icon, change text, shortcut key add tooltip and pannel for extra help
  - Ayelet

coga.personalisation's Issues

Adding context to the aria-function attribute

We added the aria-function attribute, which enables the web developer to specify the element's function (e.g. home, first name, reset, etc.)

However, we are concerned that developers will use aria-function values in incorrect contexts and they will be processed incorrectly as a result.
For example, aria-function="contact us" is intended to be treated as a link, but someone may add that to a heading with "contact us" causing it to be processed as if it were a link and mess the page.

We thought of two solutions:
A. Change the syntax of the aria-function attribute: following the name of the function have the context in which it should be used. For example, instead of having aria-function = "contact us" have aria-function = "contact us link".

B. Have the personalisation triggered only under the contexts we want to, by using tag names and roles.
For example the aria-function="contact us" will trigger if in a link or if the role is either a link or navigation.

onClick throws error - contactUs2.html

@trentonlawton

@trentonlawton
Cannot read property 'settings' of undefined
at personalise_element_importance (cogapersonalization.js:140)
at personalise_element (cogapersonalization.js:44)
at personalisePage (cogapersonalization.js:25)
at XMLHttpRequest.xhr.onload (cogapersonalization.js:245)
personalise_element_importance @ cogapersonalization.js:140
personalise_element @ cogapersonalization.js:44
personalisePage @ cogapersonalization.js:25
xhr.onload @ cogapersonalization.js:245

v1.0.css

Filenames should not have periods.

Suggest adding link to the demo in readme

Can we create a demo page for this?

Would it be possible to create a Github demo page for this?

Change to Fonts and border onCLick - contactUs2.html

Fonts, colors, font size, and borders on links should change as per contactUs.html

Close PR from Aug 12, 2015

Do not Merge to Master

Low Priority - Filename misspelled

profile_exmaple_1.json profile_exmaple_2.json
example misspelled. Should be profile_example_1.json and profile_example_2.json

This is not a coding issue

sample.json is not valid JSON

icons

Licenced not specified

contactUs2.html - Display Icons

Site map does not load an icon when personalized. Refer to conactUs.html to see how this should behave

contact us does not load an icon when personalized - PLEASE NOTE: conactUs.html does not load an icon either

submit button should change as per conactUs.html

refactored demo page is not applying coga-destination and coga-action settings

coga-destination="home" is meant to have a change of text and add a symbol

coga-destination="sitemap" has a symbol

coga-action = "submit" has a symbol
and more

7 Stale Branches

Parse error on line 104 starting with @coga-destination object

Add links to other sources of info

I suggest you add info about the call, Trello board and and google doc to the README

Actually the Goggle doc could be moved to the wiki here, unless that is seen as a barrier to use for some folks.

Please add collaborator

https://github.com/trentonlawton

https://help.github.com/articles/inviting-collaborators-to-a-personal-repository/

Woudn't the todo listbe easier to access if markdown in an issue or on wiki?

or is it test data for the code?

profile_exmaple_1.json is not a valid JSON File

Parse error on line 104 starting with @coga-destination object