Andrew:received comments on tone and possible
... need to encourage users to report problems
... put in more structure and steps to take
... look at first few sentences
WL: need to be positive and to avoid punishing people
Andrew: also can add note to thank organisation for good outcome
Shadi: first sentence could be improved
WL: suggests a more positive title should be used
Andrew: something that is more encouraging?
<shadi> [Reporting Accessibility Barriers]
WL: email sent re a behaviourist approach to reinforce good behaviour [Reinforcing Web Accessibility]
<shadi> [How To Report Accessibility Barriers]
Michael: like current title -
easier for someone who is not first language english. problem
... we are talking to people who are not likely to be familiar with success criteria
WL: choice of word "reporting" where does it go
Andrew: it contains where and how to submit 'report'
shadi: audience - is target
audience novices or advocates
... these different audiences need different levels of hand-holding
<Zakim> shadi, you wanted to clarify audience
Michael: thinks it is ok for his needs with his different audiences
Shadi: thinks that the recent edits are really good and congratulates AA
Andrew: introduces five steps from the overview,
<shadi> [a/Having problems caused by the inaccessibility of a website?/Encountering barriers caused by the inaccessible websites?]
Andrew: intention is to get to the 'meat' more quickly and less background to wade through
WL: wording complain/complaining - too negative?
Andrew: the number of these words have been reduced but have left some to support search engine searches for complaint/ing
<shadi> [repetitive? -- Many Web accessibility barriers are unintentional, though some organizations ignore the issue [@@ too blunt?]. Some developers are not aware of Web accessibility issues, some don't know how to make their websites accessible, and some get it wrong, and some just ignore it.]
Andrew: re 'ignore the issue' - is this too blunt?
WL: unintentional and ignore are not opposites
Shadi: subsequent sentence is better but reads as repetitive
Andrew: has tried to say same thing in three different ways
Andrew: who caused the problem - developer or others?
Shadi: also Andrew - maybe it doesn't matter who caused the problem - organisation or developer
Andrew: true - we are primarily talking about contacting organisations not developers
Andrew: will take out the first sentence (including the bullets) from the section "steps to take"
shadi: use "constructive approach" in the next sentence
<shadi> [When writing, a constructive approach may get the organization's attention but sometimes a firmer approach my be necessary.]
Andrew: we will drop "Consider approaching the organization as if they do not understand accessibility "
<Zakim> shadi, you wanted to ask about writing/contacting
shadi: @overview - change "write" to "contact" to apply to a broader situations
William / Andrew: we should change the wording in overview/last bullet to include the wording of the according headline (further action)
shadi: maybe we could try to redesign the h4 to make the structure clearer
William: [If you have multiple browsers you should try to...]
Darren: the screen reader / voice recognition sw brand names do not matter
Suzette: include "Step #:" to the H3
Consider sample emails ...
Michael: 3 examples are fine for me, helpful for many people
shadi: move the template and/or samples to bottom or separate page and link it
andrew: will play around with
... a separate page might be better
pierre: we have not defined what is web accessibility
Michael: if people come to this page they probably have a rough idea about accessibility
shadi: a word or two in the intro might be helpful
Pierre: provide even more examples to select from
Andrew: what about linking to BAD as examples of the problems?
Michael: before and after demo is only helpful for web developers
darren: i think the sentence "Keep in mind that a small organization may ..." is helpful
Michael: i would leave it to the
organisation's answer to indicate the timeframe for
... i would drop the words "direct" / "indirect" in Further Actions
suzette: reports about a dialog
on Web accessibility issues in her university
... and thanks Michael for taking over scribing