Document formatting issues and anomalies

[maryjom]

In moving to the new W3C document formatting and markdown, there are a few things that could be improved:

• <INS>some text</INS> is used to indicate where there is replacement or inserted text. In the old WCAG2ICT, the replacement or inserted text was enclosed in square brackets, in red bold text. Now it appears with no square brackets, in green, underlined style text. I had to add in bold and square brackets in the markdown, but can't figure out how to change the style of the text so it is red and not underlined. The underlining looks bad and is confusing when used on a large chunk of text that contains links. Makes it hard to tell the links apart from the rest of the text - all are green text and underlined.
  Here's the visual example from the 2013 WCAG2ICT:

Compared to the editor's draft:

• Would be really nice to have a special callout box that contained the WCAG2ICT interpretation that is different from the Example and Note styling. See the original WCAG2ICT screen shot above where there is a non-color filled callout box to highlight the section of WCAG2ICT guidance.
• Would be great to be able to number notes. Sometimes there can be 8 or so notes in a row.
• Would be great to have a unique style to tell the difference between the WCAG note and new WCAG2ICT notes. Maybe the use of <INS> styling will be sufficient, but it's currently not used consistently throughout and is not good if all text is underlined.
• Would be great to have control over what sections are numbered and what are not to make the section numbers more closely match the WCAG SC numbering. Otherwise, it's weird to go through the document and see a section numbered 6.1.5.3.1 that is talking about Success Criterion 1.4.2, as shown in the screen shot below.

[daniel-montalvo]

@maryjom

I edited your comment above, including checkboxes and ticking those that I think are resolved. Please let me know if that's a correct understanding.

[maryjom]

I think this can now be closed. I don't think we'll get any special callout box style for WCAG2ICT guidance and the other things have been handled in the latest updates to the editor's draft.