Difference between revisions of "Developer Space/Resources"
(→Material Collections) |
|||
| Line 13: | Line 13: | ||
*[http://wiki.fluidproject.org/display/fluid/Accessibility+Resources Fluid Wiki Accessibility Resources] | *[http://wiki.fluidproject.org/display/fluid/Accessibility+Resources Fluid Wiki Accessibility Resources] | ||
| − | [HID Emulation Device] | + | [[HID Emulation Device]] |
=== Topic Specific === | === Topic Specific === | ||
Revision as of 17:15, 4 December 2014
Material Collections
- 100 Killer Web Accessibility Resources: Blogs, Forums and Tutorials
- web2access.org.uk .
- a11yproject.
- Section 508
- dmoz
- BRL on freecat.org
- Fluid Wiki Accessibility Resources
Topic Specific
Maps
Testing
see Developer Space Components#Web Accessibility Testing
Guidelines and Handbooks
Learning
Gaming
Cultural and Language
Media HowTos
Forums and Q&As
- Forum for AT in Arabic world
- Stackoverflow
- UX@Stackexchange
- WebAim Discussion/Help
- Epub Accessibility Forum
- FreeLists
- Google Groups
- W3C Community Groups
- Google: Developer Resource Links , Configuring Google Product
More Blogs & News
- Ergohacks blog on accessibility
- Engadget [1] [2] [3] [4]
- TechCrunch [5] [6] [7]
- Accessible In-Sight Blog
Misc
- Doug Schepers on Invisible Visualization @ OpenViz Conf
- Retrofitted accessibility using "Active Browsing" via userscripts http://userscripts.org/scripts/search?q=accessibility&submit=Search
- wouldn't that be sth. for crowd sourced accessibility: http://platypus.mozdev.org/ , user cannot view web site and asks for help, other user does interactive cleanup. Contacted Scott: currently GPL but willing to relicence
- Also good for cleanups: http://sixserv.org/2011/02/12/feedability-nodejs-feed-proxy-with-readability/
Contribute
!!!!Please add your favourite resources!!!!
The mailing list for this topic is DSpace@lists.gpii.net.
You do not need to be on the team to submit something: send an email to mailto:dspace@lists.gpii.net.
Team and Leads
The following people have signed on to help develop this area. Anyone who is willing to work on this is welcome to do so. Contact one of the team leads
- User:GreggVan
- User:Till
- User:Mad
- User:Kostas Votis
- --<your name here>
About Resources on the Developer Space
See also Developers Space
The Goal of the developer space is to create a central point for finding resource information and people to assist in creating more accessible:
- content
- tools
- applications
- features
One important area of the Developer Space will be focused on tools and resources for web developers. People increasingly rely on the web as an essential medium for working, learning, and expressing themselves. Over the past decade, web applications have become more sophisticated, supporting a level of interactivity and complexity that was previously only available on proprietary desktop platforms. The web (and its associated standards of HTML, CSS, and JavaScript) has now become a viable platform for developing applications that can work across a variety of operating systems and devices. No longer limited to just the browser, web technologies are also now used to develop sophisticated mobile and desktop applications as well.
The Developer Space will provide web designers and developers with pointers to a variety of accessible and flexible components from across the web. These components will be enhanced to support user preferences and personalization out of the box, requiring less effort on the part of developers to make their applications compatible with the GPII.
As part of this work, Infusion and other tools will continue to grow to support model-based and visual programming environments that will help close the gap between developers and end-users, providing a means for users to influence and participate within the design, development and testing process more actively.
For specific components refer to Developer Space/Components
