Re: WCAG-EM Report Tool enhancement - additional input beyond SC

Hmmm. Usually such issues are related to the one or other SC, even if 
they are not fully covered by it. I think it would be best noted with 
one of the SCs so that it is not missed by the developers.

There is also "additional evaluation requirements". We could also easily 
add an "other evaluation observations" field, which does not seem like a 
bad idea anyway (not the above issue, though).

I added a feature request for the queue:
  - https://github.com/w3c/wcag-em-report-tool/issues/247

Best,
   Shadi


On 11.6.2015 17:05, Shawn Henry wrote:
> I can't remember (or see on quick skim) if we already have a place for
> this type of info?
>
> ~Shawn
>
>
> -------- Original Message --------
> Subject: Re: [WebAIM] Where does CSS issue fail WCAG2?
> Date: Thu, 11 Jun 2015 13:51:56 +0000
> From: Moore,Michael (HHSC) <Michael.Moore@hhsc.state.tx.us>
> Reply-To: WebAIM Discussion List <webaim-forum@list.webaim.org>
> To: WebAIM Discussion List <webaim-forum@list.webaim.org>
>
> When I conduct audits, I usually add a section that covers any
> functional, organizational, usability, or design issues that I find
> problematic.  I frequently find this to be a good place to mention
> things like button or form field placement that adversely impact people
> using screen magnification but do not fit neatly into the standards. I
> make it clear that these items are not required by the standards.
>
> Mike Moore
> Accessibility Coordinator
> Texas Health and Human Services Commission
> Civil Rights Office
> (512) 438-3431 (Office)
> (512) 574-0091 (Cell)
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto:webaim-forum-bounces@list.webaim.org] On
> Behalf Of Lynn Holdsworth
> Sent: Thursday, June 11, 2015 8:41 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Where does CSS issue fail WCAG2?
>
> No Mike, I'm sure they didn't mean it to look like that. But
> unfortunately my audit ccan only flag up WCAG2 failures.
>
> Cheers, Lynn
>
> On 11/06/2015, Moore,Michael (HHSC) <Michael.Moore@hhsc.state.tx.us> wrote:
>> I would think that it would fail to meet the design specifications. I
>> can't imagine that the designer meant for it to look like that.
>>
>> Mike Moore
>> Accessibility Coordinator
>> Health and Human Services Commission
>> Civil Rights Office
>> (512) 438-3431 (Office)
>> (512) 574-0091 (Cell)
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto:webaim-forum-bounces@list.webaim.org] On
>> Behalf Of Lynn Holdsworth
>> Sent: Thursday, June 11, 2015 5:45 AM
>> To: webaim-forum@list.webaim.org
>> Subject: [WebAIM] Where does CSS issue fail WCAG2?
>>
>> Hi all,
>>
>> Just doing an audit, and we have a styled focus indicator that's not
>> quite wide enough to fit around its "Next" button and starts halfway
>> through the N.
>>
>> We feel like it should fail, but it's not a text resizing issue, and
>> we can't find anything else to fail it under.
>>
>> Does this fail? If so how?
>>
>> Thanks as always, Lynn
>> _______________________________________________
>> To manage your subscription, visit http://list.webaim.org/ List
>> archives at http://webaim.org/discussion/archives
>> Address list messages to webaim-forum@list.webaim.org
>> _______________________________________________
>> To manage your subscription, visit http://list.webaim.org/ List
>> archives at http://webaim.org/discussion/archives
>> Address list messages to webaim-forum@list.webaim.org
>>
> _______________________________________________
> To manage your subscription, visit http://list.webaim.org/ List archives
> at http://webaim.org/discussion/archives
> Address list messages to webaim-forum@list.webaim.org
> _______________________________________________
> To manage your subscription, visit http://list.webaim.org/
> List archives at http://webaim.org/discussion/archives
> Address list messages to webaim-forum@list.webaim.org
>
>
>
>

-- 
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 June 2015 15:29:09 UTC