[Javascript] Accessibility (discussion)

[Terry Riegel]

Troy,

Do you use an iphone? The reason I ask is an iPhone does the things  
you describe but instead of keyboard control it uses gestures.

Terry

Sent from my iPhone

On Nov 18, 2008, at 11:50 PM, Troy III Ajnej <trojani2000 at hotmail.com>  
wrote:

>
>
> I mostly rely on existing JS - DOM - CSS browser capabilities.
>
>
> When I say accessibility, I think of people with disabilities.
>
>
> Few of important improvements would most certainly be keyboard
>
> navigation, for one;
>
> Font size scalability for second, and so one...
>
>
> Probably high-contrast style scheme available via js - css  
> collaboration
>
> on the fly switch.
>
>
> I had (relatively) recently come to an idea of making a page that
>
> will fit on all screen resolutions without breaking the layout design.
>
> (It required a completely different coding method)
>
>
> Immediately after that I came to another enhancement possibility idea
>
> -to make independent content sections independently resize-able, so
>
> the user can smoothly zoom in and out on the parts of content of his
>
> interest with simple keyboard control.
>
>
> Further enhancement I thought of, was making these sections tab-able
>
> and to receive focus which can be used to further enhance contrast
>
> through css, so the user will know where he's at more easily. etc.
>
>
> All nice and sound; encapsulated script and new size-styling aproach
>
> working on all pages.
>
>
> When all of this was done it was natural to come to another idea:
>
> to dynamically adjust the page layout on window drag or resize also.
>
>
> But there were issues with some browsers, especially those breaking
>
> keyboard conventions and some other minor differences in dom handling.
>
>
> This is as far as I got by now, but I still think that there are  
> plenty
>
> of ways that could enhance the user experience relying on other better
>
> and fresh ideas.
>
>
> So far, I think that having a B&W or high contrast grayscale scheme
>
> available to switch to, is an advance. Dynamic font-size scalability &
>
> 'reset' is a great plus. A 'tab' into a true content section  
> disregarding
>
> addons and third party adverts in the process is a relief to.
>
>
> I also thought of and added a navigational link display monitor, using
>
> banner area connected to events like mouseover and focus.
>
>
> And thisi is all I'm currently aware to deal with when accessibility  
> comes
>
> in question.
>
>
> Any other accessibility reqiurements you can reacall or think of would
>
> be appreciated for all interested on expanding the accessibility  
> ability
>
> of their web scripting & design.
>
> Regards
> ~~~ 
> ~~~ 
> ~~~ 
> ~~~ 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                        
> Troy III                          progressive art enterprise  
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  > Date: Mon, 17 Nov 2008  
> 16:48:36 -0500> From: mdougherty at pbp.com> To: javascript at lists.evolt.org 
> > Subject: Re: [Javascript] Accessibility (discussion)> > On Mon,  
> Nov 17, 2008 at 5:23 AM, Troy III Ajnej <trojani2000 at hotmail.com>  
> wrote:> >> > ...so we can exchange some of our thoughts, stands, and  
> ideas about web accessibility issues and where does JavaScript in  
> collaboration with DOM and CSS manipulations stand when dealing with  
> this consideration field.Is it possible that JavaScript can do more,  
> or even better than any browser has ever done, or is doing right now  
> in dealing with accessibility issues atop currently served web  
> content on the internet.Regards @all> > Javascript can certainly do  
> more as a multi-purpose tool. My concern> is the way in which this  
> tool is used. I've seen too many people> enter ##javascript looking  
> to build an "ajax site" - with no concept> of progressive  
> enhancement or graceful degradation of features. I> think it would  
> be a big win if people would learn to properly separate> markup/ 
> style/behavior. There are many excuses; most are indefensible> once  
> the new philosophy is adopted. I don't know how to implement,> but  
> another improvement might be a browser add-on that clearly>  
> identifies tutorials as out-of-date or plain bad advice. Something>  
> like anti-phishing checks for would-be developers to be warned away>  
> from IE-proprietary code and antiquated markup practices. If old>  
> habits are hard to break, "the internet" should stop teaching bad>  
> habits to new developers.> > that's all for now, I'm starting to  
> feel a full-blown rant coming on. :)>  
> _______________________________________________> Javascript mailing  
> list> Javascript at lists.evolt.org> http://lists.evolt.org/mailman/listinfo/javascript
> _________________________________________________________________
> Get more done, have more fun, and stay more connected with Windows  
> Mobile®.
> http://clk.atdmt.com/MRT/go/119642556/direct/01/
> _______________________________________________
> Javascript mailing list
> Javascript at lists.evolt.org
> http://lists.evolt.org/mailman/listinfo/javascript