FIREANT STUDIO

Prepared by FIREANT STUDIO for Internet2

Internet2 Accessibility Report — Client Summary (July 2026)

Technical fixes

WCAG 2.2 AA

94.7
Health score
18,313
Page views
8,259
Search clicks
4
Technical fixes
Content

10

10 open content priorities.

Traffic

18,313

Page views (Jul 1, 2026–Jul 31, 2026)

Sample

60

Pages evaluated in depth.

404's

12

12 in July scan.

Executive summary

Following the July 2026 accessibility audit, this report gives a clear picture of where internet2.edu stands today — what was fixed in the theme and infrastructure, what content teams can tackle in WordPress, and which high-traffic pages deserve attention first.

Our review targeted WCAG 2.2 AA and focused on 60 pages evaluated in depth — the URLs that carry the most weight for members and partners. Traffic in Jul 1, 2026–Jul 31, 2026: 18,313 page views from all channels and 8,259 organic Google Search clicks across this sample. Search clicks count only people who arrived from Google to that exact URL; page views include direct visits, email, internal links, and other sources. 84% of sample search clicks went to the homepage. Findings combine automated scans, manual expert review, and live-page checks so they reflect what people experience in the browser.


What’s working well

The evaluated sample enters this cycle from a solid baseline: composite health score 94.7 out of 100, with the ten most-searched sample URLs averaging 93.5 on Lighthouse accessibility. That does not mean the work is finished — it means the remaining backlog is concentrated and actionable rather than site-wide.

  • The ten sample pages with the most Google Search traffic average 93.5 on Lighthouse accessibility — a solid baseline on the URLs people reach most often from search.
  • During Jul 1, 2026–Jul 31, 2026, the 60-page sample recorded 18,313 page views from all channels and 8,259 organic Google Search clicks.
  • 57 of 60 priority pages are tracked in the full-site content review (1,599 site pages total). 3 sample pages are covered by other checks in this report rather than that inventory row.
  • Title or meta description gaps appear on 1 page in the sample — a small cleanup task rather than a site-wide pattern.

Progress since July

When the July audit closed, we tracked 4 theme-level technical items — patterns in the WordPress theme, navigation, or shared components that affect keyboard and screen reader users across many pages. A separate site-status scan also flagged 12 broken author archive URLs (server errors on legacy author pages listed in the sitemap). Those items are listed in detail on the Technical tab and, for URL status, under Site checks.


Where to start

When you plan the next content sprint, these four areas give the most return for members and partners who use assistive technology or mobile devices.

  • /cloud/internet2-net-plus-services — Start here — this page drew 280 visits from all channels in the review window and still needs several content fixes, including a statistics chart that needs a short text description for people who listen to the page instead of viewing it.
  • /network/initiatives-partnerships/insight-console — This page has the most open content items in our review sample — a strong candidate for a focused cleanup pass.
  • Links that do not say where they go (46 links across 25 pages). Phrases like “Read more” or “Click here” are hard to follow when someone hears a list of links out of context. Each link should describe its destination.
  • Tables missing row or column labels (249 table cells across 170 pages). Program and network pages rely on data tables. Proper headers help people using screen readers follow the rows and columns.

Where content work continues

The largest remaining body of work sits on the Content tab: 10 fix categories that your content team can address in WordPress — link text, image descriptions, heading order, data tables, color contrast on page styles, and similar patterns that repeat across templates. These are not theme defects; they are editorial improvements that scale when you fix shared templates and high-traffic pages first.

The table below lists sample pages by page views and open content items so teams can see where effort will reach the most visitors.


High-traffic sample pages

Page views (Jul 1, 2026–Jul 31, 2026) counts every visit to the page from any source (direct, email, internal links, search, and more). Google Search clicks (Jul 1, 2026–Jul 31, 2026) counts only people who clicked through from Google Search to this exact URL.

PageContent typePage views (Jul 1, 2026–Jul 31, 2026)Google Search clicks (Jul 1, 2026–Jul 31, 2026)Content items to address
/community/careersCommunity9681362
/servicesPages663164
/community/community-leadership-and-culture-initiative/emerging-leaders-scholarship-programCommunity611244
/community/about-usCommunity580883
/community/membershipCommunity431240
/cloud/cloud-learning-and-skills-sessions/class-events-scheduleCloud417136
/networkPages302295
/community/about-us/executive-leadershipCommunity292314
/cloud/internet2-net-plus-servicesCloud280969
/northern-tier-network-consortiumPages202355
Page 1