Make Planning Graphics Readable and Explainable
Improve one planning graphic's labels, contrast, reading order, caption, and text alternative. Inspect the finished export at its actual display size and document what you checked before handing it to the person preparing publication.
What you will make
A revised PNG or PDF graphic with a caption, text alternative, and short checklist of completed and unresolved checks.
A graphic only communicates when people can read its information and understand its meaning. Simple checks can reveal clipped labels, weak contrast, missing context, or reliance on color. They help improve a product without claiming that one exercise proves full accessibility compliance.
- Check labels and layout at the intended viewing size.
- Add a useful caption and text alternative for an informative graphic.
- Test selected contrast and reading-order conditions while reporting their limits.
Before you start
- An authorized planning map, chart, or concept illustration with a documented source or brief.
- A graphics or presentation editor and a way to measure contrast. No particular paid design tool is required.
Project connections: Bluefield VA comprehensive plan; Haysi downtown; Clintwood downtown reuse and housing; Red Onion industrial website and marketing; Clinchco and Nora workforce and former-school reuse.
Work through the method
Name the communication task
State the graphic's purpose, audience, and intended screen or print size. Check the title and caption against its documented source or concept brief.
Check your work: Purpose and viewing context are clear.
Make labels readable
Start digital labels at 16 CSS pixels at actual display size. This course convention is not a WCAG minimum. Increase size or simplify dense content.
Check your work: Labels are legible without clipping or overlap.
Check contrast and coding
Measure contrast. WCAG specifies 4.5:1 for normal text and 3:1 for qualifying large text, with exceptions. Pair colors with labels, symbols, or patterns. WCAG large text means at least 18 points (24 CSS pixels), or 14 points (about 18.67 CSS pixels) when bold. For smaller text use 4.5:1. Enter the actual foreground and background color values in a contrast checker, such as WebAIM, and record the ratio. Check labels and legends at the intended output size.
Check your work: Ratios and unresolved visual distinctions are recorded.
Write a caption and alternative
Write a caption with subject, geography or concept status, period, source, and supported message. Provide a useful text alternative and, when needed, a table or longer description.
Check your work: Essential information is available beyond the image.
Inspect sequence and export
Check title, graphic, legend, caption, and source sequence. Reopen the export at normal size. Supply PNG alternatives through the publishing page or an accompanying text file.
Check your work: The delivered graphic and accompanying text work together.
Record the review limits
Record completed checks and untested tags, reading order, or interactions. Pass the note to the person publishing the graphic; selected checks do not establish full compliance.
Check your work: The handoff identifies completed and remaining review.
Revise and explain one planning graphic
- Choose an authorized graphic and state its audience and purpose.
- Improve labels, layout, and contrast; record the digital label-size target and measured ratios.
- Write a source-faithful caption and a useful text alternative or supporting table.
- Reopen the export at its intended size and save a note of completed and unresolved checks.
Bring the method into a product
- Revised planning graphic
- Caption, text alternative, and review note
Suggested formats: PNG, PDF, TXT, CSV.
Reflect: What important message would be lost if a reader could not see the image or distinguish its colors?
Avoid these mistakes
- Sixteen pixels is a course starting target, not a universal WCAG requirement.
- Alt text belongs to the publishing context; a PNG export alone is not the whole accessible presentation.
- Selected contrast and content checks do not establish full WCAG conformance or an ADA guarantee.
Check your understanding
These short checks are practice, not course grades. Read the explanation, revise your reasoning and try again when useful.
Submit your practice product
Use the existing course login. Your file and notes are visible to you and the instructor, not the public or other students. Official graded assignments still go to Canvas.
Submit a PDF, image, DOCX, UTF-8 text/CSV, JSON or GeoJSON file. For several products, combine the evidence, text alternatives and notes into one accessible PDF or DOCX, or submit each file separately with the same project title. Keep native ArcGIS projects and complete shapefile bundles locally. Upload only work you can share with the instructor; leave out confidential client records and sensitive species or infrastructure locations.
My academy workSources and further help
- WCAG 2.2: Non-text Content
W3C. WCAG 2.2 Success Criterion 1.1.1 on alternatives for informative non-text content.
- WCAG 2.2: Contrast (Minimum)
W3C. WCAG 2.2 Success Criterion 1.4.3 contrast thresholds and exceptions.
- WebAIM contrast checker
WebAIM, Utah State University. Enter foreground and background colors and compare reported text contrast ratios.
Guidance may change. Follow the current source and check the software version, license, local rules and data limitations before applying the method.