If the idea were applied to small screens, measures would have to be taken to ensure that it would still work on smart phones, perhaps by taking the actual desktop resolution to determine what the type of device it is. JavaScript certainly provides facilities to access device names, browser resolution and screen resolution, so this shouldn't be too much of an issue.
It seems like a noble cause, Steve, and I'm sure the Google Code team will work something out. I'm just a little concerned that like subtitles, people who don't necessarily need these accessibility changes won't want them. -Keanen On Thu, Sep 2, 2010 at 2:01 AM, Steve Lee <[email protected]> wrote: > On 1 September 2010 21:44, Jason Robbins <[email protected]> wrote: > > Thanks for choosing Google Project Hosting and thanks highlighting > > these accessibility problems. We do take accessibility seriously and > > try to make the site accessible, but sometimes mistakes slip through. > > I think the items you pointed out are mainly oversights that we can > > correct without much effort. I've entered this issue to track the > > work to be done: > > http://code.google.com/p/support/issues/detail?id=4368 > > Jason, > > thanks very much for a positive response. It is very much appreciated. > > On 1 September 2010 23:45, Jason Robbins <[email protected]> wrote: > > I'm glad that you like the way that it looks now! Changes will > > certainly be made with care. > > > > I would try to keep everything very close to how you see it now, and > > only have the layout flow differently on small screens. In my > > experience, most accessibility guidelines actually help improve > > usability for everyone. And, a more fluid layout could also help with > > mobile devices, which is also something that Google Project Hosting > > could do better. > > We had to slip one contentious item in there ;-) The reflow issue is > useful on small screens and for those who use magnifiers, but not > everyone agrees about the best approach. > > Certainly the idea of accessibility is to improve the experience for > everyone, not make it worse for anyone. As Jason says you often get > benefits from increasing accessibility. An obvious one is SEO as > spiders are effectively blind users. Others include small screens or > times when you can't look at a screen. That said the big benefit here > will be the potential to increase a project community by removing > small barriers. > > I'm sure we can discuss the flow issue more here or on the ticket, we > have people who are clued up on the issues and sensitive to general > usability needs. > > Cheers > > Steve > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-code-hosting%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
