Re: Planning to close Low Vision Community Group due to inactivity unless we hear from you

I could try to socialize this a bit but we need clear guidelines on how
folks should participate. I am the IEEE management board rep for IEEE P2998
which is an accessibility standard intended to align with WCAG.

Do you have a paragraph that describes the purpose and scope of the low
vision community group? Worth noting that low vision is just a point on the
 spectrum of blindness and most of us go from good vision to being
functionally blind daily

On Tue, 24 Oct 2023 at 15:15 Kevin Prince <kevin.prince@fostermoore.com>
wrote:

> That was my point Bob, WCAG is seemingly making decisions about the
> priority of low vision issues without much push from the low vision
> community. This group was set up to discuss/advocate but seemingly has no
> traffic – I certainly didn’t receive any notifications so it’s not as if
> there’s much I can do alone.
>
> I’d love to see the community make things active: perhaps then WCAG will
> actually give low vision a priority (Not low vision myself)
>
>
>
> Kevin
>
>
>
> *Kevin Prince *
> Product Accessibility & Usability Consultant
>
> *Foster Moore*
> A Teranet Company
>
> *E* kevin.prince@fostermoore.com
> Christchurch
> *fostermoore.com <http://www.fostermoore.com/>*
>
> *From:* Bob Aiello <robertjaiello@gmail.com>
> *Sent:* Wednesday, October 25, 2023 11:12 AM
> *To:* Kevin Prince <kevin.prince@fostermoore.com>
> *Cc:* Team Community Process <team-community-process@w3.org>;
> public-low-vision@w3.org
> *Subject:* Re: Planning to close Low Vision Community Group due to
> inactivity unless we hear from you
>
>
>
> CAUTION: This email originated from outside of the organization.
>
>
>
> What were we asked to do? I am low vision and sometimes blind. Much of the
> WCAG does not really address my needs.
>
>
>
> On Tue, Oct 24, 2023 at 3:55 PM Kevin Prince <kevin.prince@fostermoore.com>
> wrote:
>
> I don't have the bandwidth to keep this alive I'm afraid. I am open to
> participation and I feel that the low level of specific low vision
> engagement has lead to some of the opoor outcomes in WCAG2.2.
>
> Any thoughts as to how we can revive this?
>
> Kevin
>
> *Kevin Prince*
>
> Product Accessibility & Usability Consultant
>
>
>
> *Foster Moore*
>
> A Teranet Company
>
>
>
> *E* kevin.prince@fostermoore.com
>
> Christchurch
>
> *fostermoore.com <http://www.fostermoore.com/>*
>
>
> -----Original Message-----
> From: Team Community Process <team-community-process@w3.org>
> Sent: Saturday, October 21, 2023 9:01 AM
> To: public-low-vision@w3.org
> Subject: Planning to close Low Vision Community Group due to inactivity
> unless we hear from you
>
> CAUTION: This email originated from outside of the organization.
>
>
> Dear participants in the
>
> Low Vision Community Group
> https://www.w3.org/community/low-vision/
>
> In March 2023 we contacted you because your Community Group appeared to
> have become inactive (per [1]). Based on feedback in response to our
> message, we did not close the group, with the expectation that the group
> would soon become more active. Six months later, your group appears to
> still be inactive, and we are more inclined to close it unless we hear
> compelling reasons not to.
>
> If your group is in fact active, we recommend the following:
>
> * Let us know where the activity is going on so that we can update our
> data and improve our tools.
>
> * Update your group home page with news of your activities. Chairs can use
> the group Wordpress instance of the group to post news; let us know if you
> have any questions.
>
> If you have good reason to believe the group will soon become active,
> please let us know.
>
> If you are merely hopeful it will, or if you would like us to close the
> group, or if we do not hear from you in the next 30 days, we will plan to
> close the group.
>
> Thank you,
>
> CG/BG System
>
> [1] https://www.w3.org/community/about/faq/#close-inactive
>
>
>