[FILECOIN V3][UXIT-3046] Fix Crawl and Audit issues [skip percy]

[barbaraperic]

📝 Description

This PR addresses several accessibility and content issues identified in the audit

🛠️ Key Changes

Accessibility Improvements
• Add alt text to blog post featured images - double checked with ChatGPT if alt is necessary (9 blog posts updated)
• Update blog post template to properly use image.alt attribute when available

Content Fixes
• Fix missing H1 headings in storage provider onboarding page
• Fix broken links across blog content

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
filecoin-site	Ready	Preview, Comment	Jan 8, 2026 3:01pm

3 Skipped Deployments

Project	Deployment	Review	Updated (UTC)
ffdweb-site	Skipped		Jan 8, 2026 3:01pm
filecoin-foundation-site	Skipped		Jan 8, 2026 3:01pm
filecoin-foundation-uxit	Skipped		Jan 8, 2026 3:01pm

[notion-workspace]

[filecoin.io V3] Fix Crawl and Audit issues

[mirhamasala]

Looking good - I do wonder whether alt image texts like these mean anything "Akave Cloud and Filecoin partnership graphic" to the user? Should we perhaps be more descriptive? ☀️

[barbaraperic]

Looking good - I do wonder whether alt image texts like these mean anything "Akave Cloud and Filecoin partnership graphic" to the user? Should we perhaps be more descriptive? ☀️

Good question! I've checked with chatGPT 👇

WCAG guidance (in plain language)

WCAG doesn’t say:

• “Describe the image fully”

It says:

• Provide a text alternative that serves the same purpose

For hero images, the purpose is usually:

• “This article is about ProPGF Batch 1 reflections”

So this is sufficient:

• alt="ProPGF Batch 1 learning and reflections graphic"

It:

• identifies the subject
• matches the article intent
• avoids redundancy
• respects user time

When hero images do need more detail

A hero image needs more descriptive alt only if it adds unique information, for example:

• a hero chart showing growth
• a timeline embedded in the hero
• a photo documenting a specific event not described elsewhere

In those cases, the image is no longer just a hero — it’s content.

[mirhamasala]

@barbaraperic

Thanks for looking into this! I did a bit of further digging since I know we also have the empty alt tag option. Pasting some info here from Claude:

---

Ask: "What does a screen reader user lose by not seeing this image?"

Use alt="" when:

• The image is purely decorative styling (borders, dividers, background patterns)
• The adjacent heading/text already conveys everything the image shows
• Announcing it would be redundant noise
• Example: A generic hero graphic with "Blog Post Title" overlaid, where the same title is in an H1 right below

Use brief descriptive alt when:

• The image provides context not fully captured by surrounding text
• It's part of the content experience (even if supporting, not primary)
• It helps users understand what kind of content this is
• Example: "ProPGF Batch 1 learning and reflections graphic" - this tells you it's about a specific batch/cohort and has a reflective focus, which might not be obvious from a headline alone

A useful test: Imagine you're on a phone with a bad connection and images aren't loading. Would seeing "[ProPGF Batch 1 graphic]" as a placeholder help you understand the page better? If yes → use brief alt. If it adds nothing → use alt="".

---

Looking at the full context: alt="" is the better choice here.

Here's why:

The title already says: "Akave Cloud x Filecoin: S3-Compatible Object Storage for Enterprise and DePIN"

The current alt text says: "Akave Cloud and Filecoin partnership graphic"

What a screen reader user would experience:

1. Heading: "Akave Cloud x Filecoin: S3-Compatible Object Storage for Enterprise and DePIN"
2. Image: "Akave Cloud and Filecoin partnership graphic"

That's essentially hearing the same information twice in a row - pure redundancy.

Apply the test: What does a screen reader user lose by not seeing this image?

• Nothing. The title already tells them this is about Akave Cloud and Filecoin working together.
• The image is almost certainly a branded hero graphic (logos, maybe some design flourishes) that reinforces what the headline already states.
• The entire article explains the partnership in detail.

If this were different, you'd want alt text:

• If the graphic showed a technical diagram of how the systems integrate
• If it displayed specific statistics or a comparison chart
• If it contained a product roadmap or timeline
• If it showed something visual that isn't described in text

But for a standard partnership announcement hero graphic? It's decorative branding. Use alt="" and let the screen reader move straight from the excellent, descriptive title into the article content.

---

We do have these patterns on fil.org as well, where we decided to use empty alt tags for events and ecosystem explorer heroes by default. We might not want that as a default option here... but, again, in this case, I do think we need to ask ourselves what these alt texts add for screen readers?

[mirhamasala]

@barbaraperic ~ Thank you for looking into this again. Left a response and some suggestions. Can be merged once looked into. 🙏🏼✨