Difference between revisions of "Talk:Accessibility pledge"

From FSCONS wiki
Jump to navigation Jump to search
(Added a link and a section for more resoures)
 
(2 intermediate revisions by one other user not shown)
Line 48: Line 48:
 
* audio transcription (for audio)
 
* audio transcription (for audio)
 
|assignedTo=Grégoire
 
|assignedTo=Grégoire
 +
|done=yes
 
}}
 
}}
{{todo|Put a link to an example of accessible material (there is one in the source page)|assignedTo=Grégoire}}
+
{{todo|Put a link to an example of accessible material (there is one in the source page)|assignedTo=Grégoire|done=yes}}
  
 
==  Make slides available before the presentation ==
 
==  Make slides available before the presentation ==
Line 58: Line 59:
 
== Additional reading - for the ambitious and interested presenter ==
 
== Additional reading - for the ambitious and interested presenter ==
 
Some resources for more reading:
 
Some resources for more reading:
 +
* [http://www.nigelbevan.com/papers/The_evaluation_of_accessibility_usability_and_user_experience.pdf Petrie, H. and Bevan, N. 2009 The evaluation of accessibility, usability and userExperience. The Universal Access Handbook, C Stepanidis (ed)]
 
* [http://ur1.ca/92hbj Bevan N (2006). International Standards for HCI. In: Encyclopaedia of Human Computer Interaction. (google scholar document)]
 
* [http://ur1.ca/92hbj Bevan N (2006). International Standards for HCI. In: Encyclopaedia of Human Computer Interaction. (google scholar document)]
 +
* [http://www.iu.hio.no/~frodes/unitech10/021-Romen/index.html Validating WCAG 1.0 and WCAG 2.0 through Usability Testing with Disabled Users]
 +
* [http://www.id-book.com/downloads/casestudy_n_1.pdf Blind users experience the Internet]
 +
* [http://www.id-book.com/downloads/casestudy-14point1.pdf 14.1: Ensuring Accessibility and Section 508 Compliance for the Recovery.gov web site]

Latest revision as of 09:41, 24 May 2012

What?

This is a draft of a new policy for fscons. The idea is that speakers can, if they want, pledge to make there talk more accessible by following those guidelines. The talks will then be marked as accessible in the program. Most of this comes from this page : http://www.w3.org/WAI/training/accessible so before publishing anything, we should probably ask for authorization…

TODO:

Make the short text explaining what the accessibility pledge is (for the CFP email), and a longer text for the landing page, where we explain that those who pledge also will have their sessions marked as "accessibility pledged" (or something) in the schedule.

Visual aspects

Slides generally

Color blindness

TODO: Template:Trim (User:Grégoire)


Use an easy-to-read font face

Needs examples, preferably including free readable fonts for print and digital (what is a slide display? is it still "digital"?)

I think the main difference between print and screen, as far as types are concerned, is resolution: printed papers has a much better resolution than most screen (but e-papers and retina display might change that…) So a projector is definitively digital (they usually have crappy resolution) --Grégoire 08:28, 16 April 2012 (UTC)
Makes perfect sense! //Rikard 12:16, 16 April 2012 (UTC)

Tiresias fonts are readable and Free --Rikard

After a quick comparison, Open Sans has a lot more coverage. In addition, it as semi-bold and extra-bold styles (in addition to regular bold style) which is nice :-) --Grégoire 12:47, 16 April 2012 (UTC)


TODO: Template:Trim (User:Grégoire)

TODO: Template:Trim (User:Grégoire)

TODO: Template:Trim (User:Grégoire)


Use sufficient color contrast

Examples needed. Here's one set of font guidelines.

TODO: Template:Trim (User:Grégoire)


Todos

TODO: Template:Trim (User:Grégoire) Property "Has description" (as page type) with input value "Develop the audio/video section: divide into

  • Subtitles (for videos)
  • audio description (for videos) and
  • audio transcription (for audio)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

TODO: Template:Trim (User:Grégoire)


Make slides available before the presentation

I'm not sure we should include that. This impose a constraint on the presenter work-flow (some don't prepare in advance I believe) and some may not want to reveal too much of the content of their presentation before hand. But if we do include it, we should define what “in god time” means and it shouldn't say “if possible” --Grégoire 08:58, 16 April 2012 (UTC)
We should include it as a "Good practice" rather than a requirement. During the accessibility conference I attended recently, we discussed policies a lot, and many came to the conclusion that "It's better that some efforts are made, than none (which can be the case when a package with a lot of requirements are presented). Some steer away and do nothing because the requirements seem "too much". I suggest we have two levels only: "You should" and "We recommend". Looser requirements like this, (I agree that while it is important, it is hard for some presenters) should be under "We recommend" (a section that could go to the end of the Pledge). Some recommend to have a three level measurement of accessibility: Green (Good/Accessible), Yellow (OK, to some extent accessible) and Red (Not at all accessible). I think that for FSCONS, the Pledge makes us "Yellow" and the pledge itself should have at most two levels "Should" and "Recommended". Those who have their slides done well in time before the conference, should be informed that it is good if they are available to the audience before hand (the presenter might not have thought about that ;-) ). --Rikard 11:30, 23 April 2012 (CEST)

Additional reading - for the ambitious and interested presenter

Some resources for more reading: