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. Thanks, jason! -- Google me at http://google.com/profiles/jrobbins On Wed, Sep 1, 2010 at 3:14 PM, Keanen Shaw <[email protected]> wrote: > Vertical stacking and page scaling would ruin the layout we're all used to. > Google takes accessibility very seriously, but I as a Google Code user > believe that much of this would disrupt the experience. > > -Keanen > > On Wed, Sep 1, 2010 at 12:44 PM, Jason Robbins <[email protected]> wrote: >> >> Hi Steve, >> >> 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 >> You may want to star that issue so that you receive notification of >> comments and updates. >> >> Good luck with your students' projects and feel free to enter >> /p/support issues for any other problems that you find. >> >> Thanks, >> jason! >> >> On Wed, Sep 1, 2010 at 12:32 PM, Steve Lee <[email protected]> >> wrote: >> > Hi >> > >> > At ProjectPossibility.org we get students to work on innovative open >> > source accessibility projects and we selected Google Code hosting as >> > being the most suitable platform to host the project development. >> > >> > However after a quick check we found a number of fairly basic >> > accessibility issues which we feel really need fixing so all users can >> > access the projects. This will help reduce barriers to community >> > engagement and allow contributions by people who need accessibility, >> > which is obviously important for our projects. >> > >> > We are keen to see Google code become accessible for these reasons, >> > otherwise we will need to find something else. We are naturally happy >> > to help out and there are others in the accessibility community who >> > may be willing to chip in. Perhaps Charles and T.V. in the Google >> > accessibility group would chip in? While the issues are fairly basic >> > their AxsJAX technology could add great accessibility features, as it >> > did to Google Reader. >> > >> > The following is the list of issues found by a Project:Possibility >> > team member. It is not exhaustive, rather the results of a quick >> > audit. >> > >> > Regards >> > >> > -- >> > Steve Lee >> > >> > Project:Possibility >> > Full Measure - open source accessibility - http://fullmeasure.co.uk >> > >> > >> > GoogleCode Accessibility Review >> > >> > Common Issues >> > >> > 1. Better Alt tag for project logo >> > 2. No “Skip Nav” or “Skip to Content” link. >> > 3. Label missing from Search Projects text field. >> > 4. Does not gracefully collapse horizontally >> > * The pages should linearize vertically as it is collapsed >> > horizontally >> > * Avoid fixed width pages. >> > * Avoid using PX, instead us EM. >> > * Use Divs instead of tables for layout >> > >> > Project Home >> > Summary Section >> > >> > * See Common Issues 1-4 >> > * Incorrect read order (Right column reads before left column) >> > * Some images lack Alt or LongDesc tag >> > * Improperly used headers (H2’s & H3’s but no H1’s) >> > >> > Updates >> > >> > * See Common Issues 1-4 >> > * Improperly used headers (H4’s but no H1’s, H2’s or H3’s) >> > >> > People >> > >> > * See Common Issues 1-4 >> > >> > Downloads >> > >> > * See Common Issues 1-4 >> > * Some images lack Alt or LongDesc tag >> > * Inaccessible drop-down menus (pop-up/mouse over) >> > >> > Wiki >> > >> > * See Common Issues 1-4 >> > * Some images lack Alt or LongDesc tag >> > * Inaccessible drop-down menus (pop-up/mouse over) >> > >> > Issues >> > >> > * See Common Issues 1-4 >> > * Some images lack Alt or LongDesc tag >> > * Inaccessible drop-down menus (pop-up/mouse over) >> > >> > Source >> > >> > * See Common Issues 1-4 >> > * Improperly used headers (H4’s but no H1’s, H2’s or H3’s) >> > >> > -- >> > 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. >> > >> > >> >> -- >> 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. >> > > -- > 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. > -- 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.
