Re: Tutorials copyedits

Applied the changes.

On 17 May 2014, at 2:51, Shawn Henry wrote:

> NOTE: Some edits below are commas and minor wording tweaks, so look 
> carefully. :-/ Sorry it was too hard for me to do these in github.
>
> ==throughout==
>
> Current punctuation:
> _1.3.1: Info and Relationships_ Information, structure, and 
> relationships conveyed through presentation can be programmatically 
> determined or are available in text. (Level: A)
>
> Suggest moving first colon and deleting colon after Level to simplify, 
> separate link from text, and match linked page punctuation:
> _1.3.1 Info and Relationships_: Information, structure, and 
> relationships conveyed through presentation can be programmatically 
> determined or are available in text. (Level A)
>
> Remember to change the status note in the full code pages.
>
> ==simple tables & captions==
>
> "Concert dates:" -> "Concerts":
>
> ==irregular tables==
>
> Current: In this table the row header cells are in the second column 
> rather than the first. The scope values row and has been used on the 
> <th> cells in the second column to ensure that data cells in the first 
> column, as well as those in cells to the right of the headers are 
> correctly associated.
>
> Suggest: In this table, the row header cells are in the second column 
> rather than the first. The <th> cells in the second column have 
> scope="row" to ensure that the data cells in the first column and the 
> data cells to the right of the headers are correctly associated.
>
> =milti-level tables==
>
> "To avoid producing an overly wide table the first row has..." ->
> "To avoid producing an overly wide table, the first row has..."
>
> "(location, size and type of accommodation)" ->
> "(location, size, and type of accommodation)"
>
> ==caption & summary ==
>
> "If both caption and summary are provided in one table, the summary 
> should not duplicate the caption." ->
> "If both caption and summary are provided for one table, the summary 
> should not duplicate the caption."
>
> Example 2
> current: "In HTML4 (and XHTML 1.x) the description can be marked up 
> using the summary attribute of the <table> element, but as this is 
> made obsolete in HTML5, the approaches in this section show how to put 
> the description within the <caption> element and using the WAI-ARIA 
> aria-describedby attribute or the <figure> element for the summary."
>
> suggest: "In HTML4 (and XHTML 1.x), the description can be marked up 
> using the summary attribute of the <table> element. Summary is 
> obsolete in HTML5. Approaches 2, 3, and 4 below show how to put a 
> description in the <caption> element, and use the WAI-ARIA 
> aria-describedby attribute or the <figure> element for the summary."
>
> "This table has an unusual table structure, the days of the week are 
> in the center column, morning times to the left and afternoon times to 
> the right." ->
> "This table has an unusual table structure: the days of the week are 
> in the center column, morning times in the left, and afternoon times 
> in the right."
>
> “Days are shown in the second column, morning opening hours in the 
> first column and afternoon opening hours are in the third column” ->
> “Days are in the second column, morning opening hours in the first 
> column, and afternoon opening hours in the third column”
>
> == faq ==
>
> "It’s better to break them up into simple tables" ->
> "It’s usually better to break up multi-level tables into simple 
> tables"
>
> I think un-italicize "Make sure that each separate piece of data has 
> its own cell."
>
> "Alignment: Align text to the left and financial data to the right, so 
> that people using screen magnification, larger text sizes or smaller 
> screens will be able to find it" ->
> "...so that people using screen magnification, larger text sizes, or 
> smaller screens will be able to find it"
>
> "On these tutorial pages, for example, header cells have always a dark 
> gray background." ->
> "For example, on these tutorial pages, header cells have a gray 
> background."
>
> "A note on layout tables: You shouldn’t use tables for layout 
> purposes. If you do don’t use any of the structural elements and 
> attributes discussed in this tutorial and add role="presentation" to 
> the <table> element. It’s much better to use Cascading Style Sheets 
> (CSS) for layout." ->
> "A note on layout tables: You shouldn’t use tables for layout 
> purposes. It’s much better to use Cascading Style Sheets (CSS) for 
> layout. If you do use layout tables, don’t use any of the structural 
> elements and attributes discussed in this tutorial, and do add 
> role="presentation" to the <table> element."
>
> "My site uses a table layout for pages." ->
> "My site uses a layout table to position information on pages."




--

Eric Eggert, Web Accessibility Specialist
WAI-ACT Project

I’m yatil on IRC.

Received on Saturday, 17 May 2014 08:56:49 UTC