WordPress.org
Get WordPress

Make WordPress Core

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#26157 closed enhancement (fixed)

Create new tag: accessibility-ready

Reported by: AccessibleJoe Owned by: matt
Priority: low Milestone: 3.8
Component: Themes Version: 3.8
Severity: normal Keywords:
Cc: Focuses:

Description

The WordPress Accessibility Team has posted ​theme check guidelines for optional accessibility theme checking. When a theme passes the accessibility checking process it will be indicated with the accessible-ready tag. Like the language-ready tag, the accessible-ready tag means that the theme is ready to be used accessibly. It is the responsibility of the theme implementers and the content editors to continue to use the theme accessibly.

Attachments (2)

26157.diff​ (472 bytes ) - added by lancewillett 13 years ago.
Add new tag to list
26157.2.diff​ (1.7 KB ) - added by lancewillett 13 years ago.
s/accessible/accessibility/ and add Twenty Fourteen tag

Download all attachments as: .zip

Change History (11)

#1 @SergeyBiryukov
13 years ago

  • Component General → Themes

#2 @samuelsidler
13 years ago

  • Cc samuelsidler added; sams removed
  • Milestone Awaiting Review → 3.8

If we're considering #21442 for 3.8, we should consider this one as well.

#3 @samuelsidler
13 years ago

  • Priority normal → low

@lancewillett
13 years ago

Add new tag to list

#4 @lancewillett
13 years ago

  • Keywords has-patch added

@lancewillett
13 years ago

s/accessible/accessibility/ and add Twenty Fourteen tag

#5 @matt
13 years ago

  • Owner set to matt
  • Resolution → fixed
  • Status new → closed

In 26658:

Create a new tag for themes that have passed the theme check guidelines for accessibility. Fixes #26157

Props lancewillett.

#6 @lancewillett
13 years ago

  • Keywords has-patch removed
  • Version → trunk

#7 @nacin
13 years ago

  • Summary Create new tag: accessible-ready → Create new tag: accessibility-ready

#8 @Otto42
13 years ago

This isn't fixed yet, because changes will need to occur on WordPress.org to support it.

Nacin: Same thing for the API, don't send it to old installs?

Also, theme directory will need to know about it, tag-filter will need to be updated, and theme-check will need to get it added.

#9 @Otto42
13 years ago

  • API Changes made
  • Theme/tag-filter updated
  • Theme Check trunk updated
Note: See TracTickets for help on using tickets.