[wp-meta] [Making WordPress.org] #7155: Accessibility Statement is not in footer

Making WordPress.org noreply at wordpress.org
Wed Jul 26 19:45:09 UTC 2023


#7155: Accessibility Statement is not in footer
--------------------------------+---------------------
 Reporter:  elblakeo31          |       Owner:  (none)
     Type:  feature request     |      Status:  new
 Priority:  lowest              |   Milestone:
Component:  WordPress.org Site  |  Resolution:
 Keywords:                      |
--------------------------------+---------------------

Comment (by alh0319):

 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 wordpress.org?

 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.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7155#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list