Re: Update on progress towards CR for Symbols

Hi Charles, all,

Taking your suggestions in order...

1. Regarding having an Editor's Note about us applying for the adapt- prefix, following discussion off-list we decided to take all the existing editor's nodes out (about data-) and leave it at that, as we will be imminently applying for the prefix. I am not opposed to adding one in to say that we have not yet actually got the prefix agreed; could be a good idea. Please make a PR if you agree, and can.

2. I filed a PR to fix remaining instances of "Content Module" in the Explainer and elsewhere (Note: the TPAC presentation has not been updated because it's historical, and the Vocabularies List has also not been updated because I'm not sure it's used—raised an issue about it the other day.)

3. I filed a PR to fix the ReSpec error (it wasn't, it turned out, totally to do with headings, but I tweaked the heading levels first, and it seems fine, so will leave them tweaked).

Keep the feedback coming, all!

Best regards,


Matthew
-- 
Matthew Tylee Atkinson (he/him)
--
Principal 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 01/11/2022, 16:25, "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.

    Hi Mathew and all, 
    (Explainer)

    First off in the explainer shouldn’t we have an editors note in there that we are currently working to get the “adapt-“ prefix? Perhaps in section 4.1.

    Also in the Explainer 
    2. Modules <https://raw.githack.com/w3c/adapt/symbols-module/index.html#modules>

    * WAI-Adapt: Content Module: <https://raw.githack.com/w3c/adapt/symbols-module/symbols/index.html> This module provides vocabularies that enable user-agents to augment or adapt content to allow authors to support AAC symbols.


    That should now be Symbols Module correct?

    I know Becky is still working on the example to remove Advertisement as a distraction.


    (Symbols Module)
    Terms <https://www.w3.org/TR/coga-usable/>

     <https://raw.githack.com/w3c/adapt/symbols-module/symbols/index.html#terms>
    This document uses a number of specific terms related to various cognitive disabilities and related user-needs. Those terms have been defined by the Cognitive and Learning Disabilities Accessibility Task Force. See the  <https://www.w3.org/TR/coga-usable/>COGA Glossary <https://www.w3.org/TR/coga-usable/#glossary> for specific definitions.



    This is showing an error due to no H2 within the <section>


    Thanks
    Charles
    EOM

    Charles LaPierre
    Principal, Accessibility and Content Quality Architect
    Benetech
    Twitter: @CLaPierreA11Y







    On Nov 1, 2022, at 8:59 AM, Matthew Atkinson <matkinson@tpgi.com> wrote:

    Hi all,

    We need your input this week on the hopefully-very-soon-to-be-CR Symbols Module. I've renamed the data-* attributes, and the module itself. That last change, to rename to the Symbols Module, is in a PR at the moment, but we expect to merge it soon. The PR is at https://github.com/w3c/adapt/pull/227 and you can follow the links there to preview the module.

    We need you to read this and suggest any changes this week, so we can have the best chance to approve it on Monday (the 7th). To suggest changes, either:

    * Make a PR against main, when the Symbols Module PR (linked above) is merged there.
    * File GitHub issues.
    * Reply to this thread.

    We're so close now; thanks for any input you can provide!


    Matthew
    -- 
    Matthew Tylee Atkinson (he/him)
    --
    Principal 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.

Received on Wednesday, 2 November 2022 16:02:10 UTC