WebAIM - Web Accessibility In Mind

E-mail List Archives

WebAIM-Forum Digest, Vol 168, Issue 6

for

From: Laurie Kamrowski-Lamb
Date: Mar 8, 2019 12:33PM

7. Acrobat dropping some table cell properties (Dona Patrick)

I haven't quite had that happen, but I have had Acrobat redraw complex
tables differently when redrawn within the same session, and I don't know
what I am doing differently to cause it. I have Adobe continuous release. I
am going through and clearing out my memory periodically due to some of the
uglier tables that I am working with crashing acrobat repeatedly.

On Fri, Mar 8, 2019 at 2:05 PM < <EMAIL REMOVED> > wrote:

> Send WebAIM-Forum mailing list submissions to
> <EMAIL REMOVED>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://list.webaim.org/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> <EMAIL REMOVED>
>
> You can reach the person managing the list at
> <EMAIL REMOVED>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
> Today's Topics:
>
> 1. WCAG 2.1 SC 1.3.5 Identify Input Purpose - Address Attribute
> Values (Steve Green)
> 2. Re: WCAG 2.1 SC 1.3.5 Identify Input Purpose - Address
> Attribute Values (Patrick H. Lauke)
> 3. Re: WCAG 2.1 SC 1.3.5 Identify Input Purpose - Address
> Attribute Values (Steve Green)
> 4. WCAG success criteria a blind teser is able to locate
> (Reinhard Stebner)
> 5. Re: WCAG success criteria a blind teser is able to locate
> (Isabel Holdsworth)
> 6. Re: WCAG success criteria a blind teser is able to locate
> (Reinhard Stebner)
> 7. Acrobat dropping some table cell properties (Dona Patrick)
>
>
>
> ---------- Forwarded message ----------
> From: Steve Green < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Thu, 7 Mar 2019 19:18:34 +0000
> Subject: [WebAIM] WCAG 2.1 SC 1.3.5 Identify Input Purpose - Address
> Attribute Values
> https://www.w3.org/TR/WCAG21/#input-purposes states that the
> autocomplete="address-level1" value represents the broadest administrative
> level in the address, and that in the UK, this is the post town.
>
> The problem is that the post town is not the broadest administrative level
> in the address in the UK - the county is. Except for towns and cities that
> are not in a county, such as Bristol, which is both a city and a county
> (and also a unitary authority!).
>
> So which value should we use? Should we always use address-level1 for the
> Town or City field? If so, that means we can't apply an autocomplete
> attribute to the County field if there is one.
>
> Or should we use address-level1 for the County and address-level2 for the
> Town, which contradicts the statement in
> https://www.w3.org/TR/WCAG21/#input-purposes. Is that section of WCAG
> normative? It doesn't seem to say either way.
>
> Regards,
> Steve Green
> Managing Director
> Test Partners Ltd
> 020 3002 4176 (direct)
> 0800 612 2780 (switchboard)
> 07957 246 276 (mobile)
> 020 7692 5517 (fax)
> Skype: testpartners
> <EMAIL REMOVED>
> www.testpartners.co.uk
>
> Connect to me on LinkedIn - http://uk.linkedin.com/in/stevegreen2
>
>
>
>
>
> ---------- Forwarded message ----------
> From: "Patrick H. Lauke" < <EMAIL REMOVED> >
> To: <EMAIL REMOVED>
> Cc:
> Bcc:
> Date: Thu, 7 Mar 2019 19:24:54 +0000
> Subject: Re: [WebAIM] WCAG 2.1 SC 1.3.5 Identify Input Purpose - Address
> Attribute Values
> On 07/03/2019 19:18, Steve Green wrote:
> > https://www.w3.org/TR/WCAG21/#input-purposes states that the
> autocomplete="address-level1" value represents the broadest administrative
> level in the address, and that in the UK, this is the post town.
>
> Note that it's not about the exact keyword, but about the intent
>
> "The terms below are not keywords that must be used, but instead
> represent purposes that must be captured in the taxonomy adopted by a
> webpage"
>
> [...]
>
> > So which value should we use? Should we always use address-level1 for
> the Town or City field? If so, that means we can't apply an autocomplete
> attribute to the County field if there is one.
> >
> > Or should we use address-level1 for the County and address-level2 for
> the Town, which contradicts the statement in
> https://www.w3.org/TR/WCAG21/#input-purposes. Is that section of WCAG
> normative? It doesn't seem to say either way.
>
> Do what you think is best in terms of autocomplete keyword to capture
> the *concept* of the broadest administrative level. i.e. follow the
> technical spec, and what you think is best reflected there, to convey
> the concept of the "broadest administrative level".
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>
>
>
> ---------- Forwarded message ----------
> From: Steve Green < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Thu, 7 Mar 2019 19:48:36 +0000
> Subject: Re: [WebAIM] WCAG 2.1 SC 1.3.5 Identify Input Purpose - Address
> Attribute Values
> What you say makes sense, but I am left wondering why the WCAG authors
> chose to include incorrect information about the UK. They only included
> examples of three countries (the others being the US and Switzerland), and
> they could easily have omitted the UK if they were in any doubt about our
> administrative system (which is very weird). Anyone who lives here would
> have known it's wrong.
>
> Steve
>
>