Opened 10 months ago

Last modified 10 months ago

#7155 new feature request

Accessibility Statement is not in footer

Reported by: elblakeo31's profile elblakeo31 Owned by:
Milestone: Priority: lowest
Component: Site Keywords:


I expected to find the WordPress accessibility statement ( in the footer but didn't. Many organizations that take accessibility seriously choose to display their accessibility statement in a place that is easy to find, usually the footer. Moreover, I've noticed in user tests those who use assistive technologies, such as screen readers, often look for an accessibility statement in a footer to understand a site's accessibility program before they start browsing content.

Beyond meeting users' expectations and establishing Accessibility as a WordPress priority, linking to the WP accessibility statement in the footer keeps in line with best practices and rules established by the W3C's Web Accessibility Initiative (WAI). Check out the "Where to put an accessibility statement" section of Developing an Accessibility Statement:

In researching tickets, an accessibility statement was mentioned as part of #3975. That ticket generally referred to footer/header links, while this ticket is only concerned with adding an accessibility statement link.

As for placement, I would suggest adding "Accessibility Statement" between "Matt" and "Privacy". Putting "Accessibility Statement" before "Privacy" follows the link order that is in the About page navigation.

Change History (7)

This ticket was mentioned in Slack in #accessibility by bbertucc. View the logs.

10 months ago

#2 @Otto42
10 months ago

  • Priority changed from normal to lowest
  • Type changed from defect (bug) to feature request

#3 follow-up: @joedolson
10 months ago

I agree that an accessibility policy statement should live at the same level of importance as the privacy statement; although I'll also observe that the the page at is different from the the accessibility statement; is the privacy statement for, reflecting the privacy somebody can expect while browsing and using the network of websites. is about the accessibility goals of the WordPress project, and is about the WordPress CMS.

For clarity, I think what we'd actually need is a statement about the accessibility of the site. Perhaps we could combine those into a single document, as long as we're clear about which sections refer to the software vs the site.

This ticket was mentioned in Slack in #accessibility by travelgirl. View the logs.

10 months ago

This ticket was mentioned in Slack in #accessibility by bbertucc. View the logs.

10 months ago

#6 in reply to: ↑ 3 @alh0319
10 months ago

I agree with @joedolson that there's a separate accessibility statement needed for the website versus the software. Is there actually anyone who has knowledge of the current accessibility status of

I've seen a fair bit of content published that looked like it was published without regard to accessibility or without an accessibility audit prior to publishing. That leads me to believe that before we can draft an honest accessibility statement about the website, we would need to get the Meta team to agree on what the accessibility policy is. I.e.:

  • What standard are they following (if any), and what testing are they committing to doing while editing/adding content?
  • What issues already exist on the site, and what is being done to address them on what timeline? (We may need an audit to answer the first part.)
  • If someone encounters an accessibility issue on the site, how can they report that issue and get help?

We need answers to those questions before we can even draft an accessibility statement for the website.

#7 @joedolson
10 months ago

Drupal handles this in an interesting way; they just have a very brief section about community sites, and point users to submit issues if they encounter accessibility problems. This could be a short-term solution, given that a complete audit of the network is simply not feasible in the short term.

See, under "Community Sites".

Note: See TracTickets for help on using tickets.