The themes team conducts a meeting on the second and fourth Tuesday of the month.
Along with the fixed agendas, we have an open floor at the end where you can ask or share anything related to themes.
We encourage all members and anyone interested to attend.
Channel: #themereview | Time: Tuesday, November 10th 2020, 15:00 UTC
- Weekly Updates
- Updating accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) requirements for links
- Removing the requirement of specific CSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. classes
- Organizing documentation and tutorials for Full Site Editing themes
- Open floor
Current statistics can be found on: https://themes.trac.wordpress.org/
Themes Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket graph: https://themes.trac.wordpress.org/ticketgraph
Updating accessibility requirements for links
When the team started applying accessibility requirements on all themes in 2019, the intention was to introduce new requirements every few months. This was not followed up for a couple of reasons, but it has always been the intention to continue to improve the accessibility of the themes.
We would like to propose that the following requirement is applied to all themes in the directory:
Links within content must be underlined.
When links appear within a larger body of block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-level content, they must be clearly distinguishable from surrounding content.
Links in navigation-like contexts (e.g. menus, lists of upcoming posts in widgets, grouped post meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data) do not need to be specifically distinguished from surrounding content.
The underline is the only accepted method of indicating links within content. Bold, italicized, or color-differentiated text is ambiguous and will not pass.
Removing the requirement of specific CSS classes
This proposal is about removing the requirement for the following CSS classes:
It is up to the theme author if they want to support legacy content, how they choose to implement post- and block alignments, and how they choose to implement sticky posts within the current requirements.
Organizing documentation and Tutorials for Full Site Editing themes
During last weeks block based theme meeting, there was a discussion about writing tutorials for full site editing themes.
Writing tutorials that will be kept up to date is going to be challenging, but that aside, this documentation needs to be placed somewhere.
Do we want to create a separate handbook for Full Site Editing themes? Or is it better to include it in the existing Theme Developer Handbook, or in the Block editors tutorial section?
Please comment in the comment box below if you have anything to bring up during the open floor.