Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #55172


Ignore:
Timestamp:
02/15/2022 11:08:19 PM (2 years ago)
Author:
sabernhardt
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #55172

    • Property Focuses accessibility added
    • Property Component changed from Themes to Bundled Theme
    • Property Summary changed from Add "Accessibility Ready" tag to Twenty-Twenty-Two theme in repository to Twenty Twenty-Two: Add "Accessibility Ready" tag to theme in repository
  • Ticket #55172 – Description

    initial v1  
    11Context:
    22
    3 [On this make blog post](https://make.wordpress.org/core/2022/01/26/preliminary-roadmap-for-6-0/#comment-42544), @piyopiyofox posted the following question:  "It’s been flagged that none of the FSE themes in the theme directory are `Accessibility Ready`. Will there be any improvements to TT2 to make it `Accessibility Ready`?"
     3[https://make.wordpress.org/core/2022/01/26/preliminary-roadmap-for-6-0/#comment-42544 On this make blog post], @piyopiyofox posted the following question:
     4> "It’s been flagged that none of the FSE themes in the theme directory are `Accessibility Ready`. Will there be any improvements to TT2 to make it `Accessibility Ready`?"
    45
    56@Kjellr answered:
    6    
    7 I’m pretty sure Twenty Twenty-Two is just missing the tag actually. The theme was reviewed throughout its development, and [found to pass WCAG AA](https://github.com/WordPress/twentytwentytwo/issues/82)
    87
    9 The theme review guidelines go beyond WCAG in some areas, and there was one conflict regarding the use of multiple H1s.[ But there was consensus that the rule would be updated in the guidelines side](https://github.com/WordPress/twentytwentytwo/issues/233#issuecomment-985756453)
    10 
     8> I’m pretty sure Twenty Twenty-Two is just missing the tag actually. The theme was reviewed throughout its development, and [https://github.com/WordPress/twentytwentytwo/issues/82 found to pass WCAG AA].
     9>
     10> The theme review guidelines go beyond WCAG in some areas, and there was one conflict regarding the use of multiple H1s. But there was consensus that the rule would be [https://github.com/WordPress/twentytwentytwo/issues/233#issuecomment-985756453 updated in the guidelines side]