Wikipedia:Featured list candidates/List of tornadoes in the tornado outbreak of May 4–6, 2007/archive1

The following is an archived discussion of a featured list nomination. Please do not modify it. Subsequent comments should be made on the article's talk page or in Wikipedia talk:Featured list candidates. No further edits should be made to this page.

The list was promoted by PresN via FACBot (talk) 00:26, 14 July 2023 (UTC) [1].[reply]

List of tornadoes in the tornado outbreak of May 4–6, 2007

Featured list candidates/List of tornadoes in the tornado outbreak of May 4–6, 2007/archive1

Nominator(s): ~ Cyclonebiskit (chat) 17:51, 2 April 2023 (UTC)[reply]

In early May 2007, a violent tornado outbreak struck the Great Plains of the United States. The first day of this outbreak has become notorious with an EF5 tornado essentially wiping the community of Greensburg, Kansas, off the map. This list covers all the tornadoes that touched down throughout this three-day outbreak. It follows the structure set by the two other tornado FLs and should be up to par with MOS requirements for such a large table. ~ Cyclonebiskit (chat) 17:51, 2 April 2023 (UTC)[reply]

Comments

Image caption is a complete sentence so needs a full stop
"In early-May 2007" - no reason for hyphen there
Daily statistics table looks a little odd with the totals centre-aligned but the columns above right-aligned
"A brief tornado lofted" - should that be "lifted?
- Lofted and lifted work as synonyms but the latter is often used when describing tornado dissipation. In this case it's about the irrigation pivot being thrown. ~ Cyclonebiskit (chat) 20:50, 3 April 2023 (UTC)[reply]
"Storm chasers observed observed" - repeated word
"This first one caused some damage to trees" => "The first one caused some damage to trees"
"A man was killed in this home" => "A man was killed in his home"
"where the recreation center and marina heavily impacted" => "where the recreation center and marina were heavily impacted"
Lots of refs have single square brackets around the title - are those meant to be there?
- Yes, those are included because the refs don't have actual titles and those are stand-ins. ~ Cyclonebiskit (chat) 20:50, 3 April 2023 (UTC)[reply]
That's what I got :-) -- ChrisTheDude (talk) 08:46, 3 April 2023 (UTC)[reply]
- I've made the above corrections and replied to two of them. Thank you for looking this over, ChrisTheDude! ~ Cyclonebiskit (chat) 20:50, 3 April 2023 (UTC)[reply]
Support -- ChrisTheDude (talk) 07:11, 4 April 2023 (UTC)[reply]

Dank

~~Supporting on prose.~~ Very nice work. I skimmed the prose and made minor edits. Nothing big jumped out at me. Earlier in my wiki-career, I used to do a lot of prose supports ... I ~~usually~~ almost always do complete reviews at FLC, but there was a lot to read here. If I get motivated, I might finish up later. I hope you'll consider reviewing (or even just prose-reviewing) ~~List of basal superasterid families or~~ List of early-diverging flowering plant families or (whenever I can nominate it) List of nitrogen-fixing-clade families. - Dank (push to talk) 15:29, 6 April 2023 (UTC) Note that my last edit wasn't strictly "prose" ... I couldn't find that phrase in the two listed sources. That's not a problem ... I just removed the phrase, and the paragraph works fine without it (prose-wise), but you can re-insert if you want to source it (or if my search failed for some odd reason). - Dank (push to talk) 16:01, 6 April 2023 (UTC) Oops ... forgot my standard disclaimer "feel free to revert or discuss". That always applies. - Dank (push to talk) 12:03, 7 April 2023 (UTC)[reply]
- @Dank: I appreciate the review! The bit you removed isn't of much importance for the purposes of this list so it's all good. I'll take a look at the early-diverging flowering plants in the next day or two. ~ Cyclonebiskit (chat) 02:49, 9 April 2023 (UTC)[reply]
Continuing.
Standard disclaimer: I don't know what I'm doing, and I mostly AGF on sourcing.
Checking the FLC criteria:
1. I covered prose above. I typically don't check sorting on number or date columns, but I did check the state column. I sampled the links in the main table.
2. The lead meets WP:LEAD and defines the inclusion criteria.
3a. The list has comprehensive items and annotations.
3b. The list is well-sourced to reliable sources, and the UPSD tool isn't indicating any actual problems (but this isn't a source review). All relevant retrieval dates are present.
3c. The list meets requirements as a stand-alone list, it isn't a content fork, it doesn't largely duplicate another article (that I can find), and it wouldn't fit easily inside another article.
4. It is navigable.
5. It meets style requirements. At a glance, the one image seems fine.
6. It is stable.
Support. Well done. - Dank (push to talk) 23:26, 12 April 2023 (UTC)[reply]

Accessibility review (MOS:DTAB)

Tables need row scopes on the "primary" column for each row, which in combination with column scopes lets screen reader software accurately determine and read out the headers for each cell of a data table. You have them for the summary table but not the main one. Row scopes can be added by adding !scope=row to each primary cell, e.g. |SW of [[Arnett, Oklahoma|Arnett]] becomes !scope=row | SW of [[Arnett, Oklahoma|Arnett]]. If the cell spans multiple rows with a rowspan, then use !scope=rowgroup instead.
Please see MOS:DTAB for example table code if this isn't clear. I don't return to these reviews until the nomination is ready to close, so ping me if you have any questions. --Pres N 18:17, 8 May 2023 (UTC)[reply]
- @PresN: does the !scope=row need to be in the first cell of the row or is the second cell okay? You've suggested using the location which has a unique identifier for each tornado and that retains the bgcolor for EF#s which is preferable. Alternatively, is |!scope=row or just |scope=row viable to avoid the addition of bolded text or does that not work with screen reader software? ~ Cyclonebiskit (chat) 21:16, 30 May 2023 (UTC)[reply]
  - @Cyclonebiskit: It can be the second cell, though a) consider if you should just move that whole column to be the first, and b) whatever cell is the header cell needs to be on its own line in the wikicode (looks like all your cells are on their own line, so no worries there). It does have to be just !, ! means header cell while | means regular cell, so |! is a regular cell that has an exclamation point in its text. If you want to remove the bolding, change {| class="wikitable sortable" to {| class="wikitable sortable plainrowheaders" at the top of the table. --Pres N 00:42, 31 May 2023 (UTC)[reply]
    - @PresN: I shifted the location columns left to accommodate the change in header cell. The Weather WikiProject has become notorious for contentious discussions on formatting changes in recent years so we'll see how a new MOS adjustment goes over ~ Cyclonebiskit (chat) 19:35, 4 June 2023 (UTC)[reply]

Jake Jakubowski

Support Very nicly written with really good statistics. Table layout looks great. The only recomendation I would give is to maybe add the {{{currency}}} template so those outside of the U.S. can understand that your using the U.S. Dollar. Jake Jakubowski (Talk) 05:58, 12 July 2023 (UTC)[reply]

Not the biggest fan of having the EF column as the header as per above, but any header is better than none, and I see the consensus over at the weather project and am not going to fight it. Source review passed, promoting. --Pres N 18:15, 13 July 2023 (UTC)[reply]

Closing note: This candidate has been promoted, but there may be a delay in bot processing of the close. Please see WP:FLC/ar, and leave the {{featured list candidates}} template in place on the talk page until the bot goes through.

The above discussion is preserved as an archive. Please do not modify it. No further edits should be made to this page.