- From: Till Halbach <halbach@nr.no>
- Date: Mon, 22 Aug 2022 22:22:23 +0200
- To: w3c-wai-ig@w3.org
- Message-ID: <7544a8d8-1f50-a494-92ce-df68d7288f98@nr.no>
I registered that people advocate for the colon, but I would argue for
"Photo of XX". IMHO, "Photo: XX" in fact means "Photo by XX".
Best,
Till Halbach
On 22.08.2022 14:21, Hickey, Casey wrote:
>
> John and Grey,
>
>
> Thank you for this conversation. One of the challenges I encountered
> when looking for clear guidance on this question was the widely
> inconsistent information I encountered while searching for answers.
> Grey isn’t alone in their perspective here. I read other sources
> sharing a desire for more descriptive information in the alt text for
> headshots. I also discovered some others that felt the alt text should
> be blank if the image is adjacent to the individual’s name. For now,
> I’ll go with what seems to be the standard of Photo: [First Name]
> [Last Name].
>
> I do hope WAI / W3 will take this topic under consideration,
> especially since it does not seem to be addressed in their guidance
> for informative images or decorative images. It’d be very nice to have
> a supported HTML image description in addition to the alt attribute.
>
> Thanks again for your responses, I appreciate the time and thought
> you’ve put in here.
>
> Casey Hickey
>
> *From: *John Foliot <john@foliot.ca>
> *Date: *Saturday, August 20, 2022 at 9:24 AM
> *To: *Grey L. Pierce <glp@uoregon.edu>
> *Cc: *Hickey, Casey <ca.hickey@northeastern.edu>, w3c-wai-ig@w3.org
> <w3c-wai-ig@w3.org>
> *Subject: *Re: Thoughts on professional portrait (headshot) images?
>
> Hi Grey,
>
> > If using <details>, <summary>, <figcaption>, etc. are determined
> to be better ways to provide the information, then that's the
> route to go, and we may want to consider that to be a basic
> requirement for portrait accessibility.
>
> Respectfully, I think you are mixing some things up here.
>
> The techniques I referenced would work for *any* image (or other
> non-textual element) that requires more than a label, including but
> not limited to what you keep referring to as "portraits", but in fact
> are "head shots" of simply pictures of individual people. The basic
> semantic mechanics however remains the same: the Accessible name is
> the 'label' for the non-textual element, and the Accessible
> description is, well, the description.
>
> Based on that, the Accessible name (aka @alt) for those types of
> images should still be kept succinct and to the point - it is an
> alternative, not a description. (I am also slightly concerned over
> your apparent suggestion of "Portrait" being some kind of 'special'
> image: we would need a clear definition of what is meant by 'portrait'
> here, as an avatar icon
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flh3.googleusercontent.com%2Fa-%2FAFdZucob3KU7gU4MIxaCixz-Sm2ioabXEdodgrLiZzxNfg%3Ds80-p&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bVLphoFpNiFWLYvF2GK2HcCE1jXalPJV6xDnW5h%2FZdM%3D&reserved=0>
> that is 80 px square is stretching the common english definition of
> 'portrait'
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FPortrait&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=26eK0Bmqmtf6cBBrxlZblh1a0LaippnggLzWKZsw5PA%3D&reserved=0>.
> In the world of Standards, ambiguity such as this is the type of
> devilish details that need to be addressed.)
>
> Second, "requirements" are set by entities outside of the W3C - all
> the W3C can do is make recommendations, and ensure that there are
> technical solutions available to enable those recommendations.
> "Requirements" are set by legislators and/or other policy
> stake-holders - it is the elected legislators who pass laws that say
> "your website must meet the WCAG 2.x standard", and not the W3C. In
> that regard, at least in the USA, you will probably never be able to
> mandate the types of details you are advocating for from the
> legislators, as it would likely run afoul of the US First Amendment
> (Freedom of Speech). (Consider as well that I may not *want* to share
> some of the types of details you are advocating for - what then?)
>
> For that reason, the editorial types of changes you are seeking can
> only truly be achieved through education and social change, it will
> never be something that would be mandated across the board: at best it
> is an editorial policy that some entities could adopt (and to that
> end, good examples and clear editorial direction to aid in that kind
> of adoption would assist in moving that ball forward.)
>
> If this is a topic you want to see more work happen on, I'll note that
> there is currently an Equity sub-group
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2022%2F08%2F15-wcag3-equity-minutes.html&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=d5OzIl7hq%2BgrSTP4SpVl0bipEacLX%2Fz610ObfbqTVn8%3D&reserved=0>
> working under the WCAG 3 effort that might be open to exploring this
> further. Volunteers are always welcome!
>
> Good luck!
>
> JF
>
> On Fri, Aug 19, 2022 at 7:57 PM Grey L. Pierce <glp@uoregon.edu
> <mailto:glp@uoregon.edu>> wrote:
>
> Hi John,
>
> I agree that a lengthy or exhaustive description wouldn't be
> appropriate for alt text of a portrait. "Photo of John Foliot, a
> white middle-aged man" is more in line with what I was suggesting,
> treating it as an image that provides supplemental information
> (https://www.w3.org/WAI/tutorials/images/informative/#example-2-images-used-to-supplement-other-information
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2Ftutorials%2Fimages%2Finformative%2F%23example-2-images-used-to-supplement-other-information&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jVPU66gDhIddMu3TvM9KPMHSCYdWf6yjjHo96YL3F%2Bo%3D&reserved=0>).
> If using <details>, <summary>, <figcaption>, etc. are determined
> to be better ways to provide the information, then that's the
> route to go, and we may want to consider that to be a basic
> requirement for portrait accessibility.
>
> --
>
> Grey L. Pierce (they/them)
>
> Digital Accessibility Architect
>
> University of Oregon
>
> ------------------------------------------------------------------------
>
> *From:*John Foliot <john@foliot.ca <mailto:john@foliot.ca>>
> *Sent:* Friday, August 19, 2022 3:50 PM
> *To:* Grey L. Pierce <glp@uoregon.edu <mailto:glp@uoregon.edu>>
> *Cc:* Hickey, Casey <ca.hickey@northeastern.edu
> <mailto:ca.hickey@northeastern.edu>>; John Foliot <john@foliot.ca
> <mailto:john@foliot.ca>>; w3c-wai-ig@w3.org
> <mailto:w3c-wai-ig@w3.org> <w3c-wai-ig@w3.org
> <mailto:w3c-wai-ig@w3.org>>
> *Subject:* Re: Thoughts on professional portrait (headshot) images?
>
> Hi Grey,
>
> > The question isn't just what percentage of people find
> portrait descriptions redundant or unnecessary...
>
>
> The alt text for a head shot *SHOULD NOT *be a lengthy
> description, _it should be succinct and to the point_.
> (i.e. alt="Photo: John Foliot", and *not *alt="Photo of John
> Foliot who has a white handlebar mustache and is wearing a cowboy
> hat. John is a heterosexual white male aged 63")
>
> As its name suggests, it is an /alternative/ to the image, not the
> /description /of the image - a nuanced but important distinction.
> This is because @alt maps to the Accessible Name (and NOT the
> Accessible Description) in the Accessibility tree accessed by
> screen readers. See here for more details:
> https://www.w3.org/TR/accname-1.1/#:~:text=Each%20platform%20accessibility%20API%20provides,See%20related%20accessible%20description
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.w3.org%2FTR%2Faccname-1.1%2F*%3A*%3Atext%3DEach*20platform*20accessibility*20API*20provides%2CSee*20related*20accessible*20description__%3BI34lJSUlJSUl!!C5qS4YX3!EW8tF-yS2bjpfauVEQZZGIds_QRfHiCRKqXk0iTFPGCSZjpWxAvAU26er0YgstifrhjyAw3h6nnk%24&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iFnFCqEIkzJMe1yQzG01NEF79zp2sVnWVdinokucS2M%3D&reserved=0>.
>
>
> Overloading text alternatives with all manner of descriptive
> details is the type of verbosity issue that I think Casey was
> concerned about (and to be clear I am not dismissing
> the importance of inclusion, simply advocating for the
> user-experience of non-sighted users). Providing information
> related to gender-presentation, race, etc. is generally
> inappropriate for text alternatives; it could (and should) be
> furnished via other methods (including potentially <details>
> & <summary>
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FHTML%2FElement%2Fdetails__%3B!!C5qS4YX3!EW8tF-yS2bjpfauVEQZZGIds_QRfHiCRKqXk0iTFPGCSZjpWxAvAU26er0YgstifrhjyA18HYnSO%24&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tESwrbCzHuS8fUDgGxTZXMmcLU6bmkSST86N2vPlizo%3D&reserved=0>,
> or perhaps <figcaption>
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FHTML%2FElement%2Ffigcaption__%3B!!C5qS4YX3!EW8tF-yS2bjpfauVEQZZGIds_QRfHiCRKqXk0iTFPGCSZjpWxAvAU26er0YgstifrhjyA4KIuCW2%24&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jWX82jyheANKGktWbXi6bUDn9gK66MAQ%2FC%2FwYOwczS8%3D&reserved=0> -
> and I personally remain extremely frustrated that Apple went off
> on their own and decided that @longdesc - despite being a valid
> attribute
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.w3.org%2FTR%2Fhtml-longdesc%2F__%3B!!C5qS4YX3!EW8tF-yS2bjpfauVEQZZGIds_QRfHiCRKqXk0iTFPGCSZjpWxAvAU26er0YgstifrhjyA-0c_dZe%24&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1c3IvjjdfdrPU5tYv2siGnssqgX8KuEgF9eVECV0mKA%3D&reserved=0>
> - is no longer supported on their platform, effectively killing
> off a useful attribute. It remains, in my opinion, yet another
> example of Apple's hubris).
>
> An important consideration here is that generally, the Accessible
> name is ALWAYS read aloud to the end user, whereas the Accessible
> Description is "on-demand" content - the user can retrieve it if
> they want, or ignore it as part of the reading experience. In this
> regard, it is not unlike bar or pie charts: the @alt text
> (Accessible name) might be "Monthly earnings for 2022", but then
> the Accessible Descriptions (furnished via multiple choices of
> technique) would be the actual earnings details for January,
> February, March, etc. Attempting to insert all of that data into
> an @alt text string would be a poor UX, and in fact depending on
> how much data is there, some screen readers might truncate the @al
> text string after 250 characters (+/-)
>
> I struggle then to support recommendations that, in support of one
> marginalized group, has a negative impact on another marginalized
> group. If the person in question wishes (for example) to be
> referenced as "they/them" then that should be included in text for
> all to see, and not buried in some alt text that most users will
> never see.
>
> Respectfully,
>
> JF
>
> On Fri, Aug 19, 2022 at 5:52 PM Grey L. Pierce <glp@uoregon.edu
> <mailto:glp@uoregon.edu>> wrote:
>
> It's worth noting the biases inherent in decisions or
> assumptions regarding not including actual descriptions of
> portraits. Race, ethnicity, and gender presentation, among
> other things, are generally apparent in a photograph, but are
> unlikely to be written anywhere, and none of those should be
> assumed based on someone's name, job title, etc. Knowing that
> information can be very helpful, particularly for people from
> marginalized racial, ethnic, or religious groups or gender
> identities. It's the same bias that leads to people writing
> alt text or descriptions that only mention a person's race if
> they aren't white (i.e., treating white as the default race of
> a human, so a white woman is described as a "woman," while a
> Black woman is described as a "Black woman," because "woman"
> on its own is assumed to imply "white woman").
>
> The question isn't just what percentage of people find
> portrait descriptions redundant or unnecessary , but whether
> it's primarily people of particular backgrounds (e.g., white,
> cisgender, etc.) who are more numerous, more likely to give
> their opinion, or more likely to be listened to who are saying
> they find them redundant. We need to ensure that we're
> including a diverse set of voices and perspectives, and giving
> them due consideration, when making decisions that may have
> disproportionate impacts on marginalized groups and people.
>
> --
>
> Grey L. Pierce (they/them)
>
> Digital Accessibility Architect
>
> University of Oregon
>
> ------------------------------------------------------------------------
>
> *From:*Hickey, Casey <ca.hickey@northeastern.edu
> <mailto:ca.hickey@northeastern.edu>>
> *Sent:* Friday, August 19, 2022 1:16 PM
> *To:* John Foliot <john@foliot.ca <mailto:john@foliot.ca>>
> *Cc:* w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org>
> <w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org>>
> *Subject:* Re: Thoughts on professional portrait (headshot)
> images?
>
> John,
>
> Thanks for this thoughtful response. I’d love to see an
> /augmentative/ image category added to WAI’s guidance for
> images in the page(s) I previously shared. In working with
> page templates and pattern libraries, I’ve been challenged by
> many scenarios where images often live in the space between
> decorative and informational. And when folks don’t feel
> confident about that choice, I fear the answer might be to err
> on the side of adding alt text even when it’s not helpful, as
> that could be considered the “safer” option. (Safer from an
> auditing/compliance standpoint, not from the standpoint of
> making the right decision).
>
> Thanks again for responding, the insight is helpful and
> appreciated.
>
> Casey
>
> *From: *John Foliot <john@foliot.ca <mailto:john@foliot.ca>>
> *Date: *Friday, August 19, 2022 at 3:23 PM
> *To: *Hickey, Casey <ca.hickey@northeastern.edu
> <mailto:ca.hickey@northeastern.edu>>
> *Cc: *w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org>
> <w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org>>
> *Subject: *Re: Thoughts on professional portrait (headshot)
> images?
>
> Hi Casey,
>
> > w3.org’s People directory
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fnam12.safelinks.protection.outlook.com%2F%3Furl%3Dhttps*3A*2F*2Fwww.w3.org*2FPeople%26data%3D05*7C01*7Cca.hickey*40northeastern.edu*7C8c93a4472a714600a3f708da8218553f*7Ca8eec281aaa34daeac9b9a398b9215e7*7C0*7C0*7C637965338264775190*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C%26sdata%3DcE8tXOWpfoM6jxJoPtyNBnhVAlc*2BkewO*2FZx3kiW57Xo*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!C5qS4YX3!GGdR83HrbI3lcrP1oJk4BsY7fQ3O1TuHn0UYtKLonqgLcyPVFTy7bhqp4cDOQQ6QnArKtCR2B9jFZixEToKHqIRW%24&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680099849130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HUYcV6c0BGtRBU98eOq1O9Q%2FUk4dt4A7EmXpUOG0uiQ%3D&reserved=0> uses
> “Photo of [first name] [last name]” as its alt text
>
> Yep. This topic has gone around before, and there really is no
> definitive answer, however I will suggest that in context, it
> is helpful to provide alt text in this scenario, as the photo
> of the person is (again, in context) an important part of the
> overall "Bio sheet" content.
>
> I've offered the following justification in the past: although
> a non-sighted user will not see the image, a head-shot image
> is actually a *VERY* important graphic file. Non-sighted users
> MAY want to show the photo to a sighted colleague ("I want to
> meet this person" or "I need a photo of Joe for this report I
> am writing for my manager" of similar types of uses), and so
> in context it is NOT a decorative image (if we had to label
> it, it is an "augmentative" image - not one of the 4 common
> categories of images). So the "SEO" aspect here is also an
> important consideration at a higher level.
>
> While I am not a daily screen reader myself, I do not think
> that most non-sighted users will be overly chuffed over a
> small bit of alternative text in this case - remember as well
> that it is trivial to skip past images and image alt-texts
> when using a screenreader, so on balance, while your concern
> over overt verbosity is appreciated, I'll venture to suggest
> it isn't an issue here.
>
> My $0.02 - your mileage may vary.
>
> JF
>
> On Fri, Aug 19, 2022 at 10:21 AM Hickey, Casey
> <ca.hickey@northeastern.edu
> <mailto:ca.hickey@northeastern.edu>> wrote:
>
> Hello WAI-IG,
>
> I’ve been giving some thought to whether headshot images
> should include alt text, especially when they’re adjacent
> to the pictured individual’s name.
>
> I’ve seen some opinions that say the image is meaningful
> because it’s conveying an impression. I also recognize
> that adding alt text to a series of profiles like this
> could weigh down the screen reader experience with
> seemingly redundant information.
>
> I’m leaning toward the latter, but I’d like to hear
> opinions/perspective from the group, or any information
> that there’s a standard/codified best practice here.
>
> WAI’s examples for Informative Images
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fnam12.safelinks.protection.outlook.com%2F%3Furl%3Dhttps*3A*2F*2Fwww.w3.org*2FWAI*2Ftutorials*2Fimages*2Finformative*2F%26data%3D05*7C01*7Cca.hickey*40northeastern.edu*7C8c93a4472a714600a3f708da8218553f*7Ca8eec281aaa34daeac9b9a398b9215e7*7C0*7C0*7C637965338264775190*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C%26sdata%3Dc4SqzPZLBA1IV4TVjKRdV5o7E0YhZb8ZIuZndxUr06k*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!C5qS4YX3!GGdR83HrbI3lcrP1oJk4BsY7fQ3O1TuHn0UYtKLonqgLcyPVFTy7bhqp4cDOQQ6QnArKtCR2B9jFZixETgeNCT2b%24&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680100005332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wMFiIW85y9Fl%2BNJZs8%2B%2FjMlfy8pkhEy6gjGvkB7%2B0EY%3D&reserved=0>
> and Decorative Images
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fnam12.safelinks.protection.outlook.com%2F%3Furl%3Dhttps*3A*2F*2Fwww.w3.org*2FWAI*2Ftutorials*2Fimages*2Fdecorative*2F%26data%3D05*7C01*7Cca.hickey*40northeastern.edu*7C8c93a4472a714600a3f708da8218553f*7Ca8eec281aaa34daeac9b9a398b9215e7*7C0*7C0*7C637965338264931857*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C%26sdata%3DETki0sW1rwxBeD7*2B6AvswKnu*2FtidjgGPSxy*2BFiZCqgk*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!C5qS4YX3!GGdR83HrbI3lcrP1oJk4BsY7fQ3O1TuHn0UYtKLonqgLcyPVFTy7bhqp4cDOQQ6QnArKtCR2B9jFZixEThgwjwlQ%24&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680100005332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hVFxYn11ah3bACDFgYcUjictDFRKLAqJ9%2FzkuQ8mE3s%3D&reserved=0>
> both come close, but neither directly address this use case.
>
> w3.org’s People directory
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fnam12.safelinks.protection.outlook.com%2F%3Furl%3Dhttps*3A*2F*2Fwww.w3.org*2FPeople%26data%3D05*7C01*7Cca.hickey*40northeastern.edu*7C8c93a4472a714600a3f708da8218553f*7Ca8eec281aaa34daeac9b9a398b9215e7*7C0*7C0*7C637965338264931857*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C%26sdata%3DpT4xtuubctvASYyDK*2BvC4pbiu8hME6KBuZa49s68b5U*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!C5qS4YX3!GGdR83HrbI3lcrP1oJk4BsY7fQ3O1TuHn0UYtKLonqgLcyPVFTy7bhqp4cDOQQ6QnArKtCR2B9jFZixETqOMa-eC%24&data=05%7C01%7CTill.Halbach%40nr.no%7Cdb201256216e46c2327e08da843993b5%7C86cc49578a634cd08c04bad9c688f3bd%7C1%7C0%7C637967680100005332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=z%2B08k6MGILNyz7IhzYnJKzfc7%2FFsDs1BTTfkdpDbVo4%3D&reserved=0>
> uses “Photo of [first name] [last name]” as its alt text,
> which leads me to second-guess my instinct here.
>
> Thank you for any thoughts.
>
> Casey Hickey
>
> Digital Accessibility Manager
> Information Technology Services
> Northeastern University
>
>
> --
>
> *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"
>
>
> --
>
> *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"
>
--
Med vennlig hilsen, / Best regards,
Till Halbach, seniorforsker / senior research scientist
Norwegian Computing Center / Norsk Regnesentral (NR) | http://nr.no/
Subscribe to our eInclusion newsletter: http://eepurl.com/s3aUD
Abonnér på e-Inkluderingsgruppens nyhetsbrev: http://eepurl.com/jsDif
Received on Monday, 22 August 2022 20:22:43 UTC