- From: Janina Sajka (janina@rednote.net) <janina@rednote.net>
- Date: Fri, 8 Jul 2022 06:43:09 -0400
- To: Accessible Platform Architectures Administration <public-apa-admin@w3.org>
Forwarded with Dr. Hollier's permission ... Scott Hollier writes: > To Lisa > > Thanks for raising the point. Judy and I decided that the Note should focus on the different audiences that would be making remote meetings accessible, so rather than distinguishing between different disability groups, the Note is structured based on the audiences implementing the guidance i.e. procurement, developers, content producers, meting hosts and users, and hybrid meetings hosts. You'll see that headings in the document don't single out any particular disability group, so the decision as made to embed the cognitive guidance with the guidance related to other disability groups so that the audiences implementing the recommendations will implement all the requirements across a range of disability groups. In that context having one standalone section of cognitive guidance when there's none for other disability groups would be inconsistent. > > However, as mentioned earlier, the guidance content is very much in the document and receives the same prominence as guidance for other disability groups. > > Hope this helps. > > Scott. > > > Dr Scott Hollier > CEO & Co-founder > > [Centre for Accessibility logo]<http://www.accessibility.org.au/> > > Centre For Accessibility Australia Ltd. > Phone +61 (0)430 351 909 > Email scott.hollier@accessibility.org.au<mailto:scott.hollier@accessibility.org.au> > Address 92 Adelaide Street, Fremantle WA 6160 > > accessibility.org.au<http://www.accessibility.org.au/> > > [Instagram logo icon]<https://www.instagram.com/centrefora11y/> [Facebook logo icon] <https://www.facebook.com/centrefora11y/> [Twitter logo icon] <https://twitter.com/centrefora11y> [LinkedIn logo icon] <https://www.linkedin.com/company/centreforaccessibility/> >
Received on Friday, 8 July 2022 10:43:21 UTC