- From: John Hicks <jwjhix@gmail.com>
- Date: Tue, 4 Nov 2014 10:07:41 +0100
- To: Jesse Beach <jesse.r.beach@gmail.com>
- Cc: Wilco Fiers <w.fiers@accessibility.nl>, "public-auto-wcag@w3.org" <public-auto-wcag@w3.org>
- Message-ID: <CAK8rWfc+fzvxA-JLnnG+Z-Wx3OoPOkfmZNFYUaG0n_6EOpVFHQ@mail.gmail.com>
Bonjour
I believe Wilco intends "Create the test on the wiki" so that we can
discuss it.
Actually, it depends on which side of the great divide we are working
from. I mentioned this case in last week's call because the general
discussion was how to test for decorative images.
Perhaps the assumption was more that all images are suspect (i.e. we need
to manually check them) except certain ones (repeating ones, for example,
or of size 1px, etc etc)
Are we eliminating unsuspect images from a complete list, or are we
introducing suspect images into an empty list?
The former is probably safer.
Happy to create the test either way, just for the record.
John
On 3 November 2014 20:58, Jesse Beach <jesse.r.beach@gmail.com> wrote:
> Wilco, when you say "create the test", what is the test being created in?
>
> Jesse Beach
>
> On Mon, Nov 3, 2014 at 11:33 AM, Wilco Fiers <w.fiers@accessibility.nl>
> wrote:
>
>> Hi John,
>> Yeah, great example. I've probably seen this a few times during audits,
>> and it's never a good sign. Thanks for the input. Do you want to create
>> this test yourself?
>>
>> Wilco
>>
>>
>> 030-2398270 (ma t/m do)
>>
>> Goed geholpen? Recommend us:
>> www.linkedin.com/company/accessibility-foundation/products
>>
>> --------------------------------------------------------------------------------------------------------------------
>> Trainingen Toegankelijkheid: www.accessibility.nl/trainingen
>> ________________________________________
>> Van: John Hicks [jwjhix@gmail.com]
>> Verzonden: maandag 3 november 2014 17:12
>> Aan: public-auto-wcag@w3.org
>> Onderwerp: SC 1.1.1 (?)
>>
>> Hello everyone,
>>
>> I said I would send an example of a situation where an automatic test
>> could at least identify a high risk situation (an background image that
>> caries information).
>>
>> We are in a table and a data-cell is empty , but the style on the cell
>> contains a non-repeating image (and only that).
>>
>> Upon reflection, I think it would be very hard to say something
>> definitive about this sort of situation. Perhaps in wcag-auto land such
>> examples really must remain manual. After all, it could be just a
>> decoration for an empty cell.
>>
>> Then again, and since some people were even speaking about analysing
>> images and other stuff, some assessment of the styles attached to the cells
>> in this table ("OK" and "KO") against a word list of "significant" sounding
>> classes .... hmm, well, yes we are reaching quite far here.
>>
>> In conclusion probably nothing to be done, but I thought it would be good
>> to share the example anyway.
>>
>> The table code is below, preceded by a the relevant CSS. I also put a
>> screen capture, many apologies for this, but I can not provide access to
>> the site and related css/script itself.
>>
>> The offending items are data-cells such as : <td
>> class="ok"> </td>
>>
>> Anyway, that is the example...
>> John
>>
>>
>>
>> PS : yes, the table itself is very wrong in many ways too !
>>
>>
>> The CSS :
>>
>> *****************************************
>> .table_cards td.ok, .table_cards td.ko {
>> background-position: center center;
>> background-repeat: no-repeat;
>> }
>> .table_cards td.ok {
>> background-image: url("../img/ok_768px.png");
>>
>> .table_cards td.ko {
>> background-image: url("../img/ko_768px.png");
>>
>>
>> The HTML:
>>
>> <table class="table_cards">
>> <tr>
>> <th class="arbo">
>>
>> </th>
>> <th class="date txt_centre asc">
>> <span>Date</span>
>> </th>
>> <th>
>> <span>Merchant</span>
>> </th>
>> <th class="montant">
>> <span>Amount</span>
>> </th>
>> <th class="statut">
>> <span>Statut</span>
>> </th>
>> </tr>
>> <tr class="close_op">
>> <td class="arbo">
>>
>> </td>
>> <td class="txt_centre">
>> JJ/MM/AAAA
>> </td>
>> <td class="commerce">
>> <span>SHOP 1</span>
>> </td>
>> <td class="txt_right">
>> 50,00 €
>> </td>
>> <td class="ok">
>>
>> </td>
>> </tr>
>> <tr class="detail_op">
>> <td class="arbo">
>>
>> </td>
>> <td colspan="4">
>> <span>Transaction on my
>> card...xxxxxxxx</span>
>> </td>
>> </tr>
>> <tr class="close_op">
>> <td class="arbo">
>>
>> </td>
>> <td class="txt_centre">
>> JJ/MM/AAAA
>> </td>
>> <td class="commerce">
>> <span>SHOP 2</span>
>> </td>
>> <td class="txt_right">
>> 277,29 $
>> </td>
>> <td class="ok">
>>
>> </td>
>> </tr>
>> <tr class="detail_op">
>> <td class="arbo">
>>
>> </td>
>> <td colspan="4">
>> <span>Transaction on my
>> card...xxxxxxxx</span>
>> </td>
>> </tr>
>> <tr class="">
>> <td class="arbo">
>>
>> </td>
>> <td class="txt_centre">
>> JJ/MM/AAAA
>> </td>
>> <td class="commerce">
>> <span>SHOP3</span>
>> </td>
>> <td class="txt_right">
>> 11,90 €
>> </td>
>> <td class="ok">
>>
>> </td>
>> </tr>
>> <tr class="close_op">
>> <td class="arbo">
>>
>> </td>
>> <td class="txt_centre">
>> JJ/MM/AAAA
>> </td>
>> <td class="commerce">
>> <span>SHOP4</span>
>> </td>
>> <td class="txt_right">
>> 1 498,36 £
>> </td>
>> <td class="ko">
>>
>> </td>
>> </tr>
>> <tr class="detail_op">
>> <td class="arbo">
>>
>> </td>
>> <td colspan="4">
>> <span>Transaction on my
>> card...xxxxxxxx</span>
>> </td>
>> </tr>
>> </table>
>>
>>
>>
>>
>>
>
Received on Tuesday, 4 November 2014 09:08:08 UTC