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.
No comments:
Post a Comment