W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > July 2013

Re: Intergrating methodology with current business processes

From: Alistair Garrison <alistair.j.garrison@gmail.com>
Date: Thu, 11 Jul 2013 14:55:33 +0100
Message-Id: <AF457FF8-C479-4BC7-96E9-C01B31E0E1E4@gmail.com>
To: Shadi Abou-Zahra <shadi@w3.org>, Eval TF <public-wai-evaltf@w3.org>
Hi Shadi, 

With regard to 1… In addition to User Stories - Use cases (hopefully including those for people with disabilities - using keyboard only, AT, etc…), simulated data for use when driving use cases, the testing environment, real users, testers…

With regard to 2… I was thinking that the evaluation process is generally part of a much large development lifecycle when we talk about self assessment.  So my focus had been on how best to integrate the methodology into this larger development lifecycle.  It is, however, true to say that people could choose to buy evaluation services from a third-party to coincide with UAT, which would also be efficient - so, it may not be exclusive to self-assessment.

With regard to 3… Yes… In light of the above. 

All the best 

Alistair

On 11 Jul 2013, at 13:55, Shadi Abou-Zahra wrote:

> OK, getting clearer but not completely yet.
> 
> #1. What "inputs" do you mean in addition to "user stories"?
> 
> #2. Why is this exclusive to situations of self-assessment?
> 
> #3. How about adding this as a note directly in section 4.a?
> 
> Best,
>  Shadi
> 
> 
> On 11.7.2013 14:41, Alistair Garrison wrote:
>> Hi Shadi,
>> 
>> 1st party evaluation = self assessment.  3rd party evaluation = getting someone external to do it.
>> 
>> The proposed subsection of the "Consideration of particular situations" might simply read:
>> 
>> Self-Assessment (as the heading)
>> 
>> For some, the most efficient use of this evaluation methodology might be in User Acceptance Testing (UAT) - be it for internally developed websites, or websites which have been developed through outsourced processes.  With regard to Step 4a, a great deal of the inputs required for this methodology might have already been generated for UAT (user stories, etc…), so its integration here might provide the lowest impact and best cost / benefit.
>> 
>> Its only a suggestion.
>> 
>> All the best
>> 
>> Alistair
>> 
>> On 11 Jul 2013, at 13:13, Shadi Abou-Zahra wrote:
>> 
>>> Hi Alistair,
>>> 
>>> It is great that you are hearing mostly positive feedback about the integration of WCAG-EM in business processes. This is important.
>>> 
>>> As to your suggestion, I do not completely understand it. What do you mean by the term "1st Party Evaluation" (so that we establish common understanding of the terminology) and what exactly would this proposed new section contain?
>>> 
>>> Thanks,
>>>  Shadi
>>> 
>>> 
>>> On 9.7.2013 17:19, Alistair Garrison wrote:
>>>> Dear Eval TF,
>>>> 
>>>> For many good reasons I considered it valuable to check if there would be an impact for an organisation (especially, those operating 1st party evaluation) if they tried to integrate our new methodology into their current business processes - and, as an aside to find out where this integration might best occur.
>>>> 
>>>> I decided to ask a company who already has a good historical reputation for accessibility - as the impact of something new would be most obvious.   The organisation very kindly gave me time to ask many and varied questions - and below is the brief summary of my quick study.
>>>> 
>>>> Summary:
>>>> 
>>>> I am pleased to say that from this quick study I found that little, if anything at all, would seemingly stop an organisation currently operating 1st party evaluation from being able to adopt this new methodology.
>>>> 
>>>> That said there is a best practice which I would like to share with you, which could be very useful all round. It is very beneficial for an organisation to start an HTML code library (if they already haven't).  When a new interface component is needed the library is checked - and if it is found not to be present a new component is made and stored in the library.  A controller job role has responsibility for ensuring that new components are built using techniques which support accessibility.
>>>> 
>>>> NB. The techniques the controller uses should be publicly available and listed - which means they can easily be used by the evaluator in the evaluation.
>>>> 
>>>> And, with regard to where to integrate the methodology in the context of organisations currently operating 1st party evaluation…  This methodology (in my opinion) is best suited to integration into User Acceptance Testing (UAT) - be it for internally developed websites, or websites which have been developed through outsourced processes.  A great deal of the inputs required for this methodology are already generated for UAT (user stories, etc…), so its integration here might provide the lowest impact and best cost / benefit.  The only thing would be to state how important Step 4a is when using the evaluation in UAT.
>>>> 
>>>> Finally, having read the evaluation methodology again I could not find suggestions for where the methodology could be integrated into current business processes.  From a 3rd party evaluation point of view it is mostly irrelevant, but from a 1st party evaluation view it could be quite useful.
>>>> 
>>>> What would the group think to including a small sub-section (entitled "1st Party Evaluation") under the Considerations for Particular Situations section - drawing information from the later suggestions above?
>>>> 
>>>> Very best regards
>>>> 
>>>> Alistair
>>>> 
>>> 
>>> --
>>> Shadi Abou-Zahra - http://www.w3.org/People/shadi/
>>> Activity Lead, W3C/WAI International Program Office
>>> Evaluation and Repair Tools Working Group (ERT WG)
>>> Research and Development Working Group (RDWG)
>> 
>> 
> 
> -- 
> Shadi Abou-Zahra - http://www.w3.org/People/shadi/
> Activity Lead, W3C/WAI International Program Office
> Evaluation and Repair Tools Working Group (ERT WG)
> Research and Development Working Group (RDWG)
Received on Thursday, 11 July 2013 13:56:04 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 11 July 2013 13:56:04 UTC