}}} tags to display raw code, the message arrive to inbox with the {{{<}}} and {{{<}}} characters converted into HTML entities.
[[Image(https://i.imgur.com/yAs3GrB.png)]]
''Example of a code snippet in a forum reply...''
The problem I see here is that if the user uses this code from the email instead the one in the forum reply, it will not work. As you can see in the below replies, she entered the forum through a video I recorded and realized that the code was different from what she received in the email notification.
[[Image(https://i.imgur.com/5pO6Ev4.png)]]
''...code delivered to the user inbox''
My proposal is to add an exception to the parsing performed to the messages before sending the mail so that it skip the sanitization in the code enclosed in {{{}}} tags including, of course, the {{{}}} tags in order to display as a code snippet in the mail message.",YordanSoares
5708,Allow only moderators to remove modlook tag,Support Forums,high,defect (bug),,new,2021-04-20T06:00:58Z,2022-04-08T14:35:45Z,"Currently, if someone reports a topic, the tag ''modlook'' is added. As far as I understand, the author or anyone replying on that topic can remove ''modlook'' tag from the list, before a moderator has the chance to review that report, so unless the topic is reported again, it stays in the wild as it is.
The ability to remove ''moodlook'' tag should only be available to moderators.
Maybe an extra check {{{user_can( $user_id, 'moderate' )}}} when ''modlook'' is removed from the list of tags would do the trick.",vladytimy
5859,Improve video thumbnail images,WordPress.tv,high,defect (bug),,new,2021-08-11T10:46:57Z,2021-08-11T10:48:57Z,"Video thumbnail images (those in 'grids layouts') on pages like https://wordpress.tv/, https://wordpress.tv/category/year/2017/ and https://wordpress.tv/tag/translation/page/2/ (excluding the video/thumbnail in the hero 'player' element when present) should be loaded more efficiently.
Specifically:
- The thumbnail should be generated/requested at an appropriate size (160x100)*
- A `loading=""lazy""` property should be added.
- Explicit `height` and `width` properties should be added.
- If available, an `srcset` property should reference a `x2` size option (at 320x200).
*E.g., https://videos.files.wordpress.com/bjn9Fo1g/video-33873a5e9c_mp4.scrubthumb.jpg, which is currently on the homepage, is loaded at 1920x1080, but squashed into a 160x100 space",jonoaldersonwp
6326,Need to synchronize authors' lists on Rosetta sites,International Sites (Rosetta),high,defect (bug),,new,2022-05-25T15:46:08Z,2022-10-21T05:58:43Z,"Despite having the role Locale Manager, I wasn't able to publish the localized Release post for WordPress 6.0 at sv.wordpress.org.
The dropdown for choice of author for the post was just 3-4 usernames long, so I had to publish from the name of ""wordpress.org"" instead.
As I was trying to figure out what had happened, I decided to remove myself as user on the local site, and then add myself back again. (I was able to do this thanks to my special role as network admin.) And this worked. Now my name got added to the list of possible author names.
So it seems that we in the Rosetta may have sites where a lot of ""contributors"", ""locale managers"", and ""editors"" currently can't be selected as authors.
I don't know how this happened. I don't know if this may be a problem in core or in other parts of wp-org, but at least this needs to be checked and fixed on the Rosetta sites.",tobifjellner
6443,/page/2/ being adding to reply links incorrectly,Support Forums,high,defect (bug),,new,2022-08-14T13:42:24Z,2023-02-01T16:26:10Z,"Replies on the first page of a topic and getting ""/page/2/"" added with the links, breaking them. For example, see https://wordpress.org/support/topic/smileys-not-working-on-mobile/?view=all
This reply is still on the first page:
{{{
https://wordpress.org/support/topic/smileys-not-working-on-mobile/page/2/?view=all#post-15900871
}}}
but doesn't work unless /page/2/ is removed.
It may be significant that this is the 10th reply in the chain. Subsequent replies also have /page/2/",sterndata
6515,Forums: Add ability to sort unresolved threads,Support Forums,high,defect (bug),,new,2022-10-04T13:26:34Z,2023-05-04T09:03:48Z,"At this moment, someone doing support for a plugin on the repository can either choose to show threads ordered by activity (e.g. [https://wordpress.org/support/plugin/wordpress-seo/active/]) or filter out the unresolved topics (e.g. [https://wordpress.org/support/plugin/wordpress-seo/unresolved/]).
However, there is no way to sort all unresolved topics by their latest activity.
For plugins with an active support forum, this hinders their ability to respond to the oldest pending requests first, as it means continuously sifting through the list manually to find the unresolved thread waiting for the longest for a reply.
Therefore, I'd like to see more sorting options for the forum threads, with the main one being the 'last post', but ideally also the 'voice count' and 'reply count'. ",TacoVerdo
6591,Add Note or Feedback comment Add/Editor not working,Developer Hub,high,defect (bug),,new,2022-11-23T13:55:50Z,2023-02-28T09:48:38Z,"Go to Any function of wordpress
For Ex : https://developer.wordpress.org/reference/functions/wp_get_attachment_url/
Try to Add comment which having some php code
for test i'm trying to add
Ex :
ID);
foreach($media as $post_images) { ?>
ID )); ?>"" />
After adding above code switch to preview and it display completely wrong code
i have tried with inbuilt [php] & [code] none works
Check the screenshot attached
",mayur8991
6691,Links on wordpress.org/gutenberg don't open,General,high,defect (bug),,new,2023-01-20T09:07:54Z,2023-07-11T02:35:54Z,"If you go to https://wordpress.org/gutenberg/ and click on a link such as ""Try Gutenberg Today in WordPress"", it tries to load the linked page within the editor and then reloads the page. It should open the page outside of the editor. This seems to happen with all other links on the page.",ben.greeley
7040,Create and add a plugin for embedding playground iframes in docs,Handbooks,high,defect (bug),,new,2023-06-08T08:13:03Z,2023-06-08T09:48:38Z,"The docs team would like to be able to embed playground instances into content. We should create a simple plugin (""Playground Embedder"") to facilitate this.
This should be relatively simple, but has a few moving parts:
- Someone needs to write a/the plugin
- The playground should be loaded via a shortcode (as content is managed in GitHub / sync processes, so a block-based approach isn't suitable)
- Playground content is delivered as an iframe, but we also need to consider;
- The shortcode should support providing parameters (details at [https://wordpress.github.io/wordpress-playground/docs/query-api/]) which passes additional parameters to the iframe URL.
- The iframe should only be loaded on click/interaction; so we need an 'inactive' state (which should presumably come with some form of skeleton view + sizing)
- This will require some simple JS (which should only be enqueued on pages where the shortcode is present) and CSS (for styling the inactive state, and for managing the h/w/etc of the active state)
The base playground URL is `https://playground.wordpress.net/`.
",jonoaldersonwp
7079,WordPress.tv mobile version grid design responsive issue,WordPress.tv,high,defect (bug),,new,2023-06-20T05:33:09Z,2023-06-22T04:57:06Z,"In mobile version grid section width is not proper. It looks like too little grid. It should be full width.
A screenshot is attached below.",nayanchamp7
7141,Huge Emojis in Support Forum,Support Forums,high,defect (bug),dd32,accepted,2023-07-14T11:02:16Z,2023-07-27T01:50:10Z,"For the past few days we've been seeing huge emojis in the support forum (basically they have no width set and the full image size is showing. [[Image(https://prnt.sc/cWAjuDkhAh-1)]]
I'm not sure where this CSS should be added but something like this fixes the issue:
{{{
#bbpress-forums div.bbp-reply-content img.emoji {
width: 1em;
vertical-align: middle;
}
}}}
",talextech
7205,Design of the search bar in Support forum is broken,Support Forums,high,defect (bug),,new,2023-08-12T12:12:47Z,2023-08-15T13:47:41Z,"In the support forum of any plugin, the search bar design is breaking up when we are adding more content than the visible input area. For example, you can try adding the below text in the search bar:
""how to protect my site from spam, can you please tell me?""
[[Image(https://img001.prntscr.com/file/img001/iiG2hB7_TreWpwOfXXP0EA.png)]]",rajinsharwar
7236,Requirements page update (MySQL and PHP),WordPress.org Site,high,defect (bug),,new,2023-08-25T00:33:21Z,2024-01-24T09:26:48Z,"There are some changes needed to update in the WP.org Requirements page:
**MySQL**
MySQL 5.7 has their EOL on October 21, 2023. Having that in mind, we should not recommend using this version as is not having more releases, and the focus is only in MySQL 8.0.
Support for MacOS ended in January 2022, for Fedora ended in April 2020, for FreeBSD in October 2019.
So, we should change this string:
''MySQL version 5.7 or greater OR MariaDB version 10.4 or greater.''
to this one:
''MySQL version 8.0 or greater OR MariaDB version 10.4 or greater.''
**PHP**
Also, the PHP notice should be change, because WordPress 6.3 doesn't apply fully.
We should change:
''Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 5.6.20+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security vulnerabilities.''
For this one:
''Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 7.0+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security vulnerabilities.''
",JavierCasares
7275,TracQuery page is fully breaking at every responsive breakpoints.,Trac,high,defect (bug),,new,2023-09-14T08:55:01Z,2023-09-14T09:17:36Z,"The link to page :- https://meta.trac.wordpress.org/wiki/TracQuery
this is breaking in all the responsive views in mobile,tablet and laptop views as its table class named listing tickets the screenshot image does not have width mentioned in it below are the several screenshot about the page break.",dhruvang21
7277,Theme Search is broken,Theme Directory,high,defect (bug),,new,2023-09-14T11:56:25Z,2023-10-18T19:49:58Z,"Context: I initially found this bug when searching for my theme ""School"" (https://wordpress.org/themes/school/)
Visiting this page via a link (or page refresh) https://wordpress.org/themes/search/school/
Shows only 9 themes and no load more button and it does not show my theme.
[[Image(https://wpgeodirectory.com/wp-content/uploads/2023/09/school-search-page-refresh.png)]]
However, if you visit another search page first such as https://wordpress.org/themes/search/go/ and THEN search ""school"" from there, it brings you to the exact same URL but
1. The themes are different (my theme shows)
2. It shows 12 themes instead of the original 9
3. It shows the load more button.
[[Image(https://wpgeodirectory.com/wp-content/uploads/2023/09/school-search-from-another-search-result.png)]]
However, if you refresh the page, it returns to the broken version of the search.
This is repeatable with other words such as ""news"".
Sometimes during my repeated searching it would work intermittently, which makes me think it could be related to a caching issue as well as something else.
All testing was done logged out.
",stiofansisland
7354,Submit Photo Issue,Photo Directory,high,defect (bug),,new,2023-11-27T13:56:09Z,2024-02-21T02:04:48Z,"I am a new contributor, i am trying to contribute new photos (https://wordpress.org/photos/submit/). But every I get this message ""Validating photo dimensions…
"". How can I upload photos? Is it a server issue?
Here is screenshot. https://www.dropbox.com/scl/fi/opckdf25xf7p6a0q49rgh/Validating-photo-dimensions.png?rlkey=p8kkl8zeh0i45pu21n3ewwf4n&dl=0",nababurbd
7419,Subtitles upload issue in wordpress.tv videos,WordPress.tv,high,defect (bug),,new,2024-01-23T09:42:49Z,2024-01-25T08:18:25Z,"When I upload subtitles.ttml file for particular video of https://wordpress.tv/ this page, after filling this details (username, email, language and file upload) when click on submit it gives error like (This site can’t be reached
The webpage at https://wptv.wordpress.com/wp-admin/admin-post.php might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR)
Please check this video - https://nimb.ws/LAPKNr
Screen shots- https://prnt.sc/If7xpRIB3W39",narolainfotech
7486,found some spelling mistakes,Handbooks,high,defect (bug),,new,2024-02-22T12:36:51Z,2024-02-22T12:36:51Z,"I found some spelling mistakes in the WordPress Plugin documentation
No.1
https://developer.wordpress.org/plugins/shortcodes/shortcodes-with-parameters/#parsing-attributes:~:text=shortcode.%20In%20the-,exampe,-above%2C%20it%20will
It will be - ""example"" not exampe.
No.2
https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#basic-strings:~:text=To%20echo%20a,instead%20of%20writing%3A
and it will be ""translation"" not tranlsation.",azimjamshed
2504,Forums: Replies from archived topics are still displayed in user profiles,Support Forums,high,defect (bug),,new,2017-02-14T21:50:32Z,2021-02-24T21:21:38Z,"1. Archive a topic (but not individual replies).
2. Replies from that topic are still displayed in participants' profiles.",SergeyBiryukov
273,Keyboard navigation friendliness for Trac,Trac,normal,defect (bug),,reopened,2014-01-10T00:40:29Z,2018-01-24T22:45:20Z,"In attempting to navigate around Trac one-handed, I noticed some funky things like randomly defined tabindices on WikiFormatting links that prevent natural tab ordering. There are also an unwieldy number of links overall that make it tiresome to navigate in general.",helen
681,Community profile badges disappear for WordCamp organisers of two different WordCamps,Profiles,normal,defect (bug),,new,2014-10-27T01:05:40Z,2021-06-07T19:37:39Z,"When a WordPress.org username gets added to the Organisers of a second WordCamp, the community profile badge disappears.
Here's the use case:
- I've been added as an organiser for WordCamp Sofia 2013 - http://2013.sofia.wordcamp.org/
- I am also an organiser of WordCamp Europe 2014 - http://2014.europe.wordcamp.org/
I noticed that my community badge had disappeared after my profile was added to the organisers of WordCamp Europe 2014. Adding a second entry for my profile as an organiser made the badge appear again. But then I was listed as an organiser for the same WordCamp twice on the Organisers page. Deleting the second profile got rid of the badge again.
Clearing the username, updating and then adding it again seemed to do the trick - the badge appeared again.
Tested it with JJJ at #wcsf14 contributor day who suggested it had something to do with the fact that WordCamp organisers are not supposed to be a part of more than one organising team. He advised me to file it here.
It's a cool bug.",petya
1424,Automate meta contributor badge assignment when receiving props,Profiles,normal,defect (bug),coffee2code,accepted,2015-12-01T19:41:01Z,2017-09-01T16:52:48Z,"Profile badges don't seem to automatically appear for all areas. My core and plugins badges appeared on my profile on their own (as far as I can tell), but my Speaker badge had to be added manually with some difficulty, and my Meta badge hasn't appeared at all after getting first props a few weeks ago (see [2016]).",morganestes
3743,On Make WP blog the 'Follow' action removes syntax highlighting on code snippets,Make (Get Involved) / P2,normal,defect (bug),,new,2018-08-03T16:11:13Z,2020-03-24T05:48:43Z,"Hello,
Just noticed this when I went to follow a post on make.wp.org, but if the post contains a code snippet with syntax highlighting that vanished once you click the follow button, either to follow or unfollow doesn't matter.
Example page - https://make.wordpress.org/core/2018/08/02/try-gutenberg-callout-in-wordpress-4-9-8/
Cheers",garrett-eclipse
3781,The Views for 'My @Mentions' and 'My Posts' give 'Page Not Found' message which is misleading,Make (Get Involved) / P2,normal,defect (bug),,new,2018-08-29T20:23:00Z,2018-09-12T17:22:58Z,"Hello,
Trying the views for 'My @Mentions' and 'My Posts' give you a 'Page Not Found' error;
https://i.imgur.com/PIWD0Vu.png
I'm not sure if this is simply because I have no @Mentions or Posts, but if that's the case maybe a more informative message would make sense than 'Page Not Found' such as 'No Posts' or 'No @Mentions' so it's not just seen as a 404 error.
Links for mine;
My @Mentions - https://make.wordpress.org/core/?mentions=garrett-eclipse
My Posts - https://make.wordpress.org/core/author/garrett-eclipse
Thanks
",garrett-eclipse
3858,Fix/add select2 support to HelpHub Contributors module,HelpHub (wordpress.org/documentation),normal,defect (bug),netweb,reviewing,2018-10-03T21:24:18Z,2018-10-30T08:28:51Z,"Currently HelpHub's Contributor module is enqueueing a non-existent select2 js file on all admin screens causing console errors :)
It shouldn't be enqueued on all admin screens either if avoidable.
ref: https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/support-helphub/inc/helphub-contributors/admin/class-helphub-contributors-admin.php#L67",dd32
3880,"Allow redefining or augmenting information in the ""INTERESTED IN DEVELOPMENT?"" section",Plugin Directory,normal,defect (bug),,new,2018-10-22T19:22:33Z,2018-11-29T00:10:25Z,"Currently:
Browse the code, check out the SVN repository, or subscribe to the development log by email or RSS.
We should really be able to override this text and these links since:
- Development is almost always on Github
- Github's code-browsing features are more intuitive and familiar to most developers
- Github provides it's own methods for subscribing to development progress
- Github provides it's own contribution documentation recommendation through the CONTRIBUTING.md -- we should be able to link to that here.
Unfortunately, I think most people are trained to ignore that section, and instead look in the readme sections for contribution information, but it seems obvious we should make this section more realistic, intuitive, and configurable by plugin authors. And if not configurable, at least providing the ability to add more text below it by way of another readme section.",jtsternberg
3922,"""How to create a WordPress business website"" landing page on WordPress.org",General,normal,defect (bug),,new,2018-11-14T16:28:33Z,2023-04-11T21:41:39Z,"Hi,
We at the WordPress marketing team have created a new extensive guide on [https://make.wordpress.org/marketing/2018/11/07/how-to-create-a-business-website-with-wordpress/ ""How to create a business website with WordPress.""].
Can we create a landing page on WordPress.org on the same topic?
The idea is that it would attract a lot of people who are not currently WordPress users but are thinking of creating a business website.
Thanks.
",joelobo
3930,"In the main menu, the submenu nav-submenu doesn't visually open by keyboard in mobile view",General,normal,defect (bug),,new,2018-11-16T12:40:51Z,2023-02-17T07:48:03Z,"The items in the submenu of Support in the header menu are not visibly open when tabbing through them using a keyboard. They are visible using the menu in desktop view.
{{{
Support
}}}
",rianrietveld
3995,W3C CSS validator patchs for all sites in meta,General,normal,defect (bug),,new,2018-12-11T10:54:46Z,2020-03-13T05:09:25Z,"I search around all folders in meta sites, and start to check all CSS files(specially in themes folders) in W3C CSS validator, I fix important errors and create a patch for all file.
Please let me know if this validations is good and I can continue this task to have better code standards :) ",man4toman
4007,Support Forums: Improve the look and usability of Forums page,Support Forums,normal,defect (bug),,new,2018-12-17T21:57:52Z,2024-03-14T03:45:45Z,"The Forums page https://wordpress.org/support/forums/ has a look that is very similar to the Support home page, and is confusing because it is. It would be better as a compact list than as big squares of white space. It should be giving the overview of the forums, yet it can't be seen without scrolling a lot.
Also, the 3 squares at the top (with icons) are not the focus of the page, but all you can see ""above the fold"". I suggest they be moved to the bottom. Their icons could be made smaller also.
I have attached a screenshot of a quick rearrangement.",joyously
4096,Redesign /mobile/,General,normal,defect (bug),sjardo,assigned,2019-01-23T20:33:06Z,2021-08-05T18:54:57Z,"Have been discussing the /mobile/ pages with @elibud. They need to be more modern and much better at informing people about the capabilities of our apps. Let's get that process going by creating a new design and then putting that live.
We can remove the link to WordPress.com and replace it with a QR code and link, potentially using http://onelink.to/
",joostdevalk
4110,Consider to audit the headings hierarchy across the .org network,General,normal,defect (bug),,new,2019-01-28T22:17:23Z,2020-04-15T05:26:19Z,"Headings are important not only for semantics and SEO: they are actually used by screen reader users as the [https://webaim.org/projects/screenreadersurvey7/#finding predominant mechanism to find information on a page].
For better accessibility, SEO, and semantics there are some best known practices, also recommended by the core accessibility team:
- a main `h1` heading should be used to communicate the main page topic
- there should be only one `h1` in a page
- the main topic of a page is rarely the site title, this is maybe true only on the home page (and it's still matter of debate)
- in all the other pages, the main `h1` is meant to be used for that specific page topic
- headings needs to have a correct hierarchy: no levels should be skipped
There are different tools to check the headings structure of a page. For the purpose of this ticket, I've used the HeadingsMap Chrome extension. I've also collected a series of screenshots to illustrate the headings hierarchy in the main pages of the .org network as of today, January 28, 2018: https://cloudup.com/cCODexEIFbq
To recap:
- Home: two h1 and incorrect hierarchy
- Showcase: incorrect hierarchy
- Themes: two h1 and incorrect hierarchy
- Plugins: two h1
- Mobile: hierarchy OK but the main page topic is not a h1
- Support: two h1 and incorrect hierarchy
- Get involved (Make): two h1 and incorrect hierarchy
- About: two h1
- Blog: hierarchy OK but the main page topic is not a h1
- Hosting: hierarchy OK but the main page topic is not a h1
I realize the .org network is made of different templates coming from different sources and I guess it's a complicated setup. However, it would be great to make sure the headings hierarchy is correct on all the network pages.",afercia
4111,Consider to audit the focus style across the .org network,General,normal,defect (bug),,new,2019-01-28T22:37:36Z,2019-01-28T22:37:36Z,"Keyboard users, or users who make a mixed use of a pointing device and keyboard, need to actually ''see'' where focus is to be able to navigate a web page using their keyboard.
The focus style is a necessary indication for these users. Great care has been taken in WordPress core and the bundled themes to make the focus style as good as possible, and there's still work to do to improve it. It would be great to see also the .org network sites taking care of the focus style.
For reference, this is also part of the WCAG recommendation:
Success Criterion 2.4.7 Focus Visible
https://www.w3.org/TR/WCAG21/#focus-visible
While a complete analysis of all the links and controls across all the .org network would be impossible for me, I've taken the time to volunteer and analyze the focus style only on the main navigation menu in the main .org sections.
To recap:
- Home: has focus style (browser native style)
- Showcase: no focus style `outline: none;`
- Themes: has focus style `outline: thin dotted;`
- Plugins: has focus style `outline: thin dotted;`
- Mobile: has focus style (browser native style)
- Support: has focus style `outline: thin dotted;`
- Get involved (Make): has focus style (browser native style)
- About: has focus style `outline: thin dotted;`
- Blog: has focus style (browser native style)
- Hosting: has focus style (browser native style)
Suggested:
- never reset the native outline style, unless that's meant to provide a better, improved focus style
- use a consistent style across all the pages: worth reminding the browsers native focus style greatly varies across operating systems and browsers
- buttons, form elements, and custom interactive elements need a focus style as well
- use a style that is compatible with Windows High Contrast mode, or provide one specifically for Windows High Contrast mode
Note: in Windows High Contrast mode, basically only `outline` and `border` work. In core, https://core.trac.wordpress.org/ticket/41286 introduced a specific style that uses a transparent outline, as already done for the new block editor Gutenberg.",afercia
4112,Proposal to change the headings hierarchy in the Home page,General,normal,defect (bug),,new,2019-01-29T11:01:54Z,2020-05-27T02:01:07Z,"Splitting this out from #4110.
The headings hierarchy in the home page has room for improvements for better SEO and accessibility:
[[Image(http://cldup.com/3VdWJjlE_Q.jpeg)]]
Currently, there are two `h1` and one level is skipped, thus producing an incorrect hierarchy.
Whether the logo should be or not be the main `h1` heading can be matter of debate. However, in this case I'd say the logo should not be the main heading across the whole .org network.
In this page, the main topic is clearly ""Meet WordPress"", which should be the only `h1` in the page, followed by the other headings in a correct hierarchy: all the headings after ""Get started with WordPress"" should be bumped up by one level.",afercia
4117,Proposal to change the headings hierarchy in the Support section,Support Forums,normal,defect (bug),,new,2019-01-29T14:19:17Z,2023-03-22T16:38:04Z,"Splitting this out from #4110.
The headings hierarchy in the Support section has room for improvements for better SEO and accessibility:
[[Image(http://cldup.com/52hVQINjaS.jpeg)]]
As mentioned in #4112 the logo shouldn't be a `h1`. The main topic in this page is ""WordPress Support"" and that should be the only `h1` in the page.
The headings hierarchy is incorrect: all the other heading should be bumped up from `h3` to `h2`.
**Categories main pages:**
they look OK with the exception the logo shouldn't be a `h1` see for example https://wordpress.org/support/category/basic-administration/
**Article pages:**
In the article pages, for example https://wordpress.org/support/article/plugins/
[[Image(http://cldup.com/JifGmi0rEQ.png)]]
- the logo shouldn't be a `h1`
- in the left sidebar, the ""Categories"" `h2` comes before the main topic `h1`, which is unexpected
- the hierarchy of the headings in the content is correct but there's a problem: the ""hash link"" to get the in-page link repeats the visible text. This way, all the headings have duplicated content.
In the example page, any software including search engines crawlers and assistive technologies perceive the following headings content:
- Introduction Introduction
- Plugin Repositories Plugin Repositories
- Default Plugins Default Plugins
- Plugin Development Plugin Development
Suggested:
- the headings shouldn't contain extraneous content: the ""hash link"" should be moved out from the headings
- ideally, it should have a meaningful link text, e.g.: ""link to the section Introduction"", ""link to the section Plugin Repositories"", etc.
Please consider the Support section has a huge amount of sub-section, pages, and content. Going through all of them is out of the scope of this ticket. However, these are general guidelines that should be applied everywhere.
",afercia
4119,Proposal to change the headings hierarchy in the Getting Involved (Make) section,Make (Get Involved) / P2,normal,defect (bug),,new,2019-01-29T15:13:53Z,2020-04-16T05:42:58Z,"Splitting this out from #4110.
The headings hierarchy in the Getting Involved (Make) section has room for improvements for better SEO and accessibility:
[[Image(http://cldup.com/LZpVRsMYSJ.jpeg)]]
- as mentioned in #4112 the logo shouldn't be a `h1`
- the main topic in this page is ""Make WordPress"" and that should be the only `h1` in the page
**The ""teaser"" or ""kicker"" text:**
it's made of two headings: `h1` + `h5`: looks like these headings are used for visual purposes but their semantic is inappropriate and the hierarchy is incorrect. These are not headings, they're not ""titles that identify a section"". Instead, they're introductory text and they should be two styled paragraphs under the main `h1` heading ""Make WordPress""
**The ""There are many different ways for you to get involved with WordPress"" `h2`:**
Either it shouldn't be a heading at all and should be changed to a styled paragraph or if it's important to keep it as a `h2`, then all the headings under it should be `h2`. For the sake of simplicity I'd suggest the first option.
**Meetings sub-section:**
""Upcoming WordPress Meetings"" should be the only heading in the page and should be a `h1`
**Team Updates section (similar to all the Make blogs):**
[[Image(http://cldup.com/N0EP37tHOq.jpg)]]
This one is a bit complicated:
- there should be just one `h1` in the page (""Team Updates"")
- each post title shouldn't be a `h1`: for example, the bundled themes take care of this and in the archive pages they render the post titles as `h2`
- if the post titles get changed to `h2`, then the headings in their content would have an incorrect hierarchy: this is even more complicated by the fact some posts use `h2` in their content and some posts use `h3` (see the screenshot above)
- in the single post page, the post title need to stay as `h1` and the headings in the content need to have a correct hierarchy
- worth nothing this is a problem with all the bundled themes too: an option could be displaying only the post excerpts and not the entire posts
- some teams need to be informed they have to use `h2` headings in their content anyways (I seem to recall with the old design `h3` headings were recommended: this is no longer the case with the new design)
Additionally, at the bottom of the page:
- ""Post navigation"", which is visually hidden with `screen-reader-text` shouldn't be a `h1`, it needs to be changed to `h2`
- the three headings in the sidebar: ""About This Blog"", ""Email Updates"", ""Recent Activity"", need to be changed from `h3` to `h2`. The current hierarchy is clearly incorrect:
{{{
1 Post navigation
3 About This Blog
3 Email Updates
3 Recent Activity
}}}
These recommendation apply to all the Make blogs, with a few additional ones. For example, in [https://make.wordpress.org/core/ the Make/Core blog]:
[[Image(http://cldup.com/MENZMYoQ3S.jpg)]]
""Welcome"" and ""Communication"" need to be changed from `h3` to `h2`. If I'm not wrong, each team can edit this part of the page so all the teams should be informed and invited to review and edit their pages to improve the headings hierarchy.
Please consider going through all the pages in the Make section is out of the scope of this ticket. However, these are general guidelines that should be applied everywhere.",afercia
4121,Proposal to change the headings hierarchy in the Blog section,WordPress.org Site,normal,defect (bug),,new,2019-01-29T16:16:28Z,2021-06-02T21:28:03Z,"Splitting this out from #4110.
The headings hierarchy in the Blog section has room for improvements for better SEO and accessibility:
[[Image(http://cldup.com/FQdgefzO-Z.jpeg)]]
As mentioned in #4112 the logo shouldn't be a `h1`. This page should have a main `h1` that identifies the main topic of the page. Suggested: ""Blog archive"".
More importantly, as for the case of the Make blogs, this page suffers from a problem which is present also in the bundled themes. In the archive pages, the post titles should be `h2`, while in the single post page, the post title should be `h1`. See also #4119.
Basically:
- each post title shouldn't be a `h2`: given the current headings structure (see screenshot above), it's impossible to understand which `h2` are post titles and which ones come from the post content
- search engines crawlers and screen reader users can't understand which headings represent the post titles
- it's impossible to change the headings from the posts content ""on the fly"" and bump them up one level automatically only in the archive page
- in the single post page, the post title needs to stay as `h1` and the headings in the content need to have a correct hierarchy starting from `h2`
- in the archive page, one option could be making the post titles `h2` and displaying only the post excerpts and not the entire posts
**Social sharing and sidebar headings:**
At the end of the headings list the headings used for the social sharing and the ones used in the sidebar have an incorrect hierarchy, currently:
{{{
2 Further Reading:
3 Share this:
3 Like this:
4 See Also:
4 Categories
4 Subscribe to WordPress News
}}}
Where ""Further Reading:"" is the last heading in the last post in the current archive. This hierarchy is clearly incorrect because neither the social headings or the sidebar ones are logically sub-headings of ""Further Reading:"".
Suggested change (not perfect, but better):
{{{
2 Social sharing
3 Share this: (output by sharedaddy so I guess it can't be changed)
3 Like this: (output by sharedaddy so I guess it can't be changed)
2 See Also:
2 Categories
2 Subscribe to WordPress News
}}}
**Single post page:**
For example: https://wordpress.org/news/2019/01/wordpress-5-1-beta-2/
- the logo shouldn't be a `h1`
- the post title should be the only `h1` in the page
- post authors should use a correct headings hierarchy in their content starting with `h1` headings, which is made easier with Gutenberg
- the social sharing headings, the ""Post navigation"" heading (visually hidden with `screen-reader-text`), and the sidebar headings have an incorrect hierarchy, much like in the archive page. Currently:
{{{
2 How to Help
3 Share this: (output by sharedaddy so I guess it can't be changed)
3 Like this: (output by sharedaddy so I guess it can't be changed)
2 Post navigation
4 See Also:
4 Categories
4 Subscribe to WordPress News
}}}
Where ""How to Help"" is the last heading in the example post content. Suggested change:
{{{
2 Social sharing
3 Share this:
3 Like this:
2 Post navigation
2 See Also:
2 Categories
2 Subscribe to WordPress News
}}}
Please consider there are other pages in the Blog section (the categories ones for example). A complete analysis is out of the scope of this ticket. However, these are general guidelines that should be applied everywhere.",afercia
4123,Proposal to improve the main navigation menu accessibility,General,normal,defect (bug),Otto42,accepted,2019-01-29T18:14:14Z,2023-06-13T06:25:20Z,"Several [https://www.w3.org/TR/wai-aria-practices-1.1/#html5-sectioning-elements HTML5 sectioning elements] automatically create [https://www.w3.org/TR/wai-aria-1.1/#landmark_roles ARIA landmark regions].
Landmark regions are exposed to assistive technologies and allow users to quickly find information in a page. Ideally, all content in a web page should be wrapped within landmark regions. For now, I'd like to propose to focus on the navigation menu.
In this specific case it's important to know that `