E-mail List Archives
Thread: Info graphic description
Number of posts in this thread: 4 (In chronological order)
From: Angela French
Date: Fri, May 11 2018 9:19AM
Subject: Info graphic description
No previous message | Next message →
Hello,
We have a rather complex infographic<https://www.sbctc.edu/colleges-staff/it-support/ctclink/governance-framework-flowchart.aspx> on a new web page that needs to be described for those who can't see it. (Heck, it needs to be described even for those who can see it! ). My question is this: should the description attempt to describe the graphic itself with the information in it, or just be a narrative of the information behind the graphic as if the graphic did not even exist? I lean towards the latter, but am wondering how others handle these sorts of graphics.
Thank you
Angela French
ctcLink Digital Asset Manager
Washington State Board for Community and Technical Colleges
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = > * o: 360-704-4316 * f: 360-704-4414
sbctc.edu<https://www.sbctc.edu/> * Twitter: @SBCTCWashington<https://twitter.com/SBCTCWashington> * Facebook: @WASBCTC<https://www.facebook.com/wasbctc/>
From: Lamond, Keith
Date: Fri, May 11 2018 9:26AM
Subject: Re: Info graphic description
← Previous message | Next message →
My approach would be slightly in between. I would start the description with, "An infographic of the CTcLink Governance Framework that provides the following information..." From there I would provide the narrative of the info graphic without providing any details of the visual layout of the graphic.
-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Angela French
Sent: Friday, May 11, 2018 11:19 AM
To: WebAim Forum ( = EMAIL ADDRESS REMOVED = ) < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Info graphic description
[External Email]
----------------------------------------------------------------------
Hello,
We have a rather complex infographic<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.sbctc.edu_colleges-2Dstaff_it-2Dsupport_ctclink_governance-2Dframework-2Dflowchart.aspx&d=DwIGaQ&cÿ2GokX4A_6S-cy_JRNEiQ&r=7QG6ffChijbDKx3bYL1y37tYFb4ByB2DeBgALZ5VET8&m=vpJ4FlVS4X9FsIXeVoP3KH6PPOdIpdpgnmjLsQ6Mf68&s=lHxi0PvslRLLWJqeXNp-keY2_eYmtbM5uGcXweibX7M&e=> on a new web page that needs to be described for those who can't see it. (Heck, it needs to be described even for those who can see it! ). My question is this: should the description attempt to describe the graphic itself with the information in it, or just be a narrative of the information behind the graphic as if the graphic did not even exist? I lean towards the latter, but am wondering how others handle these sorts of graphics.
Thank you
Angela French
ctcLink Digital Asset Manager
Washington State Board for Community and Technical Colleges = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = > * o: 360-704-4316 * f: 360-704-4414 sbctc.edu<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.sbctc.edu_&d=DwIGaQ&cÿ2GokX4A_6S-cy_JRNEiQ&r=7QG6ffChijbDKx3bYL1y37tYFb4ByB2DeBgALZ5VET8&m=vpJ4FlVS4X9FsIXeVoP3KH6PPOdIpdpgnmjLsQ6Mf68&s=Mu7zE3yFA0U5NJAgL12yqhWa4Jt8XVUwAD1kjrY_ZHc&e=> * Twitter: @SBCTCWashington<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_SBCTCWashington&d=DwIGaQ&cÿ2GokX4A_6S-cy_JRNEiQ&r=7QG6ffChijbDKx3bYL1y37tYFb4ByB2DeBgALZ5VET8&m=vpJ4FlVS4X9FsIXeVoP3KH6PPOdIpdpgnmjLsQ6Mf68&s<4G49z2sB3y0nRM5dIiR8iNe-Bo75MsoCI2ZmMZrN0&e=> * Facebook: @WASBCTC<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_wasbctc_&d=DwIGaQ&cÿ2GokX4A_6S-cy_JRNEiQ&r=7QG6ffChijbDKx3bYL1y37tYFb4ByB2DeBgALZ5VET8&m=vpJ4FlVS4X9FsIXeVoP3KH6PPOdIpdpgnmjLsQ6Mf68&s=GEF7-hsDSrsYQlXpKmjyKng5kEQ05f3gYyImF-V7iGs&e=>
The preceding message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for the person or entity to which it is addressed, and may contain information that is confidential, protected by attorney-client or other privilege, or otherwise protected from disclosure by law. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error and destroy the original message and all copies.
From: glen walker
Date: Sat, May 12 2018 2:48PM
Subject: Re: Info graphic description
← Previous message | Next message →
Is an infographic required so that it can be easily shared as an image?
If not, then had you looked into *not* creating an infographic? When I
look at it, I see several sets of bullet points, headings, and other text
that could easily be created with native html and a little styling. As it
is, I find it hard to know where to start in the image and everything seems
to point to everything. The infographic may already be done and in
production but if it's hard to understand visually, it'll be hard to
describe. If the infographic were thought of as straight html/css, it
might have been easier to convert to a graphic.
In any event, you can still conceptualize the graphic as html. You can
have a completely visually hidden html version of the graphic that allows
traversal by lists, headings, etc.
From: Mallory
Date: Tue, May 15 2018 11:37AM
Subject: Re: Info graphic description
← Previous message | No next message
I was thinking the same thing as Glen. You could have images for the arrows etc with alt text like "[section-name points to [other section name]" to get the flow stuff in.
As simple a summary as possible, and visible (because you're right, people who *can* see need it too) would help a lot, whether the viewer has a cognitive disability or not.
Usually infographics are meant to make a complex pile of words easier to understand visually. I'm not certain this one does that :P
cheers,
Mallory
On Sat, May 12, 2018, at 10:48 PM, glen walker wrote:
> Is an infographic required so that it can be easily shared as an image?
>
> If not, then had you looked into *not* creating an infographic? When I
> look at it, I see several sets of bullet points, headings, and other text
> that could easily be created with native html and a little styling. As it
> is, I find it hard to know where to start in the image and everything seems
> to point to everything. The infographic may already be done and in
> production but if it's hard to understand visually, it'll be hard to
> describe. If the infographic were thought of as straight html/css, it
> might have been easier to convert to a graphic.
>
> In any event, you can still conceptualize the graphic as html. You can
> have a completely visually hidden html version of the graphic that allows
> traversal by lists, headings, etc.
> > > >