CMS and accessibility

Wednesday, November 19, 2003

I am going to make some different projects compliant with accessibility issues, like Scoilnet for example.

Because I use dScribe as base for CMS, I think it will quite straightforward to read the content and apply a template.

So what I intend to do is to have an 'Accessible version' on top each page of Scoilnet, read the public property PageTitle of the dScribe control embedded in the page, apply an accessible version template.

What I am looking for now is some ideas for the template. I will surely work as abase with the FrontEnd accessible template (site offline for the moment), because I like the way that they provide a text-only version keeping however a sense of design. Sad that their site is down for the moment, but what they do is that they create the content in boxes, with some nice borders, so it gives a sense of unity.
It's not just plain text.

If you have any ideas let me know.

Instead of doing two versions (templates) I'd recomend doing one and doing it right. Using HTML for the semantic content and CSS for the design results in a really accessible site.

Oddur Magnusson - Wednesday, November 19, 2003 3:35:00 PM

Oddur, the idea is to create only one version for the accessible part on the fly.

Yes surely CSS is the way I would like to go, but screen readers are not always good with CSS.

Paschal - Wednesday, November 19, 2003 3:39:00 PM

That's the whole reason, the screen readers ignore the CSS link and just read the content.

That's why tableless-html + css for design is perfect for screen readers !

Oddur Magnusson - Wednesday, November 19, 2003 4:56:00 PM

3 Comments