Thanks. I searched the forum for "news 1.2" but didn't find a relevant link. Your support is greatly appreciated!

Hank

I see references to it everywhere in the site and forums but when I look for it in the downloads it doesn't seem to appear. The latest RC says that version 1.1 is included and to be careful about upgrading if you have 1.2 installed. Does it go by a different name?

Thanks


Hank

Yeah - based on PeeKay's response I did repost the question to the Theme's Design area. Re-wrote it 'slightly' but it is the same subject.

I thought I had replied back to you here already but I don't see my post so will re-state that the links you sent were fantastic. Spent several hours reading through them and have lots of good info about the concepts behind building websites that are standards-based and formatted to ensure everyone can access them.

Everyone's comments so far have been to the point and wonderful. The support I have seen here is more of a reason to choose XOOPS than almost anything else!

Thanks to everyone! Let's keeps this subjuect alive for awhile and see what comes of it.

Thanks again,

Hank

Wow!

What an excellent response. The links are great! I've already been reading on just the first link for over an hour ... Thanks so very much!


They also mention using the "em" function to control the size of fonts. I can see how setting a percentage variable could help control the size of the text on the screen. Fantastic... now all I have to do is figure out how to do so inside XOOPS.

Hank

I saw several threads that started dicussing whether XOOPS is/was/could be 508 Compliant. The threads ended about 6 months ago with folks finding it interesting but without any real answer at the time.

I am curious whether anyone continued attempting to build on the "accessibility" questions. I am trying to design a site for a Multiple Sclerosis support agency (I am NEWBIE web designer by definition for certain!) and have built the shell of it using a standard HTML template. But they need more that and I can see that XOOPS - if I spend the time necessary - could provide the interactive capability that they require.

Many of those with Multiple Sclerosis are afflicted with vision troubles and one of the most difficult areas for me so far is trying to determine how to create a method for the visitor to select their "Visual Experience" - Standard Text, Large Text, Larger Text, or Reader format. I don't necessarily need that many options but that is the concept.

I realize that the most likely answer is creating several copies of the CSS files - each with a larger font choice - and letting the visitor choose which set to when they log on. But I am also curious as to whether anyone else has built, or has considered building a site (or even better - a Theme) that implements this kind of capability?

Continuing on that vien... I am just concentrating on the visual (readability) at this point... When considering Accessible websites what other kinds of issues should I be looking at? The thoughts that cross my mind now are:

1. The Visually Impaired (see above...)
a. Impaired
b. Total blindness

2. Physically Impaired
a. Hearing
b. Limbs (missing or paralyzed)
c. Control - (tremors, etc.)

What kind of controls might be implemented to assist visitors with these other impairments? I may have thought of the problem but have not really considered any real solutions. Those who have hearing issues should not really have problems with the browsing but where aural alerts were being used they would have to be replaced or supplemented with visual keys.
Those who are blind usually have "Reading" software that can help them - but as discussed in earlier threads you have to pay attention to the ALT tags so that the reader program can tell them what button they are passing over. But is there a set of instructions anywhere (I'm just now thinking of this so will go look but am asking here to keep the flow going) that cover such items of concern?

Anyways, if anyone here has built themes addressing these kind of issues I would like to hear about them.
If you have seen sites that have these concepts being used please let me know.

I thank you in advance for your advice and comments.

Hank

Great Idea - will edit and repost the question there.
Thanks much!

The CSS method is all I can think of as well - and is probably the best answer. A bit more work perhaps but it should do the trick. I appreciate your feedback and hope none of the April Fool's day tricks got ya bad today.

Hank

I saw several threads that started dicussing whether XOOPS is/was/could be 508 Compliant. The threads ended about 6 months ago without any answer at the time.

I am curious whether anyone continued attempting to build on the "accessibility" questions. I am trying to design a site for a Multiple Sclerosis support agency (a NEWBIE by definition for certain!) and have built the shell of it using a standard HTML template. But they need more that and I can see that XOOPS - if I spend the time necessary - could provide the interactive capability that they require.

One of the most difficult areas for me so far is trying to determine how to create a method for the visitor to select their "Experience" - Standard, Large Text, Larger Text, or Reader format. That is just an idea .. I suspect I could create a link to swap CSS files for that kind of control but I really like the CMS/Portal layout of XOOPS and think that it will be a better fit.

So to state it clearly: I would like to provide a button on a XOOPS installation that flips to a selected "Visual" experience - changing font sizes up or down to accomodate those who might have problems reading the website content.

Anyone working this angle already? Did I just not read the FAQ's deeply enough to find an existing answer?

Thanks for your help in advance.

Hank