Internet2 Accessibility + Performance Audit - July 2026

Executive Summary

This report provides a shared accessibility baseline and a practical execution plan for improving user experience across content and code.

It combines automated scans, manual WCAG checks, and supporting exports into one source of truth so the team can prioritize work, resolve ownership questions, and track what improves between audit cycles.

How to use this report:

• Overview: review current status, headline counts, and scope to get the temperature of the report.
• Content: fix alt text, meta descriptions, captions, reading level, and other CMS-editable items.
• Technical: these are code level items that will need to be resolved by a development team.
• Internal Pages / Contrast: use supporting evidence and visual examples to verify priorities and fix details.

Next 30 days: Over the next 30 days, prioritize Content items first by closing the top 5 content tasks, then coordinate on Technical fixes.

Tabs at a glance:

• Overview — executive summary and headline metrics. Start here, then hand off work by tab.
• Content — CMS-editable fixes from the Manual checklist (copy, media fields, captions, alt text patterns, and other content updates).
• Metadata — crawl inventory used to find missing titles and meta descriptions at scale.
• Images — crawl inventory used to find missing alt text at scale.
• Performance — GSC traffic + lab PSI + field CrUX vitals for prioritization.
• 404 / 500 — broken URLs and server errors from the status scan.
• Technical — code/theme/plugin items from the Manual checklist, grouped and labeled for developer execution.
• Internal Pages — the full export view for sorting/filtering by URL, Type, readability, and error totals.
• Contrast — visual evidence for contrast issues and verification after fixes.

Spreadsheet links: these open the source workbook this report was generated from. Use them when you need to verify raw rows, collaborate on ownership, or work directly in the underlying exports.

Open spreadsheet: Accessibility Audit · Manual · Internal Pages · Color Contrast · Page metadata · Page images · Performance (GSC+PSI) · 404 page status

• Accessibility Audit — scan output by URL (the base crawl export used to compute page counts and scope).
• Manual — the curated FAIL list that powers the Content + Technical action cards (ownership + remediation steps).
• Internal Pages — internal-page checks and supporting URL-level details used for triage and spot verification.
• Color Contrast — contrast evidence and screenshots tied to specific elements (visual confirmation for fixes).
• Page metadata — crawl inventory of titles and meta descriptions used to identify missing or incomplete metadata.
• Page images — crawl inventory of images and alt text used to identify missing alt text across pages.
• Performance (GSC+PSI) — Search Console traffic joined to lab PageSpeed and field CrUX vitals.
• 404 page status — hard/soft 404s and 5xx responses from the site status scan.

Scope note: this is an operational remediation and progress-tracking report built for planning and execution; it is not a legal certification of conformance.

Content items

These are fixes your content team can make in the CMS: alt text, meta and titles, media and captions, link and button wording, reading level, and other fields you can change without a deploy. They are drawn from the same Manual sheet as Technical items; we have already put what looks like a copy, media, or field edit into this list. When a row needs code, a theme change, or front-end behavior, you will see it under Technical. When you want every URL in the content check at once, use Internal Pages in the spreadsheet view.

Content support: Metadata · Images

How to read each item:

• What this list is for — rows the audit marked as Content because the fix is usually a direct update in the editor, media library, or SEO fields (for example, missing or weak alt text, unclear link text, captioning, or text that is hard to read for the audience you are writing for).
• What each card shows — a severity level, a short title, plain-language “what to fix” and “why it matters for visitors,” and a line that points to the same row in the Manual tab. Use the card with whoever owns the page so the published site matches the audit.
• How to work through the list — start with the highest-severity or most visible items if you need an order, or follow your editorial calendar. Make changes in draft or preview when your platform allows, publish, then spot-check the page (or re-run the same check the audit used) so you know the issue is really cleared before you close the item.

Technical items

These are the fixes that call for code, theme, or front-end work, not a quick edit in a text field. They are drawn from the same Manual sheet as your Content items. When the change is copy, media, or a field your content team owns, work it under Content (or use Internal Pages to see the full content-check by URL). When it is structure, behavior, or assistive-technology support, you are in the right tab.

How to read each item:

• What this list is for — rows the audit marked as Technical because the fix is usually in HTML, CSS, JavaScript, the theme, or a plugin (for example, keyboard use, ARIA, focus, landmarks, or custom components).
• What each card shows — a severity level, a short title, plain-language “what to fix” and “why it matters for visitors,” and a line that points to the same row in the Manual tab. Share the card and that row with whoever updates the site so you all match the spreadsheet.
• How to work through the list — start with the highest-severity or highest-visibility items if you need an order, or follow your own release plan. Use staging or a child theme when you can, then re-test the same page the way the audit did (keyboard, focus, and a quick screen-reader or automated check) so you know the line is really done before you move on.

No technical-classified FAIL rows.

Metadata

These fields are the “labels” people see in browser tabs, search results, and link previews. Use this card to quickly find what’s missing so your team can update it in the CMS and improve clarity.

How to use this section:

• Start with gaps — fill missing titles or meta descriptions on high-traffic and high-intent pages first.
• Normalize templates — if many pages share the same wording, update the template or CMS defaults so new pages stay consistent.
• Keep it human — write for clarity first. Plain language beats keyword stuffing.

Open “Page metadata” in Google Sheets

Missing page metadata (preview)

Crawl inventory: 60 page(s) evaluated (excluding /events/ and /event/). Missing metadata in this preview includes pages missing a title or meta description.

Images

This card shows images found on the site and what they “say” to assistive technology through alt text. Use it to fix missing alt text in the CMS so everyone gets the same information.

How to use this section:

• Fix missing alt text — meaningful images should have a short, specific description.
• Avoid repeats — don’t reuse the same generic alt across many different photos.
• Decorative images — if an image is purely decorative, it can be empty alt—but that should be intentional.

Open “Page images” in Google Sheets

Images missing alt text (preview)

Preview	Image URL	Alt text	Found on pages	Where found
	https://internet2.edu/wp-content/uploads/2022/03/c-NET-stats-1024x341.png	Missing alt text	https://internet2.edu/cloud/internet2-net-plus-services/	img
	https://internet2.edu/wp-content/uploads/2026/03/NTNC-Map-2026-0208-small.jpg	Missing alt text	https://internet2.edu/northern-tier-network-consortium/	img
	https://internet2.edu/wp-content/uploads/2023/06/n-ntnc-logo-small.png	Missing alt text	https://internet2.edu/northern-tier-network-consortium/	img
	http://internet2.edu/wp-content/uploads/2020/09/Security-stats-1024x296.png	Missing alt text	https://internet2.edu/security/incommon-identity-and-access-management/	img
	https://internet2.edu/wp-content/uploads/2020/10/c-mike-erickson-profile-photo-1-550x698-1.jpg	Missing alt text	https://internet2.edu/community/about-us/executive-leadership/	img
	https://internet2.edu/wp-content/uploads/2020/10/c-carrie-groff-updated-profile-photo.jpg	Missing alt text	https://internet2.edu/community/about-us/executive-leadership/	img
	https://internet2.edu/wp-content/uploads/2025/11/members-callout-3-1-scaled.jpg	Missing alt text	https://internet2.edu/community/membership/	img
	https://internet2.edu/wp-content/uploads/2026/01/ann-doyle-headshot.jpg	Missing alt text	https://internet2.edu/community/membership/	img
	https://internet2.edu/wp-content/uploads/2026/02/gail-krovitz-headshot.jpg	Missing alt text	https://internet2.edu/community/membership/	img
	https://internet2.edu/wp-content/uploads/2025/08/therese-p-circle.png	Missing alt text	https://internet2.edu/community/membership/	img
	https://internet2.edu/wp-content/uploads/2025/08/jessica-s-headshot.jpg	Missing alt text	https://internet2.edu/community/membership/	img
	https://internet2.edu/wp-content/uploads/2026/01/amber-walters-headshot-1.jpg	Missing alt text	https://internet2.edu/community/membership/	img
	https://internet2.edu/wp-content/uploads/2025/03/eduroam-map-snip-1024x402.jpg	Missing alt text	https://internet2.edu/eduroam-global-roaming-access-service/	img
	https://internet2.edu/wp-content/uploads/2025/08/a-com-for-you-2-500x500.png	Missing alt text	https://internet2.edu/community/community-leadership-and-culture-initiative/emerging-leaders-scholarship-program/	img
	https://internet2.edu/wp-content/uploads/2020/09/Network-stats-1024x330.png	Missing alt text	https://internet2.edu/network/	img
	https://internet2.edu/wp-content/uploads/2025/07/services-image-500x500.jpg	Missing alt text	https://internet2.edu/community/membership/higher-education-membership/	img
	http://internet2.edu/wp-content/uploads/2025/03/coherent-optics-2-1024x488.jpg	Missing alt text	https://internet2.edu/internet2-and-cisco-push-coherent-optics-farther/	img

A further 59 crawled entries are excluded from this list (meta:og:image: 59). Those are page metadata tags used for social sharing previews, not image elements on the page — they have no alt attribute to write, so they are not accessibility work.

Performance / CWV

Lab PageSpeed Insights scores plus field Chrome UX Report (CrUX) vitals, joined to Google Search Console traffic for the same URLs. Use this to prioritize fixes on pages that are both slow and high-traffic.

How to use this section:

• Lab vs field — PageSpeed lab metrics (LCP/CLS/TBT) are a controlled run; CrUX values reflect real Chrome users when enough traffic exists. Where a page has too few visits for its own record, PageSpeed reports the site-wide figure instead — the “Real-user data source” column says which you are looking at.
• Start with traffic — sort by clicks in the sheet when deciding what to fix first; the preview below ranks by lab LCP to surface slow pages quickly.
• Accessibility score — The Lighthouse accessibility score is automated only; it is not a substitute for manual WCAG review.

Open “Performance (GSC+PSI)” in Google Sheets

Total GSC clicks in window: 8259 · PSI errors: 0

Slowest lab LCP (preview)

Internal Pages

This tab is the breadth view: every post and page in the automated content check, 1,599 rows in all. It is a wider net than the 60 pages evaluated in depth elsewhere in this report, and it runs automated checks only — no manual review, keyboard testing, or performance data. Totals here will not match the other tabs, and they are not meant to.

This is the same automated content check as the rest of the report, shown as a full list in the sheet: one row per post, page, or other type in the export. Use it when you want to see every URL in one place and sort or filter the way you already do in Google Sheets. The Content and Technical tabs are where we queue the most important fixes; this view helps you see patterns and totals across the site.

The key columns in plain terms:

• Rules passed: how many of the tool’s rules passed for that page on this run. A higher number usually means less to fix on that line, in the tool’s own scoring.
• Failed rules: how many rules failed. The themes often match what you are fixing under Content or Technical, but here you can see the counts on every row at once.
• Reading level: a rough U.S. grade level for the main text (for example, “5th” or “10th”). It is an editing signal, not a pass/fail for WCAG by itself—but clear, audience-appropriate writing is still a big part of content people can actually use, including on small screens, in a hurry, or with translation. If the grade looks high for who you are writing for, adjust the copy in your CMS: shorter sentences, plainer words, and headings to break up long text. On a later report run, you can see whether the grade moved in a direction you are happy with.

Open “Internal Pages” in Google Sheets

Where the errors concentrate

Every row in this export belongs to a content type, and content types share templates. That matters for sequencing: Posts accounts for 76.4% of all errors across 1,069 rows at an average of 4.81 per row. When an average repeats that evenly across a type, the cause is almost always the shared template rather than individual authoring — so one theme fix clears a large share of the total, and the remaining rows are genuine per-page edits.

Read this as a sequencing guide: types at the top return the most per fix when the work is done in the template. Types with a low average and few rows are page-level edits.

Fix these first: findings weighted by traffic

This ranks the evaluated pages by findings multiplied by Search Console clicks over the reporting window, so a problem on a page real visitors reach outranks the same problem on a page that gets almost no traffic. Traffic data is available for 43 of these pages; pages without it are ranked on findings alone and appear lower.

Priority = (content-check errors + WCAG scan violations) × clicks. It is a sequencing aid, not a severity rating — a single serious blocker on a low-traffic page can still outrank everything here.

Data preview

Showing the first 75 of 1599 data rows. Open the spreadsheet for the full export.

Color Contrast

Most of your brand color is meant to be controlled programmatically: design tokens, theme settings, global CSS, and the same components used across templates. When text and background colors come from that system, contrast usually stays within your target (for example, WCAG AA) without hand-tuning every page. The situations that most often break that pattern are one-off colors—inline styles, hard-coded hex or RGB in the page HTML, or custom blocks that bypass the theme—where an author or an old embed can pair colors the system never would. This tab is the visual evidence for where the checker saw a problem. We still confirm color contrast on every audit so nothing slides by as content and code change over time.

How to read this tab:

• What you are looking at — screenshots from the contrast export tied to specific elements, so you can see the foreground/background relationship the tool measured, not just a number in a cell.
• Why “programmatic” matters — fixes you make in the theme, token set, or shared CSS fix many pages at once and keep new content on-brand. Fixes trapped in a single page’s HTML or a custom color pick in a block editor have to be found and updated one by one, and they are the first place to look when contrast drifts.
• What we do each audit — we run the contrast check and review these results as part of the report, even when your system is well controlled, because templates change, plugins update, and editors add new content. Think of this tab as the regular safety check, not a one-time pass.

Open “Color Contrast” in Google Sheets

Image references

UI element	Screenshot	Colors tested	Contrast ratio	Meets WCAG AA
		#535353 text	7.7:1	Pass
		#01000B text on #FFFFFF background	20.9:1	Pass
		—	8:1	Pass
		—	8:1	Pass
		#535353 text	7.7:1	Pass
		#00626E text	6:1	Pass
		#00626E text	6.3:1	Pass
		#01000B text on #FFFFFF background	20.9:1	Pass
		#00626E text	6.3:1	Pass
		#FFFFFF text on #4C4C4C background	8.6:1	Pass
		#00626E text on #00626E background	7.1:1	Pass
		#01000B text	16.6:1	Pass
		—	6.4:1	Pass
		#000000 text	15.5:1	Pass
		#01000B text	18.8:1	Pass
		#00626E text on #FFFFFF background	7.1:1	Pass
		#01000B text	16.6:1	Pass
		—	6.4:1	Pass
		—	6:1	Pass
		#01000B text on #8900D3 background	12.9:1	Pass

Showing first 20 of 20 data rows. Open the spreadsheet for the full export.