- From: John Foliot <john@foliot.ca>
- Date: Tue, 20 Apr 2021 09:39:00 -0400
- To: John Foliot <john@foliot.ca>
- Cc: public-personalization-tf <public-personalization-tf@w3.org>
- Message-ID: <CAFmg2sV7Dkak10z_qb9v-6ieH4NKB0vmOzgzuJjDpZrqcUzTrA@mail.gmail.com>
All, Please disregard this email - I was off-base, but this is now overcome by time. Thanks! JF On Tue, Apr 20, 2021 at 8:21 AM John Foliot <john@foliot.ca> wrote: > All, > > Yesterday I took 2 action items to do an editorial review and cleanup of > our Explainer document (based on Matthew's valuable feedback). > > As I re-read and review our working Draft ( > https://w3c.github.io/personalization-semantics/ - which I note is now > wildly divergent from the officially published doc at > https://www.w3.org/TR/personalization-semantics-1.0/) and I've come > across this sentence in Section 1.2 Use Cases: > > "*In addition, the button could be identified as important and always > rendered or rendered in an emphasized form.*" > > Personally, I'm struggling to understand what that sentence is saying, as > are not <button>s already "always rendered"? Additionally, the presence of > the joiner "OR" in that sentence suggests that the button would be > "rendered in an emphasized form" or "rendered" (i.e. if I reverse the two > options, the sentence then makes no sense). > > So... can anyone shed some light here? Was there a second change or > modification we envisioned that is missing? Some potential thoughts at my > end include: > > "... the button could be identified as important and always rendered *with > the same (user-chosen) UI element*, or rendered in an emphasized form" > > > "... the button could be identified as important and always rendered *visually > in the same spot on the screen*, or rendered in an emphasized form" > > > ...or?.... (any other options?) > > Thanks in advance for the feedback. > > JF > > -- > *John Foliot* | Senior Industry Specialist, Digital Accessibility > > "I made this so long because I did not have time to make it shorter." - > Pascal "links go places, buttons do things" > -- *John Foliot* | Senior Industry Specialist, Digital Accessibility "I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"
Received on Tuesday, 20 April 2021 13:39:35 UTC