Difference between revisions of "Developer Space/Resources"

From wiki.gpii
Jump to: navigation, search
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
 
<div style="float:right; margin: 0em 1em 0em 1em;">
 
<div style="float:right; margin: 0em 1em 0em 1em;">
 
__TOC__
 
__TOC__
 
 
</div>
 
</div>
 
== Material Collections ==
 
== Material Collections ==
  
 
*'''[http://whdb.com/blog/2008/100-killer-web-accessibility-resources-blogs-forums-and-tutorials/ 100 Killer Web Accessibility Resources: Blogs, Forums and Tutorials]'''
 
*'''[http://whdb.com/blog/2008/100-killer-web-accessibility-resources-blogs-forums-and-tutorials/ 100 Killer Web Accessibility Resources: Blogs, Forums and Tutorials]'''
*[http://www.web2access.org.uk web2access.org.uk ].
+
*[http://www.web2access.org.uk web2access.org.uk] .
 
*[http://a11yproject.com/resources.html a11yproject].
 
*[http://a11yproject.com/resources.html a11yproject].
 
*[http://www.section508.gov/technology-tools Section 508]
 
*[http://www.section508.gov/technology-tools Section 508]
Line 18: Line 18:
 
*[http://trace.wisc.edu/resources/ TRACE resources]
 
*[http://trace.wisc.edu/resources/ TRACE resources]
 
*[http://g3ict.org/resource_center G3ICT resource center] e.g. with [http://g3ict.org/resource_center/publications_and_reports curated publications and reports]  
 
*[http://g3ict.org/resource_center G3ICT resource center] e.g. with [http://g3ict.org/resource_center/publications_and_reports curated publications and reports]  
 +
*[https://github.com/brunopulis/awesome-a11y Awesome A11y]
 +
*[https://github.com/search?o=desc&p=1&q=a11y&s=stars&type=Repositories Github A11y] and [https://github.com/search?o=desc&q=accessibility&s=stars&type=Repositories&utf8=%E2%9C%93 Accessibility]
  
  
Line 31: Line 33:
  
 
==== Text to speech (TTS) ====
 
==== Text to speech (TTS) ====
 +
* http://www.oatsoft.org/Software/Software/by-category/Repository/Function/TextToSpeech http://www.findbestopensource.com/tagged/text-to-speech
  
http://www.oatsoft.org/Software/Software/by-category/Repository/Function/TextToSpeech
+
==== Science ====
http://www.findbestopensource.com/tagged/text-to-speech
+
* http://www.access2science.com/
  
 
==== Testing ====
 
==== Testing ====
 
+
* [https://www.w3.org/wiki/Accessibility_testing W3C a11y testing]
see [[Developer Space Components#Web Accessibility Testing]]
+
* [http://shashikantjagtap.net/tag/accessibility/ shashikant jagtap's blog on testing]
 +
see [[Category_talk:Web_Accessibility_Components#Web_Accessibility_Testing]]
  
 
== Guidelines and Handbooks ==
 
== Guidelines and Handbooks ==
Line 48: Line 52:
 
** [http://raisingthefloor.org/content/cognitive-language-and-learning-disabilities Cognitive, Language, Learning Disabilities & Low Literacy]
 
** [http://raisingthefloor.org/content/cognitive-language-and-learning-disabilities Cognitive, Language, Learning Disabilities & Low Literacy]
 
* [http://www.w3.org/WAI/users/Overview.html W3C WAI Overview] & [http://www.w3.org/WAI/guid-tech.html Guidelines]
 
* [http://www.w3.org/WAI/users/Overview.html W3C WAI Overview] & [http://www.w3.org/WAI/guid-tech.html Guidelines]
 +
* [https://github.com/UKHomeOffice/posters/tree/master/accessibility UKHomeOffice Posters]
  
 
=== Learning ===
 
=== Learning ===
Line 67: Line 72:
 
**[[Platform for AT in Arabic world|Platform for developing-adapting AT for Arabic world]]
 
**[[Platform for AT in Arabic world|Platform for developing-adapting AT for Arabic world]]
 
**Resources
 
**Resources
***[http://madaportal.org/ http://madaportal.org/]
+
***http://madaportal.org/
  
  
Line 93: Line 98:
  
 
*Forum for AT in Arabic world
 
*Forum for AT in Arabic world
**[http://madaportal.org/ http://madaportal.org/]
+
**http://madaportal.org/
 
*Stackoverflow
 
*Stackoverflow
**[http://stackoverflow.com/questions/tagged/accessibility-api http://stackoverflow.com/questions/tagged/accessibility-api]
+
**http://stackoverflow.com/questions/tagged/accessibility-api
**[http://stackoverflow.com/questions/tagged/uiaccessibility http://stackoverflow.com/questions/tagged/uiaccessibility]
+
**http://stackoverflow.com/questions/tagged/uiaccessibility
**[http://stackoverflow.com/questions/tagged/accessibility http://stackoverflow.com/questions/tagged/accessibility]
+
**http://stackoverflow.com/questions/tagged/accessibility
 
*[http://ux.stackexchange.com/questions/tagged/accessibility UX@Stackexchange]
 
*[http://ux.stackexchange.com/questions/tagged/accessibility UX@Stackexchange]
 
*[http://webaim.org/discussion/ WebAim Discussion/Help]
 
*[http://webaim.org/discussion/ WebAim Discussion/Help]
Line 120: Line 125:
 
***[http://www.w3.org/community/accessibilityindia India]
 
***[http://www.w3.org/community/accessibilityindia India]
 
***[http://www.w3.org/community/cnwa China]
 
***[http://www.w3.org/community/cnwa China]
*Google: [http://www.google.com/accessibility/building/ Developer Resource Links ], [http://www.google.com/accessibility/products/ Configuring Google Product]
+
*Google: [http://www.google.com/accessibility/building/ Developer Resource Links] , [http://www.google.com/accessibility/products/ Configuring Google Product]
  
  
Line 126: Line 131:
 
== Working Groups ==
 
== Working Groups ==
 
* [http://www.w3.org/WAI/groups W3C Web Accessibility Initiative groups]
 
* [http://www.w3.org/WAI/groups W3C Web Accessibility Initiative groups]
 +
* [https://www.w3.org/WAI/PF/cognitive-a11y-tf/ Cognitive and Learning Disabilities Accessibility Task Force (Cognitive A11Y TF)] - Creating SCs that will appear in next WCAG release
  
 
== Research and recommendations ==
 
== Research and recommendations ==
  
*[http://www.w3.org/TR/2015/WD-coga-user-research-20150115/ Cognitive Accessibility User Research, W3C coga task force]
+
===  W3C coga task force ===
 +
*[http://www.w3.org/TR/2015/WD-coga-user-research-20150115/ Cognitive Accessibility User Research]
 +
*[https://rawgit.com/w3c/coga/master/issue-papers/ Issue Papers]
 +
*[https://rawgit.com/w3c/coga/master/techniques/index.html Authoring Techniques]
 +
*[https://rawgit.com/w3c/coga/master/gap-analysis/table.html Gap Analysis - Tables of User Needs]
 +
*[https://github.com/w3c/wcag21/issues?page=2&q=is%3Aissue+is%3Aopen+label%3ACOGA success criteria proposals for WCAG 2.1]
 +
*[https://w3c.github.io/personalization-semantics/ Semantics for personalization]
  
 
== More Blogs & News ==
 
== More Blogs & News ==
 +
 
*[http://www.usabilitymatters.com/?s=accessibility Usability Matters on Accessibility]
 
*[http://www.usabilitymatters.com/?s=accessibility Usability Matters on Accessibility]
 +
*[http://assistivetek.blogspot.de/ Assistive Technology Blog]
 
*[https://www.marcozehe.de/ Marco's Accessibility Blog]
 
*[https://www.marcozehe.de/ Marco's Accessibility Blog]
 
*[http://ergohacks.com/?s=accessibility Ergohacks blog on accessibility]
 
*[http://ergohacks.com/?s=accessibility Ergohacks blog on accessibility]
Line 141: Line 155:
 
*[http://g3ict.org/resource_center/bloggers G3ICT Bloggers] & [http://g3ict.org/_expert_zones Experts]
 
*[http://g3ict.org/resource_center/bloggers G3ICT Bloggers] & [http://g3ict.org/_expert_zones Experts]
 
*[http://blogs.adobe.com/accessibility/ Adobe Accessibility Blog]
 
*[http://blogs.adobe.com/accessibility/ Adobe Accessibility Blog]
 +
*[http://a11ywins.tumblr.com/ Accessibility Wins]
  
 
== Misc ==
 
== Misc ==
  
 +
*[https://material.google.com/usability/accessibility.html Google Material Design Accessibility Guide]
 
*[http://www.youtube.com/watch?v=f4P6JsAKrDM Doug Schepers on Invisible Visualization @ OpenViz Conf]
 
*[http://www.youtube.com/watch?v=f4P6JsAKrDM Doug Schepers on Invisible Visualization @ OpenViz Conf]
 
*Retrofitted accessibility using [http://mozdev.org/pipermail/greasemonkey/attachments/20050406/ab058140/IMSA2001.pdf "Active Browsing"] via userscripts [http://userscripts.org/scripts/search?q=accessibility&submit=Search http://userscripts.org/scripts/search?q=accessibility&amp;submit=Search]
 
*Retrofitted accessibility using [http://mozdev.org/pipermail/greasemonkey/attachments/20050406/ab058140/IMSA2001.pdf "Active Browsing"] via userscripts [http://userscripts.org/scripts/search?q=accessibility&submit=Search http://userscripts.org/scripts/search?q=accessibility&amp;submit=Search]
**wouldn't that be sth. for crowd sourced assistance on demand: [http://platypus.mozdev.org/ 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
+
**wouldn't that be sth. for crowd sourced assistance on demand: 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/ http://sixserv.org/2011/02/12/feedability-nodejs-feed-proxy-with-readability/]
+
**Also good for cleanups: http://sixserv.org/2011/02/12/feedability-nodejs-feed-proxy-with-readability/
  
 
== Contribute ==
 
== Contribute ==
Line 155: Line 171:
 
The mailing list for this topic is [http://lists.gpii.net/cgi-bin/mailman/listinfo/dspace DSpace@lists.gpii.net].
 
The mailing list for this topic is [http://lists.gpii.net/cgi-bin/mailman/listinfo/dspace 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 mailto: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 ==
 
== Team and Leads ==
Line 178: Line 194:
 
*features
 
*features
  
<br/>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.
+
<br />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.
 
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.

Latest revision as of 01:17, 31 January 2017

Material Collections


Topic Specific

Computer Vision

Maps

Text to speech (TTS)

Science

Testing

see Category_talk:Web_Accessibility_Components#Web_Accessibility_Testing

Guidelines and Handbooks

Learning

Gaming

Mobile Devices

Cultural and Language


Math

Media HowTos

Forums and Q&As


Working Groups

Research and recommendations

W3C coga task force

More Blogs & News

Misc

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

  1. User:GreggVan
  2. User:Till
  3. User:Mad
  4. User:Kostas Votis
  5. --<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