- From: Jonathan Avila <jon.avila@levelaccess.com>
- Date: Wed, 21 Jul 2021 15:01:09 +0000
- To: "Charles 'chaals' (McCathie) Nevile" <chaals@yandex.ru>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <BL1PR03MB6120AA4581874EBE310E7A44F1E39@BL1PR03MB6120.namprd03.prod.outlook.com>
I had no intent to exclude the alt text on the image and had emailed off list to make that clear. My recommendation was in addition to the image description in Twitter to address the issue of criteria 1.4.5 related text of images. Alt text is not available to users with low vision. The image descriptions feature should be used but it may not be enough to meet the needs of a wide range of users. Sorry for the lack of clarity in my prior message. Jonathan Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Charles 'chaals' (McCathie) Nevile <chaals@yandex.ru> Sent: Wednesday, July 21, 2021 9:58:41 AM To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org> Subject: Re: Testimonial campaign cards - embedded text question CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Louise, If you publish something on social media, in most places it is considered that you are the publisher, so you are responsible for making it accessible. I believe many people find that the twitter alt system works for the use case you described - and if not I would support Jonathan's suggestion. Having a tweet with a link, and expecting people to follow it to find out what the tweet said is not really an acceptable approach as I read WCAG, nor as I consider the situation just in terms of "what makes sense here?" Such are my thoughts.. cheers On Wed, 21 Jul 2021 22:58:41 +1000, Louise Lister <Louise.Lister@iop.org> wrote: > > > > > > Thanks Jonathan. We’ll have the testimonials on our webpage that we are > linking to so that’s probably the simplest approach. > > > > > > > > > From: Jonathan Avila <jon.avila@levelaccess.com> > > > Sent: 21 July 2021 13:55 > > To: Louise Lister <Louise.Lister@iop.org>; w3c-wai-ig@w3.org > > Subject: Re: Testimonial campaign cards - embedded text question > > > > > > > > > > > > You could provide a direct link to the text on your website or reply to > the tweet with the text. > > > > > > > > > > Jonathan > > > > > > > > > > > > GetOutlook for iOS > > > > > > ----- > > > > > From: Louise Lister <Louise.Lister@iop.org> > > Sent: Wednesday, July 21, 2021 6:08:03 AM > > To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org> > > Subject: Testimonial campaign cards - embedded text question > > > > > > > > > > > CAUTION: This email originated from outside of the organization. Do not > click links or >open > attachments unless you recognize the sender and know the content is safe. > > > > > > > > > > > > > Hello there, > > > > > > > We recently completed an audit of our website for images and alt text. > > > > > > > > One of the things we are trying to avoid going forward (unless it’s > necessary), is having images where the text in embedded. We >can do this > by posting the text next to an image on our website and make it look > attractive > still. However, in the case where we are using a twitter card on social > media that has a student testimonial of about 60 odd >words (see example > attached), does anyone know if the Twitter image description is even a > suitable alternative for creating some >social > media “alt text”: > https://help.twitter.com/en/using-twitter/picture-descriptions. And have > we failed accessibility by following a certain practice >on the web, but > not on Twitter? > > > > > > > Sorry it’s slightly on a tangent if related but would just appreciate > your thoughts on this as both web and social will often >work > hand-in-hand on this. > > > > > > > Best > > > > Louise > > > > > > > > > > > ----- > > > > This email (and attachments) are confidential and intended for the > addressee(s) only. If you are not the intended recipient >please > immediately notify the sender, permanently and securely delete any > copies and do not take action with it > or in reliance on it. Any views expressed are the author's and do not > represent those of IOP, except where specifically stated. >IOP takes > reasonable precautions to protect against viruses but accepts no > responsibility for loss or damage arising from virus > infection. For the protection of IOP's systems and staff emails are > scanned automatically.. > > > > Institute of Physics. Registered charity no. 293851 (England & Wales) > and SCO40092 (Scotland) > > Registered Office: 37 > Caledonian Road, London, N1 9BU > > > Your privacy is important to us. For information about how IOP uses your > personal data, > > please see our Privacy Policy > > > ----- > > > > > > > > > > > ----- > > This email (and attachments) are confidential and intended for the > addressee(s) only. If you are not the intended recipient >please > immediately notify the sender, permanently and securely delete any > copies and do not take action with it or in reliance >on it. Any views > expressed are the author's and do not represent those of IOP, except > where specifically stated. IOP takes >reasonable precautions to protect > against viruses but accepts no responsibility for loss or damage arising > from virus infection. >For the protection of IOP's systems and staff > emails are scanned automatically.. > > > Institute of Physics. Registered charity no. 293851 (England & Wales) > and SCO40092 (Scotland) > > Registered Office: 37 Caledonian Road, London, N1 9BU > > > > > Your privacy is important to us. For information about how IOP uses your > personal data, please see our Privacy Policy > > > > > ----- > > > -- Using Opera's mail client: http://www.opera.com/mail/
Received on Wednesday, 21 July 2021 15:01:26 UTC