RE: additional request for technical & financial factors -RE: DRAFT edits on BusCase - Policy

Henk,

Thanks for taking another pass at it! Most updates are incorporated in
the latest versions online. Comments surrounded by brackets ([...])
below. Let me know if you want to discuss any of this.

Best,

~ Shawn



Tech factors page

[DONE] Reduce the size of each page served by defining presentation in
style  sheets (which are only requested once per session), rather than
each page's  HTML. (WCAG 1.0 Checkpoint 3.3) = Reduce the size of each
page served by  defining presentation in style sheets (which are only
requested once per session),  rather than each page's HTML and by using
markup  structure rather than  images. (WCAG 1.0 Checkpoint 3.3, 3.1)

[DONE] - "Reduce site-wide style change time and effort" add also 3.1, 
[DONE] - "Reduce unwanted page downloading (and thus server requests)"
add  also 13.6, 14.3, 
[DONE] - "Render stylized information across a wide range of
configurations" add  also 3.3, 
[missing connection between 3.5 ("Use header elements to convey document
structure and use them according to specification") and this point]-
"Allow users  and user agents to request content" add also 3.5


Financial factors page

Increases findability: 
[not sure how to fit this re-wording with the lead in, "Accessibility
techniques  increase the findability of Web pages by exposing content to
search engines, both  internally (within a Web site) and externally
(across the World Wide Web). For  example:" ] - By using meta data
because some search engines use metadata to  index pages (WCAG 1.0
Checkpoint 13.2) [1]
[1.3 covers says to provide an auditory description, which is not
available to  search engines] - By using alternative text for images
since search engines  search for text strings and not for graphical
information (WCAG 1.0 Checkpoint  1.1, 1.3) [2]
[added 3.4]- By using text marked up as headings because some search
engines  give higher weight to text marked up as headings (WCAG 1.0
Checkpoint 3.5) [3] 

Increases usability:
[hum, clear & understandable content and good color contrast don't
really focus  on making it easier to find the right location or page]
Some accessibility  guidelines make it easier to find the right location
or page for everyone, thus  directly increase usability, such as: 
[added checkpoints]
- consistent navigation (WCAG 1.0 Checkpoint 13.4); 
- clear and understandable content (WCAG 1.0 Checkpoint 14.1);
- clearl link text (WCAG 1.0 Checkpoint 13.1);  
- good color contrast (WCAG 1.0 Checkpoint 2.2). 

[DONE] Other accessibility guidelines can indirectly increase usability,
for  example, by making Web pages load faster *<link to soc page>


Decreases the cost of translating
[DONE, plus others] Following accessibility guidelines for:
- using clear and consistent language (WCAG 1.0 Checkpoint 14.1), 
- separating content from presentation (WCAG 1.0 Checkpoint 3.3), 
- and using appropriate markup (WCAG 1.0 Checkpoint 3.1, 3.2) 
can reduce the cost of translating the Web site to other languages. [4]




> -----Original Message-----
> From: Henk Snetselaar [mailto:H.Snetselaar@bartimeus.nl] 
> Sent: Thursday, March 18, 2004 3:25 AM
> To: Andrew.Arch@nils.org.au; shawn@w3.org
> Subject: Re: additional request for technical & financial 
> factors -RE: DRAFT edits on BusCase - Policy
> 
> 
> Hi Shawn,
> 
> In the first moment I thought also that it was a additional 
> request, but because you did not yet alter the tech/finan 
> pages after out first proposals, I was afraid you did miss our work.
> 
> By going over the pages I have some more suggestions, but as 
> we all know, rereading even more times and by more people 
> will give more different suggestions. In many places there 
> were already specific application to the WCAG). My suggestion 
> are just additions to our former suggestions, no replacement. 
> Regards, Henk
> 
> ++++++++
> 
> Tech factors page
> 
> Reduce the size of each page served by defining presentation 
> in style sheets (which are only requested once per session), 
> rather than each page's HTML. (WCAG 1.0 Checkpoint 3.3) = 
> Reduce the size of each page served by defining presentation 
> in style sheets (which are only requested once per session), 
> rather than each page's HTML and by using markup  structure 
> rather than images. (WCAG 1.0 Checkpoint 3.3, 3.1)
> 
> - "Reduce site-wide style change time and effort" add also 3.1, 
> - "Reduce unwanted page downloading (and thus server 
> requests)" add also 13.6, 14.3, 
> - "Render stylized information across a wide range of 
> configurations" add also 3.3, 
> - "Allow users and user agents to request content" add also 3.5
> 
> 
> Financial factors page
> 
> Increases findability: 
> - By using meta data because some search engines use metadata 
> to index pages (WCAG 1.0 Checkpoint 13.2) [1]
> - By using alternative text for images since search engines 
> search for text strings and not for graphical information 
> (WCAG 1.0 Checkpoint 1.1, 1.3) [2]
> - By using text marked up as headings because some search 
> engines give higher weight to text marked up as headings 
> (WCAG 1.0 Checkpoint 3.5) [3] Increases usability:
> 
> Some accessibility guidelines make it easier to find the 
> right location or page for everyone, thus directly increase 
> usability, such as: 
> - consistent navigation (WCAG 1.0 Checkpoint 13.4); 
> - clear and understandable content (WCAG 1.0 Checkpoint 14.1);
> - clearl link text (WCAG 1.0 Checkpoint 13.1);  
> - good color contrast (WCAG 1.0 Checkpoint 2.2). 
> 
> Other accessibility guidelines can indirectly increase 
> usability, for example, by making Web pages load faster 
> *<link to soc page>
> 
> 
> Decreases the cost of translating
> Following accessibility guidelines for:
> - using clear and consistent language (WCAG 1.0 Checkpoint 14.1), 
> - separating content from presentation (WCAG 1.0 Checkpoint 3.3), 
> - and using appropriate markup (WCAG 1.0 Checkpoint 3.1, 3.2) 
> can reduce the cost of translating the Web site to other 
> languages. [4]
> +++++++++++++++++=
> 
> ++++++++++++++++++++++++++++++++++++++++
> H. Snetselaar
> Bartimeus Educational Institute for the Blind and Partially 
> Sighted Utrechtseweg 84, 3702 AD  Zeist, the Netherlands
> Tel: +31-(0)30-6982211 or +31(0)30-6982350
> Fax: +31-(0)30-6982388
> E-mail: H.Snetselaar@bartimeus.nl
> Website: www.bartimeus.nl and www.accessibility.nl
> Zie voor disclaimer (Read our disclaimer): 
> www.accessibility.nl/disclaimer.html 
> ++++++++++++++++++++++++++++++++++++++++
> 
> >>> "Shawn Lawton Henry" <shawn@w3.org> 03/17/04 11:41 PM >>>
> > From: Henk Snetselaar [mailto:H.Snetselaar@bartimeus.nl]
> > 
> > What you are asking in point 2 is done during  the face to face in 
> > Cannes, if I understand what you mean. At the least the proposed 
> > changes for Tech and Finance are not done in the document linked to 
> > your last mail to EOWG.
> > 
> > So is this an additional request to do it again, to review the Tech 
> > and Finance for links to WCAG checkpoints etc. or did you miss the 
> > e-mail we sent already.
> 
> Sorry I wasn't clear. This is an additional request. I did 
> get the e-mail from Cannes; however, I was hoping you and/or 
> Andrew could take another pass at this, per below:
> 
> > I spent quite a lot of time integrating the specific 
> checkpoints into 
> > the "Web Accessibility Benefits More Than People with Disabilities" 
> > section. First, I had to go into to WCAG to help match each 
> checkpoint 
> > number with the relevant wording (I don't quite have them all 
> > memorized :-). Then I found that some relevant checkpoints were 
> > missing, and so for each group I went through all of WCAG to see if 
> > there were additional checkpoints that we should be covering.
> > 
> > As a result, I have two requests of you:
> ...
> > 2. Could you go over the Technical and Financial pages in the next 
> > couple of days to:
> > 	- check if there are other WCAG checkpoints we should be listing
> > 	- make specific recommendations on how each WCAG
> > checkpoint is integrated into the documents.
> ... 
> 
> Specifically, I was hoping you could provide the WCAG 
> checkpoint references in a way that I can "cut and paste" the 
> text into the documents.
> 
> For example, in the e-mail on Social Factors from Cannes, you wrote:
> 	"Access for Older People - (WCAG 1.0 Checkpoint 3.4)"
> 
> I found other WCAG checkpoints that relate to issues for 
> older people and incorporated them into the document as follows:
> 
> "For example, many people with age-related visual 
> deterioration can benefit from:
> - sufficient contrast between foreground and background 
> colors (WCAG 1.0 Checkpoint 2.2)
> - text size defined as relative units (rather than absolute 
> units) so they can progressively increase the text size in a 
> regular site, as opposed to using a very differently designed 
> text-only site or a screen reader (WCAG 1.0 Checkpoint 3.4)
> - text and markup rather than images to convey information 
> (WCAG 1.0 Checkpoint 3.1)
> - text that does not blink or move (WCAG 1.0 Checkpoint 7.2, 7.3)
> 
> People with difficulty using the mouse benefit from:
> - device independence that lets them use the keyboard, rather 
> than having to use the mouse, for all Web site interaction 
> (WCAG 1.0 Checkpoint 6.4, 9.1, 9.2, 9.3, 9.4, 9.5) "
> 
> Let me know if you have further questions.
> 
> Thanks,
> 
> ~ Shawn
> 
> 
>

Received on Tuesday, 23 March 2004 21:01:32 UTC