I have seen many a conversation around here dealing with ADA 508 compliance with DotNETNuke and have learned that with the advent of .NET Framework 4, things are better.  What i am curious about though, is if there is a way for blind and visually impaired users to edit and set up modules easily?  For folks like me (I'm as blind as a bat myself and do not use the mouse), doing this is very difficult, and seemingly impossible, so if there's a workaround that does not involve hovering with the mouse, I'd be glad to hear it.  What I have the most trouble with is getting access to edit the modules after they have been placed on the page; there should be an alternative means of accessing the toolbar other than hovering over the area (for instance, allow for a certain keystroke to accomplish the same task, or an alternative link; that's ADA 508, after all.  Also, some of the other administrative links are harder to get to than I'd like them to be using the keyboard, for instance, the link for pages, if you click it via pressing enter instead of a literal double click, what happens, is it just seemingly sits there until I simulate the  click with my screen reader, and even that doesn't work half of the time.)  I am especially looking for feedback and responses from DNN core development staff and community teams.  I can and will assist you in getting DNN up to par with accessibility and ensuring that all aspects of the CMS, (front and back end), are accessible and useable by blind people.  I'm no coder (yet), but I can give advice based on common web standards and compliance with ADA section 508.  I'd like to rebuild my web site based on DNN, simply because this system has so much to offer, and so I'd appreciate any responses that you may have.  My Version of DNN is DNN 6, and my Operating system is Windows 7 and Windows server 2008 R2 depending on my situation; using IE 9.0 as the browser.  Thank you very much in advance.  I appreciate wherever this conversation goes, and I'm sure it will go far.          

I'm not actually talking about that; I'm talking about the fact that seemingly by default, the administration panel is difficult to use for a blind person.  I don't know what you mean by "mouse     over event speech wise".  And I'm not a developer, so no, I cannot yet build my own modules, though I'm learning.  For your information, I have chosen the blank web site template, so what I'm trying to do is to add my own content.  What I find very difficult is for instance, when trying to add a new page, I click the pages link, and the browser just sits there as if I didn't do anything, though what I did is pressed enter on the link (same as a double left-click).  Pressing enter should have the same affect as using the mouse and that's what I'm saying here.  It doesn't in this situation.  And then once you have a module added, for instance, say the text/HTML module on a page, what will happen is that you'll get a message saying "hover here, then use the toolbar to edit content" or something along those lines.  That, being blind and unable to use the physical mouse, I cannot do, and so I need an alternative.  And not to mention, how will changing the skin do any good at this point since the site's not even half built?  Are there some big-time DNN Fundamentals I'm missing here?  All responses are welcome.      

Oh.  Jees.  I love the idea of the container logic being altered like that.  Thanks; that's probably what I'm going to need to do.  But the biggest thing, and I suggested it in the general contact/feedback area not realizing that I am allowed on the support.dotnetnuke.com page to make certain types of requests, so feel free to move it over there, is the use of regular links to access the action menus instead of mouse overs, and regular comboboxes/listboxes for module additions instead of those weird edit boxes for the module selections that you can't scroll through.  The access key thingo was kind of just an example, and honestly, I shouldn't have said it considering I don't use those access keys that much; favouring double clicking links more instead.