We need personalization because

Current Draft	Proposed Edits
Original introduction This section is non-normative. The goals of this specification include: Expanding the accessibility information that may be supplied by the author; Facilitate preference driven individual personalization; Enable the author to specify key semantics needed to support users with cognitive impairments This is a proposal for defining syntax for adaptable content such as: links, buttons, symbols, help and keyboard. This may be a WAI-ARIA COGA Extension, however implemenation methods are currently being explored. Technology holds the promise of being extremely flexible and the design of many systems includes the expectation that users will be able to optimize their interaction experience according to their personal preferences or accessibility needs.	This section is non-normative. The goals of this specification include: Expanding the accessibility information that may be supplied by the author; Facilitate preference driven individual personalization; Enable the author to specify key semantics needed to support users with cognitive impairments This is a proposal for defining syntax for adaptable content such as: links, buttons, symbols, help and keyboard. This may be a WAI-ARIA COGA Extension, however implemenation methods are currently being explored. Technology holds the promise of being extremely flexible and the design of many systems includes the expectation that users will be able to optimize their interaction experience according to their personal preferences or accessibility needs.
We need personalization because: • The needs of individual user may conflict. • Learning new design patterns, widgets, and user interfaces can be confusing. We would like to give users the ability to decide what works best for them based on preference and ability. • Extra support can be a distraction for people who do not need it. • Making content predictable is necessary for accessibility but can often lead to less innovate design. • Ability to increase or decrease levels of complexity as people's skills improve or decline over time. • Enable websites to adapt to and meet the user's needs. Some users need extra support. This can include: • Symbols and graphics that they are familiar with • Tooltips • Language they understand • Less features • Separating advertisements so users don't confuse them with native content • Keyboard short cuts To achieve this we need standardized terms and supportive syntax.	We need personalization because: • The needs of an individual user may conflict with certain established mainstream user-patterns. • Learning new design patterns, widgets, and user interfaces can be confusing. We would like The goal is to give users the ability to decide what works best for them based on preference and ability. Personalization enable websites to adapt to and meet the user's needs. • Extra support can be a distraction for people who do not need it, so a robust solution requires the ability to increase or decrease levels of complexity as people's skills improve or decline over time. • Making content predictable is necessary for accessibility but can often lead to less innovate design. Some users need extra support. This can include: • Symbols, iconography and graphics that they are familiar with • Tooltips or similar on-demand help or clue • Language they understand • Less Fewer or more constrained features • Separating advertisements so users don't confuse them with native content The ability to programmatically distinguish between native content and third-party content on a page or screen • The ability to implement keyboard short cuts at the user-end To achieve this we need standardized terms and supportive syntax.