Skip to content

Conversation

@remibetin
Copy link
Member

This applies the same footer design as on the WAI website.

Related to w3c/wai-website-theme#163.

@remibetin remibetin requested a review from kfranqueiro January 5, 2026 11:12
@netlify
Copy link

netlify bot commented Jan 5, 2026

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit c33afb3
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/696115d7e2a0c70008261035
😎 Deploy Preview https://deploy-preview-4850--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@iadawn
Copy link
Contributor

iadawn commented Jan 5, 2026

This looks good to me. If Ken is happy I can do an understanding and techniques update this Thurs.

@w3cbot
Copy link

w3cbot commented Jan 8, 2026

kfranqueiro marked as non substantive for IPR from ash-nazg.

xslt/base.xslt Outdated
<div class="wai-global-footer__cta w3c-l-cluster w3c-l-cluster--vertical-align">
<ul class="w3c-clean-list" role="list">
<li class="w3c-with-icon--before w3c-with-icon--larger">
<img class="w3c-icon w3c-icon--larger" src="https://www.w3.org/WAI/assets/images/email.svg" width="30" height="30" alt="" aria-hidden="true">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we should even worry about what's in base.xslt, as it has probably already missed a few prior updates (it hasn't been updated since I started working here). Moreover, it looks like the code pasted here would not be valid XML, such as this non-self-closing img tag, which is why I suggest we leave it out.

I had previously gone through and removed parts of the XSLT that we definitely weren't using anymore; maybe I should remove more of it... cc @iadawn

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we can ignore base.xslt... or indeed any XSLT ... please, please? :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks like the code pasted here would not be valid XML, such as this non-self-closing img tag, which is why I suggest we leave it out.

Indeed, thanks for flagging!

I'm not sure we should even worry about what's in base.xslt, as it has probably already missed a few prior updates

I guess the only question I have is: if we don't update this file, will some pages still display the old footer?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, we have relied exclusively on the Eleventy build for roughly 18 months at this point. I partially cleaned out parts of the XSLT that I knew for sure we would never use again but had left any build tasks I'd had doubts about; I'm suspecting we don't have a use for any of what's remaining at this point, either.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @kfranqueiro I've reverted the changes made to base.xslt at this point.

@remibetin remibetin requested a review from kfranqueiro January 9, 2026 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants