Re: TPAC Slides Update

Hi Lionel, JF, Charles, Janina, all,

tl;dr: I've made updates in line with your feedback; thanks! It's still too long; will be concentrating on that next.

A quick update to the quick update:

1. Re-phrased the "call to action"s near the end, as Lionel suggested.

2. I quite like the yellow highlight, but I understand how it may appear to be a warning. The problem is that only changing the font colour could make it hard for some people to see that _any_ of the code is highlighted. I am also trying to stay within the TPAC styles as best I can. If you or anyone could come up with some different colours we could use (with >=3:1 contrast for the highlight/highlighted code), I can include them. Would've liked to've been able to use syntax highlighting like in your slides, but the TPAC template doesn't do it. I'll need help with this to get it sorted in time.

3. Tweaked the wording at the start along the lines you suggested JF. I'd like to think the changes being made were already moving us in that direction, and agree that a bit of specific technical info up-front to set expectations is helpful. I was going to reference a famous quote, then wondered who said it and found an interesting article [1]. Also: Roxette rule!

4. Oh my, it _is_ different on Windows. Fired up my VM and there we go. Thanks for catching this. I will check all the slides after to make sure they fit. I wonder if my presentation from last year has the same problem!

5. Started finalising the speaker info slide. Want to ACK that Lionel and Lisa both contributed slide material directly, and that all of us have worked on it. Feedback welcome.

A version with these changes has been pushed [2].

Important note: the deck is still too long, so some slides will be removed, or moved to being appendix/supporting material. Still need to practice on the latest version. Will update you again as soon as I can, though I note our first session is very soon (in fact I think it's when our call would've been on Monday).

best regards,


Matthew

[1] https://quoteinvestigator.com/2017/08/15/tell-em/

[2] https://github.com/w3c/personalization-semantics/pull/199

-- 
Matthew Tylee Atkinson
--
Senior Accessibility Engineer
TPG Interactive
https://www.tpgi.com

A Vispero Company
https://www.vispero.com

--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

On 13/10/2021, 19:07, "Janina Sajka" <janina@rednote.net> wrote:

    CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.


    I'd be OK with John's proposed reordering. What do others think?

    Listing AAC third doesn't bother me, because it's a technical definition
    most people won't get until they see examples. Bullet one is fairly
    specific in that way as well, but it's generally comprehendable, then
    bullet 2 breaks out the curb cut effect here. That engages, imo.

    Janina

    John Foliot writes:
    > FWIW.... on that particular screen Matthew, I also have a minor concern
    > that the order of the bullets places an undue emphasis on symbols, to the
    > detriment of (what I believe will be the most adopted attributes) *action*,
    > *destination*, and *purpose*. I personally would be much happier if those
    > bullets read like this:
    >
    > * People with cognitive and learning disabilities, such as dyscalculia,
    > AD(H)D, short-term memory loss, etc.
    > * People who are in a time of crisis, or have a migraine, or are busy
    > * People who use Augmentative and Alternative Communication (AAC) (with
    > varying vocabulary sizes)
    > * People who struggle to learn/recognise new icons
    >
    > (You may note some additional editorial suggestions)
    >
    > My 2 cents.
    >
    > JF
    >
    > On Wed, Oct 13, 2021 at 12:43 PM John Foliot <john@foliot.ca> wrote:
    >
    > > FWIW Matthew, I am seeing the same problem.
    > >
    > > [image: image.png]
    > >
    > > I'm going to blame it on Mac versus Windows, but that's just me...
    > >
    > > JF
    > >
    > > On Wed, Oct 13, 2021 at 12:34 PM Matthew Atkinson <matkinson@tpgi.com>
    > > wrote:
    > >
    > >> Hi Charles, all,
    > >>
    > >> Thanks for all the feedback everyone; I am working on it.
    > >>
    > >> Charles: I think you may be looking at an older version of the slides.
    > >> The latest version has 28 slides. You may need to force-reload in your
    > >> browser. If you are looking at the latest version, I'm not exactly sure
    > >> what could be happening there; maybe something to do with screen
    > >> resolution; please ping me off-list if you are still having problems;
    > >> thanks!
    > >>
    > >> Best regards,
    > >>
    > >>
    > >> Matthew
    > >> --
    > >> Matthew Tylee Atkinson
    > >> --
    > >> Senior Accessibility Engineer
    > >> TPG Interactive
    > >> https://www.tpgi.com

    > >> A Vispero Company
    > >> https://www.vispero.com

    > >> --
    > >> This message is intended to be confidential and may be legally
    > >> privileged. It is intended solely for the addressee. If you are not the
    > >> intended recipient, please delete this message from your system and notify
    > >> us immediately.
    > >> Any disclosure, copying, distribution or action taken or omitted to be
    > >> taken by an unintended recipient in reliance on this message is prohibited
    > >> and may be unlawful.
    > >>
    > >> On 13/10/2021, 13:35, "Charles LaPierre" <charlesl@benetech.org> wrote:
    > >>
    > >>     CAUTION: This email originated outside Vispero. Do not click links,
    > >> open attachments or forward unless you recognize the sender.
    > >>
    > >>     Small point.
    > >>     Slide #4's text  goes off the screen.
    > >>     Thanks
    > >>     EOM
    > >>     Charles LaPierre
    > >>     Technical Lead, DIAGRAM and Born Accessible
    > >>     Imageshare Product Manager
    > >>     Twitter: @CLaPierreA11Y
    > >>     Skype: charles_lapierre
    > >>
    > >>
    > >>
    > >>
    > >>
    > >>
    > >>
    > >>     On Oct 12, 2021, at 2:08 PM, Matthew Atkinson <matkinson@tpgi.com>
    > >> wrote:
    > >>
    > >>     Hello TF,
    > >>
    > >>     Lisa and I took a couple of hours this morning to really improve the
    > >> slides, and think they're in much better shape now. I also have extensive
    > >> notes (currently in some of the slides as HTML comments) about emphasis I
    > >> need to put on what COGA will need to know, and what we'll need to know
    > >> from them, so I will be sure to address that as we go through. I still may
    > >> cut out some slides—at the very least some will be moved to "appendix"
    > >> sort-of material—but I don't think any more need to be added. (There are
    > >> some placeholders for code samples I just couldn't get to this evening;
    > >> will add those very soon.)
    > >>
    > >>     PR URL: https://github.com/w3c/personalization-semantics/pull/199

    > >>     Preview URL:
    > >> https://raw.githack.com/w3c/personalization-semantics/tpac-2021-talk/talks/2021/tpac/index.html

    > >>
    > >>     We've made general changes to keep the focus on our core use-cases,
    > >> pre-empt questions about i18n issues, clarify how we're aiming to solve
    > >> problems and generally ensure that proper terminology is being used.
    > >>
    > >>     Feedback welcome though hopefully we're pretty close now.
    > >>
    > >>     Best regards,
    > >>
    > >>
    > >>     Matthew
    > >>     --
    > >>     Matthew Tylee Atkinson
    > >>     --
    > >>     Senior Accessibility Engineer
    > >>     TPG Interactive
    > >>     https://www.tpgi.com

    > >>     A Vispero Company
    > >>     https://www.vispero.com

    > >>     --
    > >>     This message is intended to be confidential and may be legally
    > >> privileged. It is intended solely for the addressee. If you are not the
    > >> intended recipient, please delete this message from your system and notify
    > >> us immediately.
    > >>     Any disclosure, copying, distribution or action taken or omitted to
    > >> be taken by an unintended recipient in reliance on this message is
    > >> prohibited and may be unlawful.
    > >>
    > >>
    > >>
    > >>
    > >>
    > >>
    > >>
    > >>
    > >>
    > >
    > > --
    > > *John Foliot* |
    > > Senior Industry Specialist, Digital Accessibility |
    > > W3C Accessibility Standards Contributor |
    > >
    > > "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 |
    > W3C Accessibility Standards Contributor |
    >
    > "I made this so long because I did not have time to make it shorter." -
    > Pascal "links go places, buttons do things"



    --

    Janina Sajka
    https://linkedin.com/in/jsajka


    Linux Foundation Fellow
    Executive Chair, Accessibility Workgroup:       http://a11y.org


    The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
    Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa

Received on Wednesday, 13 October 2021 21:06:59 UTC