Accessibility in your theme / template - How to

ClaudioRomeo wrote: trogladyle wrote:

:focus {
color: #000000!important;
}

and

input:focus {
color: #000000!important;
}

Maybe you have not considered that you are dealing with link.
For example, in my custom.css file of TCCK I inserted:

Code:

/* selected link */ a:active { color: #000000; background-color: #ffff00; } /* focused link */ a:focus { color: #000000; background-color: #ffff00; border: dotted 1px #000000; }

I don't know if it can help. I hope so.

Another important point (in my opinion) is related to the effort to provide a consistent developing environment for accessible websites.
I believe there is a need for integration between developers to avoid overlapping solutions and to provide consistent solutions.
For example, the Pro version of JCE offers powerful and easy tools to achieve great results. Nevertheless, sometimes it is difficult to decide whether these results should be achieved with JCE, Regular Labs extensions, JoomlaCK extensions or Template Creator.
Aiming at the accessibility of websites, an integration between Template Creator CK, Regular Labs and JCE could achieve great results without too much effort.
Saying it is easy, doing it is difficult, I know.
But would you consider collaborating with other developers?

I tried your code Claudio, but that didn't change the border (currently in blue), but only put a yellow bar behind SOME items. I just want to change the blue border.

ced1870 wrote:

Saying it is easy, doing it is difficult, I know.
But would you consider collaborating with other developers?

that is right. To be honest, I have already contacted some developpers for few small things, this is very difficult to get a real participation
I'm opened to collaboration, if something could be done. But for sure I will not spend my time trying to contact and convince the others
CEd

I'm happy to work with you as much as I'm able Ced. Really appreciate your products and your support, and I'm happy to help you make them better. As I mentioned, I've done a fair amount of reading on the whole accessibility issue. Yep, it can be a minefield, but, if one follows WCAG 2.0 then the rules are REASONABLY simple. There's just a LOT of rules!!

Let me know how I can help.

thank you
I have started to read your document
by my side I think that the most important missing feature in Maximenu CK is the keyboard navigation, but this is hard to implement for megamenus

I will try to put an online test website just with Maximenu CK, so that we can check together the accessibility. Would this help ?

PS : for your blue border issue, I don't know what it is
please give us an url to check what you mean, and tell me where it occurs and how

I have put a website here
wcag.ced1870.fr/

added Maximenu CK, just fixed few small issues i n Protostar and
W3C check : OK
validator.w3.org/nu/?doc=http%3A%2F%2Fwcag.ced1870.fr%2F
WCAG check : OK
webaccessibility.com
achecker.ca/checker/index.php
Color contrast : OK
color.a11y.com/Contrast/

so what's next now ?

ced1870 wrote: PS : for your blue border issue, I don't know what it is please give us an url to check what you mean, and tell me where it occurs and how

www.ckdev.info/keane - this is a new site I'm doing right now, but every site I've tried behaves the same. So, when you go there, before using the mouse on anything, do what a keyboard only user would do, use the Tab key. This does correctly tab through linked items, but that's where the border appears. Image attached - this is after the first Tab key press.