13 Feb 2008


See also: IRC log


Johannes, CarlosV, Shadi, CarlosI


Comments on WCAG 2.0 by CarlosI


CI: too many different parameters (window size, screen resolution, font-size...) that are not controllable by the content creator


saz: I read it as having to insert a <br> after 80 characters

<shadi> For the visual presentation of blocks of text, a mechanism is available to achieve the following:

<shadi> For people with some reading or vision disabilities, long lines of text can become a significant barrier. They have trouble keeping their place and following the flow of text. Having a narrow block of text makes it easier for them to continue on to the next line in a block. Lines should not exceed 80 characters.

RESOLUTION: group agrees with CarlosI that 'width no more than 80 characters' is not sensible

saz: e.g. in german (with very long words) magnification up to 200% will not wrap

<shadi> http://www.w3.org/WAI/ER/tools/advanced

saz: there are ways to use em
... note that the SC requires 'a mechanism', which can also be a style sheet switcher

<shadi> Specifying line spacing of 1.5 in CSS (HTML, CSS, future link)

jk: 1.4.8 4th bullet: line spacing vs. line-height (CSS)

saz: 5th bullet: what is the base for 200%?

<shadi> Providing options within the content to switch between layouts that use a variety of font sizes (future link)


saz: it's a business issue

ci: it's a testability problem because there are no criteria for 'essential'
... no WCAG 2 docs shed light on this 'grey' area

<shadi> http://www.w3.org/TR/2007/WD-UNDERSTANDING-WCAG20-20071211/visual-audio-contrast-text-images.html

<shadi> http://www.w3.org/TR/WCAG20/#puredecdef

<shadi> pure decoration

<shadi> serving only an aesthetic purpose, providing no information, and having no functionality

<shadi> Note: Text is only purely decorative if the words can be rearranged or substituted without changing their purpose.

<shadi> Example: The cover page of a dictionary has random words in very light text in the background.

<shadi> http://www.w3.org/TR/2007/WD-UNDERSTANDING-WCAG20-20071211/visual-audio-contrast-text-images.html#visual-audio-contrast-text-images-examples-head

jk: the more difficult thing is visual presentation of text being 'essential'

ci: e.g. corporate design guidelines requiring a certain font for headlines

RESOLUTION: group agrees with CarlosI's comment on 1.4.9

saz: ci, anything really pending things?

ci: the most interesting things for our group may be the last two comments

Updated "Content-in-RDF" Editor's Draft

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2008Feb/0002

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2008Feb/att-0002/WD-Content-in-RDF-20080207.html

<shadi> <h3><a id="example" name="example">

<shadi> <h3 id="example">

RESOLUTION: in ERT documents don't use div elements that don't have functions
... keep a elements with name and id attribute for link targets

<shadi> proposed namespace: http://www.w3.org/2007/content#

<shadi> proposed namespace: http://www.w3.org/ns/2007/content#

proposed namespace: http://www.w3.org/ns/content#

EARL namespace is http://www.w3.org/ns/earl#

<shadi> http://www.w3.org/2006/http#

saz: benefit for using years: versioning

ACTION saz and ci to send comments about Content-in-RDF to mailing list

<scribe> ACTION: saz and ci to send comments about Content-in-RDF to mailing list [recorded in http://www.w3.org/2008/02/13-er-minutes.html#action01]

Summary of Action Items

[NEW] ACTION: saz and ci to send comments about Content-in-RDF to mailing list [recorded in http://www.w3.org/2008/02/13-er-minutes.html#action01]
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2008/02/13 16:11:27 $