Re: Draft Edit: We need personalization because...

Hello John and everyone,

I have made all these edits live although the GitHub.io<http://GitHub.io> is still showing the old version, but that is just a GitHub issue I believe.

I made one more small improvement to the sentence (added custom)
“The ability to implement custom keyboard short cuts at the user-end”

Thanks
EOM
Charles LaPierre
Technical Lead, DIAGRAM and Born Accessible
Twitter: @CLaPierreA11Y
Skype: charles_lapierre


On Nov 27, 2019, at 7:54 AM, John Foliot <john.foliot@deque.com<mailto:john.foliot@deque.com>> wrote:

Thanks All.

Charles, how do we get the actual Explainer page updated? Can you handle that or do you need me to get involved? Please advise.

JF

On Wed, Nov 27, 2019 at 8:03 AM Charles LaPierre <charlesl@benetech.org<mailto:charlesl@benetech.org>> wrote:
Looks great John, thanks! +1

Thanks
EOM
Charles LaPierre
Technical Lead, DIAGRAM and Born Accessible
Twitter: @CLaPierreA11Y
Skype: charles_lapierre


On Nov 26, 2019, at 7:39 AM, John Foliot <john.foliot@deque.com<mailto:john.foliot@deque.com>> wrote:

Greetings All,

After our call yesterday, I took the opportunity to go back and try my hand on an editorial edit to the Explainer page<https://w3c.github.io/personalization-semantics/#why_accessibility>. My suggested edits can be found at:
https://github.com/w3c/personalization-semantics/wiki/We-need-personalization-because


For the group's consideration.

JF

--
John Foliot | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com<http://deque.com/>




--
​John Foliot | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com<http://deque.com/>