Template talk:Infobox NFL biography/Archive 8

Including "all" colleges attended in Infobox?
Currently this template intends to support a single college via:


 * college            =

Called out as:

In addition to this not being consistently honored, is omitting prior colleges from the Infobox even desirable? Obviously numerous, prominent players have played at multiple schools (JUCO, early college transfer, senior graduate transfer). In many cases, the particulars are flushed out within the article and are a meaningful part of the player's career arc. Some examples: Cam Newton, Warren Moon, Larry Allen, Cortez Kennedy, Dick Lane, Aaron Rodgers and Roger Staubach, and Vernon Adams 2x FCS PotY runner-up at Eastern Washington who will be ultimately listed as FBS Oregon due to a 5th year transfer.

Note 1, if pursued, this should be compliant with the usability improvements called out at Wikipedia_talk:WikiProject_Accessibility, where &lt;br&gt;s are being replaced ala college1= college2= for screen reader usability reasons.

Note 2, an editor wiser than I am may wish to comment on implications (if any) to the long-standing goal of unifying our multiple football infobox templates. UW Dawgs (talk) 00:47, 13 August 2015 (UTC)


 * I'd support allowing the other colleges. Granted we shouldn't generally overload an infobox, but an extra line or two for the few players this applies to adds relevant info, and saves countless edit wars over non-intuitive fine print over the college param. FWIW, it's commonly done for NBA players.—Bagumba (talk) 00:58, 13 August 2015 (UTC)


 * I don't object to including a second college team in the template college parameter. If we do so, please note that Infobox gridiron football person and Infobox NFL player are coded completely differently.  Infobox NFL player uses embedded "plain list" coding for input data for (1) past teams and (2) honors and awards -- that's why it does not require individual fields for every team and tenure like the CFL infobox does.  There is no good reason for mixing the two styles of coding.  The other alternative for college teams with relatively short names, e.g., "Auburn" or "Florida," you can already include both in the same field separated by a comma.  We just need to change the infobox parameter instructions on the template documentation page.  Cheers.  Dirtlawyer1 (talk) 01:20, 13 August 2015 (UTC)


 * Although I have reverted edits adding other colleges in the past, I did so only because that is the outline of the current template. That being said, I would support allowing other colleges, as long as it doesn't overcrowd infoboxes. Chambr (talk) 04:09, 13 August 2015 (UTC)


 * I'd still say two max, if both were equally important. If a player attended 5 community colleges of minor note and then a major university, I say we still just list the major one only. (I.E., players like Cam Newton are the exception, not the norm.) ~ Dissident93  (talk) 04:58, 13 August 2015 (UTC)

I have tweaked the instructions for the "collegeteam" parameter to be permit the listing of more than one college team, with the caveat "if important to understanding a player's college career history." Please review and let me know if this provides sufficient flexibility to deal with situations where a given player had significant playing time as a member of two different college teams. Dirtlawyer1 (talk) 18:20, 27 August 2015 (UTC)
 * Thank you, this solution is preferable to my over-thought implementation inclusive of years-attended. Would the instructions benefit from an explicit styling callout, re left-to-right, comma-delimited (newest-to-oldest) vs stacking (&lt;/br>, newest-above-oldest)? Currently this feels open to both executions. Most records I've seen were executed as left-right, but NFL users might be biased to stacking as is done for the player's pro teams.  UW Dawgs (talk) 18:48, 27 August 2015 (UTC)
 * Please avoid using  to achieve stacking as per WP:VLIST. plainlist or unbulleted list would achieve the same look while being accessible. ~ RobTalk 19:03, 27 August 2015 (UTC)

WP:FONTSIZE issue
As per WP:FONTSIZE, small text should not be used in the infobox, but it appears that it's fairly widespread, particularly where it is used to note when players were only on the practice squad or on the team during the offseason. I've created Category:Infobox NFL player articles with small text to track this, and I plan to remove this small text using WP:AWB imminently. and I think the best way forward is to remove this small text using WP:AWB. Interested editors may wish to consider whether they would like to handle this text with a new parameter, similar to the discussion occurring for the Infobox gridiron football person template. ~ RobTalk 05:52, 5 August 2015 (UTC) I've mocked it up in the sandbox. Compare:
 * The use of the small text for the practice squad note has been part of the standard formatting for the NFL player infobox for all of my six years working on CFB and NFL player articles. It was part of the original consensus to include off-season, preseason and practice squad tenures in the career history of NFL players.  It is included in a significant percentage of the 14,000+ transclusions of the template, and a large number of editors have worked to include that level of consistent formatting in those articles.  By removing it, the inclusion of the off-season, preseason and practice squad tenures becomes seriously misleading.  I urge you not to make any unilateral actions without getting significant input from your fellow WP:CFB and WP:NFL editors.  Thanks.  Dirtlawyer1 (talk) 06:07, 5 August 2015 (UTC)
 * Oh, I don't plan to remove the text, just the small tags. I'll hold off on removing it pending comments, which is why I posted here (imminently was a terrible choice of words), but I struggle to see how any policy-based rationale could justify inclusion of the small text rather than making it normal-sized given the policy of WP:FONTSIZE. I'll post project notices in a moment, was just taking care of some stuff first. Sorry for any confusion caused by my strong wording. ~ RobTalk 06:12, 5 August 2015 (UTC)
 * Please do not take any widespread action without consulting your fellow WP:CFB and WP:NFL editors first. There should be an agreed-to alternative in place before any action is taken; making such widespread AWB edits contrary to established consensus could be construed as WP:DISRUPTIVE.  Thanks.  Dirtlawyer1 (talk) 06:17, 5 August 2015 (UTC)
 * As noted above, I have not yet made any AWB edits and will hold off pending comments. ~ RobTalk 06:18, 5 August 2015 (UTC)
 * It should be noted that WP:FONTSIZE represents a policy - an established community-wide consensus. Inclusion of small text in this infobox is at best local consensus at the moment. ~ RobTalk 07:02, 5 August 2015 (UTC)
 * Rob, actually, WP:FONTSIZE is a guideline, not a policy. Some of us have been around long enough to know the difference.  And when existing consensus formatting has been in place for 6+ years, there is clearly no emergency that needs to be resolved in the next 24 hours.  Dial it down a notch and let's see if we can't find an alternative that works for everyone -- that might take a few days.  Dirtlawyer1 (talk) 07:24, 5 August 2015 (UTC)
 * Other than my unfortunate choice of words in my original post, which I've already noted, I've not said anything that should indicate that I'm in a rush. To be clear, I'll repeat: I have not made any AWB edits and will hold off pending comments. The difference between policy and guideline is an interesting one, and something I did not know, so thank you for linking me to it. Fortunately, WP:Local consensus applies to guidelines as well, so my previous comment is still valid. ~ RobTalk 07:29, 5 August 2015 (UTC)
 * That's not the only issue with career footnotes; they are indented using a colon, generating a definition list. A singular footnote is no list, much less a definitions one. Alakzi (talk) 08:27, 5 August 2015 (UTC)
 * Does this have accessibility implications or other practical effects? I admittedly am not at all well-versed in the specifics of the HTML behind using wiki markup, or HTML at all for that matter. ~ RobTalk 08:45, 5 August 2015 (UTC)
 * Well, a screen reader might announce a definition list, but accessibility is not otherwise impacted. However, we do strive towards semantic HTML. Alakzi (talk) 08:50, 5 August 2015 (UTC)
 * Very true. Is there an alternative way to achieve a similar aesthetic? ~ RobTalk 09:02, 5 August 2015 (UTC)
 * We've got pad, but perhaps we should add a footnotes parameter to the infobox, to avoid having to repeat a design element. Alakzi (talk) 09:06, 5 August 2015 (UTC)
 * As for alternatives to small text, we could colour the text grey, like we do in Infobox sportsperson and a bunch of other infoboxes. Alakzi (talk) 09:14, 5 August 2015 (UTC)

Alakzi (talk) 09:23, 5 August 2015 (UTC)


 * Even ignoring the accessibility issue, I think the latter is more visually appealing. Thanks for the mock-up. ~ RobTalk 10:13, 5 August 2015 (UTC)
 * What is the current relative percentage size of the text of Infobox NFL player relative to main body text? What was the then current relative percentage size of the text of Infobox NFL player relative to main body text on January 1, 2015?  Dirtlawyer1 (talk) 13:44, 5 August 2015 (UTC)
 * 95% and 90%, respectively. Alakzi (talk) 13:46, 5 August 2015 (UTC)
 * When was the infobox text reduced from 95 to 90%? Also, was the "let" -- the space between lines of infobox text -- also reduced?  Dirtlawyer1 (talk) 14:29, 5 August 2015 (UTC)
 * The font size hasn't been reduced; it was increased, at your request, from 90% to 95%. I don't recall the leading having been reduced, either. Alakzi (talk) 14:38, 5 August 2015 (UTC)
 * Yes, I recall making that request in reaction to what I perceived as the shrinking size of the infobox text, which was altering the visual appearance of the infobox. The coding base for this template was changed from pure HTML mark-up to using Template:Infobox as its base sometime in February 2015, correct? Dirtlawyer1 (talk) 15:18, 5 August 2015 (UTC)
 * Sort of. It was converted to use Infobox sometime before then by Frietjes, but she'd kept the tables for the height and weight, and had not used header cells for the remaining vital statistics' labels. Alakzi (talk) 15:24, 5 August 2015 (UTC)
 * How should we proceed? Alakzi (talk) 16:25, 6 August 2015 (UTC)
 * No-one's voiced opposition yet (just caution), but I think it would be wise to wait another 24-48 hours before proceeding to give involved editors a chance to respond. ~ RobTalk 16:31, 6 August 2015 (UTC)
 * I meant to poke Dirtlawyer1. ;-) Alakzi (talk) 16:51, 6 August 2015 (UTC)
 * Yes, A, I know I've been poked. LOL  I was still contemplating what can be done.  We can leave the infobox main text at 95% (still looks small to me, but I am going to review it on several other monitors and browsers later) and use 85% text for practice squad note.  Perhaps there is another visual effect we can use for the practice squad note -- italics?  Shaded text?  One alternative is to use an explanatory footnote instead, but that would require thousands of edits to the affected articles.
 * Also, related, but different problem: we need to increase the let for the plain list fields for the lists of teams and honors and wards. As presently coded, the let is unusually tight.  That was why I was inquiring about the history of the edits to the template base, as well as the direct edits to the infobox text size.  Dirtlawyer1 (talk) 17:09, 6 August 2015 (UTC)
 * I don't plan to comment much on the aesthetic, but I wanted to note that if the solution requires consistent formatting across articles, it should be accomplished with a new parameter as Alakzi mocked up. Italics may seem simple enough to apply in-article, but it's likely we'd be back here in a year's time when new editors who cannot be expected to know about this discussion have created new articles with small text. ~ RobTalk 17:17, 6 August 2015 (UTC)
 * I don't want to rush this, but given that there's no opposition to removing the small text, here's what I would propose. Why don't we create a new parameter a la 's mock-up to start? We can leave that formatting for now with the grey text, and continue the discussion on what the final aesthetic should be. Since the appearance of the footnote will be achieved by a parameter, it would be easy to change the formatting in all articles at the same time once the parameter is in use. You could just change the formatting of the note on the template, and you'd be all set. This will achieve immediate compliance with WP:FONTSIZE, will use something that we all can live with as an intermediary, and will allow the final discussion on formatting to take place at a leisurely pace with no pressing concerns about compliance to guidelines. I think the temporary change would clearly be a net positive for the project; it achieves compliance with guidelines immediately, while the only issue left to be decided is a matter of personal taste. I think it's uncontroversial to say that guidelines outweigh personal taste every time. Thoughts on this solution? ~ RobTalk 05:05, 8 August 2015 (UTC)
 * That would be fine with me. (I've also increased the spacing between list items slightly.) Is it always the same footnote? Could we get away with a simple on/off switch? Alakzi (talk) 05:38, 8 August 2015 (UTC)
 * Using the footnote that you had in your mock-up, a simple on/off would work. That's the most general form I've seen of the footnote. Sometimes people type the more specific "Preseason and/or practice roster only", but that is a subset of "Offseason ...", and consistency in the footnote is likely a good thing. It avoids confusion among readers that are viewing multiple articles. ~ RobTalk 06:22, 8 August 2015 (UTC)

Is this an acceptable solution in your opinion, ? ~ RobTalk 02:28, 9 August 2015 (UTC)
 * With no opposition, I'd say we're good to make the change, keeping in mind that it's extremely easy to change the formatting of a simple on/off parameter should opinions about it change at a later date. Would you mind introducing the parameter, ? I'll hold off the actual article changes for another 1-2 days to allow a little more time for comments to see if any opposition emerges. ~ RobTalk 04:03, 11 August 2015 (UTC)
 * I've made the change in the sandbox. Copy it over whenever we're ready for launch. Alakzi (talk) 08:20, 11 August 2015 (UTC)
 * None of the test cases are showing the proposed change. Also, can you explain how is the proposed new notation to be invoked?  Is there a switch to be included in the template?  If so, how do we propose to convert the existing thousands of existing to uses to the new coding?  Dirtlawyer1 (talk) 13:43, 11 August 2015 (UTC)
 * Test cases added. Yes, there is a switch; it can be invoked with yes. Rob appears to have offered to convert existing uses with AWB; he can do so at his leisure. Alakzi (talk) 13:46, 11 August 2015 (UTC)
 * In your estimation, this solution is 100% compliant with WP:ACCESSIBILITY? The shaded text does not present any related accessibility problems for visually-impaired readers?  Dirtlawyer1 (talk) 14:00, 11 August 2015 (UTC)
 * It does not violate WP:COLOR, no. Do you find the shaded text unappealing? The note is also 90% of the infobox text (that is, 12 pixels in size); we don't need to keep both the reduced font size and the shading, I imagine. Alakzi (talk) 14:09, 11 August 2015 (UTC)
 * Okay, good. Can we get an example in which the note text is 85% of main body text size?  I believe 85% is the minimum per the accessibility standards, correct?  Dirtlawyer1 (talk) 14:12, 11 August 2015 (UTC)
 * Yes, 11 pixels is the minimum. See below. Due to the fact that the infobox base font size was increased to 95%, some browsers will round the left column up to 11 pixels, while others will round it down to 10. Alakzi (talk) 14:22, 11 August 2015 (UTC)


 * It's also worth noting that, while 11px is a bright line rule, WP:FONTSIZE indicates reduced size text should be used sparingly. When there are alternatives that are equal in terms of function, they are preferable. Regardless of the outcome regarding the aesthetic, what's your opinion on the use of a parameter in general ? I assume it's preferable to individual application of footnotes, since it's standardized and easy for new editors to apply. ~ RobTalk 14:58, 11 August 2015 (UTC)
 * In order to better illustrate the proposed change, I have added example team tenures to the talk page mock-ups above. Can anyone explain why the let (i.e. line height of the infobox text) noticeably varies across the three examples?  Dirtlawyer1 (talk) 15:16, 11 August 2015 (UTC)
 * I've increased the leading in the sandbox. It doesn't vary between the first and second examples. Alakzi (talk) 15:19, 11 August 2015 (UTC)
 * Also, while we're fixing this accessibility issue, we should also address the fact that the asterisk in this type font is relatively small in comparison to the actual text. Perhaps we should use another more noticeable symbol/glyph to designate the offseason/practice squad tenures?  Suggestions?  Dirtlawyer1 (talk) 15:23, 11 August 2015 (UTC)
 * We could use a dagger (†), but people won't know how to type it out, and Dagger is an image. Alakzi (talk) 15:26, 11 August 2015 (UTC)
 * It also appears to be inaccessible. Alakzi (talk) 15:28, 11 August 2015 (UTC)
 * Well, with current micro asterisk, persons with 20/20 vision have an ACCESSIBILITY problem -- it's barely noticeable in normal size mainbody text, but it virtually disappears in 85% or small text. Clearly, it would be easier for editors if we used a glyph from the standard ASCII keyboard, but that presents a very limited set of options.  In the past I've sought the help of, who is either blind (or nearly so) and uses screen-reader software.  Maybe we should ask for his help -- I bet he has some good ideas for footnote glyphs we might use.  Let's see what he says.  Dirtlawyer1 (talk) 01:32, 13 August 2015 (UTC)
 * I'm not sure ... "^" would be fine, or just about any other symbol. It's probably better to suggest a symbol and find out what I think; ping me if you do that. I'm totally blind so can't comment on font size issues. Graham 87  02:07, 13 August 2015 (UTC)
 * Dagger is an image because it's the most compatible means of ensuring that a screen-reader has something to read out (by setting its alt text). As a bonus, you can actually set its alt text to be the full text from the footnote (as long as it's no too long or used too often as it then becomes annoying). For example  produces †, which, as you can see if you examine the element, has the full text. By placing that next to the team name, a screen reader would get the info immediately without having to find the footnote later on as they were reading through the table. As the next best option, the # symbol is bigger than * in all likely fonts and is easy to type as well as being read normally by JAWS. --RexxS (talk) 02:22, 13 August 2015 (UTC)
 * Thanks, Rexx. Those are excellent suggestions.  Dirtlawyer1 (talk) 03:25, 13 August 2015 (UTC)
 * I would prefer any option that does not involve images. We shouldn't have to resort to that to accomplish accessibility. Alakzi (talk) 07:31, 13 August 2015 (UTC)
 * I wish you were right,, but there are unfortunately occasions where it's the best solution. The relevant debates are at Wikipedia talk:Manual of Style/Accessibility/Archive 11 and Featured list candidates/Philadelphia Phillies all-time roster (C)/archive1. The relevant WCAG technique that suggests the use of images in these cases is F26. HTH --RexxS (talk) 09:41, 13 August 2015 (UTC)
 * I've looked into the use of ARIA attributes, but it seems to be prohibitively complex to maintain. Perhaps this is the best we can do. Alakzi (talk) 09:54, 13 August 2015 (UTC)

(#) would accomplish it easily enough, but that would be the sort of thing that would need to be manually changed in all articles. I doubt a bot could accomplish it, because the * character is also being used in the same field for bulletpoints, and we wouldn't want to change those. Personally, I think the * meets accessibility requirements. The character may have white space built into it, but the font is still 11pt. I doubt the guideline was intended to exclude white space built into a character, because that would mean asterisks in our main body text are non-compliant. By the way, I've gone ahead and submitted a bot approval request for an AWB bot to take care of moving things over to the new parameter. While the aesthetic is not finalized yet, the on/off switch has been agreed upon, and the built-in aesthetic is easily changed later, as previously noted. ~ RobTalk 07:40, 13 August 2015 (UTC)
 * It should be fairly trivial with regexes; simply replace  with   inside the parameter. You could add it to your BRFA. Alakzi (talk) 07:52, 13 August 2015 (UTC)
 * Looking into this. ~ RobTalk 09:18, 13 August 2015 (UTC)
 * I can do this with that bot and regex, yes, but I'd like a final yea or nay on the change before adding it to the BRFA. I don't believe there's been clear support for the use of # yet. I can always submit another BRFA if needed. ~ RobTalk 09:26, 13 August 2015 (UTC)

For future edits, can someone please update the template documentation to include the  parameter? Thanks! WikiDan61 ChatMe!ReadMe!! 14:45, 27 August 2015 (UTC)
 * Noted, will do. Dirtlawyer1 (talk) 17:48, 27 August 2015 (UTC)


 * The BRFA to complete the conversion to the new parameter was approved and the task has been run. I'm using AWB now to convert the remaining articles that were not covered by the rules approved for use in the BRFA. Hopefuly Category:Infobox NFL player articles with small text will be empty by the end of today. ~ RobTalk 18:06, 27 August 2015 (UTC)
 * Done. ~ RobTalk 14:15, 28 August 2015 (UTC)
 * Thank you for your efforts on this, Rob. I'm sure this took a little longer than you originally anticipated, but 14,000+ NFL player infoboxes are now fully compliant with WP:ACCESSIBILITY guidelines, and it was accomplished with a minimum of controversy.  Everyone with whom I have spoken seems to be pleased with the outcome.  Cheers.  Dirtlawyer1 (talk) 14:23, 28 August 2015 (UTC)
 * Thank you. Did you place any other footnotes in definition lists? Alakzi (talk) 14:26, 28 August 2015 (UTC)
 * There were a handful of articles (around 10) that had footnotes other than the one talked about here. In those cases, I kept the footnotes as they were (in a list), but removed small tags to comply with FONTSIZE. I didn't place any in lists that weren't there before. If you care to fix those with a new parameter for miscellaneous footnotes or some other method, you'll find all such articles within my last 50 contributions, and none of them would have been handled with AWB. ~ RobTalk 15:04, 28 August 2015 (UTC)
 * Rob, Alakzi is probably the wrong guy to handle the substance of those notes. If you can provide a list of player names or set of links to those articles with the additional infobox notes, I would be grateful.  In six years of working on NFL articles, this is the first time I have encountered these, and they need to be critically reviewed.  Thanks.  Dirtlawyer1 (talk)
 * I don't have any such list, unfortunately, or I would provide it. Looking through my recent contributions, I'm not finding many. It may be less than 10. More like two or three. I remember one other that used an additional footnote to denote teams he played minor league baseball on, but I didn't find that in looking through quickly. A few other footnotes I relocated to parentheses, mostly ones that denoted one day contracts. If I recall correctly, there were a total of 19 articles that I manually edited in a way other than just adding the new parameter. The edits were things like moving coaching information from "pastteams" to "pastcoaching", moving highlights from "pastteams" to "highlights", and other things like that which weren't being handled by my use of AWB. They can all be found in my recent contribs. I don't know how useful digging through my contribs for two or three articles is, and it's not something I plan to do. ~ RobTalk 15:37, 28 August 2015 (UTC)
 * Please, I know American football like the back of my hand. Alakzi (talk) 15:59, 28 August 2015 (UTC)