# Talk:Glassheart Tour

Shouldn't the tour date table have the first column as the date instead of the city, it is a list of tour dates after all. All other tour articles follow this.  — AARON • TALK   14:10, 9 May 2013 (UTC)

I've used an accessible table ... tour tables don't use a strictly WP:ACCESSIBLE format. I've tried to make this screenreader friendly. Following the advice when we wrote WP:DISCOGSTYLE, it didn't make sense having the year before the song name as this is what the screenreader emphasises... the first column. — Lil_℧niquℇ №1 [talk] 15:33, 9 May 2013 (UTC)
It is but I think for a tour dates table, the tour dates themselves should be first.  — AARON • TALK   23:27, 9 May 2013 (UTC)
I also have to agree with dates going first. It's a common Wikipedia practice and what many people are most used to using. Just because Discographies follow that format does not mean this has too. For concert tours dates seem to be the best starting point while for Discographies it would definitely be album, single, song. It should be tailored to each specific use. --Shadow (talk) 03:34, 19 May 2013 (UTC)
You guys miss the point. Everyone said the same thing about discographies when the new formats were first suggested! The idea of not having the date first is the emphasis that screenreader technology gives the information in the first column. The most important piece of information is the location not the date. Just because most of wikipedia is not accessible doesn't mean every article should be inaccessible. If you insist change the dates to the first column but the !scope formatting should be kept. — Lil_℧niquℇ №1 [talk] 09:07, 19 May 2013 (UTC)
In the cast of these tours, it is not a disaster if the tour date becomes the row header. What we need to do for any table is to pick out the key piece of information that uniquely identifies the row. In the case of singles, "year" is often no good because an artist may release more than one single in a year. In this case, each concert has a unique date (but actually not a unique city as London was played twice). Someone reading the table using a modern screen reader is able to move around a table in any direction, not just row-by-row, top-to-bottom. So that they know where they are, a screen reader can be set to announce the row header and column header for each cell that is visited. As an example, a screen reader user could navigate down the "Venue" column and hear something like "Venue; 15 April 2013; Tempodrom" then ""Venue; 16 April 2013; Jahrhunderthalle". What Lil' is suggesting is that people might prefer "Venue; Berlin; Tempodrom" then ""Venue; Frankfurt; Jahrhunderthalle". I don't think in this case, there is enough difference to fall out over. Where there is a difference, however, is that Lil' quite rightly has tried to mark up the row header with  ! scope="row" . This is a requirement from MOS:DTT, part of WP:ACCESS, which is itself part of our Manual of Style, and should not be ignored without very good reason. We use this markup to make our tables as accessible as possible with as many different screen readers as possible. So please can you come to a compromise that leaves the row headers and row scopes in place, please? I've done an example edit to show how to mark up row headers per MOS:DTT. If this causes formatting problems, then please let me know. --RexxS (talk) 21:13, 19 May 2013 (UTC)

Should concerts played by lewis in Bahrain, Malta etc. be included in the tour dates? Because they have included pretty much the exact same set list every time. These one off concerts are the same as the main bulk of the Glassheart Tour.  — ₳aron 13:52, 26 October 2014 (UTC)

http://www.manchestereveningnews.co.uk/whats-on/whats-on-opinion/review-leona-lewis-manchester-o2-3862123  — ₳aron 18:20, 30 April 2015 (UTC)
http://www.standard.co.uk/showbiz/celebrity-news/motown-tunes-for-leona-lewis-8685069.html
http://www.independent.co.uk/arts-entertainment/five-pairs-of-tickets-to-see-leona-lewis-to-be-won-8602506.html
http://www.ipswichstar.co.uk/news/review_leona_lewis_glassheart_tour_ipswich_regent_april_29_1_2173690

Hello fellow Wikipedians,
I have just modified 4 external links on Glassheart Tour. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

Added archive https://web.archive.org/web/20130110041714/http://southwestshows.co.uk:80/2012/10/leona-lewis-brings-glassheart-tour-to-plymouth-pavilions-in-2013-news/ to http://southwestshows.co.uk/2012/10/leona-lewis-brings-glassheart-tour-to-plymouth-pavilions-in-2013-news/
Added archive https://web.archive.org/web/20130111185308/http://www.sonymusic.de:80/Leona-Lewis/News/I/51556/O/W to http://www.sonymusic.de/Leona-Lewis/News/I/51556/O/W
Added archive https://web.archive.org/web/20121011064740/http://www.leonalewismusic.com/gb/news/detail/leona_uk_tour/ to http://www.leonalewismusic.com/gb/news/detail/leona_uk_tour/
Added archive https://web.archive.org/web/20130511234701/http://www.plymouthpavilions.com/prod-productions_details.asp?pid=735 to http://www.plymouthpavilions.com/prod-productions_details.asp?pid=735
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 18:01, 12 January 2017 (UTC)