User:Lil-unique1/Usable and accessible
This essay contains the advice or opinions of one or more Wikipedia contributors on WP:ACCESSIBILITY. Essays may represent widespread norms or minority viewpoints. Consider these views with discretion. Essays are not Wikipedia policies or guidelines. |
Hello fellow wikipedians. You may or may not be aware but for the last few months, WP:Manual of Style has been undergoing massive changes and copy editing to remove redundancy. Whilst this was on-going it was decided to improve and update the accessibility guidelines. Please find a guide and essay on how to improve the accessibility and usability of articles and specifically improve music-related articles. There are several different options but each is supported by a relevant wikipedia policy. I have had very little input to the accessibility changes but I am involved in trying to manage its implementation at WP:DISCOGSTYLE. If you have any questions please ask me on on the essay talk page but if you are unhappy with the policy please ask the relevant policy page as this is just an essay not the policy itself.
- Note that the changes below, especially for data tables, do not currently apply to charts formatted using the {{singlechart}} - this will be addressed at a later date.
What is an accessible and usable article?[edit]
Accessibility is split into two fields. The reader and the editor. I'm sure you've come accross articles before and noticed that they have elaborate presentation schemes and lots of bright color etc. However such articles are not accessible for the following reasons:
- If a completely new editor wishes to modify the article with credible information they will find it extremely difficult because they won't know all of the intricate coding that goes into making the page look pretty. (usability issue)
- If viewed on a portable device e.g. mobile phone or iPod touch such pages often appear misformed. (interoperability issue)
- Often color is used as a method of conveying information, however those of partial or no sight maybe using digital screen reading software which cannot read such markups. They can only read the physical information. (accessibility issue)
So from this we can see that accessibility and usability affect both editors and readers of an article. Therefore making an article more accessible and usable is beneficial to both editors and readers.
Improving data tables[edit]
The key here is to think simple and you're half way there.
The major issue in music articles is data tables e.g. chart tables, release history tables and single discography tables. Below is a guide on how we can make those articles more simpler to read and edit per WP:Accessibility.
The code[edit]
The traditional wikitable is made using the following code: {| class="wikitable" |- ! column header 1 ! column header 2 |- ! row header 1 | normal cell 1,2 || normal cell 1,3 |- ! row header 2 | normal cell 2,2 || normal cell 2,3 |} |
Tables should now be formatted using the following code: {| class="wikitable" |- ! scope="col" | [column header 1] ! scope="col" | [column header 2] |- ! scope="row" | [row header 1] | [normal cell 1,2] || [normal cell 1,3] |- ! scope="row" | [row header 2] | [normal cell 2,2] || [normal cell 2,3] |}
|
Real data example 1[edit]
Taken from a real song, here is what the correct coding should look like.
{| class="wikitable" |- ! Country ! Date ! Format |- | United States | June 29, 2010 | [[Contemporary hit radio|Pop]] |} |
{| class="wikitable" |- ! scope="col"| Country ! scope="col"| Date ! scope="col"| Format |- ! scope="row"| United States | June 29, 2010 | [[Contemporary hit radio|Pop]] |}
|
So what does this look like to ordinary readers?
|
|
Real data example 2[edit]
Alternatively you can normalise the font size (remove the boldface) by using:
{| class="wikitable" |- ! scope="col"| Country ! scope="col"| Date ! scope="col"| Format |- | scope="row" United States | June 29, 2010 | [[Contemporary hit radio|Pop]] |- | scope="row" United Kingdom | August 31, 2010 | Urban music |} |
|
Overall advice[edit]
Do's[edit]
- Make minimal or little use of color:
- Color is difficult for those of partial sight to interpret.
- Color is difficult for new editors to format.
- Make minimal or no use of:
- <sup> </sup> <sub> </sub> <small> </small>
- Accept in cases of where is it really needed e.g O2
- Make use of simplistic tables (reduce color, and other mark up WP:deviations)
- ASK for advice.
Don'ts[edit]
- Projects e.g. WP:DISCOGSTYLE do not override the manual of style.
- Don't assume that because you've based your article on a WP:Good article or WP:Featured article it is automatically perfect, or follows all aspects of WP:MOS