- From: Charmane K. Corcoran <corcora1@msu.edu>
- Date: Fri, 2 Jul 2004 14:59:06 -0400
- To: public-wai-eo-site@w3.org
Not so concerned about CSS, more concerned about them giving a flat image file for the design. I have a segment of the university here that believes that is THE only way to design a web page. Then, you figure out later if it is going to work. Maybe I read it wrong. I am mainly concerned that they can make the what ever design accessible and some designs just can't be. I have had to fight through several battles over this approach to design and how it can be a problem. I just want to make sure we are aware of the potential issue. I am not sure how you can word it to avoid that pitfall without requiring accessible code so.... As long as you are convinced that this isn't setting us up for a problem, I will defer to your discretion. Charmane > >> >While we prefer comps in valid, accessible XHTML and CSS, we >> understand >> >that it is often not an effective use of time and effort to >> make early >> >comps fully meet standards and work well on multiple configurations. >> Therefore, at this stage we will accept comps as graphics files, >> preferably PNG, >> >> In my experience, often when someone provides a design in graphic >> format, it may or may not be able to translate into an accessible >> format. I have a concern about getting a design in graphic format. >> If it is in xhtml, at least we have an idea if it can be easily made >> accessible or not. If it is in a graphic, it will take a lot more >> thought. I would vote that it has to be in code and not in graphic >> format. They can put in graphic AND code but not just graphic. That >> could be a disaster waiting to happen, in my opinion. You could end >> up approving a design that is cannot be converted to accessible code. >> I am not familiar with PNG so I can't address that type of graphic >> but the standard flat graphics have posed significant problems in the >> past. Just raising the flag to avoid a potential problem. > >(First, for clarifiction: the pages I provided are in XHTML. We would >need CSS to determine if the design is feasible.) > >Some of the visual design volunteers are likely not CSS experts. We have >another volunteer to help with the CSS. We will be careful not to >approve any design until it has been proven do-able. > >> 2. Under TIMELINE >> We are preceding with visual design now in order to >> >> should be "proceeding" > >Good catch! Thanks! > >~ Shawn -- MSU: Advancing Knowledge. Transforming Lives. Libraries, Computing & Technology: Connecting People and Information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Have a Productive Day! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Charmane K. Corcoran Information & Accessibility Specialist Michigan State University Client Advocacy Office 316A Computer Center East Lansing MI 48824 E-mail: corcora1@msu.edu Phone: Dept. Office - 517/353-4856 Direct/Vmail - 517/355-4500 Ext. 244 FAX: Office: 517/355-0141 HmPg: http://www.msu.edu/~corcora1/
Received on Friday, 2 July 2004 14:59:09 UTC