Showing posts with label absolute. Show all posts
Showing posts with label absolute. Show all posts

Monday, March 26, 2012

Accessibility and Atlas

This Atlas stuff looks interesting and will make my job a whole lot easier if I can avoid fiddling with pesky Javacript!

But, my absolute priority is Accessibility. All my sites must be Accessible, which includes the content management side, and I prefer to be AAA standard.

My question is: As ATLAS is run inside ASP.NET 2.0, can I assume that I will get XHTML 1.0 Strict output? Also, is the ATLAS model accessible? ie. if JavaScript does not exist, is the user-interface still usable using alternative means (I don't mind implementing complex techniques like drag-n-drop in an alternative manner, though) and what if the user agent does not understand CSS, or uses a different CSS media, such as "mobile", "tv" or "embossed"?We're still working on accessibility. The controls are built to comply with accessibility norms by default. If there is no javascript at all, you're responsible for building your own alternative representation, Atlas can't help you as it entirely relies on Javascript. About CSS, I don't understand what the problem is: Atlas is very neutral as far as CSS is concerned so it's exactly as if you were using plain HTML.
Thanks for your response.

By "We're still working on it", do you mean it will be accessible in the final release?

Also, as regards CSS, I am not quite ready to implement richer controls in my project and have so far held off downloading anything. I didn't know the "richness" of the controls. So far so good, though.
Yes, we're very committed to accessibility and it will improve from release to release until the final one.

Wednesday, March 21, 2012

a issue in <atlas:UpdatePanel>:do not work with .css file in format of absolute path

i found a issue in <atlas:UpdatePanel> control, under <ContentTemplate> control, we usually put lots of html control or server control, withclass attribute orcssclass attribute.

if the .css file is in a format ofabsolute path like below

<link type="text/css" rel="stylesheet" href="/myWeb/css/RichClientUI.css"/
then the partial render html tagcan not apply style setting defined in .css file.

if the .css file is in a format of relative path like below

<link type="text/css" rel="stylesheet" href="../../css/RichClientUI.css"/>

then the partial render html tagcan apply style setting defined in .css file.

i think this should a bug. coz in web design, we usually use a method like <%=Util.GetApplicationPath%> to get a real web app path against a IIS Website, so that we can deploy our web app under awebsite or avirtual directory without changing any resource (e.g css/js/gif/jpg/etc.) path.-->

you should try to use the "~" character in your path

for example:
<img src="http://pics.10026.com/?src=~/Images/myimage.gif" runat="server"> this would start the path at your application root for the website or virtual directory then take you to the images folder then of course display your image...


the "~" character is very useful, but it has a restriction when use. coz it always renderrelative web application root path based onthe same web server. in web farm condition, we usually require absolute resource path. further, the absolute resource path maybe dynamically generated according some business logic, so this is why we need a static method like <%=Util.GetApplicationPath()%> to getruntime absolute resource path.


change the <%=Util.GetApplicationPath()%> to<%# Util.GetApplicationPath()%> and I think you will get your desired results...I ran into the same issue with a project I was working ...